Subject: Re: requirements - msg#00598

Previous Message by Date: click to view message preview

Re: Fwd: Failed start with pt_br

We need an answer on that! Harry? Pavel? Unless you already replied to Youness, tell us if it's still a bug! Le 05-11-27 à 16:04, Youness Alaoui a écrit : Hi everyone, it seems it's a known bug, I already heard something about it a few weeks ago, I just checked and it seems it's not fixed yet... or at least, the file is still langpt_BR... I see thre are some other files in the same state, like fr_CA, zh-CN, zh-TW... I don't know if they were fixed though... I just noticed that the langlist file contains a pt_BR language.. maybe it was fixed, but in the langlist file instead of the filename... I just wanna make sure it's fixed before the release... we also might want to change the zh-CN and zh-TW to zh_CN and zh_TW (underscore instead of dash) in order to make the filenames consistent with fr_CA and pt_BR... maybe post-0.95 ------- Forwarded message ------- From: "Eduardo Jorge" <serrano.neves@xxxxxxxxx> To: kakaroto@xxxxxxxxxxxxxxxxxxxxx Subject: Failed start with pt_br Date: Sun, 27 Nov 2005 14:51:01 -0500 Hi, I'm trying to start amsn, after the instalation, using pt_br and this show me an error: Error in startup script: couldn't open "lang/langpt_br" : no such file or directory and i look for dir lang, and the file is langpt_BR, and i move it to langpt_br, and amsn starts ok. i download the package: Linux-i386 installer Tks! -- Serrano Neves - a.k.a eth0 / www.serrano.neves.eti.br "Talk is cheap. Show me the code." - Linus Torvalds -- KaKaRoTo ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Amsn-devel mailing list Amsn-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/amsn-devel ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click

Next Message by Date: click to view message preview

Re: Something else?!

