USM Unified Slackware Package Manager

Here is a place for your projects which are not officially supported by the Porteus Team. For example: your own kernel patched with extra features; desktops not included in the standard ISO like Gnome; base modules that are different than the standard ISO, etc...
Bogomips
Full of knowledge
Full of knowledge
Posts: 2564
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: USM Unified Slackware Package Manager

Post#286 by Bogomips » 28 Aug 2014, 20:37

Functional Inconsistency
  1. usm -g <package> Processes all dependencies. As a result, one has to go through a whole lot of processing even if just one package file is wanted. Would be nice if there was a switch, say, like -depth d, which would cut off dependency processing at a certain level. So, if just the one package file was required, switch would be -depth 0, for example.
  2. usm -d /var/log/packages/package-name Here it would be desirable for dependencies to be chased down the line, as with the -g switch,

    Code: Select all

    root@porteus:/home/guest# usm -d /var/log/packages/okular-4.12.3-i486-1ftm
    
     Processing  okular-4.12.3-i486-1ftm
    ####################################
    libspectre.so.1 => not found
    Required by: okular-4.12.3-i486-1ftm (/usr/lib/kde4/okularGenerator_ghostview.so)
    ####################################
    Searching  libspectre.so.1:  found 2 packages.
    Choose a package to download or choose 'None' to neglect
    1) libspectre-0.2.7-i486-1.txz  3) None
    2) libspectre-0.2.7-i486-1.txz
    #? 1
     The following packages are ready to download: 
    libspectre-0.2.7-i486-1.txz [40 KB]
     Press [r] to remove packages, [q] to quit, or enter to start downloading.
    
    but they are not. :(

    Code: Select all

    root@porteus:/home/guest# activate p1/mods/libspectre-0.2.7-i486-1.xzm
    Updating shared library links:  /sbin/ldconfig
    
    loop12    7:12   0     5M  1 loop /mnt/live/memory/images/flashplayer-plugin-11.2.202.400-i3
    loop13    7:13   0    40K  1 loop /mnt/live/memory/images/libspectre-0.2.7-i486-1.xzm
    
    guest@porteus:~$ ldd /usr/lib/libspectre.so.1|grep 'not found'
            libgs.so.9 => not found
    
    And ghostscript, after providing libgs.so.9, will want cups. (Duplicate package names have still not been eradicated here.)
usm -d /var/log/packages/package-name

Code: Select all

root@porteus:/home/guest# usm -d okular-4.12.3-i486-1ftm
 This is not a valid file.

root@porteus:/home/guest# usm -d /var/log/packages/okular-4.12.3-i486-1ftm
 Processing  okular-4.12.3-i486-1ftm
Like to put forward for consideration: usm -d [/var/log/packages/]<package-name>. If no path is given, path defaults to /var/log/packages for given package-name.
brokenman wrote:
Wonder if it's for the same reason there is no 'none' option any more in the non-GUI version.
Nothing has changed there. The 'None' option is only available when using: usm -d /var/log/packages/package-name.
Incidentally the 'None' option is also available in usm -d, and this is where I got confused:

Code: Select all

root@porteus:/home/guest# usm -d
...
####################################

libcups.so.2 => not found
Required by: gtk+2-2.24.20-i486-1 (/usr/lib/gtk-2.0/2.10.0/printbackends/libprintbackend-cups.so)
...
libsmbclient.so.0 => not found
Required by: vlc-2.1.5-i486-1alien (/usr/lib/vlc/plugins/access/libaccess_smb_plugin.so)

####################################
 Missing dependencies:  21

libHalf.so.7
libIex.so.7
libIlmImf.so.7
libIlmThread.so.7
libImath.so.7
libaa.so.1
libaspell.so.15
libcaca.so.0
libclucene-core.so.1
libcups.so.2
libenchant.so.1
libgs.so.9
libiodbc.so.2
libjasper.so.1
libmysqlclient.so.18
libpcreposix.so.0
libraptor2.so.0
librdf.so.0
libsmbclient.so.0
libtcl8.6.so
libtk8.6.so
Searching  libHalf.so.7:  found 2 packages.
Choose a package to download or choose 'None' to neglect
1) ilmbase-1.0.3-i486-1.txz  3) None
2) ilmbase-1.0.3-i486-1.txz
#? 3

