Login: GUEST @ JH4XSY.14.JNET1.JPN.AS [Tsuchiura]
home | newest check | boards | help index | log | ps | userlogin | send sysop | slog | status forward | bcm news | users | version | remove cookieI0OJJ > FBB 25.09.26 22:03l 120 Lines 3217 Bytes #9 (0) @ WW BID : 239-I0OJJ Read: GUEST Subj: Re: linfbb 7.0.13 released Path: JH4XSY<IW0QNL<OK0NBR<OK2PEN<VE2JOS<VE3CGR<LU9DCE<LU1DBQ<I0OJJ Sent: 260925/1252Z 239@I0OJJ.ITA.EU [Rome] $:239-I0OJJ From: I0OJJ@I0OJJ.ITA.EU To : FBB@WW Hi Bernard and all, very TNX for this new release. However I found two faults occurred here. The first: this new version of 'satupdat' and already that released on 'r247-trunk' (May 2026) are not able to process the updated 'amsat.txt' file. It reports the following msg and: file 'satel.dat' is not updated and the input 'amsat.txt' file is correctly deleted after the process. --------- >sp I0OJJ >SATUPDAT results Update of F6FBB's BBS satellite data base orbital parameters Version 1.91 - September 2026 - Bernard Pidoux, bernard.f6bvp@gmail.com Reading AMSAT format Update merging new list with old list deleting data older than 100 days. reading file satel.dat sorting by catalog number.............................................................................................. 95 data less than 100 days Reading file: amsat.txt Nothing to update on 25/09/26 at 02:40:40 Update of F6FBB's BBS satellite data base orbital parameters Version 1.91 - September 2026 - Bernard Pidoux, bernard.f6bvp@gmail.com Reading AMSAT format Update merging new list with old list deleting data older than 100 days. reading file satel.dat sorting by catalog number.............................................................................................. 95 data less than 100 days Reading file: amsat.txt Nothing to update on 25/09/26 at 02:40:40 >/ex ---------- The second is the failure on processing/purging the old msgs. I had a very few msgs dated May 2026 and: - they were not listed on the PMS by doing the 'l' and 'll' commands from the PMS prompt: - msgs where visible only on the ../mail(x) direcyories. TIP: in the above kinda situation the cure was to give repeatedly the /k command and the one by one msg which appearing with the 'll' command killed each time. If you have *many* old msgs the suggested way is to start the PBBS from scratch because the above procedure shold be almost impossible. I think that a current and purged FBB PMS should not have any listing failure after the 7.0.13 update. -- 73 and ciao, gustavo i0ojj non multa, sed multum ------------- From f6bvp%f6bvp.frpa.fra.eu@i0ojj.ampr.org Fri Sep 25 13:23:32 2026 Received: from i0ojj.ampr.org by i0ojj.ampr.org (JNOS2.0q.1) with SMTP id AA17068505 ; Fri, 25 Sep 2026 13:23:32 +0200 X-Forwarded-To: N2NOV Date: 23 Sep 26 18:29:00 GMT Message-Id: <21827_F6BVP@n2nov.bbs> From: f6bvp@f6bvp.frpa.fra.eu To: fbb@ww Subject: linfbb 7.0.13 released X-BBS-Msg-Type: B X-JNOS-User-Port: Circuit (ARECS:N2NOV-7 N2NOV-7) -> Sending message X-Forwarded-To: ir0eq X-Forwarded-To: gb7cip X-Forwarded-To: kq6up X-Forwarded-To: n6rme R:260923/1829Z @:F6BVP.FRPA.FRA.EU #:21827 [Paris] $:21827_F6BVP From: F6BVP@F6BVP.FRPA.FRA.EU To : FBB@WW 7.0.13 is released Source tarballs fbb-7.0.13.tar.gz and fbb-7.0.13.tar.bz2 are in the root of the Files area of the linfbb project on SourceForge: https://sourceforge.net/projects/linfbb/files/ SHA-256 checksums: 78f745a43120842433e9ea3ac32a61da77c999206e07107ffa1d38c9ab1cd522 fbb-7.0.13.tar.gz f6b92c71fb26b85b4e5a9cfcdf3d62f3be349b9916189544a8a474e2a190dc6c fbb-7.0.13.tar.bz2 73 de Bernard, F6BVP -------------
前のメール | 次のメール