Re: When will mc-4.6.2 be released?
Hello Marcel, On Fri, 2005-02-11 at 14:25 +0100, Marcel Pol wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Leonard den Ottolander wrote: | The problem with Fedora using a 4.6.1a tarball is caused by the fact | that Jindrich Novy didn't read pchel's message that HEAD is now a post | 4.6.1 branch and he should have been updating to MC_4_6_1_PRE instead. A small problem that comes from that is that the utf8 patches are developed against head now. There are a few rejects when applying to current 4.6.1. Since I'm no C coder I'm not able to upgrade the Mandrake package to current 4.6.1, and I'd rather not touch head. The failed hunks apply to these files: edit/editcmd.c src/view.c Would it be possible for someone to look at this? I asked Jindrich Novy directly but didn't get an answer, and the 0.4 release of the src.rpm is still based on head. I sent you a reply in the same day that I received your email, but I got an immediate delivery failure, because there were pernament fatal errors delivering the message to mpol[at]mandrake.org - the address you sent me your request from and I had no clue to figure out what's your working email. I forwarded you my answer once again today to the gmx.net mailbox that you currently use. I did a few another fixes to the UTF8 pathes that haven't occur at rawhide yet. If you still need to sync the UTF8 patches with your version of mc including the latest fixes, please let me know. greetings, Jindrich -- Jindrich Novy [EMAIL PROTECTED], http://people.redhat.com/jnovy/ ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: When will mc-4.6.2 be released?
Hello Marcel, Jindrich, On Fri, 2005-02-11 at 14:25, Marcel Pol wrote: A small problem that comes from that is that the utf8 patches are developed against head now. There are a few rejects when applying to current 4.6.1. Since I'm no C coder I'm not able to upgrade the Mandrake package to current 4.6.1, and I'd rather not touch head. That is a very bad development. We want these patches to be used downstream for 4.6.1. For post 4.6.1 we hope to implement support for multibyte character sets by wrapping relevant functions. Jindrich, I have asked you repeatedly to revert from the use of HEAD for the pre 4.6.1 releases. Please, please, please could you use a PRE tarball for the development rpms for Fedora Core and Red Hat Enterprise Linux? I've put a lot of effort to get these patches from Red Hat (Jakub Jelinek) and SuSE (Vladimir Nadvornik) synchronized and I would hate it to see that effort wasted. Thanks. Leonard. -- mount -t life -o ro /dev/dna /genetic/research ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: When will mc-4.6.2 be released?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Leonard den Ottolander wrote: | On Fri, 2005-02-11 at 14:25, Marcel Pol wrote: | |A small problem that comes from that is that the utf8 patches are |developed against head now. There are a few rejects when applying to |current 4.6.1. Since I'm no C coder I'm not able to upgrade the Mandrake |package to current 4.6.1, and I'd rather not touch head. | | | That is a very bad development. We want these patches to be used | downstream for 4.6.1. For post 4.6.1 we hope to implement support for | multibyte character sets by wrapping relevant functions. | | Jindrich, I have asked you repeatedly to revert from the use of HEAD for | the pre 4.6.1 releases. Please, please, please could you use a PRE | tarball for the development rpms for Fedora Core and Red Hat Enterprise | Linux? I've put a lot of effort to get these patches from Red Hat (Jakub | Jelinek) and SuSE (Vladimir Nadvornik) synchronized and I would hate it | to see that effort wasted. Thanks. I'm sorry, it turns out I was partly wrong here. The devel tree for Fedora4 has a package from cvs head, while updates for Fedora3 hold a 4.6.1-pre3 package with an utf8 patch that applies cleanly against it. Sorry for any confusion. - -- Marcel Pol -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCDgJnMgeuL0xhZZ4RAkcsAJ4uR0Ko9BQGO5jjSLZB53EokygC+ACeJpcd K4Bq2ElBG7Yx3uWxZYSiKys= =rQiX -END PGP SIGNATURE- ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: When will mc-4.6.2 be released?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Leonard den Ottolander wrote: | The problem with Fedora using a 4.6.1a tarball is caused by the fact | that Jindrich Novy didn't read pchel's message that HEAD is now a post | 4.6.1 branch and he should have been updating to MC_4_6_1_PRE instead. A small problem that comes from that is that the utf8 patches are developed against head now. There are a few rejects when applying to current 4.6.1. Since I'm no C coder I'm not able to upgrade the Mandrake package to current 4.6.1, and I'd rather not touch head. The failed hunks apply to these files: edit/editcmd.c src/view.c Would it be possible for someone to look at this? I asked Jindrich Novy directly but didn't get an answer, and the 0.4 release of the src.rpm is still based on head. Regards, - -- Marcel Pol -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCDLIzMgeuL0xhZZ4RAtypAJ0fPna/3nyamLq1DOmg0/9gKYeckACeL8a3 PdyoZrwFhatuQb6mfdoLd+4= =EKou -END PGP SIGNATURE- ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: When will mc-4.6.2 be released?
Marcel Pol wrote: A small problem that comes from that is that the utf8 patches are developed against head now. There are a few rejects when applying to current 4.6.1. Since I'm no C coder I'm not able to upgrade the Mandrake package to current 4.6.1, and I'd rather not touch head. The failed hunks apply to these files: edit/editcmd.c src/view.c Would it be possible for someone to look at this? I asked Jindrich Novy directly but didn't get an answer, and the 0.4 release of the src.rpm is still based on head. I can do it. Just send me the files. Roland ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: When will mc-4.6.2 be released?
Hello, all! On Tue, 2005-02-08 at 05:49, Pavel Shirshov (pchel) wrote: Pavel Roskin doesn't release of mc-4.6.1-pre3 because: - mc exists when run remotely over ssh with X forwarding enabled: . . . I wouldn't call this an OpenSSH issue. From http://www.openssh.com/txt/release-3.8: This is a newly introduced issue that is caused by a change in openssh. It should be fixed for the next release, BUT IT SHOULD NOT DELAY THE RELEASE OF 4.6.1. I agree. As for me 4.6.1 should be released soon. Also I have some questions about cpio issue. It was reported by Pavel Roskin: 1. #9 0x0041f07a in regex_command (filename=0x0, action=0x47d8fb Open, move_dir=0x0) at ext.c:262 filename=0x0 is very bad thing. Is this core image copesponded to your mc executable? 2. Is this problem exists for 4.6.0 on AMD64? 3. Can you open this .cpio by 4.6.1-pre on ia32? -- Regards, Andrew V. Samoilov GET INTERNET ACCESS FROM BCS! http://www.bcs.zp.ua Join BCS today! For your FREE webmail, visit: http://email.zp.ua/ ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: NetBSD support (was: When will mc-4.6.2 be released?)
Roland Illig wrote: Pavel Shirshov (pchel) wrote: RI By the way: NetBSD already has a current Midnight Commander RI (4.6.1-pre2b), and although mcslang does not work at all, it was RI easy to make it build and run, as there is also a `slang' package. I'll see on NetBSD problem today. Please don't. The mc runs fine on NetBSD, so we don't need a fix there. I got a complaint about this statement and I regret it. I also fixed the issue in the current CVS version. Roland ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re[2]: NetBSD support (was: When will mc-4.6.2 be released?)
Hello Roland, Thursday, February 10, 2005, 6:38:31 PM, you wrote: Please don't. The mc runs fine on NetBSD, so we don't need a fix there. RI I got a complaint about this statement and I regret it. I also fixed the RI issue in the current CVS version. Backported to mc-pre. Thx. -- Best regards, Pavelmailto:[EMAIL PROTECTED] ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: When will mc-4.6.2 be released?
Hi Roland, On Wed, 2005-02-09 at 21:39, Roland Illig wrote: Sorry, I think I got this wrong. There was a weird numbering scheme, but as Leonard told me today, it is the mc-4.6.1a (in configure.ac) that is confusing. I was somewhat mistaken. 4.6.1a is a valid tag for HEAD assuming this is the branch for the 4.6.2 release. Miguel only changed the tag for the PRE branch which is fine. The problem with Fedora using a 4.6.1a tarball is caused by the fact that Jindrich Novy didn't read pchel's message that HEAD is now a post 4.6.1 branch and he should have been updating to MC_4_6_1_PRE instead. Leonard. -- mount -t life -o ro /dev/dna /genetic/research ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re[2]: When will mc-4.6.2 be released?
Hello Leonard, Wednesday, February 9, 2005, 11:05:22 PM, you wrote: LdO This is a newly introduced issue that is caused by a change in openssh. LdO It should be fixed for the next release, BUT IT SHOULD NOT DELAY THE LdO RELEASE OF 4.6.1. I'm absolutely agree with you. Pre isn't release. It's _prerelease_. Let people will try to use mc! -- Best regards, Pavelmailto:[EMAIL PROTECTED] ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
When will mc-4.6.2 be released?
Hi all, especially our project maintainers, the release of a new MC version is long overdue. Also there has been some confusion concerning our version numbering scheme, as some distributions consider a version 4.6.1-pre3 to be higher than 4.6.1. For these reasons I vote that the current Midnight Commander be released _this_ _month_, not as mc-4.6.1, but as mc-4.6.2. To avoid repeating those confusion, we should not announce those many release candidates. I think the next main releases should be 4.7, 4.8, 4.9, ... with 4.7.1, 4.7.2, ... being the release candidates. By the way: NetBSD already has a current Midnight Commander (4.6.1-pre2b), and although mcslang does not work at all, it was easy to make it build and run, as there is also a `slang' package. So don't be too afraid about bugs. Even the Debian people will manage the undefined references from the link editor. Roland ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: When will mc-4.6.2 be released?
Hi Roland, On Mon, 2005-02-07 at 22:20, Roland Illig wrote: the release of a new MC version is long overdue. Also there has been some confusion concerning our version numbering scheme, as some distributions consider a version 4.6.1-pre3 to be higher than 4.6.1. Nope. The point is that at December 3rd pchel tagged HEAD 4.6.1a. According to his scheme HEAD was supposed to be used for experimental code that should *not* go into 4.6.1. Essentially we where then working with two branches. However, it seems Miguel has reverted this tagging. This is ok, except for the fact that now some experimental code that was not supposed to go into 4.6.1 is now in the prerelease. I'm not sure if this is a problem, but this was *not* the intention 2 months ago. But then 2 months ago the intention was to have a release before the new year, so this tagging shouldn't be my main concern. Leonard. -- mount -t life -o ro /dev/dna /genetic/research ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: When will mc-4.6.2 be released?
Hello Roland, Tuesday, February 8, 2005, 2:20:18 AM, you wrote: RI the release of a new MC version is long overdue. Also there has been RI some confusion concerning our version numbering scheme, as some RI distributions consider a version 4.6.1-pre3 to be higher than 4.6.1. mc numbering like linux kernel, see at www.kernel.org. rc - release candidate pre - prerelease mc-4.6.1-pre3 - prerelease 3 of mc-4.6.1 RI For these reasons I vote that the current Midnight Commander be released RI _this_ _month_, not as mc-4.6.1, but as mc-4.6.2. I don't agree with it. RI To avoid repeating those confusion, we should not announce those RI many release candidates. I think the next main releases should be RI 4.7, 4.8, 4.9, ... with 4.7.1, 4.7.2, ... being the release RI candidates. RI By the way: NetBSD already has a current Midnight Commander RI (4.6.1-pre2b), and although mcslang does not work at all, it was RI easy to make it build and run, as there is also a `slang' package. I'll see on NetBSD problem today. RI So don't be too afraid about bugs. Even the Debian people will manage RI the undefined references from the link editor. Pavel Roskin doesn't release of mc-4.6.1-pre3 because: - mc exists when run remotely over ssh with X forwarding enabled: X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 38 (X_QueryPointer) Resource id in failed request: 0x60 Serial number of failed request: 6 Current serial number in output stream: 6 This is an openssh issue. Please compare https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=125838 . You need to use ssh with -Y instead of -X IIRC. I wouldn't call this an OpenSSH issue. From http://www.openssh.com/txt/release-3.8: * ssh(1) now uses untrusted cookies for X11-Forwarding. Some X11 applications might need full access to the X11 server, see ForwardX11Trusted in ssh(1) and xauth(1) for more information. So, mc needs full access, but it cannot get in certain cases. If that happens, mc should stop using X events without exiting. It's not like mc is completely useless without full access to the X server. - And - I have a cpio archive (CONTENTS.cpio from an rpm) that I cannot open in mc. mc crashes. I'm sorry, but I cannot send that archive. Here's the backtrace (Fedora Core 3 on AMD 64): #0 0x004726a2 in cpio_open_archive (me=0x5b4600, super=0x5f03d0, name=0x5efcb0 /home/proski/tmp/CONTENTS.cpio, op=0x6 Address 0x6 out of bounds) at cpio.c:245 #1 0x0046a161 in vfs_s_get_path_mangle (me=0x5b4600, inname=0x5efcb0 /home/proski/tmp/CONTENTS.cpio, archive=0x7fffde38, flags=0) at direntry.c:483 #2 0x0046a25b in vfs_s_get_path (me=0x5b4600, inname=0x488da6 070702, archive=0x7fffde38, flags=0) at direntry.c:511 #3 0x0046a33e in vfs_s_inode_from_path (me=0x5b4600, name=0x8000 Address 0x8000 out of bounds, flags=5) at direntry.c:566 #4 0x0046a3e3 in vfs_s_opendir (me=0x5b4600, dirname=0x8000 Address 0x8000 out of bounds) at direntry.c:595 #5 0x0046a4a9 in vfs_s_chdir (me=0x488da6, path=0x8000 Address 0x8000 out of bounds) at direntry.c:649 #6 0x0046e963 in mc_chdir (path=0x488da6 070702) at vfs.c:691 #7 0x004307da in _do_panel_cd (panel=0x5d86a0, new_dir=0x5efc80 CONTENTS.cpio#ucpio, cd_type=cd_parse_command) at main.c:588 #8 0x00430ab6 in do_panel_cd (panel=0x5d86a0, new_dir=0x8000 Address 0x8000 out of bounds, cd_type=cd_parse_command) at main.c:630 #9 0x0041f07a in regex_command (filename=0x0, action=0x47d8fb Open, move_dir=0x0) at ext.c:262 #10 0x0043a0c0 in do_enter (panel=0x488da6) at screen.c:1942 #11 0x0043a924 in panel_callback (panel=0x5d86a0, msg=WIDGET_DESTROY, parm=0) at screen.c:2137 #12 0x0041be9e in dlg_process_event (h=0x5d8540, key=10, event=0x0) at dialog.c:651 #13 0x0041c202 in run_dlg (h=0x5d8540) at dialog.c:777 #14 0x00431612 in main (argc=0, argv=0x0) at main.c:1674 I wasn't even testing mc. I just tried to use it. - I'm using mc-4.6.1-current and mc-4.6.1-preX very long time. Without problem. -- Best regards, Pavelmailto:[EMAIL PROTECTED] ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
