Hardcoded FISH scripts do not work properly

[gms]

It is not possible to enter any remote diectory except "/" and view any file.

[andrew_b]

Telepathy module is totally broken.

What are you doing? What system are you using?

[gotar]

Probably he didn't install separated #2242 files or took some broken distro package. Anyway contrib/dist/redhat/mc.spec.in doesn't seem to include them too.

[andrew_b]

Hm.. rpmbuild show a message about unpacked files in $BUILDROOT. Package builder should look to that messages.

[andrew_b]

But anyway. mc.spec.in must be fixed.

[zaytsev]

After the buildbot was destroyed the SPEC is no longer kept current. I have finally created a new KVM host for restoring the buildbot, but I don't have time to setup mock and the whole thing. I hope to get to it sooner or later. Maybe in a few weeks.

[gms]

Replying to andrew_b:

Telepathy module is totally broken.

What are you doing? What system are you using?

I'm using Debian.
In mc 4.7.3 FISH works well, configure options were the same.

[zaytsev]

You are kidding??? Where is mc -V ? Which configure options?

[zaytsev]

aptitude show mc

[gms]

Replying to zaytsev:

You are kidding??? Where is mc -V ? Which configure options?

LANG=C ./mc -V
GNU Midnight Commander 4.7.4
Virtual File Systems: cpiofs, tarfs, sfs, extfs, ftpfs, fish
With builtin Editor
Using system-installed S-Lang library with terminfo database
With subshell support as default
With support for background operations
With mouse support on xterm
With internationalization support
With multiple codepages support
Data types: char: 8; int: 32; long: 32; void *: 32; size_t: 32; off_t: 64;

LANG=C mc -V
GNU Midnight Commander 4.7.3
Virtual File Systems: tarfs, extfs, cpiofs, ftpfs, fish
With builtin Editor
Using system-installed S-Lang library with terminfo database
With subshell support as default
With support for background operations
With mouse support on xterm
With internationalization support
With multiple codepages support
Data types: char: 8; int: 32; long: 32; void *: 32; size_t: 32; off_t: 64;

[zaytsev]

Where did you get it? Compiled from source? How did you install it? Are the FISH scripts in place?

[gms]

Hmm... this bug occurs only when create a debian package (but all the files are in place).
Thanks 2 all!

[zaytsev]

How did you create a package? How do you know they are in place?

P.S. This ticket is a nice provocation to get rid of hardcoded FISH scripts since they don't seem to work anyway! :-)

[andrew_b]

Replying to zaytsev:

P.S. This ticket is a nice provocation to get rid of hardcoded FISH scripts since they don't seem to work anyway! :-)

Generally they work but some bugs are present. :)

[gms]

Replying to zaytsev:

How did you create a package? How do you know they are in place?

P.S. This ticket is a nice provocation to get rid of hardcoded FISH scripts since they don't seem to work anyway! :-)

When i do

#./configure --prefix=/usr --sysconfdir=/etc --libexecdir=/usr/lib;make;make install

anything works,but when i build deb with debian files from ​ftp://ftp.debian.org/debian/pool/main/m/mc/mc_4.7.0.9-1.debian.tar.gz

#fakeroot debian/rules binary
#dpkg -i mc_4.7.4-1_i386.deb

FISH becobes broken.
PS: other VFS's still work fine

[angel_il]

Branch: 2347_fish_fix
changeset: f6309b162ea464c7cd3ce0f2903871065f8734e9

[zaytsev]

Of course if you build a package for 4.7.4 from my sources for 4.7.0.9 FISH scripts are not going to be installed where they belong. What else did you expect??? New FISH is not backported yet to the stable branch.

What I find annoying is that instead of providing all the details at once, we have to fish them out of you one by one.