Comments on that? We ship it or not? Le 05-11-27 à 10:22, Karel Demeyer a écrit : I didn't follow the activities, so maybe it's already done, please don't shoot me, but I'd like to make sure the inkdraw plugin I made won't be shipped with 0.95, as the inksending/receiving doesn't work all time... I don't want to be bothered with bugreports about it yet you see ;) Great work guys! Karel On za, 2005-11-26 at 14:46 -0500, Youness Alaoui wrote: ok, here's the things I still think needs to be corrected before the release (minor things)... these things are what I noticed after extracting the deb file (make deb && dpkg -x -d dpkg amsn_0.95....) : * I suggest we add in /usr/bin/amsn-remote and /usr/bin/amsn- remote-CLI not just /usr/bin/amsn * there is a ~/msn/sndplay file that should be removed (Jerome ?) * when we create the deb file, there is a /usr/share/pixmaps/ msn.png that points to the compile dir where the png file was : kakaroto@kakaroto:~/msn/export/pkg/usr$ ls bin/ -l total 0 lrwxrwxrwx 1 kakaroto kakaroto 18 Nov 26 14:14 amsn -> ../share/ amsn/amsn* kakaroto@kakaroto:~/msn/export/pkg/usr/share$ ls -l pixmaps/ total 4 lrwxrwxrwx 1 kakaroto kakaroto 72 Nov 26 14:14 msn.png -> /home/kakaroto/msn/export/debian/amsn/usr/share/amsn/icons/48x48/ msn.png you see, the bin points to the correct amsn file, but the msn.png points elsewhere .. I think it actually points to the temporary directory when the deb file was created... * In the lang directory, there are some files that should be removed : LANG-HOWTO genpage.c missing.py addkey.tcl lang1.tmpl lang2.tmpl lang3.tmpl langchk.sh sortlang complete.pl convert.tcl genlangfiles.c and when I say removed, I'm talking about 'not included in the package' only! * the AppMain.tcl file should be removed when we create a linux/ windows package * amsn.desktop can be removed from the /usr/share/amsn/ directory... * the sxml.tcl file is made as executable, we should remove the executable flag... * These utils/ subdir should be removed, as they are not used yet : pixmapoption/ pixmapbutton/ pixmapprogbar/ and maybe scalable-bg/ too, we'll need to ask Tom, but from a grep, it seems it's only used in pixmapprogbar and pixmapbutton which are removed anyways... * the pixmaps in utils/pixmapscroll/horizontal and utils/pixmapscroll/vertical directories should be made skinable (although it might not be a good time to move all that) * the webcamsn.tcl file in utils/webcamsn should be removed since it was only used as a test.tcl file... * the utils/linux/capture/test.tcl file should be removed. * the libtray.so should have a pkgIndex.tcl file with it and we should do a package require instead of a load... (it might not be a good time to do it also) * fix the make deb so that it won't need to sign the deb file.. if it's needed to make an official release, then the package will have to do that additional step manually... I'll remind you of my problem : dpkg-deb: building package `amsn' in `../ amsn_0.95cvs-20051126_i386.deb'. make[1]: Leaving directory `/home/kakaroto/msn/export' dpkg-genchanges -b dpkg-genchanges: binary-only upload - not including any source code signfile amsn_0.95cvs-20051126_i386.changes gpg: WARNING: unsafe permissions on configuration file `/home/kakaroto/.gnupg/gpg.conf' gpg: WARNING: unsafe enclosing directory permissions on configuration file `/home/kakaroto/.gnupg/gpg.conf' gpg: skipped "Phil <lephilousophe@xxxxxxxxxxxxxxxxxxxxx>": secret key not available gpg: [stdin]: clearsign failed: secret key not available The deb file seems to be created and perfectly 'healty', it just stays in the parent directory... * the control of the debian package might need some thing : conflicts: ccmsn depends: tcl8.4 tk8.4 tcltls * I'd also need someone to do the exact same thing with rpm files... I don't know how it works, but I'll see if I can extract the rpm to a directory... * we might need to check for this kind of things also in the src package (cvs export).. * one last thing... revert back the budy icons... please :( KaKaRoTo On Sat, 26 Nov 2005 10:57:31 -0500, Youness Alaoui <kakaroto@xxxxxxxxxxxxxxxxxxxxxx> wrote: humm... well, even daily is ok, but in a digest, will we get the diff too ? yes, and that's the problem, it's a pain in the ass to go looking for the comments individually... anyways, now, I'm just looking at what CIA-13 has to say on the amsn IRC channel.. it gives me a summary KaKaRoTo On Sat, 26 Nov 2005 06:30:09 -0500, Arieh Schneier <lio_lion@xxxxxxxxxxxxxxxxxxxxx> wrote: I was going to say to go to: http://lists.sourceforge.net/lists/listinfo/amsn-commits and set your option to digest, but then realised the digest is daily instead of weekly. Lio. ----- Original Message ----- From: "Youness Alaoui" oups.. ok, sorry :) I don't read the commits because I filter them, get them to another directory (Opera names that a filter) and mark them as read.. if I don't, I'll have too much to look into and I don't have time to look at normal emails, so imagine with the commits... it would be nice to have a digest of all commits once per week so we can look at what was done, but only get the message that was sent, not the diff... maybe CIA would be a place to look at for this thing, but I don't know if they have a "send me weekly summaries of the activities..." I'll have to look into that. KaKaRoTo On Fri, 25 Nov 2005 16:25:21 -0500, Jérôme Gagnon-Voyer <gagnonje5000@xxxxxxx> wrote: Hey, you should read the amsn-commits list, it was done on 17th november ;-0 De : roadkillbunny@xxxxxxxxxxxxxxxxxxxxx Objet : [Amsn-commits] msn autoupdate.tcl,1.32,1.33 Date : 17 novembre 2005 22:07:57 HNE À : amsn-commits@xxxxxxxxxxxxxxxxxxxxx Update of /cvsroot/amsn/msn In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv26417 Modified Files: autoupdate.tcl Log Message: Fixed: autoupdate now checks for all 'sections' of release numbers Index: autoupdate.tcl ================================================================== = RCS file: /cvsroot/amsn/msn/autoupdate.tcl,v retrieving revision 1.32 retrieving revision 1.33 diff -C2 -d -r1.32 -r1.33 *** autoupdate.tcl 17 Sep 2005 16:32:31 -0000 1.32 --- autoupdate.tcl 18 Nov 2005 03:07:55 -0000 1.33 *************** *** 530,539 **** set yourver [split $version "."] ! if { [lindex $lastver 0] > [lindex $yourver 0] } { ! set newer 1 ! } else { ! # Major version is at least the same ! if { [lindex $lastver 1] > [lindex $yourver 1] } { set newer 1 } } --- 530,537 ---- set yourver [split $version "."] ! for {set x 0} {$x<[llength "$lastver"]} {incr x} { ! if {[lindex $lastver $x] > [lindex $yourver $x]} { set newer 1 + break } } Le 05-11-25 à 16:12, Youness Alaoui a écrit : one more TODO item and pretty important : Make sure the auto-updater recognizes 0.94 < 0.95 < 0.95.1 < 0.95.2 < 0.95.10 < 0.96 KKRT On Fri, 25 Nov 2005 15:56:18 -0500, Youness Alaoui <kakaroto@xxxxxxxxxxxxxxxxxxxxxx> wrote: Yes, I do agree.. as I said, December 1st, if nothing major appears, we release 0.95... if we can't fix the bug by december 1st, we'll use the orkaround and that's it... Harry, maybe you didn't get the latest change because the anonymous CVS wasn't up to date... JUST IN CASE, I would suggest you get the latest cvs again and do a `make clean all`... if the bug still happens, i would really appreciate it if you did like you did at first : give us the backtrace of the segfault ... without the backtrace from gdb, we can't find where the new bug happens... Thanks, KaKaRoTo On Fri, 25 Nov 2005 15:06:19 -0500, Jérôme Gagnon-Voyer <gagnonje5000@xxxxxxx> wrote: Don't forget we just have to re-enable the check for the PWC driver at the start of aMSN. That way, the config buttons will just be disabled so nobody will get a seg fault, that's not a "serious bug" for a release because we can prevent the bug from happening (yes it's better to fix the bug but at least we can prevent it) Le 05-11-25 à 14:09, Harry Vennik a écrit : That is to say, we thought it would be fixed now, but it is not. At this moment I don't think anyone understands why the change by Phil didn't fix it. I tried to find it out this morning, but no success. I will try again tomorrow, if I don't get it again, and neither does anyone else, then I think we should not have this prevent us from releasing 0.95, even though I regard it as quite a serious bug. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Amsn-devel mailing list Amsn-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/amsn-devel ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Amsn-devel mailing list Amsn-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/amsn-devel ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click

