Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

SNAFU w/ installing tarball under MX-16 KDE - SOLVED

Help on MX KDE Re-spins
Message
Author
skidoo
Forum Regular
Forum Regular
Posts: 816
Joined: Tue Sep 22, 2015 6:56 pm

Re: SNAFU w/ installing tarball under MX-16 KDE

#11 Post by skidoo » Mon Jun 05, 2017 2:28 am

Stevo wrote:a few notes:

You should not run any configure step beforehand, as the Debian build process will handle that, and will indeed pass different configure options than the default. (In fact, looking at INSTALL.md, it appears that ne does not use a configure file process at all, so that command will fail)
Oops... and thanks for clarifying that.
The build folder doesn't have to be in /tmp; it can be any folder in your home directory, just as long as there are no whitespaces in the path to that folder.
My rationale for using /tmp has been "tmpfs ~= speedy ramdrive". Maybe that's moot?
With (or without) -rfakeroot option, does dpkg-buildpackage already employ a tmpfs working directory?

User avatar
eemaestro
Forum Guide
Forum Guide
Posts: 1010
Joined: Wed Aug 02, 2006 12:12 pm

Re: SNAFU w/ installing tarball under MX-16 KDE

#12 Post by eemaestro » Mon Jun 05, 2017 11:51 am

I looked for the file control in ne-3.1.0/ but it wasn't there. I tried to build from this untarred tarball subdirectory after installing textinfo with #apt-get install texinfo.
Here's what I got.

Code: Select all

jon@mx1:~/ne-3.1.0$ less INSTALL.md
jon@mx1:~/ne-3.1.0$ make build install
( cd doc; make )
make[1]: Entering directory '/home/george/ne-3.1.0/doc'
texi2dvi  ne.texinfo
You don't have a working TeX binary installed, but the texi2dvi script
can't proceed without it. If you want to use this script, you have to
install some kind of TeX, for example TeX Live Debian packages. You can do
that with this command:
       apt-get install texlive
<builtin>: recipe for target 'ne.dvi' failed
make[1]: *** [ne.dvi] Error 1
make[1]: Leaving directory '/home/jon/ne-3.1.0/doc'
makefile:26: recipe for target 'docs' failed
make: *** [docs] Error 2
jon@mx1:~/ne-3.1.0$ find ./ -name "*control*"
Evidently I need to stop putting the cart before the horse. Where is that control file ?

skidoo
Forum Regular
Forum Regular
Posts: 816
Joined: Tue Sep 22, 2015 6:56 pm

Re: SNAFU w/ installing tarball under MX-16 KDE

#13 Post by skidoo » Mon Jun 05, 2017 12:15 pm

The terminal output you pasted explicitly advises how to proceed:

Code: Select all

 apt-get install texlive
ps:
For any/every package, you will find a control file within the *.debian.tar.bz2 (aka "debian source file")

Image

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 15646
Joined: Fri Dec 15, 2006 8:07 pm

Re: SNAFU w/ installing tarball under MX-16 KDE

#14 Post by Stevo » Mon Jun 05, 2017 1:50 pm

The control file is provided by a Debian packager inside a /debian folder--the upstream source almost always lacks one of these. So you need to be using "debianized" source files, such as you can get from packages.debian.org.

Re location of the build file: I didn't see any speedup when I built a kernel package on an SSD drive vs a rotating drive, so I don't know if a /tmp in RAM would make it any faster. We await your tests! Anyway, some package builds, such as web browsers, kernels, and especially things like llvm and mesa, would end up with /tmp holding many GB, and also require a lot of RAM, so I'd worry about running out of RAM for those. I don't think that would come into play for ne, though.

User avatar
eemaestro
Forum Guide
Forum Guide
Posts: 1010
Joined: Wed Aug 02, 2006 12:12 pm

Re: SNAFU w/ installing tarball under MX-16 KDE

#15 Post by eemaestro » Mon Jun 05, 2017 2:17 pm

Code: Select all

# cd
root@mx1:~# find /home/jon/ -name "*debian.tar.bz2"
root@mx1:~# find /home/jon/ -name "*.tar.bz"       
root@mx1:~# find /home/jon/ -name "*.tar.gz"
.
.
.
/home/jon/Downloads/ne-3.1.0(1).tar.gz
.
.
.
Okay, skidoo, so after finding the control file in texinfo_5.2.0.dfsg.1-6.debian.tar.xz that I downloaded from
https://packages.debian.org/jessie/texinfo, I see that it
specifies the standard debian libraries under Depends:, for example,

