When i create a slackware package, with the tool makepkg, the resulting package doesnt show the description of the package in the pkgtool program.
View 2 RepliesA slacky.eu user Spina, I did notice a bug in calculating the size of the package when the directory contains a space in the name. Example:
Code:
/tmp/prova dir# LANG=en installpkg abook-0.6.0pre2-i686-4cf.txz
/bin/du: cannot access `/tmp/prova': No such file or directory
/bin/du: cannot access `dir/abook-0.6.0pre2-i686-4cf.txz': No such file or directory
Verifying package abook-0.6.0pre2-i686-4cf.txz.
Installing package abook-0.6.0pre2-i686-4cf.txz:
PACKAGE DESCRIPTION:
# abook
# Abook is a text-based addressbook program designed to use with mutt
# mail client. Abook runs on Linux, FreeBSD and some other UNIXes.
# Home: [URL]
# Package abook-0.6.0pre2-i686-4cf.txz installed.
This error is caused by 'readlink -f'
COMPRESSED="$(/bin/du -sh $(readlink -f $package) | cut -f 1)"
instead with
Code:
COMPRESSED="$(/bin/du -sh "$(readlink -f $package)" | cut -f 1)"
it's ok
I always have just one issue making a slackware pkg using makepkg the darn install/slack-desc never "shows" and gives the package description when doing installpkg/upgradepkg on the finished package Example A I make a package today from "ranger" cli file manager heres the slack-desc
Code:
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|' on
# the right side marks the last column you can put a character in. You must make
# exactly 11 lines for the formatting to be correct. It's also customary to
# leave one space after the
[Code]...
PACKAGE NAME: tango-icon-theme-extras-0.1.0-noarch-1.txz
PACKAGE LOCATION: ./slackware/l
PACKAGE SIZE (compressed): 64 K
[code]....
What the right place to report errors in package descriptions ? There are more than two dozens categories mentioned on the openSUSE "reporting a bug" web page but none of them seem to fit. The packager of the concerned rpm is bugs.opensuse.org, no email printed out when launching rpm -qpi <package name>.
View 2 Replies View RelatedBack in the days of slow machines, displaying the package description during an install provided for some reading to break up the boredom (if one was inspired to sit there and watch it do the install). Now days, the descriptions just fly by, several a second most of the time (unless doing things manually). Do we really need this anymore? It's unreadable.
I'd rather see a list of packages being installed scroll by, one package name per line (with size info). Even that might get hard to read during the buzz of small packages being installed causing rapid scrolls.
I installed a slackware package using pkgtool.
At the end of the install process I get the following warning: WARNING: Package has not been created with 'makepkg'
It appears that the package was installed if I look at the file system. I see new files/directories from the package. But, when I try to launch the new application from /usr/bin I get this error: No such file or directory
I am a normal user "su -" to root when I did the pkgtool install and when I tried to run the application from /usr/bin.
I can see the binary in /usr/bin with a directory listing with the following permissions. -rwxr-xr-x 1 root root
I see the application as installed in the pkgtool and can un-install it.
why I can not launch the binary in /usr/bin?
I have recently installed the Slack 13.1 x86_64 on my laptop. It works fine! But I have one trouble with it. I cannot run the installpkg and pkgtool with my normal user. It says to me that there is no command found. Is it a problem with the sudoers file or these commands are not really installed? Maybe my path is incomplete?
View 15 Replies View RelatedDisplays ONLY the description text for the RPM package
how can you do it , ive read online that
"# rpm -qi " gets you all the information how can i just get description ?
I was browsing Distrowatch and reading the various distro descriptions. Of course it mentions the text installer (although I really think it can be called graphical, just not X) and the vanilla packages, etc. But then I got to the last paragraph which says:Quote:
While this philosophy of simplicity has its fans, the fact is that in today's world, Slackware Linux is increasingly becoming a "core system" upon which new, custom solutions are built, rather than a complete distribution with a wide variety of supported software. The only exception is the server market, where Slackware remains popular, though even here, the distribution's complex upgrade procedure and lack of officially supported automated tools for security updates makes it increasingly uncompetitive. Slackware's conservative attitude towards the system's base components means that it requires much manual post-installation work before it can be tuned into a modern desktop system.
I know that many of these things are the typical idea of slackware, but I was wondering if other Slackers felt it was a fair assessment. I run current and with slackpkg I don't find upgrading to be difficult in the least and while there is of course some configuration to be done, I don't find it to be particularly heavy. I mean the common extra configuration I can think of is basically alsamixer/alsactl and changing inittab if you want a graphical login. The rest is just customization which I would do with any other distro, I'd just have to use distro-specific tools to do it instead of the vanilla "most of these things will work with most other distro" that Slack uses.
Now to be fair, I'm new to linux (9 months) and started using Slackware with 13 after first using Mandriva and Ubuntu for a few months, so maybe I'm missing some history. But I was wondering if people that actually use Slackware find the quoted bit to be fair.
I have searched all over. I cannot find any info on the description of the Fedora mirror release directory structure and the reason for having a "Fedora" and "Everything" directory? Yes I looked at [URL] I mostly work with the Red Hat 5.x. The Fedora release software is kept on a mirror and the DVD release as, (using i386 release):
[Code]....
I am new to deb package. I have read some docs, but did not know how to specify the destination for to-be-installed files. For example, I want to install under user's home directory. How to specify that?
View 7 Replies View RelatedI've created a guest user in the group "user." I'd like to limit its read access to its own home directory. However, by navigating through File system>home it's able to read my home directory. I was under the impression that users were limited to their own home directories. Am I missing something, or is there a group I can assign this guest to, to limit its read access to its own home directory? I've read about Pessulus (I use Gnome), but that seems to be geared toward limiting access to applications, not directories.
Ideally, I'd like to create a group that cannot navigate through any files except its own home directory. But it seems that if I try to do that, the guest user will not be able to execute any applications. I've read all the posts (and other forums) I could find about creating such a limited account, but the chroot jail is beyond my understanding. I get the feeling that it's geared toward networks.
i have a linux pakages with the name rubygems.1.3.2.tar.gz,i know how to install it, but i dont know where to install means in which directory.
View 6 Replies View Relatedi wanted to know whether the gcc,g++ libraries are pre-installed i slackware 12.1 or not. if not then from where can i download them .how do i install them? how do i install the java jdk package also?
View 1 Replies View RelatedThere is a "standalone seamonkey-solibs package for RPM, gxine, etc". But after recent upgrades in -current, I can't use rpm without full seamonkey package installed. Can someone revise the contents of seamonkey-solibs and add missing files to it?
$ LANG=C rpm -qp --qf %{NAME} opera-11.00-1156.i386.rpm
error: opera-11.00-1156.i386.rpm: Header SHA1 digest: BAD
error: opera-11.00-1156.i386.rpm: not an rpm package (or package manifest)
And `rpm2txz -nd opera-11.00-1156.i386.rpm` doesn't work as expected without seamonkey package installed.
We currently have a NFS shared Directory mounted as read-only on our server.This directory contains multiple sub-directories and files. It being read-only is a equirement. Now, we need a directory underneath to be read-write. Is there a graceful way to make that happen? Like a special mount option to use? Basically objective is: /u01 is mounted as read-only and has 3 directories: dir1, dir2, dir3 dir3 has 2 sub-directories- sub1,sub2/u01/dir3/sub2 needs to be read-write, while all other are read-only.
View 2 Replies View RelatedI am trying to install the nvidia-drivers from Slackbuilds.org. When I try to run the SlackBuild, I get the following error:
Code:
install: cannot stat `cuda.h': No such file or directory
What am I missing?
The nvidia-kernel SlackBuild ran fine and created the kernel package.
Im trying to install topolight in my slackare 13 virtual box, I downloaded the tar file and when I try and decompress it doesnt decompress root@me:/home/Italy# tar -xzf typolight-2.8.3.tar.gz and how do I get to my toplolight root directory than.
View 2 Replies View RelatedIn light of my previous achievement in wireless networking, I've decided to create a larger issue for myself to solve. Which hopefully I can get some help with. Because my system is totally kisspoped up, for those of you who get what that means. I was trying to install GRUB via the .txz package and it created a mirrored image of the /boot folder. Which for some reason contained the / folder. Which in turn held /boot and all the other folders / is expected to contain.
Now, trying to remove the extra /boot folder proved difficult, but once I finally was able to figure it out, I remembered I could removepkg and that would probably mend the situation. However, I was already 20-something percent through moving the files to trash. Now when I checked /, /boot was gone from there. Along with various other folders. SO! Apparently the /tmp/boot folder created was in reality the /boot folder, albeit in the wrong place and having the wrong contents. Somehow, one folder existed as two different versions of itself at the same point in time. Much as a Time Lord might. Deleting one made the other vanish with it.
Good news:I removed it via Thunar and it should be in the root user's trash /home and some other folders had yet to be trashed when I hit cancel, so I can still use some things Bad news:I never ran X as root, so I don't know if it HAS a trash folder I can only use things already started up because the binaries are gone, but the configuration files in /home are still there (although /usr/bin remains)
Ideally, there would be a big UNDO button somewhere in this long row of function keys. Reasonably, there should be some kind of restoration tool. Realistically, I think I'm going to have to reinstall the system, which wasn't easy in the first place due to my faulty disc bay which detects discs at will.
Want to remove programs with no explanations on how to use so used pkgtool to remove gxine, xine, and xmms.
When I try to remove juK or Dragon Player, they do not show up in pkgtool list. Dragon Player will not now run from the multimedia list and JuK can't run after starting because it is missing files which were removed by pkgtool above. How do I now go about finding and removing these last two?
I'm not entirely sure how to describe this. I've got a user account set up and I've downloaded a few programs I'd like to install. When I'm in my account, I go to the terminal and type then get;
$ pkgtool
bash: pkgtool: command not found
However, if I'm in root and do the same thing, it brings up the menu. What do I have to do to get pkgtool to work from my user account?
I am trying to install tilp, a program for the link between a computer and a Texas Instruments calculator. I have downloaded all the packages to a local directory. I tried telling yum to install all the packages at the same time, though, the dependencies still fail to resolve (though they are all in the directory). I don't know if it would be safe to force install without the dependencies (even though I would install them later).
View 4 Replies View RelatedWe are pleased to present one of our new creations: pkgbuild, a tool written in standard C++, using libCURL, ZLib, BZip2 and libLZMA (part of XZ). It is a modern Slackware packages builder, network-transparent, multi-architecture, designed to greatly simplify the creation of a package, automatically executing the required post processing.
What does it do? Recognize and build packages for the following architectures: i386, i486, i586, i686, x86_64, IA64, IA32e, s390, s390x, sparc and sparc64.
[Code]...
I came from the Debian world so I did not do much building software from source. I successfully built wine from source, now the wine binary is in the same directory where the Makefile and all of the other source stuff is. I can run wine from that directory fine, but I sort of want to move it somewhere else. I tried moving the wine binary somewhere else, but when I try to run it I get
[code]...
What all do I have to move into the new directory to get wine working in the new directory? By convention, where should I move wine, I want it available for all users, should I move it to /opt/wine, or /usr/local/wine, or somewhere else?
I downloaded from http://ftp.nluug.nl/os/Linux/distr/s...ce/n/net-snmp/ source and I build new package and works ok no errors. If I change net-snmp.SlackBuild and add CFLAGS --with-mib-modules=ucd-snmp/lmSensors --with-ldflags=-lsensors while I need lmsensors support in net-snmp. But the package compiling ends with error:
[Code]...
I am very happy to announce that today I succeeded to install full Slackware ARM on the pandaboard: URL...I did the following:
* sd with 2 partitions, one (vfat) for bootloaders (MLO, u-boot.bin) and uImage and the other one (ext2) for minirootfs
* copy xloader (MLO), uboot and uImage from Angstrom distro on the first partition
* copy Slackware ARM minirootfs on the second partition with Angstrom modules in the usual path (/lib/modules/...)
* boot in ARMedslack
* install all the others packages via NFS
I had to make some changes to configuration files as indicated here:URL...The next step is to build a kernel and modules for omap4 by myself and use them instead of the Angstrom ones.One question: is there any kind of package manager, such as slap-get, sbopkg, etc. for Slackware ARM? If not, can I use the SlackBuilds from slackbuilds.org? How to modify them?
Anybody know of a slackware package for the Iced Tea Java thing? I have the rpm (I have fedora anyhow) but I would like a slackpkg to cstick in here.
View 8 Replies View RelatedWhile installing OpenSUSE 11.2 on system with videocard with VGA/DVI outs in most cases work only DVI out. VGA out not work. Need choise what VGA or DVI out must work while installing the system.
I tried to create future request, but a have trouble with that again
At url After describing the problem (entering description) and doing request. Site give me an error "Please enter a description"
When I update my system by KpackageKit I have the ability to read what was fixed by that package update by clicking on package's name. How to read this info in command line by yum?
View 4 Replies View Related