**** BEGIN LOGGING AT Sun Oct 25 02:59:56 2009 Oct 25 05:46:52 03bzhou * r10787 10optware/trunk/make/pure-ftpd.mk: pure-ftpd: 1.0.23 -> 1.0.24 Oct 25 06:13:46 03bzhou * r10788 10optware/trunk/make/lftp.mk: lftp: 4.0.2 -> 4.0.3 Oct 25 12:30:17 Hi eno, are you online Oct 25 15:14:34 carterb: i'm here Oct 25 15:15:08 Hi, I have problems uploading the patch Oct 25 15:15:19 is my cert out of date Oct 25 15:16:04 should not be, it was created quite new Oct 25 15:16:12 ok Oct 25 15:16:15 is there any error message? Oct 25 15:16:31 yes, i am going to start the vm Oct 25 15:19:13 03bzhou * r10789 10optware/trunk/make/msmtp.mk: msmtp: 1.4.18 -> 1.4.19 Oct 25 15:19:14 03bzhou * r10790 10optware/trunk/make/mpop.mk: mpop: 1.0.18 -> 1.0.19 Oct 25 15:19:43 what is the command to open the connection? Oct 25 15:20:29 you first need to do a new 'svn checkout' using https Oct 25 15:21:36 see http://www.nslu2-linux.org/wiki/Optware/AddAPackageToOptware Oct 25 15:22:05 (Developer section) Oct 25 15:22:27 i've forgotten Oct 25 15:25:59 03bzhou * r10791 10optware/trunk/make/keychain.mk: keychain: 2.6.9 -> 2.7.0 Oct 25 15:59:01 hello Oct 25 16:03:13 hi eno, do you know why there is a kernel needed at vt4-toolchain? Oct 25 16:14:28 toolchain usually needs kernel header Oct 25 16:15:11 how stable is xfs/jfs on debian 5.0? old versions hat the nullpointer dereference bug which crashed the whole system Oct 25 16:23:25 Hi eno, still on?? Oct 25 16:44:34 oh, thanks. Oct 25 16:53:09 03bzhou * r10792 10optware/trunk/make/unzip.mk: unzip: worked around cs05q3armel ICE Oct 25 18:36:33 Hi, I know have write access to svn, but I do not know where to put my patch file at Oct 25 18:37:46 sorry, I NOW have write access Oct 25 18:43:25 carterb: apply your patch against the optware tree Oct 25 18:43:40 what is the command Oct 25 18:43:42 and check in the files that have been changed Oct 25 18:43:45 to do that Oct 25 18:44:13 do you have the pastebin URL? Oct 25 18:44:22 yeah Oct 25 18:44:59 oh, outdated Oct 25 18:45:03 do you need it Oct 25 18:45:18 cd optware; patch -p0 < your.patch Oct 25 18:46:01 http://pastebin.com/f483578d Oct 25 18:47:31 how do I have to name the patch Oct 25 18:47:39 or doesnt it matter Oct 25 18:47:56 it does not matter, since you're not committing the patch Oct 25 18:48:08 but rather the changed optware files Oct 25 18:48:15 what is meant by committing Oct 25 18:48:37 a.k.a "checking in" Oct 25 18:48:50 with "svn commit" Oct 25 18:49:28 once you've applied your patch, rebuild and re-test Oct 25 18:50:12 use "svn diff" to make sure you'll only include necesary files Oct 25 18:50:31 sorry, i do not understand Oct 25 18:50:34 then "svn commit [files]" Oct 25 18:50:43 i did svn diff to get the patch, right? Oct 25 18:50:59 what do I have to upload Oct 25 18:51:01 you used "svn diff" on another tree Oct 25 18:51:29 now you re-did "svn co" Oct 25 18:52:02 you can apply the old patch to transfer your changes to the new tree Oct 25 18:52:20 how Oct 25 18:52:43 "cd optware; patch -p0 < your.patch" Oct 25 18:54:23 so i did, and now Oct 25 18:55:12 was the patch application successful? Oct 25 18:55:40 yes, the needed files are patched Oct 25 18:56:00 if so, your new tree should contain the same set of changes as the old tree Oct 25 18:56:09 so it is Oct 25 18:56:36 you can optionally use "svn diff" again to verify Oct 25 18:56:48 rebuild and re-test Oct 25 18:56:59 then you're ready to commit your changes Oct 25 18:57:13 with "svn commit [files]" Oct 25 18:57:45 what do you mean with rebuild... build the ipk-package and test it on my mashine?? Oct 25 18:58:48 yeah, if you're absolutely sure your changes will work you can skip it since you've tested it before Oct 25 18:59:22 for svn command, you can use "svn --help command-name" Oct 25 18:59:53 and in "svn commit [files]" i put every fill with full path? Oct 25 18:59:58 i happen to use git-svn as my svn client Oct 25 19:00:00 file Oct 25 19:00:21 if you don't specify any file, you commit all the changes Oct 25 19:00:39 so thats what I will do, ok? Oct 25 19:00:45 yes Oct 25 19:01:21 these files are logically in the same group, they should be committed in a single transaction Oct 25 19:02:04 I get the message that some lines will be ignored Oct 25 19:02:38 paste the message here Oct 25 19:04:04 -- Diese und die folgenden Zeilen werden ignoriert -- Oct 25 19:04:04 M sources/sane-backends/rc.sane-backends Oct 25 19:04:04 M sources/sane-backends/postinst Oct 25 19:04:04 M make/sane-backends.mk Oct 25 19:04:50 file is called svn-commit.tmp Oct 25 19:06:19 even with google translate, i don't understand why this is happening Oct 25 19:06:46 i remember there's a command "svn info" Oct 25 19:06:48 translation of the german text is: Oct 25 19:06:48 These lines will be ignored Oct 25 19:07:20 what's the output of "svn info"? Oct 25 19:08:12 oli@oli-ubuntu:~/slug/slug_https/optware$ svn info Oct 25 19:08:12 Pfad: . Oct 25 19:08:12 URL: https://svn.nslu2-linux.org/svnroot/optware/trunk Oct 25 19:08:12 Basis des Projektarchivs: https://svn.nslu2-linux.org/svnroot/optware Oct 25 19:08:12 UUID des Projektarchivs: 1f1dca69-5516-0410-b834-e485effd04c3 Oct 25 19:08:12 Revision: 10791 Oct 25 19:08:14 Knotentyp: Verzeichnis Oct 25 19:08:16 Plan: normal Oct 25 19:08:18 Letzter Autor: bzhou Oct 25 19:08:20 Letzte geänderte Rev: 10791 Oct 25 19:08:22 Letztes Änderungsdatum: 2009-10-25 16:25:58 +0100 (So, 25. Okt 2009) Oct 25 19:10:27 these look okay Oct 25 19:12:58 when committing, does it ask for a commit log message? Oct 25 19:13:40 it maybe just that in the default commit message, some of the lines will be ignored Oct 25 19:14:06 it invoked your default EDITOR, right? Oct 25 19:14:18 yes Oct 25 19:14:30 when i close it Oct 25 19:14:37 if that's the case, you need to added a log message at the top Oct 25 19:14:57 Where? At what top Oct 25 19:15:08 in the format of "sane-backends: " Oct 25 19:15:34 if you specify the commit message with -m "sane-backends: ..." Oct 25 19:15:50 At the top of the file that is opened by my default editor Oct 25 19:15:51 then it won't launch the editor at all Oct 25 19:15:56 yes Oct 25 19:16:31 so Oct 25 19:16:31 svn commit -m ..... Oct 25 19:16:48 right Oct 25 19:17:24 i've been using -m "msg..." forever, so I forget the editor message Oct 25 19:18:29 03carterb * r10793 10optware/trunk/ (3 files in 2 dirs): sane-backends: new xinetd-script; new init.d-script Oct 25 19:18:47 carterb, here we go Oct 25 19:18:48 looks good, not? Oct 25 19:18:59 yeah, hard work :-) Oct 25 19:19:01 looks good Oct 25 19:19:41 I have to log every conversation with you, next time I do it by myself Oct 25 19:19:43 getting more familiar with diff (svn diff), patch, and svn would help Oct 25 19:19:59 yes, i will read the help Oct 25 19:20:09 thanks for your support on my first patch Oct 25 19:20:27 when will the package be build? Oct 25 19:20:48 so when can I install it Oct 25 19:20:51 :-) Oct 25 19:21:25 next round will probably in 4-5 hours Oct 25 19:21:51 watch http://logs.nslu2-linux.org/buildlogs/ Oct 25 19:22:16 the autobuild is scheduled to start every 15 minutes if one is not on-going Oct 25 19:22:52 there're lots of other builds (slugos firmware, packages, openwrt ...) before optware Oct 25 19:23:11 you have got a link for every question, right :-) Oct 25 19:23:11 I really like the whole optware thing Oct 25 19:23:22 ok, I'll try it tomorrow Oct 25 19:23:34 great, thx for your work Oct 25 19:24:04 The next days, I'm going to figure out, whats the problem with erl-ejabberd Oct 25 19:24:17 had no time the last days Oct 25 19:24:20 cool Oct 25 19:24:37 you are maintainer of erlang, right? Oct 25 19:24:44 yes Oct 25 19:24:57 k Oct 25 19:27:58 03bzhou * r10794 10optware/trunk/make/mldonkey.mk: mldonkey: 3.0.0 -> 3.0.1 Oct 25 19:28:27 With the help of some people of the forum , I figured out some problems with sane-backends. Some backends do not work right on optware. I do not know the reason exactly, (a lot of work, corresponding to san-backends developers) but when I have some fixes, can I update the package like I did it today or do I have to send in patch before? Oct 25 22:40:23 03bzhou * r10795 10optware/trunk/ (2 files in 2 dirs): lighttpd: 1.4.23 -> 1.4.24 Oct 26 00:28:24 03bzhou * r10796 10optware/trunk/make/transmission.mk: transmission: 1.75 -> 1.76 **** ENDING LOGGING AT Mon Oct 26 02:59:58 2009