LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 02-28-2011, 06:52 AM   #1
kjhambrick
Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware-64 -current
Posts: 57

Rep: Reputation: 25
compat32pkg - .conf.new Warnings ?


Sebastian --

First of all, thanks a $Million for compat32pkg !

It's a beauty.

I am just now doing the 'final' few tweeks on my new x86_64 Laptop running multilib-enabled Slackware Current and as part of the process, I installed compat32pkg and ran:

Code:
[root@kjhlt5 compat32pkg]# compat32pkg -l all

compat32pkg ver. 1.2.110112 (stable)

(WARNING) The system on the mirror /dld/slackware/slackware-current-32 is a          
(WARNING) development version (ie current) of Slackware.

(WARNING) The Packages to format compat32 built from packages on this mirror
(WARNING) should not be installed onto the local system unless this one follows
(WARNING) the development branch of Slackware.

[--list-updates] Started on Mon 28 Feb 2011 05:05:12 AM CST     
[--list-updates]   Using mirror /dld/slackware/slackware-current-32
[--list-updates]   Local system is Slackware/x86_64 version 13.1.0
[--list-updates]   Mirrored system is Slackware/i486 version current
[--list-updates]   Slackware-32 packages will be stored into /var/cache/compat32pkg/slackware-32
[--list-updates]   compat32 packages will be stored into /var/cache/compat32pkg/compat-32
                                                                            
[--list-updates]   3 update(s) were found (0,105 sec.)

[ package-basename                 ] [ installed version                ]           [ update version                 ]
  glib2                                2.26.1 build 2                       ->       2.28.1 build 1                  
  gtk+2                                2.22.1 build 3                       ->       2.24.1 build 1                  
  seamonkey-solibs                     2.1b1 build 3                        ->       2.1b2 build 1                   

[--list-updates] Ended on Mon 28 Feb 2011 05:05:12 AM CST
Woo Hoo ! Awesome !

Next, to test compat32pkg, I ran:

Code:
cmpat32pkg -c 'list:glib2,gtk+2,seamonkey-solibs'
The compat32pkg script seemed to do the 'right thing', placing the three Slackware Packages in the /var/cache/compat32pkg/compat-32/ directory as it was configured to do:

Code:
[root@kjhlt5 multilib]# ls -la /var/cache/compat32pkg/compat-32/*
-rw-r--r-- 1 root root  791308 Feb 28 05:13 /var/cache/compat32pkg/compat-32/glib2-compat32-2.28.1-x86_64-1.txz
-rw-r--r-- 1 root root 1673364 Feb 28 05:13 /var/cache/compat32pkg/compat-32/gtk+2-compat32-2.24.1-x86_64-1.txz
-rw-r--r-- 1 root root 1935036 Feb 28 05:13 /var/cache/compat32pkg/compat-32/seamonkey-solibs-compat32-2.1b2-x86_64-1.txz
Finally, I upgraded the three packages using the standard Slackware upgradepkg and finally I get to the point !

Note the warnings about 'etc/gtk-2.0/i486-slackware-linux/im-multipress.conf.new' ...

Did I do something wrong ?

Is there a missing file in the SlackPkg ?

Thanks again !

-- kjh

Code:
[root@kjhlt5 multilib]# upgradepkg /var/cache/compat32pkg/compat-32/glib2-compat32-2.28.1-x86_64-1.txz /var/cache/compat32pkg/compat-32/gtk+2-compat32-2.24.1-x86_64-1.txz /var/cache/compat32pkg/compat-32/seamonkey-solibs-compat32-2.1b2-x86_64-1.txz

+==============================================================================
| Upgrading glib2-compat32-2.26.1-x86_64-2 package using /var/cache/compat32pkg/compat-32/glib2-compat32-2.28.1-x86_64-1.txz
+==============================================================================

Pre-installing package glib2-compat32-2.28.1-x86_64-1...

Removing package /var/log/packages/glib2-compat32-2.26.1-x86_64-2-upgraded-2011-02-28,06:11:57...
  --> Deleting /usr/doc/glib-2.26.1/AUTHORS
  --> Deleting /usr/doc/glib-2.26.1/COPYING
  --> Deleting /usr/lib/libgio-2.0.so.0.2600.1
  --> Deleting empty directory /usr/doc/glib-2.26.1/

Verifying package glib2-compat32-2.28.1-x86_64-1.txz.
Installing package glib2-compat32-2.28.1-x86_64-1.txz:
PACKAGE DESCRIPTION:
# glib2-compat32 (library of C routines)
#
# GLib is a library which includes support routines for C such as lists,
# trees, hashes, memory allocation, and many other things.
#
# This package contains 32-bit compatibility binaries.
Executing install script for glib2-compat32-2.28.1-x86_64-1.txz.
Package glib2-compat32-2.28.1-x86_64-1.txz installed.

Package glib2-compat32-2.26.1-x86_64-2 upgraded with new package /var/cache/compat32pkg/compat-32/glib2-compat32-2.28.1-x86_64-1.txz.

+==============================================================================
| Upgrading gtk+2-compat32-2.22.1-x86_64-3 package using /var/cache/compat32pkg/compat-32/gtk+2-compat32-2.24.1-x86_64-1.txz
+==============================================================================

Pre-installing package gtk+2-compat32-2.24.1-x86_64-1...
mv: cannot stat `etc/gtk-2.0/i486-slackware-linux/im-multipress.conf.new': No such file or directory

Removing package /var/log/packages/gtk+2-compat32-2.22.1-x86_64-3-upgraded-2011-02-28,06:11:59...
  --> Deleting /usr/doc/gtk+-2.22.1/AUTHORS
  --> Deleting /usr/doc/gtk+-2.22.1/COPYING
  --> Deleting /usr/lib/libgdk-x11-2.0.so.0.2200.1
  --> Deleting /usr/lib/libgtk-x11-2.0.so.0.2200.1
  --> Deleting empty directory /usr/doc/gtk+-2.22.1/

Verifying package gtk+2-compat32-2.24.1-x86_64-1.txz.
Installing package gtk+2-compat32-2.24.1-x86_64-1.txz:
PACKAGE DESCRIPTION:
# GTK+ version 2 (multi-platform GUI toolkit)
#
# This is GTK+, a multi-platform toolkit for creating graphical user
# interfaces.  Offering a complete set of widgets, GTK+ is suitable for
# projects ranging from small one-off projects to complete application
# suites.
#
# This package contains 32-bit compatibility binaries.
Executing install script for gtk+2-compat32-2.24.1-x86_64-1.txz.
mv: cannot stat `etc/gtk-2.0/i486-slackware-linux/im-multipress.conf.new': No such file or directory
Package gtk+2-compat32-2.24.1-x86_64-1.txz installed.

Package gtk+2-compat32-2.22.1-x86_64-3 upgraded with new package /var/cache/compat32pkg/compat-32/gtk+2-compat32-2.24.1-x86_64-1.txz.

+==============================================================================
| Upgrading seamonkey-solibs-compat32-2.1b1-x86_64-3 package using /var/cache/compat32pkg/compat-32/seamonkey-solibs-compat32-2.1b2-x86_64-1.txz
+==============================================================================

Pre-installing package seamonkey-solibs-compat32-2.1b2-x86_64-1...

Removing package /var/log/packages/seamonkey-solibs-compat32-2.1b1-x86_64-3-upgraded-2011-02-28,06:12:02...
  --> Deleting /usr/doc/seamonkey-2.1b1/LICENSE
  --> Deleting /usr/lib/seamonkey-2.1b1/libfreebl3.chk
  --> Deleting /usr/lib/seamonkey-2.1b1/libfreebl3.so
  --> Deleting /usr/lib/seamonkey-2.1b1/libmozjs.so
  --> Deleting /usr/lib/seamonkey-2.1b1/libmozsqlite3.so
  --> Deleting /usr/lib/seamonkey-2.1b1/libnspr4.so
  --> Deleting /usr/lib/seamonkey-2.1b1/libnss3.so
  --> Deleting /usr/lib/seamonkey-2.1b1/libnssckbi.so
  --> Deleting /usr/lib/seamonkey-2.1b1/libnssdbm3.chk
  --> Deleting /usr/lib/seamonkey-2.1b1/libnssdbm3.so
  --> Deleting /usr/lib/seamonkey-2.1b1/libnssutil3.so
  --> Deleting /usr/lib/seamonkey-2.1b1/libplc4.so
  --> Deleting /usr/lib/seamonkey-2.1b1/libplds4.so
  --> Deleting /usr/lib/seamonkey-2.1b1/libsmime3.so
  --> Deleting /usr/lib/seamonkey-2.1b1/libsoftokn3.chk
  --> Deleting /usr/lib/seamonkey-2.1b1/libsoftokn3.so
  --> Deleting /usr/lib/seamonkey-2.1b1/libssl3.so
  --> Deleting empty directory /usr/lib/seamonkey-2.1b1/
  --> Deleting empty directory /usr/doc/seamonkey-2.1b1/

Verifying package seamonkey-solibs-compat32-2.1b2-x86_64-1.txz.
Installing package seamonkey-solibs-compat32-2.1b2-x86_64-1.txz:
PACKAGE DESCRIPTION:
# seamonkey-solibs-compat32 (Shared libraries from Seamonkey)
#
# This package contains a subset of the shared libraries from Seamonkey
# to provide runtime support for programs that require nss, nspr, and
# js.  These libraries are used in programs like RPM and gxine, and can
# be used in others.  This package is built from the Seamonkey sources
# and is provided as a standalone runtime package for people who do not
# want to install the entire seamonkey package (as for server use).
#
# This package is runtime only.  The include files and other files for
# development can be found in the seamonkey package.
Executing install script for seamonkey-solibs-compat32-2.1b2-x86_64-1.txz.
Package seamonkey-solibs-compat32-2.1b2-x86_64-1.txz installed.

Package seamonkey-solibs-compat32-2.1b1-x86_64-3 upgraded with new package /var/cache/compat32pkg/compat-32/seamonkey-solibs-compat32-2.1b2-x86_64-1.txz.
 
Old 03-01-2011, 04:11 AM   #2
phenixia2003
Member
 
Registered: May 2006
Location: France
Distribution: Slackware
Posts: 284

Rep: Reputation: 162Reputation: 162
Hello,

Quote:
Originally Posted by kjhambrick View Post

First of all, thanks a $Million for compat32pkg !

It's a beauty.


Quote:
Originally Posted by kjhambrick View Post
I am just now doing the 'final' few tweeks on my new x86_64 Laptop running multilib-enabled Slackware Current and as part of the process, I installed compat32pkg and ran:

Code:
[root@kjhlt5 compat32pkg]# compat32pkg -l all

[...]
Woo Hoo ! Awesome !

Next, to test compat32pkg, I ran:

Code:
cmpat32pkg -c 'list:glib2,gtk+2,seamonkey-solibs'
The compat32pkg script seemed to do the 'right thing', placing the three Slackware Packages in the /var/cache/compat32pkg/compat-32/ directory as it was configured to do:

[...]

Finally, I upgraded the three packages using the standard Slackware upgradepkg and finally I get to the point !

Note the warnings about 'etc/gtk-2.0/i486-slackware-linux/im-multipress.conf.new' ...

[...]
Code:
Pre-installing package gtk+2-compat32-2.24.1-x86_64-1...
mv: cannot stat `etc/gtk-2.0/i486-slackware-linux/im-multipress.conf.new': No such file or directory
[...]

Did I do something wrong ?
Is there a missing file in the SlackPkg ?
After looking at this, what you are pointing out is not related to compat32pkg but to convertpkg-compat32
which adds the code below at the end of the file doinst.sh that comes with gtk+2-compat32:

AlienBob script convertpkg-compat32 (-current snippet) :
Code:
...
if [ "$PKGNAM" = "gtk+2" ]; then
    # Deal with the .new file in gtk+2 that does not get processed:
    echo "config etc/gtk-2.0/i486-slackware-linux/im-multipress.conf.new" \
      >> install/doinst.sh
...
fi
In fact, gkt+2 for 13.0 and 13.1 comes with a file im-multipress.conf per architecture. This is
not the case anymore in gtk+2 for -current which comes with a single file im-multipress.conf
in etc/gtk-2.0 :

gtk+2 slackbuild for 13.1 (snippet) :
Code:
...
mv $PKG/etc/gtk-2.0/$host/im-multipress.conf $PKG/etc/gtk-2.0/$host/im-multipress.conf.new || exit 1
...
gtk+2 slackbuild for -current (snippet) :
Code:
...
# Don't clobber im-multipress.conf
mv $PKG/etc/gtk-2.0/im-multipress.conf $PKG/etc/gtk-2.0/im-multipress.conf.new || exit 1
...
As you have upgraded to -current, you certainly have a valid im-multipress.conf in etc/gtk-2.0 (the
one that comes with 64-bit version of gtk+2), therefore, you can simply ignore the warnings about
'etc/gtk-2.0/i486-slackware-linux/im-multipress.conf.new'. Moreover, I guess that, for compatibilities
reasons, AlienBob will leave how the package gtk+2 is processed by convertpkg-compat32.


Cheers.

--
SeB
 
1 members found this post helpful.
Old 03-02-2011, 04:18 AM   #3
kjhambrick
Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware-64 -current
Posts: 57

Original Poster
Rep: Reputation: 25
Quote:
Originally Posted by phenixia2003 View Post
Hello,

gtk+2 slackbuild for -current (snippet) :
Code:
...
# Don't clobber im-multipress.conf
mv $PKG/etc/gtk-2.0/im-multipress.conf $PKG/etc/gtk-2.0/im-multipress.conf.new || exit 1
...
As you have upgraded to -current, you certainly have a valid im-multipress.conf in etc/gtk-2.0 (the
one that comes with 64-bit version of gtk+2), therefore, you can simply ignore the warnings about
'etc/gtk-2.0/i486-slackware-linux/im-multipress.conf.new'. Moreover, I guess that, for compatibilities
reasons, AlienBob will leave how the package gtk+2 is processed by convertpkg-compat32.


Cheers.

--
SeB
Thanks again Sebastian !

The 64bit.conf vs MultiLib .conf explanation makes sense.

-- kjh
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[ANN] compat32pkg 1.2.110112 phenixia2003 Slackware 6 02-25-2011 04:31 AM
First release of compat32pkg. A simple tool for managing package to format compat32.. phenixia2003 Slackware 12 09-24-2010 07:02 AM
ld : warnings and errors rajesh_b Programming 2 01-22-2007 07:50 AM
c warnings kpachopoulos Programming 1 08-25-2006 06:45 AM
rootkit warnings - they serious? jayeola Linux - Security 5 05-06-2006 12:31 PM


All times are GMT -5. The time now is 02:49 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration