installpkg messing up perms
in [Slackware]
|
From: Helmut Hullen on 13 Jul 2010 09:15 Hallo, Dario, Du meintest am 07.07.10: > Lately, `installpkg` seems to be messing up permissions on system > directories here: the latest incident being '/' set to 700 after > installing a slackbuild. What do you mean with "installing a slackbuild"? Have you built a package ("binary") with the help of a "<packet>.SlackBuild" script an then installed this packet? If yes: which packet? Which SlackBuild script? Viele Gruesse Helmut "Ubuntu" - an African word, meaning "Slackware is too hard for me".
From: Dario Niedermann on 13 Jul 2010 09:25 Grant <omg(a)grrr.id.au> wrote: > SlackBuilds do not carry packages last I looked. A SlackBuild script > allows you to make a package [...] Lest the obvious remain unstated. > Me? I prefer to build from source, and install extras to the > /usr/local tree, but each to 'is own ;) I too do that, for stuff I can't find at slackbuilds.org. -- > head -n1 /etc/*-{version,release} && uname -moprs Slackware 12.2.0 Linux 2.6.27.7-crrm i686 AMD Turion(tm) 64 Mobile Technology MK-36 GNU/Linux
From: Dario Niedermann on 13 Jul 2010 09:36 Helmut Hullen <Helmut(a)Hullen.de> wrote: > What do you mean with "installing a slackbuild"? Have you built a > package ("binary") with the help of a "<packet>.SlackBuild" script an > then installed this packet? Yep. > If yes: which packet? Which SlackBuild script? It happened several times, most recently with 'cmus': http://slackbuilds.org/repository/12.2/audio/cmus/ and others I can't recall, since I didn't think/know at the time that the issue was related to installpkg. -- > head -n1 /etc/*-{version,release} && uname -moprs Slackware 12.2.0 Linux 2.6.27.7-crrm i686 AMD Turion(tm) 64 Mobile Technology MK-36 GNU/Linux
From: Helmut Hullen on 13 Jul 2010 10:00 Hallo, Dario, Du meintest am 13.07.10: >> Me? I prefer to build from source, and install extras to the >> /usr/local tree, but each to 'is own ;) > I too do that, for stuff I can't find at slackbuilds.org. On "slackbuilds.org" you can't find binaries, you only can find scripts to make binaries from source. Viele Gruesse Helmut "Ubuntu" - an African word, meaning "Slackware is too hard for me".
From: Helmut Hullen on 13 Jul 2010 10:33
Hallo, Dario, Du meintest am 13.07.10: >> What do you mean with "installing a slackbuild"? Have you built a >> package ("binary") with the help of a "<packet>.SlackBuild" script >> an then installed this packet? > Yep. >> If yes: which packet? Which SlackBuild script? > It happened several times, most recently with 'cmus': > http://slackbuilds.org/repository/12.2/audio/cmus/ > and others I can't recall, since I didn't think/know at the time that > the issue was related to installpkg. Strange. I've just downloaded the cmus source packet (2.2.0) from cmus.sf.net, the SlackBuild packet from slackbuilds.org, put them into a subdirectory, unpacked the SBo packet, changed the name of the source packet in the Build script and started it. It run without any error message, it made the cmus slackware tarball, it didn't install it. All worked fine. The tarball has no "/etc" directory, no files in this directory. It has no "/install/doinst.sh" script. All files and directories belong to "root:root" - that's all ok. If I would run cd / installpkg /path/to/cmus-v2.2.0*.txz nothing bad would happen. --------------------------------------------------------------- When I ask "http://slackfind.net" for "cmus" I find some binaries, version 2.2.0 and 2.3.2 Have you perhaps tried one of these binaries? Viele Gruesse Helmut "Ubuntu" - an African word, meaning "Slackware is too hard for me". |