Searching  libIex.so.7:  found 2 packages.
Choose a package to download or choose 'None' to neglect
1) ilmbase-1.0.3-i486-1.txz  3) None
2) ilmbase-1.0.3-i486-1.txz
#? 3

Searching  libIlmImf.so.7:  found 2 packages.
Choose a package to download or choose 'None' to neglect
1) openexr-1.7.1-i486-1.txz  3) None
2) openexr-1.7.1-i486-1.txz
#? 3

Searching  libIlmThread.so.7:  found 2 packages.
Choose a package to download or choose 'None' to neglect
1) ilmbase-1.0.3-i486-1.txz  3) None
2) ilmbase-1.0.3-i486-1.txz
#? 3
Not only are duplications occurring within options, but also across options.

Would also be nice if "None' was not variable, but remained constant, like say 0, from a user standpoint.
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

User avatar
brokenman
Site Admin
Site Admin
Posts: 6104
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v4 all desktops
Location: Brazil
Contact:

Re: USM Unified Slackware Package Manager

Post#287 by brokenman » 29 Aug 2014, 02:22

Does this mean a package cannot be moved from $STORAGE?
Yes. If it is moved you will have broken symlinks. Leaving the packages in storage will allow package management. Yes this can be switched off in usm.conf
As a result, one has to go through a whole lot of processing even if just one package file is wanted.
Not sure I understand. If you just want one package why not just: usm -g that-package nodeps
Here it would be desirable for dependencies to be chased down the line, as with the -g switch
I understand what you mean but there are situations where this is not possible. When using the usm -g switch I can be sure that all dependencies can be resolved since the original package comes from the slackware repository. The looping resolver should always succeed in finding dependencies of dependencies. USM can't be sure that whatever package you have installed manually (and are checking) can be resolved all the way down the line. It would be a nice feature, and perhaps I could try, and just leave a list of dependencies that couldn't be resolved. Given some time I could give this a shot. Originally the system dep resolver was written as a separate entity to the package resolver.
Like to put forward for consideration: usm -d [/var/log/packages/]<package-name>. If no path is given, path defaults to /var/log/packages for given package-name.
usm -d okular-4.12.3 should default to /var/log/packages/okular-4.12.3-i486-1ftm correct?
This could be done. I always just use /var/log/packages because the auto TAB completion makes it as fast as typing the package name separately. Also supported is /mnt/sda8/txz/okular-4.12.3-i486-1ftm
Not only are duplications occurring within options, but also across options.
Yes I noticed a duplicated package tonight while testing int his area. Thanks. Not sure what you mean by 'across options'
Would also be nice if "None' was not variable, but remained constant, like say 0, from a user standpoint
Again, not sure what you mean. Choosing 'None' means that the packages presented should be left out of the download list. Skipped. You choose none of the offered packages for that library and go on to the next library.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
brokenman
Site Admin
Site Admin
Posts: 6104
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v4 all desktops
Location: Brazil
Contact:

Re: USM Unified Slackware Package Manager

Post#288 by brokenman » 29 Aug 2014, 03:59

In regards to system & package resolution using: usm -d XXX

Fixed duplicate packages.
Added 'auto add' of single packages. If only one package is available during dep resolution then it is automatically added to the download list without stopping to ask a question. User can remove what they don't need at the end.
Thank you.
How do i become super user?
Wear your underpants on the outside and put on a cape.

tome
Contributor
Contributor
Posts: 657
Joined: 26 Jun 2013, 14:03
Distribution: x64 Openbox
Location: against russian attacks and lies
Contact:

Re: USM Unified Slackware Package Manager

Post#289 by tome » 29 Aug 2014, 10:30

Very thanks brokenman for added new features, hopefully they will be useful for everyone.

Some unfinished things:
1.

Code: Select all

usm -v
/usr/bin/usm: line 63: /etc/usm/version.txt: No such file or directory
 You are using USM version:  3.1.5
2. all=alien? It should update all!

Code: Select all

usm -u all
/usr/bin/usm: line 63: /etc/usm/version.txt: No such file or directory
 Starting alien database update 
