upload to calm: should curr-2 be vaulted while still in setup.ini?

upload to calm: should curr-2 be vaulted while still in setup.ini?

[Brian Inglis]

Hi folks,

After upload, noticed in calm deployment log that release current - 2 is 
being vaulted, but it's still showing in setup.ini.
If current - 2 is selected in setup, won't this cause setup to fail, as 
as it will no longer be available under release/, nor propagated on 
mirrors?

> INFO: adding 1 package(s) for arch x86_64 > INFO: move from Brian Inglis's upload area to release area:> INFO: 
deploying x86_64/release/cpuid/cpuid-20221003-1-src.hint> INFO: 
deploying x86_64/release/cpuid/cpuid-20221003-1-src.tar.xz> INFO: 
deploying x86_64/release/cpuid/cpuid-20221003-1.hint> INFO: deploying 
x86_64/release/cpuid/cpuid-20221003-1.tar.xz> INFO: vaulting 1 old 
package(s) for arch x86_64> INFO: move from release area to vault:> 
INFO: vaulting x86_64/release/cpuid/cpuid-20220812-1-src.hint> INFO: 
vaulting x86_64/release/cpuid/cpuid-20220812-1-src.tar.xz> INFO: 
vaulting x86_64/release/cpuid/cpuid-20220812-1.hint> INFO: vaulting 
x86_64/release/cpuid/cpuid-20220812-1.tar.xz> SUMMARY: 12 INFO(s)
[prev]
version: 20220812-2
install: x86/release/cpuid/cpuid-20220812-2.tar.xz 132096 
3eb7f8d86db037c242d7dccbd79b28a4a57771eb08f4e187fd5be124e6b3aff4aa615636e83ed39e6529982869460282b195454914ff6ff573ce2f427b58dcad
source: x86/release/cpuid/cpuid-20220812-2-src.tar.xz 139888 
e8e958c2f799fdbed04076878f1a2293066f6004dc3754892354f5484bed172e7ae49d0f0043c0a1a4b5ef52a85b803305de136ec5edd71852a3e5dc02d9ac26
depends2: cygwin, perl_base
build-depends: binutils, coreutils, cygport, gcc-core, gzip, make, perl, tar

-- 
La perfection est atteinte,
non pas lorsqu'il n'y a plus rien à ajouter,
mais lorsqu'il n'y a plus rien à retirer.
	-- Antoine de Saint-Exupéry

Re: upload to calm: should curr-2 be vaulted while still in setup.ini?

[ASSI]

Brian Inglis writes:
> After upload, noticed in calm deployment log that release current - 2
> is being vaulted, but it's still showing in setup.ini.
> If current - 2 is selected in setup, won't this cause setup to fail,
> as as it will no longer be available under release/, nor propagated on
> mirrors?

You've had two releases with this version…

> INFO: vaulting x86_64/release/cpuid/cpuid-20220812-1-src.hint
> source:           x86/release/cpuid/cpuid-20220812-2-src.tar.xz 139888


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables

Re: upload to calm: should curr-2 be vaulted while still in setup.ini?

[Brian Inglis]

On Sun, 09 Oct 2022 08:58:45 +0200, ASSI wrote:
> Brian Inglis writes:
>> After upload, noticed in calm deployment log that release current - 2
>> is being vaulted, but it's still showing in setup.ini.
>> If current - 2 is selected in setup, won't this cause setup to fail,
>> as as it will no longer be available under release/, nor propagated on
>> mirrors?

> You've had two releases with this version…

>> INFO: vaulting x86_64/release/cpuid/cpuid-20220812-1-src.hint
                                                       *
>> source:           x86/release/cpuid/cpuid-20220812-2-src.tar.xz 139888

Doh - thanks - that explains it!
Both my memory and visual cortex failing me here, even after a number of 
re-reads, I didn't pick up on that - hopefully the lesson is retained.  ;^>

-- 
La perfection est atteinte,
non pas lorsqu'il n'y a plus rien à ajouter,
mais lorsqu'il n'y a plus rien à retirer.
	-- Antoine de Saint-Exupéry