On Sunday, February 11th, 2024 at 6:16 PM, [email protected] 
<[email protected]> wrote:

> Hi again,
> 
> Don't know if the information is helpful but more than 800 pkg's remain 
> uncompressed, maybe out of date?
> 
> I don't know if u store it for templates or other reasons.
> 
> -----stripped------
> 
> bloodcm
> blueMSX-libretro
> bsnes-mercury
> cannonball-libretro
> chocolate_duke3D
> fbalpha
> fmsx-libretro
> gambatte-libretro
> gens-gs
> glPortal
> gw-libretro
> ^C
> [root@arcadia t1]# for i in $(grep .asc 
> /opt/slackware-repositories/slackbuilds/15.0/CHECKSUMS.md5 | cut -d" " -f3 
> |rev | cut -d. -f4 |
> cut -d/ -f1| rev) ; do if [ "$(grep $i 
> /opt/slackware-repositories/slackbuilds/15.0/CHECKSUMS.md5 | wc -l)" == "2" ] 
> ; then echo $i ; fi ; done | wc -l
> 803
> [root@arcadia t1]#
> 
> Cheers,
> 
> 
> 
> -------- Forwarded Message --------
> 
> From:
> 
> - Sun <>, 26 GMT <>
> 
> X-Mozilla-Status:
> 
> 0001
> 
> X-Mozilla-Status2:
> 
> 00800000
> 
> Content-Type:
> 
> multipart/alternative; boundary="------------8Ti6ei1b5em3QFTEhtIhpt8F"
> 
> Message-ID:
> 
> <[email protected]>
> 
> Date:
> 
> Sun, 11 Feb 2024 12:35:22 +0100
> 
> MIME-Version:
> 
> 1.0
> 
> User-Agent:
> 
> Mozilla Thunderbird
> 
> Content-Language:
> 
> en-US
> 
> To:
> 
> [email protected]
> 
> From:
> 
> [email protected] <[email protected]>
> 
> Subject:
> 
> unattended package python3 3.7.2
> 
> 
> 
> Hi,
> I think i found an unattended package. python3 3.7.2
> 
> from last update with rsync, the python3.tar.gz seems that is old. I found it 
> because don't have an extracted dir with the SlackBuild file and others ... 
> and that make me curious.
> 
> [root@arcadia t1]# grep python3 
> /var/lib/srpm/repositories/sbo/15.0/CHECKSUMS.md5 | tail -20
> c2124db45079c4a5da5b3bcef405ecf5 ./python/python3-zxcvbn/README
> 53fea0b9500c79fdce7bd062a0ed4c1d 
> ./python/python3-zxcvbn/python3-zxcvbn.SlackBuild
> a33997f0ddb2f53a45ecbafaa937192e ./python/python3-zxcvbn/python3-zxcvbn.info
> 5a57d63831a7525b534550277e4a07ec ./python/python3-zxcvbn/slack-desc
> a22977ecb64571bec6ad412ffa807102 ./python/python3.tar.gz
> ab6fb66d89dd19f037d24c6bdee81608 ./python/python3.tar.gz.asc
> 0d1931eeacdf713b2ba148b2fc77ad43 ./system/python3-docker-compose.tar.gz
> 288689b99fdeec238f258a58c263f09e ./system/python3-docker-compose.tar.gz.asc
> f75c198eff9a1380fd7fd36a6d58fce8 ./system/python3-docker-compose/README
> 1022470b1dba49604f7bab796001098c 
> ./system/python3-docker-compose/python3-docker-compose.SlackBuild
> 1b4a5d97267ea0cbfec736e0dc4a1f33 
> ./system/python3-docker-compose/python3-docker-compose.info
> ba06334d025d892dcf9f9390a6057240 ./system/python3-docker-compose/slack-desc
> 47327a75b6b992f233db9889919d6148 ./system/python3-nvidia-ml-py.tar.gz
> a571f1b03c02a3a35fafc1b27bff7e1e ./system/python3-nvidia-ml-py.tar.gz.asc
> da2082d1f5880f5150f220996b6ac3d2 ./system/python3-nvidia-ml-py/README
> 3d460b5e71059f7e761f329a9789b2ad 
> ./system/python3-nvidia-ml-py/python3-nvidia-ml-py.SlackBuild
> 2bdc12478783998e3c05ea34dbfed411 
> ./system/python3-nvidia-ml-py/python3-nvidia-ml-py.info
> f4020b4564a1fd325dad9a5a6fae5c45 ./system/python3-nvidia-ml-py/slack-desc
> 4bd0be69e441b4131997982b9a0861c7 ./system/python3-urwid.tar.gz
> 2372411b8895787ae82c8c86890114d5 ./system/python3-urwid.tar.gz.asc
> [root@arcadia t1]#
> 
> Happy to help,
> 
> regards.
> 

I think OP found in oversight in the SBo tree.  Removed packages are not fully 
being removed.  That is, the *.tar.gz and *.tar.gz.asc files are not being 
deleted.  For example, QtiPlot was removed March 2022 but QtiPlot.tar.gz and 
QtiPlot.tar.gz.asc are still available at 
https://slackbuilds.org/slackbuilds/15.0/academic/

See 
https://www.linuxquestions.org/questions/slackware-14/slackbuilds-rsync-have-uncompressed-packages-4175733765/#post6483028

Erich

_______________________________________________
SlackBuilds-users mailing list
[email protected]
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Reply via email to