Downloading: vercheck.txt  DONE
awk: fatal: cannot open file `/etc/usm/version.txt' for reading (No such file or directory)
Downloading: CHECKSUMS.md5.gz  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT.gz  DONE
Downloading: LIBS.TXT.gz  DONE
File verification was good.
Optimizing manifest
 alien  database updated. 


extra-deps.txt was updated 4931 seconds ago. Skipping.
ignore-deps.txt was updated 4931 seconds ago. Skipping.

You can change the time limit for skipping in: /etc/usm/usm.conf
The default is 3 hours
3. Downloading manifest for salix could be skipped.

Code: Select all

 usm -u salix
/usr/bin/usm: line 63: /etc/usm/version.txt: No such file or directory
 Starting salix database update 
Downloading: vercheck.txt  DONE
awk: fatal: cannot open file `/etc/usm/version.txt' for reading (No such file or directory)
Downloading: CHECKSUMS.md5  DONE
Downloading: PACKAGES.TXT  DONE
Downloading: LIBS.TXT.gz  DONE
Downloading: OPTIFEST.gz  DONE
Downloading: MANIFEST.bz2  DONE
 salix  database updated. 
4. It could be also little change:
alien|ponce|salix|slackware|slacky|all -> alien|ponce|salix|slackware|slackwarepatches|slacky|all

5. Tried next time usm -u all but it doesn't work and stops at "Updating config file"
You have mind and feelings. Be wise and clever.

User avatar
brokenman
Site Admin
Site Admin
Posts: 6104
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v4 all desktops
Location: Brazil
Contact:

Re: USM Unified Slackware Package Manager

Post#290 by brokenman » 29 Aug 2014, 14:06

Thanks Tome.

1) Forgot to git add the version.txt file. Done now.
2) Added other repos to update function (they were removed for testing)
3) It now skips salix manifest file
4) I added slackwarepatches to the update list (I will need to do some testing tonight)
5) Pull latest git again. Missing version.txt was the cause.
How do i become super user?
Wear your underpants on the outside and put on a cape.

Bogomips
Full of knowledge
Full of knowledge
Posts: 2564
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: USM Unified Slackware Package Manager

Post#291 by Bogomips » 29 Aug 2014, 19:32

@brokenman
Thanks for the usage tips and the explanations. Gives some idea of the obstacles being faced. :wall:
brokenman wrote:
Does this mean a package cannot be moved from $STORAGE?
Yes. If it is moved you will have broken symlinks. Leaving the packages in storage will allow package management. Yes this can be switched off in usm.conf
This sounds too fiddly for my limited package management demands, so will have to forego package management. Hope the off switch is going to be in custom usm.conf.
brokenman wrote:Not sure I understand. If you just want one package why not just: usm -g that-package nodeps
Despite having referred to usm man page many times, still managed to miss the nodeps switch. :sorry: Anyway have tried to separate a long usm -g listing into separate levels, which was not very easy to do. Hence the thought of a -depth switch, -depth 0 being equivalent of -nodeps; -depth 1 would terminate processing after one level, allowing one to see which packages would be pulled in; -depth 2 etc.
usm -d okular-4.12.3 should default to /var/log/packages/okular-4.12.3-i486-1ftm correct? This could be done. ... Also supported is /mnt/sda8/txz/okular-4.12.3-i486-1ftm
If there is no sda8 or sda8 is a swap partition?
Not sure what you mean by 'across options'
In the following code section there are duplications for (libHalf.so.7,libIex.so.7,libIlmThread.so.7,ibImath.so.7) and the duplications are themselves offered as the same option 4 times (4x same package). Same duplicated options for (libcups.so.2,,libpcreposix.so.0), 2x same package.

Code: Select all

root@porteus:/home/guest# usm -v
 You are using USM version:  3.1.5
root@porteus:/home/guest# usm -d
....
Searching  libHalf.so.7:  found 2 packages.
Choose a package to download or choose 'None' to neglect
1) ilmbase-1.0.3-i486-1.txz  3) None
2) ilmbase-1.0.3-i486-1.txz
#? 3

Searching  libIex.so.7:  found 2 packages.
Choose a package to download or choose 'None' to neglect
1) ilmbase-1.0.3-i486-1.txz  3) None
2) ilmbase-1.0.3-i486-1.txz
#? 3

Searching  libIlmImf.so.7:  found 2 packages.
Choose a package to download or choose 'None' to neglect
1) openexr-1.7.1-i486-1.txz  3) None
2) openexr-1.7.1-i486-1.txz
#? 3

Searching  libIlmThread.so.7:  found 2 packages.
Choose a package to download or choose 'None' to neglect
1) ilmbase-1.0.3-i486-1.txz  3) None
2) ilmbase-1.0.3-i486-1.txz
#? 3

Searching  libImath.so.7:  found 2 packages.
Choose a package to download or choose 'None' to neglect
1) ilmbase-1.0.3-i486-1.txz  3) None
2) ilmbase-1.0.3-i486-1.txz
#? 3

Searching  libaa.so.1:  found 2 packages.
Choose a package to download or choose 'None' to neglect
1) aalib-1.4rc5-i486-5.txz  3) None
2) aalib-1.4rc5-i486-5.txz
#? 3

Searching  libaspell.so.15:  found 2 packages.
Choose a package to download or choose 'None' to neglect
1) aspell-0.60.6-i486-1.txz  3) None
2) aspell-0.60.6-i486-1.txz
#? 3

Searching  libcaca.so.0:  found 2 packages.
Choose a package to download or choose 'None' to neglect
1) libcaca-0.99.beta18-i486-2.txz  3) None
2) libcaca-0.99.beta18-i486-2.txz
#? 3

Searching  libclucene-core.so.1:  found 2 packages.
Choose a package to download or choose 'None' to neglect
1) clucene-2.3.3.4-i486-2.txz  3) None
2) clucene-2.3.3.4-i486-2.txz
#? 3

Searching  libcups.so.2:  found 2 packages.
Choose a package to download or choose 'None' to neglect
1) aaa_elflibs-14.1-i486-3.txz  3) None
2) aaa_elflibs-14.1-i486-3.txz
#? 3

Searching  libenchant.so.1:  found 2 packages.
Choose a package to download or choose 'None' to neglect
1) enchant-1.6.0-i486-1.txz  3) None
2) enchant-1.6.0-i486-1.txz
#? 3

Searching  libiodbc.so.2:  found 3 packages.
Choose a package to download or choose 'None' to neglect
1) libiodbc-3.52.7-i486-2.txz
2) libiodbc-3.52.8-i486-1_slack14.1.txz
3) libiodbc-3.52.7-i486-2.txz
4) None
#? 4

Searching  libjasper.so.1:  found 2 packages.
Choose a package to download or choose 'None' to neglect
1) jasper-1.900.1-i486-3.txz  3) None
2) jasper-1.900.1-i486-3.txz
#? 3

Searching  libmysqlclient.so.18:  found 3 packages.
Choose a package to download or choose 'None' to neglect
1) mariadb-5.5.32-i486-1.txz            3) mariadb-5.5.32-i486-1.txz
2) mariadb-5.5.37-i486-1_slack14.1.txz  4) None
#? 4

Searching  libpcreposix.so.0:  found 2 packages.
Choose a package to download or choose 'None' to neglect
1) aaa_elflibs-14.1-i486-3.txz  3) None
2) aaa_elflibs-14.1-i486-3.txz
#? 3

Searching  libraptor2.so.0:  found 2 packages.
Choose a package to download or choose 'None' to neglect
1) raptor2-2.0.9-i486-1.txz  3) None
2) raptor2-2.0.9-i486-1.txz
#? 3

Searching  librdf.so.0:  found 2 packages.
Choose a package to download or choose 'None' to neglect
1) redland-1.0.16-i486-1.txz  3) None
2) redland-1.0.16-i486-1.txz
#? 3

Searching  libsmbclient.so.0:  found 3 packages.
Choose a package to download or choose 'None' to neglect
1) samba-4.1.0-i486-2.txz             3) samba-4.1.0-i486-2.txz
2) samba-4.1.11-i486-1_slack14.1.txz  4) None
#? 4

Searching  libspectre.so.1:  found 2 packages.
Choose a package to download or choose 'None' to neglect
1) libspectre-0.2.7-i486-1.txz  3) None
2) libspectre-0.2.7-i486-1.txz
#? 3

Searching  libtcl8.6.so:  found 2 packages.
Choose a package to download or choose 'None' to neglect
1) tcl-8.6.1-i486-1.txz
2) tcl-8.6.1-i486-1.txz
3) None
#? 3

Searching  libtk8.6.so:  found 2 packages.
Choose a package to download or choose 'None' to neglect
1) tk-8.6.1-i486-1.txz
2) tk-8.6.1-i486-1.txz
3) None
#? 3
 The following packages are ready to download: 
 Press [r] to remove packages, [q] to quit, or enter to start downloading.
brokenman wrote:
Would also be nice if "None' was not variable, but remained constant, like say 0, from a user standpoint
Again, not sure what you mean. Choosing 'None' means that the packages presented should be left out of the download list. Skipped.
If there are 2 packages offerred, user has to press 3 for 'none', then if 5 are offered - press 6 for 'none', then 3 offered - press 4 for 'none'. Easier if just had to press 0 (same key) for 'none', less of a strain on the brain. 8)
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

User avatar
brokenman
Site Admin
Site Admin
Posts: 6104
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v4 all desktops
Location: Brazil
Contact:

Re: USM Unified Slackware Package Manager

Post#292 by brokenman » 29 Aug 2014, 21:46

This sounds too fiddly for my limited package management demands, so will have to forego package management. Hope the off switch is going to be in custom usm.conf.
Do you think the default should be OFF? This way nothing will be broken if a file is moved.
-depth 1 would terminate processing after one level, allowing one to see which packages would be pulled in
This is doable. The older PPM had similar functionality to prevent runaway dependency resolving.
If there is no sda8 or sda8 is a swap partition?
Sorry I have should have been more explicit. Also supported is: usm -d /whatever/path/has/a/package-1.2.3-i486.txz
where the package is any slackware package for your architecture sitting on a local filesystem.

Code: Select all

and the duplications are themselves offered as the same option
Got it now. I fixed this last night and pushed it to github. If only one package is an option it is now automatically selected.
All duplicates should also be gone.
Easier if just had to press 0 ... less of a strain on the brain.
LOL. Yes I know what you mean. In a dark room it is also more difficult. I will see if I can do it. It made for less coding at the time.

Thanks for your suggestions and clear explanations.
How do i become super user?
Wear your underpants on the outside and put on a cape.

Bogomips
Full of knowledge
Full of knowledge
Posts: 2564
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: USM Unified Slackware Package Manager

Post#293 by Bogomips » 30 Aug 2014, 22:48

brokenman wrote:
This sounds too fiddly for my limited package management demands, so will have to forego package management. Hope the off switch is going to be in custom usm.conf.
Do you think the default should be OFF? This way nothing will be broken if a file is moved.
YES. I suppose, for newbies, it's one less level of complexity, especially if you are still feeling your way round the system. And those who know what they are on about, will know how to go about coordinating with package management.
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

User avatar
brokenman
Site Admin
Site Admin
Posts: 6104
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v4 all desktops
Location: Brazil
Contact:

Re: USM Unified Slackware Package Manager

Post#294 by brokenman » 31 Aug 2014, 02:17

Sat Aug 30 10:04:14 UTC 2014
Changed symlinks creation to default false
Changed None in systemDeps resolution to always be number 1 (thanks Bogomips)
Added depth=n argument in CLI to quit after given loops of resolution. (thanks Bogomips)

Pushed to github for inclusion in next release.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
brokenman
Site Admin
Site Admin
Posts: 6104
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v4 all desktops
Location: Brazil
Contact:

Re: USM Unified Slackware Package Manager

Post#295 by brokenman » 02 Sep 2014, 16:24

Update to v3.1.6

The latest release included some important changes. Please update and test.

- Getting the version no longer checks for database. (usm -v)
- The command: usm info was added. It gives current status and info.
- A custom usm.conf file is now possible. It must be named usm-custom.conf and exist in /etc/usm. This will stop updates overwriting your changes.
- The large MANIFEST database files are now deleted after being used. This saves considerable storage space.
- An option has been added in usm.conf to allow usm to create a symlink to a package if it already exists in storage instead of downloading it again. This allows for packages management in your storage folder. It also means you must leave all packages in place in this folder so as not to break any symlinks. By default this setting is false.

Here is the complete changelog.

+-------------------------
Sat Aug 30 10:04:14 UTC 2014
Changed symlinks creation to default false
Changed None in systemDeps resolution to always be number 1 (thanks Bogomips)
Added depth=n argument in CLI to quit after given loops of resolution. (thanks Bogomips)

+-------------------------
Thu Aug 27 09:10:12 UTC 2014
Added version check out of usm.conf (thank Tome/Bogomips)
Added custom usm-conf.txt path
Added option to install packages after download (thanks Tome)
Added symlink (default) in storage folder for doubled packages. (thanks Tome)
Added removal of MANIFEST file when updating database. Saves over 100Mb.

+-------------------------
Thu Aug 21 23:03:45 UTC 2014
Fixed module question showing in slackware (thanks Slaxmax)
Fixed deselect option not working in CLI (thanks Slaxmax)
Added database dir to preferences in GUI
Fixed extra-deps being removed in global update (thanks Bogomips)
Removed multiple updates of config file during global update
Add ignored-deps.txt functionality for deps that are not required
Change default time from 24 hours to 3 hours for skipping updates (thanks Ed_P)
Fixed sbo not updating in global update (thanks cttan)
Added openldap-client missing dep for ekiga (thanks cttan)
Fixed dolphin not opening storage folder (thanks router)
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Ed_P
Contributor
Contributor
Posts: 7675
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.0 ISO
Location: Western NY, USA

Re: USM Unified Slackware Package Manager

Post#296 by Ed_P » 02 Sep 2014, 18:27

brokenman wrote:Don't mess around with the .wh files at all. Just download the new initrd.xz and replace the one in your current porteus install. It is located in: /mnt/sdxY/boot/syslinux/initrd.xz (where sdxY is the location of your porteus install.)

The error message will still appear but won't affect the functioning of Porteus in any way. It is a USM error that will be fixed in the next update.
This initrd.xz file that I downloaded for my 3.0 no longer works. And the link to redownload it no longer works. I see that the file in 3.0.1 is a different size than the one downloaded so I don't think I can use it.

https://imageshack.com/i/p9zPXlI8p

Suggestions?
Ed

User avatar
fanthom
Moderator Team
Moderator Team
Posts: 5591
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

Re: USM Unified Slackware Package Manager

Post#297 by fanthom » 02 Sep 2014, 18:54

I see that the file in 3.0.1 is a different size than the one downloaded so I don't think I can use it.
because i had to update SGN variable to 3.0.1 release.
please upgrade to 3.0.1 and job done.
Please add [Solved] to your thread title if the solution was found.

User avatar
Ed_P
Contributor
Contributor
Posts: 7675
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.0 ISO
Location: Western NY, USA

Re: USM Unified Slackware Package Manager

Post#298 by Ed_P » 02 Sep 2014, 22:04

I had problems with 3.0.1 when it first came out. I don't remember what they were. And I don't like the new version of FireFox in it.

Any idea why the initrd.xz file I've been using stopped working?
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 6104
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v4 all desktops
Location: Brazil
Contact:

Re: USM Unified Slackware Package Manager

Post#299 by brokenman » 02 Sep 2014, 22:53

Please keep on topic or I will remove posts. This is the USM thread.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
brokenman
Site Admin
Site Admin
Posts: 6104
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v4 all desktops
Location: Brazil
Contact:

Re: USM Unified Slackware Package Manager

Post#300 by brokenman » 05 Sep 2014, 02:29

I've added package status to usm. (thanks Bogomips)

When showing the final list of packages it will now show either:
[installed]
[upgrade]
[downgrade]
Packages can be downloaded even if they are installed. If you choose the option to install packages after download then the packages are installed using: upgradepkg --install-new.
Downgrade is not supported through usm.

Pushed to github for inclusion in next release.
How do i become super user?
Wear your underpants on the outside and put on a cape.

Post Reply