=== persia changed the topic of #ubuntu-motu to: https://wiki.ubuntu.com/MOTU | Want to get involved with the MOTUs? https://wiki.ubuntu.com/MOTU/Contributing | Unmet Deps time! http://qa.ubuntuwire.com/debcheck/ | QA resources from http://qa.ubuntuwire.com [01:33] Hi, I have a question about the MOTU. I was wondering if you build a package for Ubuntu, do you have to watch the main site for new versions/patches/etc.? That's really the only thing holding me back from contributing, as I don't always have the time to do said actions. [01:34] usually a good idea, yes [01:34] sometimes people file bugs about software that's out of date [01:34] there are also watch files, which let you scan for changes [01:35] Hobbsee: so, there's really no "Oh, here's a package that hasn't been updated/built yet, I guess I have time to help out..." It's really quite a commitment when you work on a project, right? [01:36] s/project/package/ [01:36] Megaqwerty: you do not need to work on "new packages" - you're quite free to do bug fixes, etc. [01:36] Megaqwerty: or work in teams, which keep packages up to date [01:37] Hobbsee: so, are you saying joining a team is more like: A) Report on needed update posted B) Whomever has the time updates it ? [01:38] Megaqwerty: yeah. i don't do it like that - i just fix bugs, etc usually [01:38] Megaqwerty: Well, joining a team is more like coordinating between team members about things to be done and who has time to do it. Not just waiting for someone to have time. [01:38] projects often have rss feeds, etc, so the info comes to you, too [01:39] persia: could you elaborate on how that works? [01:41] Megaqwerty: Teams generally have mailing lists, dedicated IRC channels, and sometimes wiki pages that indicate who is working on what, and the currrent progress. It's a little different for each team. If your interests match a team, you'd do best to contact that team and ask "How can I help?". If you just want to help out, chasing bugs is probably easiest. [01:41] persia: so, are the teams listed on the MOTU site? [01:43] Megaqwerty: Some of them. There are also teams that don't restrict themselves to universe or main, and work on a subset of software, like the mozilla team or the games team or the edubuntu team. [01:43] Megaqwerty: A better question perhaps is, what interests you? [01:46] persia: well, anything really. I currently work on Getdeb packages which are generally pretty broad in spectrum. I like the environment where they have a bugtracker which lists what packages need to be updated or created, and I just pick whatever I feel I have the time to do. But I wanted to start contributing directly to ubuntu, which is what brought me here. So, I'm really up for anything that's not too difficult (anything with a makef [01:47] *Some form of a makefile [01:48] Megaqwerty: If you're coming from getdeb, I'd like to encourage you to try to tackle part of http://qa.ubuntuwire.com/uehs/no_watch.php or http://qa.ubuntuwire.com/uehs/no_updated.php. The first list is packages not maintained in Debian where we don't know the upstream status, and the second list is packages not maintained in Debian where we ship an older version. [01:49] Getting these updated would be a great step towards having the most current software. Most are in universe, so you'd be working with MOTU (although some belong to special teams: check the Maintainer entry in the source package). [01:51] persia: Thanks! let me look at the pages and see if I have any further questions about how this all works. :) [01:52] persia: Okay, so say I wanted to work on "anyevent" I would go to the launchpad page, build the latest version...then what? [01:53] Megaqwerty: First, check to see if there is already an update bug, which would be tracking status. If there isn't, or if it is unassigned, open one and assign yourself. Then, update the package from CPAN to work with hardy, and create an interdiff for sponsor review. You probably want to review https://wiki.ubuntu.com/MOTU/Contributing for hints and process. [01:54] persia: is an "interdiff" the same as a .diff.gz? [01:55] Megaqwerty: No, it's the differences between two diff.gz files. See https://wiki.ubuntu.com/UbuntuDevelopment/Interdiff [01:56] persia: alright, cool. the name makes more sense now ;) [01:57] Megaqwerty: We use interdiff to communicate packaging changes when there is a new upstream version, as debdiff mixes the packaging and upstream changes, and is confusing. With an interdiff, the sponsors can construct the new diff.gz from the old diff.gz, and look at the specific changes when reviewing the work. [01:59] persia: okay, so how do I go about giving this diff to a sponsor? Attach it to the "new version" bug report? [02:00] persia, I received the upload email... thanks [02:00] Megaqwerty: First, test to make sure you can reconstruct your diff, then subscribe the sponsors queue. See https://wiki.ubuntu.com/MOTU/Contributing#head-b205c74e27fe15e79e10c9e7f14d3cdfb359d81d for details. [02:00] effie_jayx: There's another missing manpage in that package, but it takes so long to bootstrap, I'm not sure I want to build it again :) [02:01] persia, I also received some bug reports for builds... 4 different emails stating a build error... [02:01] I don't quite understand those emails [02:01] persia, it takes a while to build ... yes... [02:02] effie_jayx: The updated package failed to build when uploaded. There seems to be a persistent problem right now. If you need help understanding the mail, best to ask here (although I'm not the best person to answer). [02:02] persia, State: Chroot problem [02:02] I checked the log [02:03] E: Internal Error, Could not perform immediate configuration (2) on libstdc++6 [02:03] it happens on 4 architectures... [02:04] effie_jayx: it's broken [02:05] Hobbsee, the package? [02:06] Hobbsee, it builds ok here.. [02:06] should I add a build log? [02:06] effie_jayx: no, the buildds are broken [02:07] Hobbsee, :S [02:28] persia: okay, I have more of a packaging question for you: Is use of cdbs encouraged, discouraged, or neither? [02:29] Megaqwerty: neither really. I like it, but that's me. Best practice for an update is to try to keep the current packaging, except where you need to fix bugs. [02:30] persia: Cool. I wasn't planning on changing the rules, but from all of the package sources I've downloaded from Ubuntu, I could never really tell. [02:31] Megaqwerty: For Debian packages, the tools used are chosen by the maintainer, and Ubuntu generally leaves those alone. For new-in-Ubuntu packages, the tools are chosen by the initial packager, and others usually leave these alone. [02:32] persia: Got it. === bigon is now known as bigon` [03:18] I'm new to Bash scripting and Debian packaging, and I need to know how to run some Python within my postinst and prerm scripts. [03:20] cdm10: the short anwser is "dont" postinst scripts are shell scripts, keep them that way :) [03:20] imbrandon: alright, so I have to learn some shell-scripting... darn. [03:20] :) [03:20] imbrandon: Anyway, I don't really understand the structure of it. I have one created by dh_make. [03:22] dh_make is only a template and often dosent fit what ou need it for, postinst is just a script that gets called after installation as the name implys [03:22] imbrandon: alright... so, how might it be called, and how do I need to handle the different parameters that might be passed to it? [03:22] I just want to add something to anacron when it installs, and remove it when it's removed. [03:22] hey [03:23] imbrandon: can u do me a favor? [03:23] are you using cdbs ? [03:23] heya nxvl [03:23] imbrandon: yeah [03:23] sure [03:23] imbrandon: please install tuxpaint-config and check if it apears on the menu [03:23] imbrandon: you are using KDE, right? [03:23] nxvl: sure give me a moment [03:23] imbrandon: thnx [03:23] not right now i'm not [03:23] oh [03:23] i'm in gnome [03:23] i need to check it on kde [03:23] nevermind [03:23] actualy right now i'm at console but thats totaly seperate [03:24] :) [03:24] imbrandon: yes to the cdbs question :) [03:24] yep [03:24] i'm working on bug #173294 [03:24] Launchpad bug 173294 in tuxpaint-config "There are no easy way to change tuxpaint configuration" [Low,Confirmed] https://launchpad.net/bugs/173294 [03:24] and as i have seen it installs the .desktop for kde [03:24] and not for gnome [03:24] so i wanted to make sure [03:25] cdm10: sure then make a anacron file and install it via the .install file in /etc/cron.daily or similar [03:25] is normaly how that is handled [03:25] imbrandon: Wrong advice. I believe python is (partially) allowed in maintainer scripts in Ubuntu. Perl is definitely allowed. [03:25] imbrandon: Ah, so I don't have to muck around in anacrontab. That's good. [03:26] minghua: hrm strange , never seen it in practice [03:26] imbrandon: I'm not sure what you mean by the .install file, and I also need some documentation as to how to create this file... could you help me with that? [03:26] cdm10: debian/.install , it should be explained int he packing guide [03:27] lemme find a refrence [03:27] imbrandon: thanks [03:29] imbrandon: hmm, I don't see *.install in there. Would that be generated by dh_make? And, why can't I just add that cron file thingy to the files that my setup.py installs? (I'm using distutils) [03:29] Do I have to create the .install file? [03:29] imbrandon: to install a .desktop file it's only needed to dh_desktop on install at rules, doesn't it? [03:29] nxvl: yea [03:29] install files are documented in man dh_install. [03:30] is there a problem if the upstream install a desktop file and i add anotherone on debian/ ? [03:30] maintainer scripts are demystified from http://women.debian.org/wiki/English/MaintainerScripts [03:30] (the upstream one seems to work only for kde) [03:30] imbrandon: sudo's postinst, for example. [03:30] nxvl: Don't do that. If upstream puts it in the wrong place, move it. Upstream .desktop files are better. [03:31] persia: what i need to edit is the makefile, thats the way to do it? [03:31] imbrandon: The postinsts of linux-image-* in Debian are perl scripts too, not sure about Ubuntu though. [03:31] persia: Is this file actually called .install, or is it called package.install? [03:31] nxvl: patch it [03:31] nxvl: Yes. patch the Makefile. [03:31] then send patch upstreams [03:31] cdm10: Either debian/install or debian/.install, depending. See the man page. [03:31] really? patch the Makefile? [03:31] * minghua also found bash's preinst is a ELF binary -- which makes sense. [03:31] I would just add a bit in rules to move the file [03:32] Amaranth: either way is better than making a new one [03:32] persia: alright. So, when I dpkg_buildpackage it, it should put that file in the right place on the filestructure of the .deb? [03:32] the most strange think is that it has some gnome lines commented [03:32] Hi people, I'm building my 1st .DEB package, but I only know how to copy files to the system (lot of simplistic tutorials). To start, I want to know just how to put an icon of my application on the system menu. How???? Is this the wrong channel? Please let me know. [03:32] Amaranth: That works too. I just don't like mv in debian/rules, as it often causes the fails-to-build-twice-in-a-row bug. [03:32] eh, why does it need to build twice in a row? :P [03:32] RenatoSilva: You need a .desktop file. [03:32] RenatoSilva: You need to create a .desktop file and put it into the /usr/share/applications/ directory. [03:32] Amaranth: To prove that debian/rules clean really does. [03:33] RenatoSilva: You could look at other .desktop files as an example. [03:33] cdm10: that file tells where it to put the other files in the stuc , you really should read the package guide [03:33] imbrandon: where would I find that? A google gives me this: http://www.debian.org/doc/maint-guide/ [03:33] !packageguide [03:33] packagingguide is The packaging guide is at http://wiki.ubuntu.com/PackagingGuide - See https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages for information on getting a package integrated into Ubuntu - Other developer resources are at https://wiki.ubuntu.com/UbuntuDevelopment - See also !backports [03:34] imbrandon: ah, thanks [03:36] cdm10: may I text-edit them? I'm taking a look right now.... [03:37] RenatoSilva: Nautilus is weird about .desktop files, you may have to drag them into gedit or run some editor on them. [03:38] cdm10: ok [03:41] When creating a script for /usr/bin for a python app, is it better to have the script be a python script that imports and runs your application, or to have it be a shellscript that just executes your python script+ [03:41] ? [03:42] cdm10: import and run [03:42] persia: alright... just asking 'cause I noticed that system-config-printer just execs it. [03:42] cdm10: With a shell script? [03:43] persia: yep. [03:43] Odd. Most things I see are executable python scripts in /usr/bin/ [03:44] cdm10: how to make this .desktop to appear somehwere? [03:45] RenatoSilva: Not entirely sure, I just looked at other ones and followed their lead... [03:46] DEBUILD_DPKG_BUILDPACKAGE_OPTS="-i -ICVS -I.svn -I.bzr" [03:46] err [03:47] .desktop entry spec is at http://standards.freedesktop.org/desktop-entry-spec/latest/, and the desktop menu spec (where things end up) is at http://standards.freedesktop.org/menu-spec/latest/ [03:47] cdm10: oh true! [03:47] cdm10: sorry [03:47] persia: I'm wondering if there are some conventions for .desktop files specific to Ubuntu/Gnome. [03:48] cdm10: There are a couple things used by the desktop team to hide some applications by default, etc. For universe packages, we try to follow the standards, and push to Debian and upstream. The advantage of getting them upstream is that otherwise they don't get translated. [03:49] I'm intending to put source and bin and extras altogether in a single folder, like a win application. In this way, what should be a good place to put the application base directory? /usr/local/myapp? [03:49] persia: ok... does that spec have a list of the categories that can be used? [03:50] RenatoSilva: You don't want to do that. Please put executables in /usr/bin, architecture specific stuff in /usr/lib/, and other stuff in /usr/share/? [03:50] cdm10: http://standards.freedesktop.org/menu-spec/latest/apa.html [03:50] persia: thanks [03:50] * persia suggests reading the whole spec, and not just that page [03:52] persia: thank you, I always have seen lib as for libraries and share for shared files [03:52] persia: the executable is a single jar, put it directly on bin or must have a script calling java ? [03:52] RenatoSilva: You may be interested in http://www.pathname.com/fhs/pub/fhs-2.3.html [03:53] RenatoSilva: I'm the wrong person to ask about Java. Best to ask questions generally of the channel. [03:54] ok [03:54] the executable is a single jar, put it directly on bin or must have a script calling java ? [03:55] RenatoSilva: looks like frostwire ( a java app ) uses a script, but i'm no java expert either and thats only one example and i dunno if its the best one [03:55] What's the preferred mechanism for having an app run as root? Should I put #! /usr/bin/gksudo /usr/bin/env python into my launch script in /usr/bin? It seems sorta ugly... [03:56] cdm10: No the .desktop should call your program with gksudo [03:56] cdm10: have the desktop file use it [03:56] cdm10: Please don't use #!/usr/bin/env python. #!/usr/bin/python is much preferred. [03:56] persia: alright, I'll fix that [03:56] Amaranth: That won't work for KDE :( [03:57] What worries me is having it work in both KDE and Gnome... [03:57] persia: Install two .desktop files [03:57] Amaranth: Ugly, and hard to push upstream. [03:58] How do I have it run the appropriate thing? (gksudo|kdesu) [03:58] The menu package provides a `su-to-root` function, but menu isn't in the default Ubuntu install. It's also possible to have a script that detects the right function, and calls that. The better solution is to make the app not require root. [03:59] persia: If I do put gksu/gksudo in the .desktop file, should I depend on it? [04:00] yes [04:00] ok. [04:00] cdm10: You could, but it would annoy KDE users. [04:00] persia: sometimes thats unavoidable, if the app is gtk youir going to anyhow [04:00] Well, it's a GTK app... which would probably annoy them as well. [04:00] imbrandon: True. [04:01] This may be a bit offtopic, but it could save me from having to run as root. [04:01] Are there user-specific anacrons, like with cron? [04:01] sure [04:02] http://f8d.org/?c=236 [04:02] both in the main crontab and user crontabs can both run jobs as other users [04:03] m h dom mon dow user command [04:03] Actually, I'd rather have my app run as root... so, is there any best way to do this? [04:03] depend on gksu, use it in the .desktop, NotShowIn=KDE? [04:03] one question, gui app on a cron ? sounds bad [04:03] imbrandon: no, the gui part doesn't go into cron. [04:03] cdm10: Can you not do something with capabilities? Apps running as root are not ideal. [04:04] cdm10: dont use the NotShowIn , it will pull aditional deps in kde but no reason to disallow it [04:04] imbrandon: alright [04:04] persia: It's a backup application, and I'd like it to be able to run when no one's logged in, and I'd also like to have something running in anacron... and I'm not sure how to have anacron run something every day as each user. [04:06] cdm10: Right. Split the app into the portion that does backup and the portion that does configuration. Have the backup run as root (or a backup user with capabilities) in anacron, configured by the postinst. Grant a special group write access to the configuration file, and have the tool edit the file. [04:07] persia: This is getting way more complex than I had planned :) but it sounds like the right way to do it. [04:08] persia: Actually, I don't like that idea... because the user will be able to set the backup target, and if it's running as root, that's a great way to let normal users change stuff that should only be accessible by root... I could drastically change the app so that this wouldn't happen, but that's not really an option at this point. [04:08] cdm10: As an added benefit, the .desktop file doesn't need to give root to the GUI configuration tool :) [04:11] persia: but what about the problem of the user being able to set anything as the backup target? [04:12] cdm10: Do you mean the security concern that one user could back up another user's files? That's the reason one has to be a member of the backup group to be able to modify the configuration file. Those users would be trusted. [04:13] persia: No, one user could set any directory to be the target of the backup. [04:13] cdm10: The worry of overwriting files then? Same protection: trusted group. [04:14] persia: I sorta wanted to make something that someone could install and have it Just Work without having to mess around with groups. [04:14] persia: So, having it run as root could be a good idea... 'cause there's already a set of trusted users in place that can run it. [04:15] system administrators and root users dont always == [04:15] cdm10: Then just use one of the already trusted groups. I forget whether adm or admin is default, but those seem reasonable. In the default case, the installing user would be the trusted user. In special cases, the administrators would modify the groups. [04:15] admin is default [04:16] imbrandon: Very true, but they are likely the same for the standard use case, no? [04:16] persia: So, that means users won't have to sudo-authenticate each time? [04:16] persia: mostly yea [04:16] cdm10: Right. The configuration file would be group-writable, so the backup admin (who would belong to that group) could edit the file. Others would get a permission denied error (be sure to trap this in your code, and present a nice message). [04:17] persia: Isn't it a better idea to have them sudo-authenticate, so they know that they're doing something that could potentially mess up their system? [04:18] persia: I mean, someone could set some important folder as their backup target... rdiff-backup wouldn't prevent that, I don't think. [04:18] cdm10: If you like. I just don't like sudo for GUIs because of the potential for a bug in the GUI to crash the system. [04:19] persia: hmm, I'll think about how to do this. [04:19] Programming is one thing, but packaging... that's a minefield. [04:19] It's confused me more than anything else in the process :) [04:20] cdm10: The packaging can be simple, but it tends to expose lots of issues with the underlying code, which can make it very complex indeed :) [04:20] persia: yeah... [04:23] persia: So, if I were to do this groups thing... I'd use the admin group, which is the same as the group with sudo access (by default, in Ubuntu), right? [04:23] persia: and I'd have to create the config file in the postinst so I could set the group ownership. [04:23] cdm10: That'd be my quick & dirty suggestion. There are other ways to do it as well. [04:24] cdm10: You can push the config file normally, and use the postinst to reset ownership & permissions. [04:24] persia: ok [04:25] persia: I think I'll wimp out and just have it all run as root, for the time being... it's a work in progress, so I'll probably change it to a better way in the future. [04:26] persia: Where can I find documentation on how to create a crontab file to put in cron.daily (which I'm told will be executed automatically by anacron) [04:27] * persia suspects the answer is in man dh_installcron, and suggests reading the debhelper man pages more generally, and asking questions generally of the channel. [04:28] persia: sorry, I thought you had said something about the cron thing before, which is why I asked you... you're right, i'm bad at reading documentation, and should get better instead of annoying people on IRC :) [04:29] cdm10: apt-mirror uses dh_installcron you can look at it for a simple example of what your wanting [04:29] its pretty simplistic use of it [04:29] but i do recomend reading the doc stil [04:30] still* [04:30] imbrandon: thanks [04:31] the quick and dirty is use dh_installcron in your rules ( or cdbs ) and make a debian/cron.d file with the correct info ( this is but just one way to accomplish this ) [04:31] imbrandon: are you using hardy or gutsy? [04:32] nxvl: gutsy with hardy and sid chroot(s) [04:32] i'll likely upgrade to hardy mid-jan [04:32] imbrandon: i need to test the hardy menu entry, is there any way to check it with chroot? [04:32] imbrandon: so, including the proper cdbs thingy will let me just stick a cron.d file into debian/ ? ok. Is there something like that for .desktop files? Right now, my setup.py file handles those. [04:33] i have a hardy VM at work, but at home i can run one, my PC crashes if i try :P [04:33] if you use the debhelper.mk via cdbs yes just create a debian/cron.d ( please read on it though ) [04:33] cdm10: No, and it's a bug, but you do want to include dh_desktop in case someone fixes it in the future. [04:34] persia: So, where should I stick my .desktop files? I have them in a data/ directory now. [04:34] cdm10: yea there is a dh_* ( debhelper ) script for damn near anything you want, and cdbs makes use of most of those , but its good to know what ones you need/want and what you can overide etc [04:35] persia: I'd like to keep them in a place where my setup.py can find them, so I can install them from there until they fix the problem... [04:35] imbrandon: ok, but the desktop one is broken? [04:36] correct [04:36] imbrandon: did you use pbuilder as chroot or another one? [04:36] nxvl: generaly pbuilder as chroot, except for sid, i use a real debootstrapd chroot and sbuild both [04:37] oh! ok [04:37] because i sometimes do gui stuff in my sid one so i have lots of other stuff mounted bind [04:37] with it [04:39] nxvl: depending on how complicted you want to get you cold probably use a nested x server and xhost+ localhost on it, then export DISPLAY=:X in the pbuilder-chroot and use ome gui apps in it [04:39] might need to bind mount tmp too not sure [04:39] could* [04:39] imbrandon: i prefer to use VMs :D [04:40] nxvl: yea most of the time its far easier to use a vm [04:40] and since i'm most of the time at work, it's not usual that i make whing at home [04:40] i only came to my beth [04:41] :) [05:03] cdm10: are ypou still there? [05:03] and the others [05:03] RenatoSilva: oh, hi... sorry 'bout that [05:03] persia: did you see irclogs.ubuntuwire.com ? december is a few days behind and i'd like to fix a few more things before i add a link to it etc but its generaly useable [05:04] err ircstats.uw.c [05:04] not logs [05:04] cdm10: about what? [05:05] RenatoSilva: never mind [05:05] finaly i'm happy with the changes :D [05:05] imbrandon: I think you're duplicating http://ubuntuircstats.org/ (although your data goes back further). What is the additional value? [05:06] cdm10: I want to thank you n everybody very very much coz I just have right now my first .DEB package in life! rs...magic! rsss [05:06] now i can sleep well [05:06] :D [05:06] persia: its going to be a join effort once worked out [05:06] joint* [05:06] cdm10: I want to share it with you, who wants to see it? [05:07] imbrandon: OK. I like the ubuntuircstats graphs better, but I like the ircstats.uw.c history. Also, it'd be nice to have consistent naming, so I'm in favour of ircstats.uw.c. [05:07] RenatoSilva: You should look into getting a PPA [05:07] cdm10: PPA? [05:07] RenatoSilva: It's part of Launchpad, it lets you set up your own package repo [05:08] persia: yea the problem with the other graphs is its irssi log specific, and the historical data is all eggdrop [05:08] but thats all tech, it can be worked arround [05:08] imbrandon: That's fine. Can history usefully be extracted from irclogs.u.c ? [05:09] cdm10: hosted at Launchpad? [05:09] RenatoSilva: yeah [05:09] after 2 or 3 hours of wgeting and some magling with shell scripts yea :) [05:09] persia: how was the christmas out there? [05:09] cdm10: can't believe, very nice! [05:09] persia: in other words doable and will be done but takes a bit o work [05:09] nxvl: Everyone went to work, and had a productive day. Most people are frantically cleaning in preparation for next Monday. [05:09] all my data came from irclogs.u.c [05:10] imbrandon: Understood. My personal preference is for a reduced set of namespaces and close integration and collaboration with everyone. Sounds like you're on the right path :) [05:10] yup yup :) [05:11] imbrandon: Also, I really like the separation of word use frequency and nick reference on the ircstats.uw.c page. If that could be kept, it would be nice. [05:11] persia: wats next monday? [05:11] nxvl: The 31st of January. [05:11] s/January/December/ [05:12] persia: yup [05:12] oh right! [05:14] persia: so there is no christmas spirit on Tokyo? [05:14] cdm10: I'm logged in on Launchpad. How to find this PPA? [05:14] imbrandon: in USA there is a lot os christmas spirit or there is also not much? [05:14] nxvl: Not especially. It's not a popular holiday here. Some people go out on dates. [05:14] RenatoSilva: google for launchpad ppa, i'm sure you'll find a guide [05:14] nxvl: its really commercialy popular here [05:15] imbrandon: same here [05:15] imbrandon: but people say that it's a family holiday [05:15] RenatoSilva: http://www.google.com/url?sa=t&ct=res&cd=1&url=https%3A%2F%2Fhelp.launchpad.net%2FPPAQuickStart&ei=dONxR5n9FKHWeczmiTM&usg=AFQjCNFK9uNfZO57MR7ZCYjmToRT7Fy69Q&sig2=yHmN7DuTrz_tPm8rtBFIlg [05:15] err [05:15] https://help.launchpad.net/PPAQuickStart [05:15] there ya go [05:16] sorry bout the long paste [05:17] RenatoSilva: also you can click on "PPA Archive" on the left and the click on help, top left [05:18] imbrandon: thank u [05:19] uouah, I have to become an Ubuntero rs [05:20] thats easy, just agree and sign the CoC [05:20] then upload it to LP [05:20] it seems theny get a src pkg and build there, I can't send a binary pkg ... [05:20] ppa is broken currently [05:20] i think [05:21] RenatoSilva: yeah, so your build-depends have to be right [05:21] i don't use PPA, and i haven't use it never [05:21] imbrandon: they accept binary pkgs? [05:21] RenatoSilva: correct, then it will build the binary from the source for i386 and x86_64 [05:21] RenatoSilva: Why would anyone want a binary package? [05:21] RenatoSilva: they'll make a binary package for you on the server [05:21] Hobbsee: likely but it will be fixed eventualy* :) [05:22] persia: my source is Java, how they will know how to compile it? [05:22] imbrandon: in some days, yes [05:22] RenatoSilva: that's what your rules file is for... [05:22] RenatoSilva: You will provide an automated build system and call it with debian/rules. [05:23] persia: but to build the app it must have installed a Java 6 compiler [05:23] RenatoSilva: you need to put that in your build-depends [05:23] RenatoSilva: what bug are you working at? [05:23] and it'll install it before it attempts to compile it. [05:23] RenatoSilva: Yes. That's what the build-depends line in debian/control does. [05:23] RenatoSilva: sure then build-depends on IcedTea or gcj [05:24] cdm10: build-depends..hum... cool [05:24] * imbrandon goes back to uploading christmass pictures while i wait for libvisual to compile [05:24] Hobbsee: have a good christmass ? [05:24] cdm10: install before compiling?? [05:24] imbrandon: yeah : [05:24] imbrandon: flickr? [05:24] * :) [05:24] nxvl: bug? [05:24] RenatoSilva: hmm? [05:25] nxvl: yea i store most all my pictures on flickr [05:25] * nxvl adds imbrandon as friend [05:25] RenatoSilva: I'm not the best person to ask, actually. All I know is that you make a rules script to compile the package, and put the stuff you need in order to compile it in the build-depends. [05:25] imbrandon: I guess I'd build-depend from sun-java6-jdk [05:25] RenatoSilva: thats not possible on our buildd's [05:26] because of the lic screen [05:26] thus IcedTea or gcj [05:26] imbrandon: Are you sure? I thought there was some preseeding in place. [05:26] persia: ahh well if they fixed it reciently yes [05:26] * persia thinks it was only a few days ago [05:26] but not that i'm aware but i dont follow java closely [05:26] ahh very very likely then [05:27] RenatoSilva: then it looks like you can but you'll likely have to jump through a hoop or two [05:27] sorry i cant be more specific than that, its my extent of java experince [05:27] imbrandon: java is free software now [05:27] RenatoSilva: sure, well in a sense , but yea i'm aware [05:28] RenatoSilva: i was more specificly talking aobut the debconf question agreeing to the doj?? thing when installing on the buildds [05:28] but persia sugests thats likely fixed now [05:29] RenatoSilva: aren't you working on a bug? whats your package? a debianization? [05:29] imbrandon: I guess many apps just can't leave original Sun Java 6 because the other compilers just don't do all the things Sun's one (version 6) does [05:30] RenatoSilva: i totaly understand the delima, i just dident know there was a solution untill just now [05:30] i prefer not to use java at all :D [05:30] RenatoSilva: Yes, but Sun Java 6 isn't free. Java 7 will be free, and there are free Javas around. [05:30] nxvl: btw, fwiw my pics ( except the ones i'm currently uploading arent there yet ) are at http://www.flickr.com/photos/imbrandon/sets [05:31] since you asked :) [05:31] nxvl: my packange is just my 1st package rs.. I took a Java calculator I've wrote and packaged it into a .DEB right now rs...and the guys are telling me now about Lauchpad's personal repository rs [05:31] imbrandon: i was looking at them :P [05:32] RenatoSilva: oh ok, so there is a debianisation :p [05:32] Hobbsee: btw, got a sec? help me fill in the missing names of these KDE people, i forgot who some of them were :) lol /me is bad [05:32] http://www.flickr.com/photos/imbrandon/2092209213/in/set-72157603397616729/ [05:32] persia: hum, why? source not completely opened still? [05:33] RenatoSilva: Source is open, but license isn't DFSG-free. [05:33] imbrandon: hm. i think that's johnflux on the far left. [05:33] imbrandon: i don' tknow the other one [05:33] nxvl: what's a debianisation? someone learning hwo to build a .deb? rsss... [05:34] imbrandon: don't quote me on that, though [05:34] ahh right yup john [05:34] okies [05:34] * Hobbsee was not at mtv [05:34] and those two were not in sevilla :) [05:34] persia: DFSG? [05:34] RenatoSilva: not, it's making a .deb package from a source for first time [05:34] yea i know, but you likely would have met the kde peeples :) [05:34] aleaste some of them :) [05:34] RenatoSilva: http://www.debian.org/social_contract#guidelines [05:35] nxvl: so ...now I'm a deb packager [05:35] nxvl: rss [05:35] Hobbsee: yea i know its john , i rember now, he was my room mate at UDS MTV [05:35] RenatoSilva: stuff like [05:35] When preparing a new upstream release, should I strive for prettification or minimal divergence if an older version is in Debian? [05:35] minimal divergence, then perfecion via a patch sent upstream [05:35] ( to debian ) [05:36] so both :) [05:36] imbrandon: you were at mtv uds? [05:36] I don't remember seeing you there :P [05:36] nxvl: actually my interest on learning this is that every time a new version of Ubuntu comes, I have to follow some manual steps to get my modem working... [05:36] Amaranth: yea , i sat at your table talking beryl stuff most of the time, infact i made most of the beryl package while at uds [05:36] are the modems stiff alive? [05:36] oh yeah [05:36]