On 9/15/21 08:04, L A Walsh wrote:

I have a question about the date listed in the subject.

If I look at the repomd.xml file in oss/repodata, on dl.os.org, I see a timestamp of 09-Sep-2021 13:48 (i.e. 20210909 , not 20210908).

Looking inside that file I see the cpeid having a value of 20210907!

Looking at the time the message was sent, that gives me a 4th date of 20210910.

Why are there 4 dates associated with the release(s) that go out?

internal date:          0907 title date (in message) 0908 file date:              0909 actual message date     0910.

So why don't any of them agree? Shouldn't at least there be any/some agreeance?

---- Now tell me how this wasn't trimmed, and didn't have the wrong subject (except)

Well Tumbleweed snapshot dates would be a much better subject, given that your email isn't specific to this email but all snapshot emails. An understanding of the process will help you here, There are multiple "staging" where packages are built and tested individually or in groups. Once a day all the packages from statings that have passed are grouped into one "snapshot", this is where me title in the message comes from. This combined snapshot then goes through QA and is only pushed to mirrors if it passes QA this is why the "file date" could be later then the snapshot date due to the time it takes to do QA. Then I presume we wait for all the files to upload and then give some time for mirrors to sync before sending the email otherwise downloads are really slow because large number of people fetch it from the primary mirror. As for the "Internal date" depending on a staging and which other packages are also in the same staging project it may take anywhere from 1 hr to several weeks (in extreme cases) for a package to pass staging so the internal date is probably some reflection on when a packager submitted the package to tumbleweed but sometimes stuff gets moved or rebuilt so it wouldn't be 100% accurate. But in summary getting a new package to users is generally a multi day process and so you wind up with various dates depending on which part of the process you look at but we consider the date in the email to be the unique identifier for each snapshot. Cheers -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B

On 9/15/21 08:04, L A Walsh wrote:

...

I have a question about the date listed in the subject.

If I look at the repomd.xml file in oss/repodata, on dl.os.org, I see a timestamp of 09-Sep-2021 13:48 (i.e. 20210909 , not 20210908).

Looking inside that file I see the cpeid having a value of 20210907!

I do not know what file you are looking at, but if I look inside repomd.xml of Tumbleweed snapshot 20210908 I see date 20210908. http://download.opensuse.org/history/20210908/tumbleweed/repo/oss/repodata/r...

On 2021/09/14 22:43, Andrei Borzenkov wrote:

...

On 9/15/21 08:04, L A Walsh wrote:

...

I have a question about the date listed in the subject.

If I look at the repomd.xml file in oss/repodata, on dl.os.org, I see a timestamp of 09-Sep-2021 13:48 (i.e. 20210909 , not 20210908).

Looking inside that file I see the cpeid having a value of 20210907!

I do not know what file you are looking at, but if I look inside repomd.xml of Tumbleweed snapshot 20210908 I see date 20210908.

But that's not the repomd.xml that was at download.opensuse.org/tumbleweed/repo/oss/repodata/repomd.xml after her announcement -- that's part of the problem -- her announcement proceeds that file being updated. http://download.opensuse.org/history/20210908/tumbleweed/repo/oss/repodata/r... The file you get from 'history' shows a last-mod date of 20210909, which seems to indicate it wasn't put in place until the day after the release announcement. I've been taking her release announcement as being what's available at http:download.opensuse.org/tumbleweed/repo/oss/repodata/repomd.xml (as I thought that was the current release). I hadn't thought of use 'history/date' to download the current release (until you just now mentioned it). I'll have to watch, but would have thought when she announced "X", that was the version at 'current' (download.opensuse.org/tumbleweed/repo/oss/repodata/repomd.xml) and wouldn't expect current to show up in 'history' until the next current is announded (at which time what was 'current' became 'history'). Though I see that having no release yet announced for the 14th, the release for the 13th is in(at) both 'current' and the 0913 history URL. Does (or will) the release being announced, appear in history at the same time? It seems like it appears a day later, given the filemod time. I.e. the file with the 0913 date in the cpeid field has a last mod date of 0914.

On 9/15/21 11:09, L A Walsh wrote:

On 2021/09/14 17:57, Simon Lees wrote:

...

But in summary getting a new package to users is generally a multi day process and so you wind up with various dates depending on which part of the process you look at but we consider the date in the email to be the unique identifier for each snapshot.

---     And where in the release is that date recorded?

Currently its recorded as the "VERSION_ID" in "/etc/os-release" which is installed as part of the openSUSE-Release package and is also the version number of this package. So ass you can see from the perspective of an updated filesystem this is the version number we reference. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B

On Wed, 2021-09-15 at 19:24 -0700, L A Walsh wrote:

you just now mentioned it).

I'll have to watch, but would have thought when she announced "X", that was the version at 'current' (download.opensuse.org/tumbleweed/repo/oss/repodata/repomd.xml) and wouldn't expect current to show up in 'history' until the next current is announded (at which time what was 'current' became 'history'). Though I see that having no release yet announced for the 14th, the release for the 13th is in(at) both 'current' and the 0913 history URL.

The most relevant information you might be missing is that the 'snapshot release date' is the 'date, when the checkin round for said snapshot happened, i.e when I started building that snapshot'. So, currently, I am building snapshot 0915 (checkin of yesterday), 0914 is still in QA and likely to come out today) The checkin date is chosen as that is the date we can put into RPMs during build - at publish, we are way too late to inject dates and this would be terribly releasing something else than what was in QA before. The release announcement is generated at the time when the snapshot appears on download.o.o - which can be 'days' after it started building. Cheers, Dominique

On 2021/09/16 00:12, Dominique Leuenberger / DimStar wrote:

The most relevant information you might be missing is that the 'snapshot release date' is the 'date, when the checkin round for said snapshot happened,

==== Ok, that explains quite a bit. I wasn't parsing your subject as being the snapshot date, but as being the snapshot-release date, for example Snapshot#20210914 was released on 20210916(~4am PDT). and was wondering why a release dated 0914 wouldn't be released until 0916 -- but that's because it's the date the snapshot was taken. It was disconcerting in my own download process why, what appeared to be the latest download, was 2 days old. I'm zooming in on some details around my download process like wanting to know that the last-mod timestamps I'm seeing are correct. Seems to be the case despite over zealous spam processing (which isn't done by you, I understand)...I guess I'd still be a bit embarrassed by the poor implementation done in your name, but that's more just me -- and like how I get embarrassed when gmail does something flakey (as they don't follow mail-RFC's...*sigh*). thanks for the explanation, -linda