-current had no updates since the middle of December, any Idea what's
going on ?
Holidays ?

-rasp

On 1/8/24 07:56, Ralph Spitzner wrote:
> -current had no updates since the middle of December, any Idea what's
> going on ?
> Holidays ?
>
>
>     -rasp

http://ftp.arm.slackware.com/slackwarearm/slackwareaarch64-current/

Rinaldi

RinaldiJ wrote on 1/8/24 4:10 PM:

>
> http://ftp.arm.slackware.com/slackwarearm/slackwareaarch64-current/
>
> Rinaldi

I know,I rsync that every night, however PACKAGES are way out of date
comared to slackware 64.
slackpkg reports no changes in PACKAGES.txt ....

On Mon, 08 Jan 2024 17:02:10 +0100, Ralph Spitzner wrote:

> RinaldiJ wrote on 1/8/24 4:10 PM:
>
>
>> http://ftp.arm.slackware.com/slackwarearm/slackwareaarch64-current/
>>
>> Rinaldi
>
> I know,I rsync that every night, however PACKAGES are way out of date
> comared to slackware 64.
> slackpkg reports no changes in PACKAGES.txt ....

I don't use slackpkg myself, but have a vauge memory of reading something
about this somewhere. In that case, if I remember right, the problem was
that this update had not been installed:

+--------------------------+
Sat Nov 18 19:26:33 UTC 2023
patches/packages/ca-certificates-20231117-noarch-1_slack15.0.txz:
Upgraded.
This update provides the latest CA certificates to check for the
authenticity of SSL connections.
+--------------------------+

The lack of the above package in combination with Slackware mirrors
updating their SSL certificates caused slackpkg to fail connecting to
mirrors. Do you have ca-certificates-20231117-noarch-1_slack15.0.txz
installed?

regards Henrik

Henrik Carlqvist wrote on 1/8/24 7:55 PM:

> The lack of the above package in combination with Slackware mirrors
> updating their SSL certificates caused slackpkg to fail connecting to
> mirrors. Do you have ca-certificates-20231117-noarch-1_slack15.0.txz
> installed?

ca-certificates-20230721-noarch-1 is installed however connecting is not
the problem, I also mirror aarch64 via rsync.....
this is what slackpkg tells me:
-----------------------------------------------------------------
slackpkg update

Updating the package lists...
Downloading...
Downloading
https://spitzner.org/slackarm/CHECKSUMS.md5.asc..." rel="nofollow" target="_blank">https://spitzner.org/slackarm/CHECKSUMS.md5.asc...
--2024-01-08 22:58:08-- https://spitzner.org/slackarm/CHECKSUMS.md5.asc
Resolving spitzner.org (spitzner.org)... 10.0.68.1
Connecting to spitzner.org (spitzner.org)|10.0.68.1|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 691 [application/pgp-signature]
Saving to: ‘/tmp/slackpkg.BzlJ4Y/CHECKSUMS.md5.asc’

/tmp/slackpkg.BzlJ4Y/CHECKSUMS.md5.asc
100%[============================================================================================>]
691 --.-KB/s in 0s

2024-01-08 22:58:08 (256 MB/s) -
‘/tmp/slackpkg.BzlJ4Y/CHECKSUMS.md5.asc’ saved [691/691]