Code: Select all

Depends: ${shlibs:Depends}, ${misc:Depends}, libtext-unidecode-perl, libintl-perl, libxml-libxml
I see that three external libraries are needed to link the object code.
I don't know what sets the BASH variables shlibs:Depends and misc:Depends.
I don't know what the Suggests: line means. Nor "Multi-Arch: foreign"

Will my tarball ne-3.1.0(1).tar.gz be good for updating to the 3.X version of ne ?
Or do I need to find a corresponding *.debian.tar.bz2 file in order to ensure that ALL external references are correctly linked during the make install process? I guess I would need to find the *.debian.tar.bz2 file in order to have a control file to read. But I don't know if that's necessary for a system-wide install of ne 3.X.

User avatar
kmathern
Forum Veteran
Forum Veteran
Posts: 9270
Joined: Wed Jul 12, 2006 2:26 pm

Re: SNAFU w/ installing tarball under MX-16 KDE

#16 Post by kmathern » Mon Jun 05, 2017 2:31 pm

...do I need to find a corresponding *.debian.tar.bz2 file ...?
There isn't a corresponding *.debian.tar.bz2 file yet for the 3.1.0 version of ne, the 3.0.1-2 one for Stretch works okay though (see my comment in this post viewtopic.php?p=415376#p415376), I didn't try it but the Jessie 2.5-1 *.debian.tar.bz2 file might even work also.
Last edited by kmathern on Mon Jun 05, 2017 3:43 pm, edited 1 time in total.

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 15646
Joined: Fri Dec 15, 2006 8:07 pm

Re: SNAFU w/ installing tarball under MX-16 KDE

#17 Post by Stevo » Mon Jun 05, 2017 3:21 pm

I built packages of the latest 3.1.1 release of ne. I just adapted the latest debian folder from upstream Debian.

https://drive.google.com/open?id=0BxE7w ... UNTTEJYQjg

eemaestro, we have a guide in the wiki on how to do this, or there's a shorter "cargo cult" guide to backporting in the Debian wiki. They work for many packages in that mode, but many will require some more research into the various versions of libraries and build tools in order to get a successful backport. Ne didn't require anything except following the recipe.

User avatar
eemaestro
Forum Guide
Forum Guide
Posts: 1010
Joined: Wed Aug 02, 2006 12:12 pm

Re: SNAFU w/ installing tarball under MX-16 KDE

#18 Post by eemaestro » Mon Jun 05, 2017 8:18 pm

Okay, Stevo, I got your deb file from that URL and installed it.

Code: Select all

# dpkg -i ../ne-3.1.1/ne_3.1.1-0mx15+1_amd64.deb
(Reading database ... 202706 files and directories currently installed.)
Preparing to unpack .../ne_3.1.1-0mx15+1_amd64.deb ...
Unpacking ne (3.1.1-0mx15+1) over (2.5-1) ...
Setting up ne (3.1.1-0mx15+1) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for menu (2.1.47) ...
root@mx1:/home/george/linux# apt-get install -f
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
Thank you for simplifying my life, Stevo!
Since I don't know the recipe yet, I googled "debian package management primer for C programmers" and found some URLs to brief me on the recipe, how to make the recipe, and how to adapt the recipe to CPU architecture. Some are part of debian.org. I'm starting with such basics as https://www.debian.org/doc/manuals/debi ... cs.en.html
It seems to work so far. In a few days, if all checks out with this version, maybe I'll suggest adding it to the mx16 repo.

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 15646
Joined: Fri Dec 15, 2006 8:07 pm

Re: SNAFU w/ installing tarball under MX-16 KDE

#19 Post by Stevo » Mon Jun 05, 2017 9:16 pm

This is what I meant for a simple guide--it's the first result I searched for "backports debian wiki":

https://wiki.debian.org/Backports

and it had a link to the entry to create your own backports:

https://wiki.debian.org/SimpleBackportCreation

Like I said, it works for many packages without changing any other files. If they fail, often we can tweak them to get them to build, but experience and strong Google-fu help a lot with that. Some require new base packages, so we are just stumped for those ones.

Post Reply

Return to “MX KDE”