Re: [Slackbuilds-users] updating dozens/hundreds packages/queues more easily/correctly weekly?

2024-04-01 Thread David Chmelik
On 4/1/24 9:02 PM, "Lockywolf 

Jeremy Hansen  writes:


On Mon, Apr 1, 2024, 8:07 PM  wrote:

  I installed more packages built from SlackBuilds.org (SBo) than urchlay
  (a few years ago 1150+, now more) and see after updates, some/many need
  most/all dependencies rebuilt but you never know until either building
  or using crashes.  Is there a way to keep track and rebuild these
  without having to manually load dozens/hundreds queues in sbopkg (nor
  use its command-line)--I heard it may be easier with sborepo?  I have no
  need for my own repository and want to avoid creating one (other than
  just a directory/folder) but are there instructions on updating more
  easily/correctly weekly just for users?

Simply put, sbopkg does not have any proper way to handle this other than 
rebuilding the entire tree.

The only program I know that decently handles this is slackrepo, but it seems 
to be best used on a clean
machine (either virtual or not), which can be difficult with certain users 
setups.

But I also have only used sbopkg and slackrepo (with the latter used in 
conjunction with slapt-get to handle
dependencies of packages), so others might be better set up for it without me 
being aware of it.

Jeremy

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Might it be that sboupgrade is what you need?
Not sure if it can detect broken ldd, but it seems to be able to update
the deps if the target package needs them.
I already use it but don't think it uses ldd nor detects certain other 
things including (not only) updates such as package-1.0-x86_64-1_SBo to 
package-1.0-x86_64-2_SBo... sbotools hasn't updated since Slackware 14.2 
so fixes may be unlikely.

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] updating dozens/hundreds packages/queues more easily/correctly weekly?

2024-04-01 Thread Lockywolf

Jeremy Hansen  writes:

> On Mon, Apr 1, 2024, 8:07 PM  wrote:
>
>  I installed more packages built from SlackBuilds.org (SBo) than urchlay 
>  (a few years ago 1150+, now more) and see after updates, some/many need 
>  most/all dependencies rebuilt but you never know until either building 
>  or using crashes.  Is there a way to keep track and rebuild these 
>  without having to manually load dozens/hundreds queues in sbopkg (nor 
>  use its command-line)--I heard it may be easier with sborepo?  I have no 
>  need for my own repository and want to avoid creating one (other than 
>  just a directory/folder) but are there instructions on updating more 
>  easily/correctly weekly just for users?
>
> Simply put, sbopkg does not have any proper way to handle this other than 
> rebuilding the entire tree.
>
> The only program I know that decently handles this is slackrepo, but it seems 
> to be best used on a clean
> machine (either virtual or not), which can be difficult with certain users 
> setups.
>
> But I also have only used sbopkg and slackrepo (with the latter used in 
> conjunction with slapt-get to handle
> dependencies of packages), so others might be better set up for it without me 
> being aware of it.
>
> Jeremy
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/

Might it be that sboupgrade is what you need?
Not sure if it can detect broken ldd, but it seems to be able to update
the deps if the target package needs them.

-- 
Your sincerely,
Vladimir Nikishkin (MiEr, lockywolf)
(Laptop)


signature.asc
Description: PGP signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] updating dozens/hundreds packages/queues more easily/correctly weekly?

2024-04-01 Thread Jeremy Hansen
On Mon, Apr 1, 2024, 8:07 PM  wrote:

> I installed more packages built from SlackBuilds.org (SBo) than urchlay
> (a few years ago 1150+, now more) and see after updates, some/many need
> most/all dependencies rebuilt but you never know until either building
> or using crashes.  Is there a way to keep track and rebuild these
> without having to manually load dozens/hundreds queues in sbopkg (nor
> use its command-line)--I heard it may be easier with sborepo?  I have no
> need for my own repository and want to avoid creating one (other than
> just a directory/folder) but are there instructions on updating more
> easily/correctly weekly just for users?
>

Simply put, sbopkg does not have any proper way to handle this other than
rebuilding the entire tree.

The only program I know that decently handles this is slackrepo, but it
seems to be best used on a clean machine (either virtual or not), which can
be difficult with certain users setups.

But I also have only used sbopkg and slackrepo (with the latter used in
conjunction with slapt-get to handle dependencies of packages), so others
might be better set up for it without me being aware of it.

Jeremy

>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] oidentd very outdated and won't be updated?

2024-04-01 Thread B. Watson




On Mon, 1 Apr 2024, dchme...@gmail.com wrote:


I use oidentd but don't make network utility SlackBuilds (I'm far
from a network expert) so if anyone else does, one might consider
asking him you can takeover oidentd?


Yet you maintain network/icyque... which uses the network in more
complex ways than oidentd does.

It's not rocket science. There's already a slackbuild and it already
works. You could take it over and update it. You don't have to be
a network expert, you just have to know how to use whatever you're
packaging, and make sure it works (you probably use it for IRC and
already know how to tell if the IRC server got an ident response).

Since the build is unmaintained, whoever wants it updated badly
enough can take it over. You're the only one who's interested enough
to post to the mailing list about it in the 5+ years since it was last
updated, so you're the #1 candidate to become its new maintainer.

Just for testing, I downloaded the latest oidentd source (v3.1.0) and
ran oidentd.SlackBuild with VERSION=3.1.0 in the environment, and it
built just fine. So updating the build isn't going to take you a lot
of time and effort (just VERSION and DOWNLOAD need to be changed).

I'd say, go for it. You can do this.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



[Slackbuilds-users] updating dozens/hundreds packages/queues more easily/correctly weekly?

2024-04-01 Thread dchmelik
I installed more packages built from SlackBuilds.org (SBo) than urchlay 
(a few years ago 1150+, now more) and see after updates, some/many need 
most/all dependencies rebuilt but you never know until either building 
or using crashes.  Is there a way to keep track and rebuild these 
without having to manually load dozens/hundreds queues in sbopkg (nor 
use its command-line)--I heard it may be easier with sborepo?  I have no 
need for my own repository and want to avoid creating one (other than 
just a directory/folder) but are there instructions on updating more 
easily/correctly weekly just for users?


___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



[Slackbuilds-users] oidentd very outdated and won't be updated?

2024-04-01 Thread dchmelik
I asked oidentd maintainer (Mario Preksavec, mario at slackware dot hr ) 
when there'll be a new version, as it's many versions/years behind 
(about since Slackware 14.2 was new?) and he said he doesn't want to 
maintain it.  I don't recall he told SlackBuilds.org (SBo) team or this 
emailing list, and couldn't find record of that, so mentioning it.  I 
use oidentd but don't make network utility SlackBuilds (I'm far from a 
network expert) so if anyone else does, one might consider asking him 
you can takeover oidentd?

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



[Slackbuilds-users] Pycharm VERSION="2023.3.5.233.15026.15" - MD5SUM error

2024-04-01 Thread Diniz Bortolotto
Hi Dimitris.
Could you please check/fix pycharm.info on SlackBuild?
I'm getting an MD5SUM error on tarball. Maybe JetBrains changed the
package?!?

--2024-04-01 14:02:23--
https://download.jetbrains.com/python/pycharm-community-2023.3.5.tar.gz
Resolving download.jetbrains.com (download.jetbrains.com)... 52.84.83.87,
52.84.83.13, 52.84.83.46, ...
Connecting to download.jetbrains.com
(download.jetbrains.com)|52.84.83.87|:443...
connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location:
https://download-cdn.jetbrains.com/python/pycharm-community-2023.3.5.tar.gz
[following]
--2024-04-01 14:02:23--
https://download-cdn.jetbrains.com/python/pycharm-community-2023.3.5.tar.gz
Resolving download-cdn.jetbrains.com (download-cdn.jetbrains.com)...
65.8.214.63, 65.8.214.84, 65.8.214.67, ...
Connecting to download-cdn.jetbrains.com
(download-cdn.jetbrains.com)|65.8.214.63|:443...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 611250164 (583M) [binary/octet-stream]
Saving to: ‘pycharm-community-2023.3.5.tar.gz’

pycharm-community-2 100%[===>] 582.93M  36.7MB/sin 16s


2024-04-01 14:02:40 (35.6 MB/s) - ‘pycharm-community-2023.3.5.tar.gz’ saved
[611250164/611250164]

Found pycharm-community-2023.3.5.tar.gz in /var/cache/sbopkg.
Checking MD5SUM:
 MD5SUM check for pycharm-community-2023.3.5.tar.gz ... FAILED!


*Expected: fbacc6b64807bfe93b44792347a6a206Found:
   1ce10a2f41ddaa6f45cb45373241106c*
Best Regards,
Diniz Bortolotto
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/