No changes in ChangeLog.txt between your last update
and now.
Do you really want to download all other files (y/N)?
-------------------------------------------------------------------------------------------------------
also this is "-current", not 15.0
on my Intel Stuff slackpkg finds updates almost daily, it's just the
ARM stuff that's stuck (as there actually is nothing new on the
server:ftp.arm.slackware.com/slackwarearm/slackwareaarch64-current/,
hence my question if (I believe mozes was what he's called) was on
vacation or something, or whoever maintains aarch64 is on a break.

I just thought some arm people might be reading this group.
Probably not.......

-rasp

On Tue, 09 Jan 2024 00:08:43 +0100, Ralph Spitzner wrote:
> it's just the ARM stuff that's stuck (as there actually is nothing
> new on the server:
> ftp.arm.slackware.com/slackwarearm/slackwareaarch64-current/ ,
> hence my question if (I believe mozes was what he's called) was on
> vacation or something, or whoever maintains aarch64 is on a break.

Looking at ftp.arm.slackware.com/slackwarearm/slackwareaarch64-current/
you can see that ChangeLog.txt was last updated 5/1, from

http://ftp.arm.slackware.com/slackwarearm/slackwareaarch64-current/
ChangeLog.txt

-8<----------------------
Fri Jan 05 08:08:08 UTC 2024

This update batch was built on Linux 6.6.9, and everything appears to be
operating
smoothly. We anticipate a release in approximately a week.

NOTICE - Attention RockPro64 & Pinebook Pro users: Prior to Linux 6.6,
it's crucial
to update your Boot Loader. Refer to the note in the previous batch dated
'Wed Jan 03 08:08:09 UTC 2024' for instructions.

This project is made possible entirely through your support!

If you appreciate our efforts and have the means to contribute to our
operational
expenses, your support would be greatly appreciated!

You'll find the ways you can help here:
https://arm.slackware.com/sponsor/

A heartfelt thank you to everyone who has supported and continues to
support the
project. Your contributions mean a lot to us.

Enjoy!

Stuart <mozes@slackware>

a/dcron-4.5-aarch64-10.txz: Rebuilt.
Add /etc/default/run-parts. Thanks to lostintime.
ap/vim-9.1.0-aarch64-1.txz: Upgraded.
d/clisp-2.50_20230718_669249717-aarch64-1.txz: Upgraded.
kde/fcitx5-configtool-5.1.3-aarch64-1.txz: Upgraded.
l/poppler-24.01.0-aarch64-1.txz: Upgraded.
n/c-ares-1.25.0-aarch64-1.txz: Upgraded.
n/mobile-broadband-provider-info-20231023-aarch64-1.txz: Upgraded.
n/ncftp-3.2.7-aarch64-1.txz: Upgraded.
x/fcitx5-5.1.6-aarch64-1.txz: Upgraded.
x/fcitx5-qt-5.1.4-aarch64-1.txz: Upgraded.
x/pixman-0.43.0-aarch64-1.txz: Upgraded.
x/xcb-imdkit-1.0.6-aarch64-1.txz: Upgraded.
xap/vim-gvim-9.1.0-aarch64-1.txz: Upgraded.
+--------------------------+
Wed Jan 03 08:08:09 UTC 2024
a/hwm-bw-raspberrypi-1.20230405-aarch64-4.txz: Rebuilt.
Upgraded to U-Boot........: 2023.01
a/hwm-bw-rk3399-2023.01-aarch64-1.txz: Upgraded.
Upgraded to U-Boot version 2023.01.
RockPro64 and Pinebook Pro users, take note: This update tackles the
issue of
the MMC (SD card) interface becoming inaccessible post a soft reboot, a
problem identified during my extensive testing of Linux 6.6. Upon
updating to
this version of U-Boot, I've been unable to replicate the issue.
Consequently, I strongly recommend this as a mandatory update.

The upgrade instructions for both Hardware Models can be found here:
https://docs.slackware.com/
slackwarearm:inst_sa64_rk3399_pinebookpro#managing_the_boot_loader_firmware
+--------------------------+
....
-8<----------------------

What does that URL look like when you study it in a browser? Do you use
some kind of proxy or caching server that has not been updated as it
should?

Also the file CHECKSUMS.md5.asc was updated at the same date. What does
it look like when you study that file in a web browswer? Does that file
have the same content as the file downloaded by slackpkg?

regards Henrik

On Mon, 8 Jan 2024 14:56:20 +0100, Ralph Spitzner wrote:
> -current had no updates since the middle of December, any Idea what's
> going on ?
> Holidays ? [...]

Everyone knows this is an architecture so what's the point of having that
abbreviation in the name? No one says amdarch64 or x86arch64. Why not
just say arm and assume it's 64-bit if 32-bit (arm32) is older and not
made as much or anymore?

On Thu, 11 Jan 2024 11:11:14 -0000 (UTC), David Chmelik wrote:

> On Mon, 8 Jan 2024 14:56:20 +0100, Ralph Spitzner wrote:
>> -current had no updates since the middle of December, any Idea what's
>> going on ?
>> Holidays ? [...]
>
> Everyone knows this is an architecture so what's the point of having
> that abbreviation in the name? No one says amdarch64 or x86arch64. Why
> not just say arm and assume it's 64-bit if 32-bit (arm32) is older and
> not made as much or anymore?

It would seem AArch64 is ARM's official naming for it, not something "we"
came up with. And for a shortened name, they also have chosen their own,
A64 (vs AArch32/A32).

Worse yet (subjective), Apple called it ARM64 when they developed support
for it, and when the GNU version was perhaps "sideported", they decided
to use the ARM64 code as a base and rename it AArch64 again...

Personally I think "Acorn" is still a cool name too. Ah well..