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