LinuxQuestions.org
Share your knowledge at the LQ Wiki.
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 05-15-2018, 01:08 PM   #31
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1 on Lenovo Thinkpad W520
Posts: 8,418

Rep: Reputation: 3179Reputation: 3179Reputation: 3179Reputation: 3179Reputation: 3179Reputation: 3179Reputation: 3179Reputation: 3179Reputation: 3179Reputation: 3179Reputation: 3179

Quote:
Originally Posted by BW-userx View Post
so you're saying it is safe to remove the one version and leave the other?
Yes, if only the package's full name differ betwen the two but they have exactly the same content.

Of course if their content differ and you mistakenly used installpkg instead of upgradepkg (although you really intended to upgrade), results are generally unpredictable and probably bad: if you write removepkg pkg2, files will remain coming from pkg1 (those found in pkg1 but not pkg2) and from pkg2 (those bearing the same name in pkg1 and pkg2).

Then what you need to do is remove both packages and install anew the one you want.
 
1 members found this post helpful.
Old 05-15-2018, 01:25 PM   #32
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: MID-SOUTH USA
Distribution: Slackware 14.2 / Slackware 14.2 current / Manjaro
Posts: 6,447

Rep: Reputation: 1293Reputation: 1293Reputation: 1293Reputation: 1293Reputation: 1293Reputation: 1293Reputation: 1293Reputation: 1293Reputation: 1293
Quote:
Originally Posted by Didier Spaier View Post
Yes, if only the package's full name differ betwen the two but they have exactly the same content.

Of course if their content differ and you mistakenly used installpkg instead of upgradepkg (although you really intended to upgrade), results are generally unpredictable and probably bad: if you write removepkg pkg2, files will remain coming from pkg1 (those found in pkg1 but not pkg2) and from pkg2 (those bearing the same name in pkg1 and pkg2).

Then what you need to do is remove both packages and install anew the one you want.
see, what I do when shown dups, I use the whole name to insure the system knows exactly what I am talking out. (so at least someone understands me not pointing at you.)

so I got this vlc now in current with dups ( on purpose of course )

Code:
> # ls /var/log/packages | grep libinput
> libinput-1.10.6-x86_64-1
> libinput-1.5.4-x86_64-1alien
> xf86-input-libinput-0.27.1-x86_64-3
I am removing alien because I already know that they system has its own to use for vlc.
Code:
> # vlc
> VLC media player 3.0.0 Vetinari (revision 3.0.0-30-gef4c265336)
> Segmentation fault
that is where I am at right now with vlc.

Code:
> root@slackcurr.ent.org:~
> # removepkg libinput-1.5.4-x86_64-1alien
> 
> Removing package /var/log/packages/libinput-1.5.4-x86_64-1alien...
> Removing files:
>   --> /usr/lib64/libinput.so (symlink) was found in another package. Skipping.
>   --> /usr/lib64/libinput.so.10 (symlink) was found in another package. Skipping.
>   --> /lib/udev/hwdb.d/90-libinput-model-quirks.hwdb was found in another package. Skipping.
>   --> /lib/udev/libinput-device-group was found in another package. Skipping.
>   --> /lib/udev/libinput-model-quirks was found in another package. Skipping.
>   --> /lib/udev/rules.d/80-libinput-device-groups.rules was found in another package. Skipping.
>   --> /lib/udev/rules.d/90-libinput-model-quirks.rules was found in another package. Skipping.
>   --> /usr/bin/libinput-debug-events was found in another package. Skipping.
>   --> /usr/bin/libinput-list-devices was found in another package. Skipping.
>   --> /usr/include/libinput.h was found in another package. Skipping.
>   --> /usr/lib64/pkgconfig/libinput.pc was found in another package. Skipping.
>   --> /usr/man/man1/libinput-debug-events.1.gz was found in another package. Skipping.
>   --> /usr/man/man1/libinput-list-devices.1.gz was found in another package. Skipping.
>   --> Deleting /usr/doc/libinput-1.5.4/COPYING
>   --> Deleting /usr/lib64/libinput.la
>   --> Deleting /usr/lib64/libinput.so.10.10.5
>   --> Deleting empty directory /usr/doc/libinput-1.5.4/
one more to remove, because I added both files that do not need to be there.
Code:
> root@slackcurr.ent.org:~
> # ls /var/log/packages | grep libwacom
> libwacom-0.22-x86_64-1alien
> libwacom-0.29-x86_64-2
OH NO
Code:
> # vlc
> VLC media player 3.0.0 Vetinari (revision 3.0.0-30-gef4c265336)
> Segmentation fault
damage control mode. I got it under control... just give me a minute or two... I might need to reboot, I am in the process of compiling and installing items at the moment. Though killing it will do no harm.


