| getxsick | that's fine | 00:00 |
|---|---|---|
| ub3rst4r | hello | 03:27 |
| ub3rst4r | am i allowed to change my license from GNU GPLv3 to a free for non-commercial use license? | 03:28 |
| ub3rst4r | and it will still be open source | 03:29 |
| greg-g | it will not be open source by any definition currently accepted | 03:29 |
| greg-g | and, Creative Commons licenses are not for source code, just FYI :) | 03:30 |
| greg-g | oh, thought I was in the #CC channel, but my comments still stand ;) | 03:30 |
| ub3rst4r | anyone? | 03:31 |
| greg-g | I just gave you some answers | 03:32 |
| wgrant | ub3rst4r: Non-commercial is not open sourc.e | 03:32 |
| ub3rst4r | wgrant what do u mean? | 03:33 |
| nigelb | http://www.opensource.org/docs/osd | 03:35 |
| ub3rst4r | so everyone can just fucking steal from me and i get shit all? | 03:35 |
| ub3rst4r | thats what your trying to say? | 03:35 |
| nigelb | !ohmy | ub3rst4r | 03:37 |
| ubottu | ub3rst4r: Please remember that all Ubuntu IRC channels share the same attitude of providing friendly and polite interaction with all users of all ages and cultures. Basically, this means no foul language and no abuse towards others. | 03:37 |
| ub3rst4r | well my program is being sold for like $5 on ebay by some scammer meanwhile noone has the courage to donate to me o | 03:38 |
| wgrant | That is unfortunate, but open source licenses allow that. | 03:39 |
| ub3rst4r | so joe blow can come and rip me off and meanwhile noone will let me change my license or make it so it cant be sold | 03:40 |
| elb | you can change your own license any time you want | 03:42 |
| elb | if you own the copyright, you choose the license | 03:42 |
| wgrant | ub3rst4r: You can change your license. It just won't meet any accepted definition of open source, and your software will no longer be eligible for free usage of Launchpda. | 03:42 |
| elb | your question was whether or not non-commercial use is open source, and the answer is "no" | 03:42 |
| ub3rst4r | so why do u have the cc license listed? | 03:43 |
| ub3rst4r | it forbids non-commercial use | 03:43 |
| wgrant | CC-0, CC-BY, CC-SA and CC-BY-SA are fine. | 03:46 |
| wgrant | Creative Commons licenses with NC or ND components are non-free. | 03:46 |
| ub3rst4r | do u know any where where i can my source code hosted with a non-commercial license? | 03:47 |
| ub3rst4r | heres a question | 03:55 |
| ub3rst4r | if these people are allowed to sell my software | 03:55 |
| ub3rst4r | shouldnt i be allowed to sell it? | 03:56 |
| greg-g | you can | 03:56 |
| tsimpson | there is nothing stopping you from selling open-source software | 03:56 |
| ub3rst4r | but then id still get removed from lp | 03:57 |
| greg-g | yes, LP is for Open Source projects only | 03:57 |
| tsimpson | most open source licences (that I know of) do not restrict you from offering the software for a fee | 03:57 |
| tsimpson | they just require you to offer the source code for free or at-cost | 03:58 |
| wgrant | No, LP is not just for open source projects. But non-free projects are required to pay for use. | 03:58 |
| ub3rst4r | u guys drive me nuts | 03:58 |
| greg-g | wgrant: correct, sorry | 03:58 |
| ub3rst4r | just cus i wouldnt have the source code for free i have to pay $250 | 03:59 |
| wgrant | ub3rst4r: Canonical provides Launchpad as a free service to support development of Free software. | 03:59 |
| ub3rst4r | thats pretty much capitalism | 03:59 |
| === Ursinha is now known as Ursinha-afk | ||
| doctormo | ub3rst4r: That's pretty much honesty, launchpad the service has rules, launchpad the code base, your free to host it yourself (once you get all the trademarks out) | 05:15 |
| ub3rst4r | kthx | 05:16 |
| marine1 | new ff 3.7 alpha build freezes everytime i open it | 06:03 |
| marine1 | built it from ppa source | 06:04 |
| wgrant | marine1: You should contact the owner of the PPA. | 06:06 |
| wgrant | PPAs contents are not controlled by the Launchpad team. | 06:06 |
| marine1 | wgrant: ok so besides that whatwould you recommend?? | 06:07 |
| wgrant | marine1: Go to the page for the PPA from which you obtained the unstable Firefox build, and ask them, perhaps. | 06:07 |
| marine1 | wgrant: i would if this version of ff wouldn't freeeze. | 06:08 |
| greg-g | install the supported package instead? | 06:08 |
| ripps | marine1: install another browser, epiphany perhaps? | 06:08 |
| marine1 | ripps: can i do that thru synaptic?? | 06:09 |
| greg-g | yep | 06:10 |
| greg-g | yw | 06:10 |
| ripps | oh geez, I should have specified epiphany-browser, he's probably gonna install that boulder dash game by accident | 06:12 |
| wgrant | Hahaha. | 06:13 |
| ZykoticK9 | Could an Op please rename the following post please https://answers.launchpad.net/ubuntu/+question/105776 coarse language used in title and body of post. Thanks. | 06:47 |
| wgrant | "mr angry" indeed. | 06:49 |
| wgrant | ZykoticK9: Ask at https://answers.launchpad.net/launchpad/+addquestion. | 06:49 |
| wgrant | An admin should tend to it on Monday. | 06:49 |
| ZykoticK9 | wgrant, ok thanks | 06:49 |
| ZykoticK9 | wgrant, I'll just ignore it then :) | 06:49 |
| Rashless | hi people! =) | 06:52 |
| Rashless | how to rename launchpad account if I already have ppa? | 06:53 |
| Rashless | is there means to delete the ppa? | 06:54 |
| wgrant | Rashless: You'll have to ask at https:answers.launchpad.net/launchpad/+addquestion, and an admin may be able to do it for you. | 06:54 |
| wgrant | But it's a bit awkward at the moment until we allow proper PPA deletion (in the next month or so, probably) | 06:54 |
| Rashless | ok. thanks! | 06:55 |
| === gnomefreak76 is now known as gnomefreak | ||
| Penguin | Hi, are there any beginner guides on uploading code to launchpad? | 11:58 |
| wgrant | Penguin: Have you checked help.launchpad.net? | 12:00 |
| Penguin | wgrant: Yeah, but it skips the part that I need to know | 12:01 |
| wgrant | Penguin: Which part is that? | 12:01 |
| Penguin | wgrant: It tells you how to uplaod a source directory, but it doesn't tell you what a source directory is | 12:02 |
| wgrant | Penguin: Which document are you reading? | 12:02 |
| Penguin | I'm guessing I need a makefile but not totally sure.. | 12:03 |
| wgrant | Launchpad knows nothing about Makefiles. | 12:03 |
| wgrant | What are you trying to upload to? | 12:03 |
| wgrant | A PPA? A branch? | 12:04 |
| Penguin | https://help.launchpad.net/Code/UploadingABranch | 12:04 |
| Penguin | Soz, that's the guide | 12:04 |
| wgrant | Penguin: Branch contents are just files. | 12:04 |
| wgrant | Launchpad cares not what is inside. | 12:04 |
| Penguin | Err... | 12:04 |
| Penguin | And PPAs are..? | 12:05 |
| wgrant | If you don't know what a PPA is, you don't need to deal with them yet. | 12:05 |
| Penguin | Okay... | 12:06 |
| Penguin | It's a blobber game: https://code.launchpad.net/~blobber/+junk/blobber | 12:06 |
| Penguin | Written in python. | 12:07 |
| wgrant | A Bazaar branch just contains some tree of files. | 12:07 |
| wgrant | It does not care what you put in it. | 12:07 |
| Penguin | Oh, okay... | 12:07 |
| Penguin | But I still need some way of making a deb easily. | 12:08 |
| wgrant | OK, that's where PPAs come in. | 12:08 |
| wgrant | !packaginguide | 12:08 |
| wgrant | !packagingguide | 12:08 |
| ubottu | 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 | 12:08 |
| tumbleweed | how does one get a new language added to launchpad translations? | 12:08 |
| * tumbleweed has someone who wants to translate northern sotho | 12:08 | |
| Penguin | !packaginguide | 12:08 |
| wgrant | Penguin: Follow the first link that ubottu mentioned. | 12:09 |
| Penguin | The python guide presumably?: https://wiki.ubuntu.com/PackagingGuide/Python | 12:11 |
| Penguin | Wow, wow, it's skipped it out again - it's telling me to run dh_make and stuff on the source file - but it hasn't told me how to make that yet | 12:14 |
| wgrant | Penguin: The structure of a source tree is not defined. | 12:14 |
| wgrant | It could be anything at all. | 12:14 |
| Penguin | And dh_make will automatically make a deb? | 12:15 |
| wgrant | No. It will give you a template to fill in to produce a source package, from which can then be built a deb. | 12:15 |
| wgrant | The packaging guide should tell you waht you need to know. | 12:16 |
| wgrant | Otherwise, see #ubuntu-packaging. | 12:16 |
| Penguin | So I will have three files: [ Original > Source > .deb ] - is that right? | 12:17 |
| wgrant | Right. | 12:17 |
| Penguin | So I'll just want to delete my original won't I? | 12:18 |
| wgrant | Why? | 12:18 |
| Penguin | Well I'll have the source - which is kind of the same..? | 12:19 |
| crackhead | Hi, how do I report a bug? I can't find the link | 12:20 |
| wgrant | Penguin: Your project's source is turned into a Debian source package, which then gets turned into a Debian binary package (a .deb). To update the package, you merge the changes from your original source into the source package. | 12:20 |
| Penguin | Oh wait, I think I got it now... | 12:20 |
| wgrant | crackhead: What are you trying to report bug against? | 12:20 |
| crackhead | Ubuntu 9.10 | 12:20 |
| wgrant | crackhead: If it is a graphical application, use the "Report a Problem..." item in the Help menu. | 12:21 |
| crackhead | It's my lenovo u550 hotkeys for brightness | 12:21 |
| wgrant | Otherwise see https://wiki.ubuntu.com/ReportingBugs | 12:21 |
| nigelb | crackhead, also might want to see https://wiki.ubuntu.com/Bugs/FindRightPackage to identify the correct package | 12:23 |
| crackhead | Can I run apport to report a problem that way? | 12:24 |
| crackhead | How am I supposed to find package when I don't know what the problem is? The brightness hotkeys just don't work | 12:25 |
| * Penguin 's head hurts. | 12:25 | |
| Penguin | Right, I think I kind of get it now. | 12:26 |
| wgrant | crackhead: See the page that nigelb linked you too | 12:26 |
| wgrant | s/too/to/ | 12:26 |
| Penguin | How do I license it under public domain though? There doesn't seem to be a dh_make option for that. | 12:26 |
| Penguin | I just successfully built the example .deb - yay! | 12:53 |
| Penguin | So what kind of numbering scheme would you guys advise? I was thinking having 0.0a1 as my first package - this seem okay? | 12:56 |
| crackhead | Thanks. I figured it out - using apport with reporting "Hal" package.. Then just changed the package later in the edit details page.. :) | 13:03 |
| crackhead | how does one change a nick on this irc? | 13:03 |
| === crackhead is now known as joshyg6 | ||
| === joshyg6 is now known as register | ||
| === register is now known as Guest14036 | ||
| === Guest14036 is now known as joshyg6 | ||
| joshyg6 | REGISTER iliad2 josheg@gmail.com | 13:06 |
| joshyg6 | REGISTER test josheg@gmail.com | 13:07 |
| joshyg6 | Why does this not work? | 13:07 |
| joshyg6 | hello? | 13:10 |
| wgrant | joshyg6: You are transmitting the registration command and your password to the #launchpad channel. | 13:11 |
| wgrant | You probably meant to /msg nickserv register PASSWORD EMAIL | 13:11 |
| joshyg6 | what am i doing wrong? can you delete that? or something? sorry | 13:11 |
| joshyg6 | all the instructions aren't accurate.. it says "syntax: register <password> <email add>" and doesn't tell you to use the /nick etc. | 13:12 |
| wgrant | What gave you those instructions? They sound like they came from /msg nickserv help register | 13:12 |
| joshyg6 | they came from help register yes.. | 13:13 |
| joshyg6 | they need to put it in more explicitly with the / nick serv and all | 13:13 |
| geser | joshyg6: http://freenode.net/faq.shtml#userregistration is pretty clear on the steps | 13:14 |
| joshyg6 | the nickserv help message doesn't state the / nick serv format | 13:14 |
| joshyg6 | go check it | 13:15 |
| lfaraone | If someone doesn't have bzr, can they download a tarball of the working tree from Launchpad like Github allows? | 15:07 |
| Seba1 | Hi, I need help please | 15:27 |
| Seba1 | I have been almost 10 hours trying to insert an image in Ubuntu Artwork Incoming Lucid, and could not do it, please help | 15:27 |
| Seba1 | please somebody | 15:28 |
| manish | Seba1, where? in the wiki? | 15:44 |
| Seba1 | yes | 15:45 |
| Seba1 | in the wiki | 15:45 |
| Seba1 | especifically | 15:46 |
| manish | page link please? | 15:46 |
| Seba1 | in Artwork Incoming Lucid | 15:46 |
| Seba1 | https://wiki.ubuntu.com/Artwork/Incoming/Lucid/ | 15:46 |
| manish | Seba1, you are logged in? right? | 15:47 |
| Seba1 | yes | 15:50 |
| manish | you are using the Submit section for submitting? | 15:51 |
| Seba1 | yes, I am logged, | 15:51 |
| Seba1 | yes | 15:51 |
| Seba1 | the submit | 15:51 |
| Seba1 | I already writed the submission | 15:51 |
| manish | can you give the link for page you created? | 15:51 |
| Seba1 | the only thing I cannot do is to display images in the submission | 15:51 |
| Seba1 | https://wiki.ubuntu.com/Artwork/Incoming/Lucid/ABetterThemeForLucid | 15:51 |
| manish | Seba1, checking | 15:52 |
| Seba1 | ok | 15:52 |
| manish | Seba1, in which section you want to put the image? | 15:53 |
| Seba1 | in many sections | 15:53 |
| Seba1 | I mean | 15:53 |
| Seba1 | in concept | 15:53 |
| manish | Seba1, I can't understand how they uploaded images | 15:54 |
| manish | I think MoinMoin should allow hotlinking images on the wiki | 15:55 |
| Seba1 | what's that | 15:55 |
| manish | Seba1, upload your image using this | 15:55 |
| manish | https://wiki.ubuntu.com/Artwork/Incoming/Lucid/ABetterThemeForLucid?action=AttachFile | 15:55 |
| Seba1 | okay, let me see | 15:55 |
| manish | and then include the image using {{attachment:imagename.png}} | 15:56 |
| manish | {{attachment:imagename.png}} | 15:56 |
| manish | Seba1, is this the theme you actually made? http://fibermarupok.deviantart.com/art/Banshee-RythmBox-Re-Imagined-156231564 | 15:57 |
| Seba1 | nop | 15:57 |
| Seba1 | as explained below in the same section, I found it in the web | 15:57 |
| manish | ohkay | 15:57 |
| getxsick | can i use versions like svn1234-1 ? | 15:57 |
| Seba1 | I just want to post it in artwork so the designers can consider that theme | 15:58 |
| manish | Seba1, cool :) | 15:58 |
| Seba1 | thank you very much | 15:58 |
| Seba1 | :-D | 15:58 |
| manish | Seba1, works? | 15:59 |
| Seba1 | i'm checking, I'm on a netbook, so not being so fast here lol | 16:00 |
| Seba1 | yess, UPLOADED, yuppiii | 16:01 |
| Seba1 | in the preview, just in case you are going to the page to see the images | 16:01 |
| Seba1 | I have to upload 8 images in the preview, and then saving and then it will be available in the page itself | 16:02 |
| Seba1 | THANKSSSSSSSSSSSS | 16:02 |
| geser | getxsick: sure, AFAIK there is no other requirement on the version numbers than that they must be monotonic increasing. So think also about the future (e.g. 1.0-1 is smaller than svn1234-1). | 16:03 |
| getxsick | well i thought about 2 archives, for nightly builds and releases, is it wroth path? :) | 16:04 |
| geser | not really, a user installs 1.0 (from the release), some time passes and the user wants to try a nightly build (because of e.g. a new feature), 2.0 gets released and there is no way for the user to upgrade to 2.0 (as the nightly version is bigger) | 16:07 |
| getxsick | geser: right | 16:08 |
| Spads | getxsick: the ~ is sort of magical in revision numbers, so for example 2.0~svn1234-1 is considered less than 2.0 | 16:09 |
| geser | or something like 1.0+svn1234-1 | 16:09 |
| Spads | yeah, either approach is valid, depending on your needs | 16:09 |
| getxsick | are they equivalent? | 16:10 |
| geser | both are greater than 1.0 and smaller 2.0, so in this regard they are equal | 16:11 |
| geser | it depends if you know that the next release number will be: will it be 1.1 or 2.0? | 16:12 |
| getxsick | lets say i have 1.1 release currently, and next release will be 1.1.1 | 16:13 |
| getxsick | shoudl i use 1.1+svn1234-1 or 1.1~svn1234-1 ? | 16:13 |
| geser | 1.1~svn1234-1 < 1.1 < 1.1+svn1234-1 < 1.1.1~svn1234-1 < 1.1.1 | 16:18 |
| geser | hint: you can compare two versions with "dpkg --compare-versions 1.1 \< 1.1+svn1234-1 && echo true || echo false" | 16:19 |
| getxsick | thanks! | 16:21 |
| getxsick | geser: W: pypy source: out-of-date-standards-version 3.8.0 (current is 3.8.3) | 16:42 |
| getxsick | i used 1.3~svn73032-1 | 16:43 |
| === yofel_ is now known as yofel | ||
| geser | this is not about the version of your package but about the value of Standards-Version in debian/control (which Debian policy this package comply with) | 17:31 |
| === lionel___ is now known as 5EXAAKZ44 | ||
| === knielsen_ is now known as knielsen | ||
| === yofel is now known as Guest68359 | ||
| === tsimpson is now known as Guest89542 | ||
| === apachelogger_ is now known as apachelogger | ||
| === Guest89542 is now known as tsimpson | ||
| Muscovy | Could anyone tell me how to put versions of packages for more than one dist in the same PPA? I get errors about uploads of the same things when I try. | 18:47 |
| getxsick | Muscovy: you have to add ~karmic e.g. | 18:48 |
| getxsick | or ~9.10 | 18:48 |
| getxsick | or whatever | 18:48 |
| Muscovy | Where do I add it? | 18:48 |
| getxsick | cause all those packages are stored in the same directory | 18:48 |
| * geser wonders if there is a PPA FAQ covering this question | 18:48 | |
| Muscovy | Oh, ok. | 18:49 |
| Muscovy | Do I format it like package-x.y~karmic? | 18:51 |
| getxsick | Muscovy: yes | 18:51 |
| Muscovy | :D | 18:51 |
| Penguin | Packaging is hard. | 18:53 |
| Penguin | dh-make has generated the following in my changelog: ' Initial release (Closes: #nnnn) <nnnn is the bug number of your ITP> ' - what's this all about? | 18:55 |
| Muscovy | Tha | 18:56 |
| Muscovy | The changelog template. | 18:56 |
| Penguin | I know it's a template, but what's this '(Closes: #nnn) <nnn is the bug number of your ITP>'? | 18:57 |
| * Penguin starts playing the harmonica while waiting for a response. | 18:58 | |
| Muscovy | It's giving an example format of change description. Ex: saying the update fixed bug number nnn. | 18:58 |
| Penguin | Muscovy: Oooooh! That makes perfect sense now! Thanks! | 19:00 |
| * Penguin slaps head | 19:00 | |
| Penguin | BTW, what does ITP stand for though? | 19:00 |
| Muscovy | getxsick: I tried just naming the directory with a ~karmic on the end, but that seems to completely not factor. Is there a specific place, like changelog or control that I put it? | 19:00 |
| Muscovy | And I'm not sure, Penguin. | 19:01 |
| tumbleweed | Penguin: Intent-To-Package, which is a bug you file against wnpp in debian | 19:01 |
| getxsick | Muscovy: use it in changelog | 19:01 |
| Muscovy | Currently my headers in changelog are: package-name (3.2.4) lucid; urgency=high | 19:02 |
| === lionel_ is now known as lionel | ||
| Penguin | tumbleweed: Thanks | 19:03 |
| getxsick | Muscovy: urgency=high ? why? | 19:03 |
| Muscovy | I had completely messed up the package. | 19:03 |
| getxsick | Muscovy: also, use 3.2.4~karmic | 19:03 |
| tumbleweed | Penguin: if you are aiming for revu, rather than debian, file it in ubuntu, and specify the bug as LP#xxxx | 19:05 |
| Penguin | tumbleweed: Soz, this is my first package and you've completely lost me there. | 19:07 |
| Muscovy | I know how you feel penguin, i just started days ago. | 19:09 |
| Penguin | After finally making it through the maze of dh_make, I understand that I must yet pass through the labyrinth that is lintian before my work is done. | 19:09 |
| * Penguin sighs. | 19:09 | |
| Penguin | Muscovy: Did you find it this hard? | 19:10 |
| Muscovy | What sort of errors is lintian giving? | 19:10 |
| Muscovy | Fairly. | 19:10 |
| Muscovy | IMO, the hardest was learning how to deal with makefiles. | 19:10 |
| tumbleweed | yeah, it takes some practice to quiet lintian. but you'll learn in the process | 19:10 |
| * Penguin looks shifty... | 19:10 | |
| Penguin | I didn't use a make file... | 19:11 |
| Muscovy | Ok, anything I've tried to specify lucid in this line moreso than "lucid" is failing. | 19:11 |
| Muscovy | openoffice-splash-art (3.2.4) lucid; | 19:11 |
| Muscovy | ANd yet it think it's no different than my karmic package. | 19:11 |
| Penguin | If you're packaging a python app. I thought you were supposed to use distutils... | 19:12 |
| Muscovy | I don't know there. | 19:12 |
| * Penguin heads onwards into lintian. | 19:13 | |
| Muscovy | My packages so far have been artwork, so my makefiles just have "dh $@", which I seem to utterly fail without. | 19:13 |
| getxsick | so i have release packages and nightly builds, can i keep it in the same ppa? or it's better to have 2? | 19:13 |
| tumbleweed | yes, a setup.py using distutils is the best solution for python | 19:13 |
| Muscovy | Unless you add a -nightly or something, from my limited understanding, I don't see how they could share a PPA. | 19:14 |
| Penguin | Muscovy: I always wondered how the artwork works, since it doesn't need to be compiled... | 19:14 |
| Muscovy | I have no clue why I need a makefile. | 19:15 |
| Muscovy | I got the source of light-themes to see how it was done. | 19:15 |
| Muscovy | The principal two things are that mystery makefile and an "install" files, which contains the name of any folders to be copied, followed by where to put them. | 19:16 |
| Muscovy | In that case it was: | 19:16 |
| Muscovy | Ambiance Radiance usr/share/themes | 19:16 |
| Muscovy | I have no idea why usr had no initial /. | 19:16 |
| Penguin | There are some things that us mere mortals shall never know.... | 19:18 |
| tumbleweed | Muscovy: man dh_install | 19:19 |
| mtaylor | eek. why isn't lp-submit using launchpadlib... | 19:20 |
| * Penguin looks at the insane amount of windows he has open, all to complete one simple task. | 19:27 | |
| * Penguin thanks god for compiz-cube. | 19:27 | |
| === jkakar_ is now known as jkakar | ||
| Penguin | Lintian just brought up an error, googling reveals nothing, anyone know what it means? 'warning: cannot find binary, udeb or source package vec2d_1-1_all.deb in dist or lab (skipping)' | 19:31 |
| Penguin | 'vec2d_1-1_all.deb' being the .deb that I'm checking. | 19:32 |
| tumbleweed | Penguin: you sure you pointed it at a file that exists? | 19:33 |
| tumbleweed | the deb will be in .. | 19:33 |
| * Penguin is embarrassed | 19:34 | |
| Penguin | tumbleweed: That was exactly it. | 19:34 |
| Penguin | I had two terminals open, must have typed it into the wrong one. | 19:35 |
| Penguin | Almost done, just two questions on lintian errors. | 19:47 |
| Penguin | I presume, since this isn't for debian, I can just ignore 'W: blobber: new-package-should-close-itp-bug'? | 19:48 |
| geser | yes | 19:49 |
| Penguin | Great! | 19:49 |
| Penguin | I'm finally done! | 19:49 |
| * Penguin offers cookies on the house. | 19:50 | |
| getxsick | do i need to keep ~karmic.orig.tar.gz, ~jaunty.orig.tar.gz ? can't i use just one? | 20:03 |
| tumbleweed | getxsick: you should use a single one that they all build on | 20:05 |
| tumbleweed | i.e. 1.9+bzr13.orig.tar.gz and 1.9+bzr13-1~karmic.dsc | 20:06 |
| getxsick | tumbleweed: This package has a Debian revision number but there does not seem to be | 20:11 |
| getxsick | an appropriate original tar file or .orig directory in the parent directory; | 20:11 |
| getxsick | (expected one of pypy_1.2.0+karmic.orig.tar.gz, pypy_1.2.0+karmic.orig.tar.bz2, | 20:11 |
| getxsick | pypy_1.2.0+karmic.orig.tar.lzma or pypy-1.2.0.orig) | 20:11 |
| tumbleweed | getxsick: http://packages.debian.org/pypy confirms no debian version | 20:12 |
| getxsick | tumbleweed: so? | 20:13 |
| tumbleweed | getxsick: you are packaging daily builds? | 20:13 |
| getxsick | tumbleweed: now, for a release, but yes i wanna pack daily builds as well | 20:14 |
| tumbleweed | getxsick: ubuntu version numbers appear to look like this: pypy | 1.0.0-svn55443-1 | jaunty/universe | source, amd64, i386 | 20:15 |
| tumbleweed | any reason not to stick with that? | 20:15 |
| getxsick | tumbleweed: it's completely outdated | 20:15 |
| getxsick | actually i would like to not keep that 1.0.0 in ubuntu any more | 20:15 |
| tumbleweed | so you are packaging 1.2? or later than 1.2 | 20:16 |
| getxsick | i'm packing 1.2 and daily | 20:16 |
| tumbleweed | for 1.2, use 1.2-0ubuntu1 | 20:16 |
| getxsick | 1.2-0ubuntu1~karmic-1 ? | 20:16 |
| tumbleweed | for daily, use 1.2+svnXXXX-0ubuntu1 or 1.3~svnXXXX-0ubuntu1 (assuming the next release will be called 1.3 and is due real-soon-now) | 20:17 |
| getxsick | tumbleweed: but if i wanna build it for few series, i have to add that ~karmic, ~jaunty or something like that, right? | 20:17 |
| tumbleweed | oh right you need to include release too | 20:17 |
| getxsick | so 1.2-0ubuntu1~karmic-1 looks ok, for you? | 20:18 |
| tumbleweed | yeah, that's the most common version scheme | 20:18 |
| tumbleweed | even though it's pretty long | 20:18 |
| getxsick | what about orig files | 20:18 |
| tumbleweed | karmic1, not karmic-1 | 20:18 |
| getxsick | how to name it | 20:18 |
| tumbleweed | the difference between the upstream version and debian/ubuntu version is at the - | 20:19 |
| tumbleweed | so we are talking 1.2.orig.tar.gz and 1.2+svnXXXX.orig.tar.gz | 20:19 |
| getxsick | tumbleweed: dpkg-source: warning: Version number suggests Ubuntu changes, but Maintainer: does not have Ubuntu address | 20:24 |
| getxsick | :-) | 20:24 |
| tumbleweed | getxsick: in Ubuntu, the maintainer is MOTU (for universe) | 20:24 |
| getxsick | tumbleweed: yeah, but i'm not | 20:24 |
| tumbleweed | getxsick: not a motu? that's not an issue. List MOTU as the maintainer, and yourself as XSBC-Original-Maintainer | 20:25 |
| getxsick | tumbleweed: is it really a correct way for PPA packages? | 20:26 |
| tumbleweed | getxsick: I agree for your dailies, leave yourself as maintainer. I doubt there's any policy on that, though | 20:30 |
| getxsick | tumbleweed: i think, i should drop that 0ubuntu1...don't see a reason to keep it | 20:31 |
| tumbleweed | getxsick: the reason to keep it is taht if the same version gets uploaded to debian | 20:32 |
| tumbleweed | it'll have a version number of -1 | 20:32 |
| getxsick | tumbleweed: that can't happen | 20:32 |
| tumbleweed | getxsick: why? | 20:32 |
| getxsick | tumbleweed: debian dropped our package some time ago and decided that it's not gonna be back :) | 20:32 |
| tumbleweed | heh. I think you need to keep it though, ubuntu policy | 20:33 |
| getxsick | so why most of PPA packages don't have it? | 20:34 |
| tumbleweed | probably because PPA packages aren't normally very well packaged. They should be careful to ensure that they are lower or higher than the relavent ubuntu / debivan version numbers (as appropriate) | 20:35 |
| getxsick | so what about daily? drop it? | 20:36 |
| tumbleweed | you probably want to be replaced by official packages when they appear, so just keep that in mind | 20:37 |
| tumbleweed | beyound that, it's up to you how you manage your version numbers | 20:37 |
| getxsick | tumbleweed: i decided to use package-x.y.z-ppa1~release1 i guess it's optimal for now | 20:59 |
| tumbleweed | getxsick: rather use ~ppa1 | 21:00 |
| getxsick | tumbleweed: why? | 21:00 |
| tumbleweed | ~ sorts before anything else | 21:01 |
| tumbleweed | i.e. x.y.z is a higher version number than x.y.z~1 | 21:01 |
| getxsick | tumbleweed: yeah, but in the past i used x.y.z-n so now ~ppan makes it smaller than previous | 21:03 |
| tumbleweed | that would be agood reason not to use ~ :) | 21:03 |
| getxsick | that's why i try to use -ppan :) | 21:03 |
| getxsick | heh, maybe i will try to clean it up one day | 21:04 |
| getxsick | btw. is there any good manual to read about versioning on LP? | 21:04 |
| tumbleweed | getxsick: http://www.za.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version | 21:05 |
| AndrewGee | Hi all. I keep getting "Unexpected form data" error messages when submitting most forms on launchpad. Is there any obvious solution I've missed, or should I perhaps file a bug? | 21:10 |
| lfaraone | I have a series of HTML pages in Launchpad. Can I view them "bare", so that they are rendered in my browser? | 21:39 |
| === crimsun_ is now known as crimsun | ||
| mwhudson | lfaraone: no | 22:03 |
| mwhudson | it would be nice in some ways, but there's also some security concerns | 22:03 |
| === MTeck-ricer is now known as MTecknology | ||
| === azop_ is now known as azop | ||
| === \u03b5 is now known as epsy | ||
| === epsy is now known as \u03b5 | ||
| getxsick | i have package_x.y.z~svn1234.orig.tar.gz, however dpkg-source creates own archives for each ubuntu version | 22:39 |
| getxsick | how to avoid it? | 22:39 |
| geser | there must be some small mistake | 22:40 |
| geser | can you pastebin the output when running "debuild -S" | 22:41 |
| getxsick | geser: http://paste.pocoo.org/show/194992/ | 22:42 |
| geser | ah, it's because you don't have a Debian revision. Everything before the last - is considered the upstream version and matched against the version when looking for the .orig.tar.gz | 22:45 |
| geser | try 1.3~svn20100328r73052-0jaunty1 and pypy_1.3~svn20100328r73052.orig.tar.gz and you should get .diff.gz | 22:46 |
| getxsick | geser: thx! | 22:56 |
| lfaraone | mwhudson: so something a la http://vhernandez.github.com/gtksheet/ is outside the scope. | 23:18 |
| mwhudson | lfaraone: i've lost context, sorry | 23:19 |
| mwhudson | oh | 23:19 |
| mwhudson | yes, for now it is :( | 23:19 |
| lfaraone | mwhudson: okay, thanks. | 23:19 |
| === yofel_ is now known as yofel | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!