Skip to main content ↑ ↓
Topic: package converted from deb invalid SOLVED (Read 339 times) previous topic - next topic
0 Members and 4 Guests are viewing this topic.

package converted from deb invalid SOLVED

Wanted to install eterm terminal emulator from deb packages. Libast is a dep, it is in AUR but compiling fails. Installed libast from deb but dep prob as Debian calls it libast2.. Tried to change it to libast in PKGBUILD but got invalid package.
Tempted to just dump the files in right places and see if it works.

Re: package converted from deb invalid

Reply #1 –
Is there a question here? What you should be asking is if what you're doing is a good idea and the answer is "no"

Re: package converted from deb invalid

Reply #2 –
Yeah no biggie. It is just a terminal, can't see that disaster will ensue. Ok, the problem with libast was that I for some reason changed the version number set by the Debian package. Just changing the package name from libast2 to libast in PKGBUILD made the 'dependeny issue' go away. Now the only problem is a syntax error thrown by the eterm package

Quote
/tmp/alpm_5hOV4P/.INSTALL: linje 21: syntaksfeil ved «}», som er et uforventet symbol
/tmp/alpm_5hOV4P/.INSTALL: linje 21: `}'
/usr/bin/bash: linje 1: fant ikke kommando post_install
feil: kommandoen feilet

in English: it can't find command post install  (in line 21)

Not worth wasting time on I guess -- but the enlightenment terminal emulator is mighty cool with the right set of custom backgrounds  ;)

Re: package converted from deb invalid

Reply #3 –
You've lost me a bit here ?
I saw this earlier and had a go at making packages for libast and eterm based on the Aur versions.

In both cases I had to make changes to the source to get them to compile and also I used the debian Eterm patchset as the code seems unmaintained by the original dev's.
I also had to find other copies of the source code as the links in the PKGBUILD's are dead.

Yet you seem to be saying you just built it by just "changing the package name from libast2 to libast in PKGBUILD".
it doesn't make sense ?

Eterm:

Re: package converted from deb invalid

Reply #4 –
Btw the eterm or libast (can't remember exactly now) AUR build fails because the link to the source code is dead due to eterm.org no longer being there. But tinycorelinux.net has both source packages so this could be fixed.

Ok now I have the Eterm terminal trying to start but get the common error

Eterm:  Error:  Unable to load font "-adobe-helvetica-medium-r-normal--10-100-75-75-p-56-iso8859-1".  Falling back on "fixed"
Eterm:  Error:  Unable to load font "-misc-fixed-medium-r-semicondensed--13-*-*-*-c-*-iso10646-1".  Falling back on "k14"
Eterm:  FATAL:  Couldn't load the fallback font either.  Giving up.
 
This is due to missing xorg-fonts package but from what I have seen before installing these on another distro sometimes does not help.
...and as expected installing all available xorg-fonts packages including xorg-fonts-type1 from Arch made no difference. Maybe Debian uses different folders for them

Re: package converted from deb invalid

Reply #5 –
Still confused as to how you built it but never-mind.

You need:
xorg-fonts-misc
xorg-fonts-75dpi

Re: package converted from deb invalid

Reply #6 –
Quote from: gripped – on
You've lost me a bit here ?
I saw this earlier and had a go a making packages for libast and eterm based on the Aur versions.

In both cases I had to make changes to the source to get them to compile and also I used the debian Eterm patchset as the code seems unmaintained by the original dev's.
I also had to find other copies of the source code as the links in the PKGBUILD's are dead.

Yet you seem to be saying you just built it by just "changing the package name from libast2 to libast in PKGBUILD".
it doesn't make sense ?

Eterm:


No. I got conversion of Debian packages using debtap to work, but then got a syntax error installing the eterm package. Then tried just installing the files manually from the deb package, this works in several distros but may give a font error which is hard to fix.
And I have installed these font packages, same error.

Re: package converted from deb invalid

Reply #7 –
Have you restarted X since installing them ?
There's probably a command to refresh the fonts but restarting X was easier than looking.
They won't be found otherwise.

I can write up how to build proper pacman packages but won't waste my time unless you intend to build them?

Re: package converted from deb invalid SOLVED

Reply #8 –
Thank you but I had better look for that documentation myself.
Yes, did restart.