Previous Message by Thread: click to view message preview

Re: requirements

Nobody opposed to that, and I agree with you also, so I will just add a msg_box on start of aMSN. Like TkCxImage. The decision to drop TCL/ TK 8.3 was already taken anyway. There's no rush to remove all the "ifs" inside aMSN but now we can do it slowly without having to wonder if we will get bugreport for that. Le 05-11-28 à 17:16, Thomas Geirhovd a écrit : It doesn't make sense to partially 8.3. If aMSN don't work well with it, and nobody cares enough to maintain 8.3 compatibility, it should be dropped to save size, and make the code more readable. If someone want's to add 8.3 support later, they can find the code in cvs. And yes, we should display a warning. We don't want bugreports about something we don't support, right? On 11/27/05, Youness Alaoui <kakaroto@xxxxxxxxxxxxxxxxxxxxxx> wrote: Hi, since amsn now requires tcl/tk 8.4, should we change remove the code that depends on tcl 8.3 ? there are some bugs with binword procs, maybe we should remove the use of these procs... should we also display a warning if the user uses 8.3 ? and say "upgrade to tcl/tk 8.4 or you may suffer" ? -- KaKaRoTo ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Amsn-devel mailing list Amsn-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/amsn-devel -- Thomas Geirhovd ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Amsn-devel mailing list Amsn-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/amsn-devel ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click

Next Message by Thread: click to view message preview

Re: requirements

Thanks, On Tue, 29 Nov 2005 22:39:28 -0500, Jérôme Gagnon-Voyer <gagnonje5000@xxxxxxx> wrote: Done Le 05-11-29 à 22:10, Jérôme Gagnon-Voyer a écrit : Nobody opposed to that, and I agree with you also, so I will just add a msg_box on start of aMSN. Like TkCxImage. The decision to drop TCL/TK 8.3 was already taken anyway. There's no rush to remove all the "ifs" inside aMSN but now we can do it slowly without having to wonder if we will get bugreport for that. Le 05-11-28 à 17:16, Thomas Geirhovd a écrit : It doesn't make sense to partially 8.3. If aMSN don't work well with it, and nobody cares enough to maintain 8.3 compatibility, it should be dropped to save size, and make the code more readable. If someone want's to add 8.3 support later, they can find the code in cvs. And yes, we should display a warning. We don't want bugreports about something we don't support, right? On 11/27/05, Youness Alaoui <kakaroto@xxxxxxxxxxxxxxxxxxxxxx> wrote: Hi, since amsn now requires tcl/tk 8.4, should we change remove the code that depends on tcl 8.3 ? there are some bugs with binword procs, maybe we should remove the use of these procs... should we also display a warning if the user uses 8.3 ? and say "upgrade to tcl/tk 8.4 or you may suffer" ? -- KaKaRoTo ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Amsn-devel mailing list Amsn-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/amsn-devel -- Thomas Geirhovd ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Amsn-devel mailing list Amsn-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/amsn-devel ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Amsn-devel mailing list Amsn-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/amsn-devel ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Amsn-devel mailing list Amsn-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/amsn-devel -- KaKaRoTo ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click