LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   libgmp and libpng in latest -current upgrades (https://www.linuxquestions.org/questions/slackware-14/libgmp-and-libpng-in-latest-current-upgrades-792497/)

AGer 03-03-2010 06:42 AM

Quote:

Originally Posted by dive (Post 3882859)
slackpkg and upgradepkg are shell scripts.

Oh yes indeed! Just forgot about that. Installpkg is a shell script too, so theoretically things may get complicated.
Quote:

Originally Posted by dive (Post 3882859)
There's no way to avoid that.

I would say "no reasonable way".

As for the idea that more checks should be added to slackpkg, I guess since the effect is rare and dependency tracking is necessary to be sure (have reasonable basis for hope?) that it will never happen again, it is better to do nothing.

If somebody is still willing to do something, I would propose to make a small Slackware rescue ISO image with, among other things, slackpkg.

disturbed1 03-03-2010 06:51 AM

Quote:

As for the idea that more checks should be added to slackpkg, I guess since the effect is rare and dependency tracking is necessary to be sure (have reasonable basis for hope?) that it will never happen again, it is better to do nothing.
Just some simple logic for which upgrades to perform first should suffice. Rather than upgrading all in alphabetical order, perhaps upgrade by package sets. Then again, this is current, and we're supposed to already know how to do this :)

The Slackware install disc is already a rescue disk. You can create a ~21MB ISO with just the isolinux/ and kernels/ directory. Read isolinux/README.TXT

dive 03-03-2010 07:27 AM

Quote:

Originally Posted by AGer (Post 3883759)
.
I would say "no reasonable way".

The latest upgrade for coreutils removes the dependency to libgmp, so that will help enormously in the future.

Quote:

Originally Posted by Changelog
a/coreutils-8.4-i486-2.txz: Rebuilt.
Use --without-gmp, at least for now. We don't want utilities in /bin
requiring a library in /usr/lib{,64} that may not be available.


botnet 03-03-2010 02:08 PM

thank you speek, that worked perfectly

AGer 03-04-2010 08:48 AM

Quote:

Originally Posted by disturbed1 (Post 3883763)
Just some simple logic for which upgrades to perform first should suffice. Rather than upgrading all in alphabetical order, perhaps upgrade by package sets. Then again, this is current, and we're supposed to already know how to do this :)

I agree that will reduce the probability of a massive upgrade failing since package sets are rudimentary dependency tracking. This may be done since it should not be hard and will not add much complexity. My point is that I do not see how to proof that a mass upgrade will never fail, so just reducing a probability that is already low cannot be a high priority.

Quote:

Originally Posted by disturbed1 (Post 3883763)
The Slackware install disc is already a rescue disk. You can create a ~21MB ISO with just the isolinux/ and kernels/ directory. Read isolinux/README.TXT

I thought about it. I guess the install disk is not a rescue disk since it may be outdated due to changes to slackpkg or the kernel. Unofficial current ISO builds almost solve that, but they are too large. And, naturally, when there is a problem it is too late to do isolinux.

I would agree if it is said that Slackware does not need a rescue disk since is easy to manage and any good LiveCD can be used, but I guess it would be nice to have one if there are no better things to do.

disturbed1 03-04-2010 09:38 AM

Quote:

Originally Posted by AGer (Post 3885450)
I agree that will reduce the probability of a massive upgrade failing since package sets are rudimentary dependency tracking. This may be done since it should not be hard and will not add much complexity. My point is that I do not see how to proof that a mass upgrade will never fail, so just reducing a probability that is already low cannot be a high priority.

I thought about it. I guess the install disk is not a rescue disk since it may be outdated due to changes to slackpkg or the kernel. Unofficial current ISO builds almost solve that, but they are too large. And, naturally, when there is a problem it is too late to do isolinux.

I would agree if it is said that Slackware does not need a rescue disk since is easy to manage and any good LiveCD can be used, but I guess it would be nice to have one if there are no better things to do.

What!?

This is Slackware -current which implies a certain ... anyways ;)


but they are too large.
21MB is too large?
Grab isolinux/ kernels/ from your favorite mirror, and place in a directory ~/slackboot
Code:

cd ~/slackboot
mkisofs -o /tmp/slackware-dvd.iso \
  -R -J -A "Slackware Install" \
  -hide-rr-moved \
  -v -d -N \
  -no-emul-boot -boot-load-size 4 -boot-info-table \
  -sort isolinux/iso.sort \
  -b isolinux/isolinux.bin \
  -c isolinux/isolinux.boot \
  -V "SlackDVD" .
cdrecord /tmp/slackware-dvd.iso

There, 21MB Slackware Rescue disc. The same tools that are used to install Slackware, can be use to rescue Slackware. Networking, recovery, hell I've even rescued Windows systems from the Slackware DVD.

If you must have slackpkg, install it while your in the installation environment. If you can't wget it from the installation environment, place the .txz on the CD and use installpkg. Better yet, extract the initrd and remaster it.
Code:

mkdir /tmp/new.initrd
cd /tmp/new.initrd
cat /slackmirror/isolinux/initrd.img | gzip -cd | cpio -i -H newc

Do your stuff, explode a few packages
Code:

find . | cpio -o -H newc | gzip -9c >../new.initrd.img

AGer 03-05-2010 10:01 AM

Quote:

Originally Posted by disturbed1 (Post 3885534)
There, 21MB Slackware Rescue disc. The same tools that are used to install Slackware, can be use to rescue Slackware. Networking, recovery, hell I've even rescued Windows systems from the Slackware DVD.

There must be some misunderstanding. I agree that lots of things can be done with Slackware DVD and it is possible to get the same or enhanced functionality in much smaller space. The installation media is good enough and sufficient under most scenarios. However, it is not ideal as a rescue disk.

It is possible to customize initrd, but this alone does not result in an ideal rescue disc. To my taste, ideal Slackware rescue CD is like Slax. Unfortunately, Slax itself is not in the best shape right now.

As I see it, the problem that initiated this thread, putting aside unnecessary technical details, is: "since once in 3 years an upgrade goes wrong, it must go seriously wrong once in 30 years". This does not look big enough to me to do anything right now, but why not to evaluate the options?

sahko 03-05-2010 12:40 PM

Quote:

Originally Posted by AGer (Post 3885450)
I thought about it. I guess the install disk is not a rescue disk since it may be outdated due to changes to slackpkg or the kernel. Unofficial current ISO builds almost solve that, but they are too large. And, naturally, when there is a problem it is too late to do isolinux.

The simpler way to run current IMO is to have an rsynced Slackware tree in your computer. Doing that will give you the opportunity to create your own updated custom Slackware ISO everytime theres an update, furthermore one humongous like the latest.

PS. Thats also the reason i dont use slackpkg, which might be a great tool, but IMO its more useful for keeping up with stable releases and things that go into patches/
Keeping up with current means you have to examine the packages you install yourself, & not some automated tool like slackpkg is, cause things might break anytime. If you do that, you might know beforehand and avoid a possible disaster.


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