latest-stable link points to 7.2 not 7.2.1

[Geert Kloosterman]

Hi,

I discovered https://www.beegfs.io/release/latest-stable redirects to https://www.beegfs.io/release/beegfs_7.2/ instead of the more recent https://www.beegfs.io/release/beegfs_7.2.1/ 

Is this intended? 

Also note that at in the listing at https://www.beegfs.io/release/ both versions are marked as LATEST STABLE even though one is more recent than the other.

Right now http://www.beegfs.io/release/latest-stable/dists/beegfs-rhel8.repo results in v7.2 that does not work on RHEL8.3

Best regards,

Geert Kloosterman

[alexand...@thinkparq.com]

Hi Geert,

 

thanks a lot for letting us know and please apologize for the inconvenience. We are going to correct this ASAP.

 

As a download source, you could also use the following link https://www.beegfs.io/c/download/ which will point you to the new download section, where you can select the version, architecture, and operating system to download.

 

 

 

Thanks a lot

 

Kind regards

 

Alex

 

[Steffen Grunewald]

Hi Alexander,

thanks for spreading the new download link! One question though -

On Thu, 2021-03-18 at 08:26:24 +0100, alexand...@thinkparq.com wrote:
>
> As a download source, you could also use the following link
> https://www.beegfs.io/c/download/ which will point you to the new download
> section, where you can select the version, architecture, and operating

^^^^^^^^^^^^
> system to download.

Are there plans to build for arm64 (aarch64) in the near future?

And, well, another question shows up: What about Debian Bullseye support?
Bullseye has entered the pre-release freeze stages, any software for it,
I presume, would have a defined set of prerequisites now. (We're planning
to purchase a number of AMD Milan machines which may require a backported
kernel though.)

Thanks,
Steffen

[Philipp Falk]

Hi Geert,

thank you very much for reporting these outdated redirects. I have
corrected the latest-stable redirect and also updated the tags in the
release directory.

Best regards
- Philipp

* Geert Kloosterman <geert.kl...@brightcomputing.com> [210317 18:00]:

> --
> You received this message because you are subscribed to the Google Groups "beegfs-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to fhgfs-user+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/fhgfs-user/35ae7790-1d1e-405a-bd3b-5a469df67fe6n%40googlegroups.com.


--
Philipp Falk | System Engineer | m: philip...@thinkparq.com
ThinkParQ GmbH | Trippstadter Strasse 110 | 67663 Kaiserslautern | Germany
CEO: Frank Herold | COB: Dr. Franz-Josef Pfreundt | Registered: Amtsgericht Kaiserslautern HRB 31565 I VAT-ID-No.:DE 292001792

Confidentiality Notice: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential or proprietary information.

[Geert Kloosterman]

Hi Alex,

I see it's fixed now, thanks!

Cheers,

Geert

[Steffen Grunewald]

On Thu, 2021-03-18 at 08:26:24 +0100, alexand...@thinkparq.com wrote:
>

> As a download source, you could also use the following link
> https://www.beegfs.io/c/download/ which will point you to the new download
> section, where you can select the version, architecture, and operating
> system to download.

Good morning,

I found that some 7.1.2 packages (both for deb9 and deb10) are delivered
without a "Last-Modified:" header. Timestamps are shown correctly in the
Online Repository.

This results in timestamps diverging from the source - packages affected
are beegfs-client, beegfs-meta, and beeond.
All others appear to be fine in this respect.

It seems to be an older issue, I could reproduce it with 7.2 and 7.1.5,
too. I didn't check older versions (but there are hints that 7.1.3 was
also affected).

Since the Packages* files haven't been recreated since after the release,
this is mildly confusing because a mirror would - for those files - show
the date of mirroring, not of package creation.

Can this be fixed?

Thanks,
Steffen


--
Steffen Grunewald, Cluster Administrator
Max Planck Institute for Gravitational Physics (Albert Einstein Institute)
Am Mühlenberg 1 * D-14476 Potsdam-Golm * Germany
~~~
Fon: +49-331-567 7274
Mail: steffen.grunewald(at)aei.mpg.de
~~~

[Steffen Grunewald]

Good morning,

I had almost missed the release of 7.2.2, and found the same issue:

# ls -ltr | cut -c24-

307244 May 21 17:20 beegfs-client-dkms_7.2.2_all.deb
58407056 May 21 17:20 beegfs-meta-dbg_7.2.2_amd64.deb
1348948 May 21 17:20 beegfs-utils_7.2.2_amd64.deb
8320 May 21 17:20 beegfs-utils-dev_7.2.2_amd64.deb
811940 May 21 17:20 beegfs-storage_7.2.2_amd64.deb
29410188 May 21 17:20 beegfs-storage-dbg_7.2.2_amd64.deb
447252 May 21 17:20 beegfs-mon_7.2.2_amd64.deb
18610 May 21 17:20 beegfs-mirror-md_7.2.2_amd64.deb
457342 May 21 17:20 beegfs-mirror-md-dbg_7.2.2_amd64.deb
668684 May 21 17:20 beegfs-mgmtd_7.2.2_amd64.deb
23230888 May 21 17:20 beegfs-mgmtd-dbg_7.2.2_amd64.deb
9178196 May 21 17:20 beegfs-helperd-dbg_7.2.2_amd64.deb
10716 May 21 17:20 beegfs-common_7.2.2_amd64.deb
10324 May 21 17:20 beegfs-client-dev_7.2.2_amd64.deb
301644 May 21 17:20 beegfs-client-compat_7.2.2_all.deb
521954 May 21 17:20 libbeegfs-ib_7.2.2_amd64.deb
65594 May 21 17:20 beeond-thirdparty-gpl_7.2.2_amd64.deb
51908836 May 21 17:20 beegfs-utils-dbg_7.2.2_amd64.deb
9260 May 21 17:20 beegfs-mon-grafana_7.2.2_all.deb
13654172 May 21 17:20 beegfs-mon-dbg_7.2.2_amd64.deb
337740 May 21 17:20 beegfs-helperd_7.2.2_amd64.deb
314104 May 21 21:13 beegfs-client_7.2.2_all.deb
1334524 May 21 21:13 beegfs-meta_7.2.2_amd64.deb
21138 May 21 21:13 beeond_7.2.2_amd64.deb

21:13 was the time of mirroring, meaning that there was no "Last-Modified:"
for the three packages at the bottom of the list... so the old problem
persists.

Also, will there be arm64 packages at some point?
What about Bullseye support?

Thanks,
Steffen

On Fri, 2021-03-19 at 09:48:53 +0100, Steffen Grunewald wrote:
> I found that some 7.1.2 packages (both for deb9 and deb10) are delivered
> without a "Last-Modified:" header. Timestamps are shown correctly in the
> Online Repository.
>
> This results in timestamps diverging from the source - packages affected
> are beegfs-client, beegfs-meta, and beeond.
> All others appear to be fine in this respect.
>
> It seems to be an older issue, I could reproduce it with 7.2 and 7.1.5,
> too. I didn't check older versions (but there are hints that 7.1.3 was
> also affected).