LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
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-09-2005, 08:28 PM   #61
nirav_patel
LQ Newbie
 
Registered: Jan 2005
Posts: 11

Rep: Reputation: 0

How do I set proxy for swaret?
I tried setting env var but it failed. I also need to auhtenticate with proxy (squid)
 
Old 05-10-2005, 08:45 PM   #62
nirav_patel
LQ Newbie
 
Registered: Jan 2005
Posts: 11

Rep: Reputation: 0
Hi All,
How to config swaret to use proxy[authentication]?
 
Old 05-11-2005, 09:23 AM   #63
JockVSJock
Member
 
Registered: Jan 2004
Posts: 602

Rep: Reputation: 31
Quote:
Originally posted by Xian


These same people:
1. Do not read the changelogs.
2. Do not bother looking at their config files.


Now, if you are running Slack and are unwilling to do just those two very simple things, then I'm sorry but to be honest you really don't need to be trying to update your installation, or even running Slack at all. There really is no application at your disposal which will save you from yourself. These individuals are not wanting to spend the five minuets it takes to do just the basics of managing their system, but yet will get angry when they have to spend a few hours getting everything back in place after a botched upgrade session.

And then after all this they tend to not even blame the person which really did the damage, which is themselves, but instead want to gripe about an application that they used improperly and with outright ignorance.
Running Slackware since 2003 when RH went to Enterprise, and using Swaret since then to maintain packages.

I haven't had any problems yet, other then the apache thing I've posted. But what you write bothers me, cause I really don't know how to read the changelogs, or do I ever look at the config files.

Could you post an example of this?

thanks
 
Old 05-11-2005, 09:32 AM   #64
keefaz
Senior Member
 
Registered: Mar 2004
Distribution: Slackware
Posts: 4,445

Rep: Reputation: 94
JockVSJock, read the Changelog after you do a swaret --update
Code:
most /var/swaret/.cache/ChangeLog.txt
For config file, that depend on the package you install/upgrade, but
you could try as root :
Code:
updatedb
locate .new
That should show you the new configuration files installed
(updatedb will surelly take some time, it is normal)
 
Old 05-27-2005, 06:19 PM   #65
gargamel
Senior Member
 
Registered: May 2003
Distribution: Slackware, SLAX, OpenSuSE
Posts: 1,599

Rep: Reputation: 142Reputation: 142
Quote:
Originally posted by SiegeX
Ask and ye shall receive! As promised I worked hand-in-hand with the author of slapt-get to be able to bring this functionality to you that
uses the existing framework with little to no modifications. Luckilly I was able to come up with a solution that only required a very minor change
to slapt-get which is introduced in the now-released 0.9.9i version.
n of slapt-get availible HERE [*]Remove ALL non-official SOURCE lines from your slapt-getrc[*]Create a file called unofficialrc in the same directory as your slapt-getrc file[*]Add all the unofficial SOURCE lines to this new unofficialrc file[*]Make the EXCLUDE line in your unofficialrc look like the following --> EXCLUDE=/slackware/[a-z]+[/list=1]

If you want to upgrade official packages with only official sources you need only run the following code
Code:
slapt-get --update && slapt-get --upgrade
Now for the new feature, if you want to upgrade ONLY unofficial packages with unofficial sources then run the following code
Code:
slapt-get --update --config unofficialrc && slapt-get --upgrade --config unofficialrc
[...]


Now how does it work you ask? The question at hand was how do we know if the package is official or not without having to download
huge manifest files and parsing those. This actually took a bit of thinking but the solution turned out to be very simple. While browsing
through the /var/log/packages/ directory I noticed that every official package had the text slackware followed by the
two-letter diskset abbreviation in the Package Location line (this is what the regex /slackware/[a-z]+ does). All that
Jason (slapt-get author) had to do was tell slapt-get to add this to its list of lines to exclude on. Enjoy

SiegeX, sorry for the long delay. Thousands of unplanned things kept me from trying this out. Now, here is what I get with the latest slapt-get 0.9.9k, after following the steps above, and then trying to upgrad only unofficial packages. As you can see, slapt-get tries to upgrade lots of KDE stuff, unfortunately.


Code:
# slapt-get --update --config unofficialrc
Retrieving package data [ftp://ftp3.linuxpackages.net/pub/Slackware-10.1/]...Cached
Retrieving patch list [ftp://ftp3.linuxpackages.net/pub/Slackware-10.1/]...Done
Retrieving checksum list [ftp://ftp3.linuxpackages.net/pub/Slackware-10.1/]...Cached
Reading Package Lists...Done
root@orion8:/etc/slapt-get# slapt-get --update --simulate --config unofficialrc
Retrieving package data [ftp://ftp3.linuxpackages.net/pub/Slackware-10.1/]...Cached
Retrieving patch list [ftp://ftp3.linuxpackages.net/pub/Slackware-10.1/]...Done
Retrieving checksum list [ftp://ftp3.linuxpackages.net/pub/Slackware-10.1/]...Cached
Reading Package Lists...Done
root@orion8:/etc/slapt-get# slapt-get --upgrade --simulate --config unofficialrc
Reading Package Lists... Done
The following packages have been EXCLUDED:
  librsvg libvorbis doxygen libgtkhtml libcroco arts gimp gkrellm getmail flac
  openssh xscreensaver gthumb joe xine-ui xfig nail portmap nmap vim apache
  stunnel glade flex tetex samba gstreamer libogg lftp bison gnet t1lib gftp
  mysql gnupg blackbox iptables tcl abiword fluxbox xvim xchat gst-plugins
  transfig xfce
The following packages will be upgraded:
  k3b kdegraphics postfix kdeaccessibility kdeadmin kdebindings kdelibs gxine
  kdeaddons php kdebase kdenetwork kdesdk ruby kdepim kdeartwork kdevelop
  kdegames kdetoys qt kdewebdev kdemultimedia kdeutils parted kdeedu
25 upgraded, 0 newly installed, 0 to remove and 45 not upgraded.
Need to get 225MB of archives.
After unpacking 36MB of additional disk space will be used.
k3b-0.11.23-i486-1 is to be upgraded to version 0.11.24-i486-1pcx
kdegraphics-3.3.2-i486-3 is to be upgraded to version 3.4.0-i486-1jim
postfix-2.1.3-i486-2stb is to be upgraded to version 2.2.3-i486-1stb
kdeaccessibility-3.3.2-i486-1 is to be upgraded to version 3.4.0-i486-1jim
kdeadmin-3.3.2-i486-1 is to be upgraded to version 3.4.0-i486-1jim
kdebindings-3.3.2-i486-3 is to be upgraded to version 3.4.0-i486-1jim
kdelibs-3.3.2-i486-2 is to be upgraded to version 3.4.0-i486-1jim
gxine-0.4.4-i486-1 is to be upgraded to version 0.4.4-i686-2ag
kdeaddons-3.3.2-i486-1 is to be upgraded to version 3.4.0-i486-3jim
php-4.3.11-i486-1 is to be upgraded to version 4.3.11-i486-2jim
kdebase-3.3.2-i486-1 is to be upgraded to version 3.4.0-i486-3jim
kdenetwork-3.3.2-i486-1 is to be upgraded to version 3.4.0-i486-1jim
kdesdk-3.3.2-i486-1 is to be upgraded to version 3.4.0-i486-1jim
ruby-1.8.1-i686-1kvh is to be upgraded to version 1.8.2-i686-1
kdepim-3.3.2-i486-1 is to be upgraded to version 3.4.0-i486-1jim
kdeartwork-3.3.2-i486-1 is to be upgraded to version 3.4.0-i486-1jim
kdevelop-3.1.2-i486-1 is to be upgraded to version 3.2.0-i486-1jim
kdegames-3.3.2-i486-1 is to be upgraded to version 3.4.0-i486-1jim
kdetoys-3.3.2-i486-1 is to be upgraded to version 3.4.0-i486-1jim
qt-3.3.3-i486-3 is to be upgraded to version 3.3.4-x8_64-1pcx
kdewebdev-3.3.2-i486-1 is to be upgraded to version 3.4.0-i486-1jim
kdemultimedia-3.3.2-i486-1 is to be upgraded to version 3.4.0-i486-1jim
kdeutils-3.3.2-i486-1 is to be upgraded to version 3.4.0-i486-1jim
parted-1.6.21-i486-1 is to be upgraded to version 1.6.22-i486-1h3x
kdeedu-3.3.2-i486-2 is to be upgraded to version 3.4.0-i486-1jim
Done
I suppose that slapt-get operates correctly within its own philosophy. I guess what happens is this:

- I have k3b installed on my system.
- slapt-get finds that there is an upgrade of k3b available.
- That update has dependencies.
- Therefore slapt-get wants to upgrade these other packages, too.

Well, maybe not: I don't see how k3b should depend on kdepim or kdevelop...

So, unfortunately slapt-get 0.9.9k still tries to upgrade official packages with unofficial ones. I wouldn't regard this wrong on its own, but it is just not what I want, and it is probably unsolvable.

Thanks anyway for your good effort!

Best wishes

gargamel
 
Old 05-27-2005, 07:03 PM   #66
mrcheeks
Senior Member
 
Registered: Mar 2004
Location: far enough
Distribution: OS X 10.6.7
Posts: 1,690

Rep: Reputation: 50
swaret experiences .... , it never played tricks on me untill the day it upgraded the kernel without my permission.
 
Old 02-09-2007, 09:30 AM   #67
tramni1980
Member
 
Registered: Jul 2006
Location: Tübingen, Germany
Distribution: Slackware64-13.37
Posts: 737

Rep: Reputation: 37
Question

Hello!
I am a newbie. Having read all that thread, I have the following question to ask you.
It seems to me that using Slackware, one is best to do package management by hand, utilising the "holy trinity" installpkg, upgradepkg and removepkg. So, my question is:
When I want to upgrade a package that I have an older version of intalled, I have to resolve all its dependencies. Sometimes it turns out that I have to upgrade some of the dependencies as well, because the new version of the package I want to upgrade to, requires newer version of the depencies. So, is it safe to upgrade the dependencies? Is there a risk that some other package that I have on my system will be incompatible with the new version of the dependency? What is the best, if any, procedure to follow in such cases?

Thank you for your attention.
Regards, Martin.
 
Old 02-10-2007, 02:52 PM   #68
Alien_Hominid
Senior Member
 
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247

Rep: Reputation: 53
If you are upgrading from slackware current, there are no problems for you. Because if package is upgraded there, its dependencies are upgraded too. If you don't like auto-updaters, then read changelog and update manually. If you updating from linuxpackages then usually important prerequisites are mentioned. Then you could aswell compile your own package from source, then use makepkg or checkinstall to create your own package and don't worry about incompatibility.
 
Old 04-06-2007, 07:32 PM   #69
gargamel
Senior Member
 
Registered: May 2003
Distribution: Slackware, SLAX, OpenSuSE
Posts: 1,599

Rep: Reputation: 142Reputation: 142
Quote:
Originally Posted by SiegeX
[...]

Again I bolded out the important part. As you can see, all those offical packages are now EXCLUDED! The only packages it wants to upgrade
are the ones I made myself, and I can easily remove those from the upgrade list by adding them to the EXCLUDE line.

Now how does it work you ask? The question at hand was how do we know if the package is official or not without having to download
huge manifest files and parsing those. This actually took a bit of thinking but the solution turned out to be very simple. While browsing
through the /var/log/packages/ directory I noticed that every official package had the text slackware followed by the
two-letter diskset abbreviation in the Package Location line (this is what the regex /slackware/[a-z]+ does). All that
Jason (slapt-get author) had to do was tell slapt-get to add this to its list of lines to exclude on. Enjoy
I just gave it another try with slapt-get 0.9.11h. Now, it almost does what I want. Not yet quite, however. Eg:

I have hplip installed (from /extra or /testing, not sure at the moment). slapt-get finds a newer version in a 3rd party repository and suggests to install it. However, other than the "official" hplip package, the 3rd party package depends on net-snmp, so slapt-get wants to install this, too.

Now, I have just two questions:

(1) What regex trick could I use to prevent official packages from /extra and /testing being touched?

Of course, I can add all the individual package names to my EXCLUDEs, but if there's a way to exclude the /extra and /testing directories and their whole content, I'd prefer it.

Currently my problem is: I want to upgrade only 3rd party packages, and leave official packages, even those from /extra and /testing, untouched. And I don't want to have new packages installed when there's no real dependency.

(2) How can I prevent slapt-get from installing new packages?

Eg, in my system slapt-get wants to install apache2. No idea, why, I don't see any dependencies with that package. Is there a way to restrict the installation of new packages to cases when another package depends on them?

Thanks in advance!

gargamel
 
Old 04-06-2007, 08:42 PM   #70
tuxdev
Senior Member
 
Registered: Jul 2005
Distribution: Slackware
Posts: 2,012

Rep: Reputation: 111Reputation: 111
I also vote for issue 2. Last time I tried slapt-get (and I admit it has been a while), slapt-get would try to install tcsh and a few other packages, which I had implied that I don't want by not having those packages on my system.
 
  


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
ReadHat9 is dead, Long Live RedHat9! or How to get up2date and fresh RPMs post RHN9 timtak Red Hat 8 06-30-2006 05:27 AM
swaret and slackpkg lodder Slackware 5 10-14-2005 04:37 AM
Slackpkg vs. Swaret. mdarby Slackware 3 11-18-2004 10:10 PM
swaret or slackpkg ? frochet Slackware 8 06-11-2004 01:08 PM
slapt-get, swaret, or SlackPkg ??? GloVe Slackware 2 10-05-2003 12:11 PM


All times are GMT -5. The time now is 05:39 PM.

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