talk about Murphy's Law

back:
I had to install the updated version of vlc...
did the same steps and everything is working, I just removed the second packages ailen's and kept the system packages installed, using the correct version for vlc. no harm it's working. just as I suggested.
Code:
# vlc
VLC media player 3.0.2 Vetinari (revision 3.0.2-2-g34d098f437)
[0000000001ca1ba0] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
[0000000001d95fe0] skins2 interface error: cannot instantiate dialogs provider
[0000000001c7a370] main playlist: playlist is empty
[0000000001d95fe0] [cli] lua interface: Listening on host "*console".
VLC media player 3.0.2 Vetinari
Command Line Interface initialized. Type `help' for help.

Last edited by BW-userx; 05-15-2018 at 01:43 PM.
 
Old 05-16-2018, 09:51 AM   #33
aikempshall
Member
 
Registered: Nov 2003
Location: Bristol, Britain
Distribution: Slackware
Posts: 518

Original Poster
Rep: Reputation: 51
I've gone back to the beginning.

A fresh install of current

Ran

Code:
slackpkg update
slackpkg install-new

It told me that I needed to install some new packages of which wireless_tools was one of them -

so now I have these two packages -


Quote:
wireless-tools-29-x86_64-10
wireless_tools-29-x86_64-12
installed

I will now have to remove the earlier one

Code:
removepkg wireless-tools-29-x86_64-10

In current's changelog it states -
Quote:
n/wireless-tools-29-i486-10.txz: Removed.
n/wireless_tools-29-i586-11.txz: Added.
Renamed package to match upstream tarball name.

A case of check the change log for each new install.

I'm going to raise a separate thread for my observations with installing ktown on top of current.
 
Old 05-17-2018, 02:08 AM   #34
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware
Posts: 789

Rep: Reputation: 289Reputation: 289Reputation: 289
Here is the proper sequence with slackpkg.

# slackpkg update
# slackpkg install-new
# slackpkg upgrade-all
# slackpkg clean-system << this will take care of wireless-tools-29-i486-10.txz
 
1 members found this post helpful.
Old 05-17-2018, 03:21 AM   #35
aikempshall
Member
 
Registered: Nov 2003
Location: Bristol, Britain
Distribution: Slackware
Posts: 518

Original Poster
Rep: Reputation: 51
Quote:
Originally Posted by chrisretusn View Post
Here is the proper sequence with slackpkg.

# slackpkg update
# slackpkg install-new
# slackpkg upgrade-all
# slackpkg clean-system << this will take care of wireless-tools-29-i486-10.txz

Thanks chrisretusn it's beginning to dawn on me what I've been doing wrong! In the case of converting to ktown the sequence I should have followed is

# slackpkg update
# slackpkg install-new
# slackpkg upgrade-all
# slackpkg clean-system
# slackpkg remove kde



whereas what I did was

# slackpkg update
# slackpkg remove kde

Having followed this incorrect procedure my physical system looked nothing like what slackpkg was expecting when I did the "slackpkg remove kde"
 
Old 05-21-2018, 12:49 AM   #36
aikempshall
Member
 
Registered: Nov 2003
Location: Bristol, Britain
Distribution: Slackware
Posts: 518

Original Poster
Rep: Reputation: 51
I've now tried

Code:
# slackpkg update
# slackpkg install-new
# slackpkg upgrade-all
# slackpkg clean-system
# slackpkg remove kde
Working a expected. Marking this as solved.

Thanks for all your help and encouragement.

Alex
 
1 members found this post helpful.
  


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
[SOLVED] Duplicate packages dr.s Slackware 1 09-27-2015 05:26 PM
[SOLVED] Stale/duplicate packages in 14.1 patches/packages/ GazL Slackware 3 06-17-2015 09:06 AM
Duplicate packages in Aptitude wearetheborg Debian 2 06-02-2007 05:36 PM
Sort installed packages by # of dependant packages installed brianez21 Debian 1 01-18-2006 05:06 PM
Duplicate packages-rpm jerrymei Linux - Software 2 10-07-2005 02:33 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 10:57 AM.

Main Menu
Advertisement
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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration