hi,
intrigeri wrote (11 Apr 2012 08:00:28 GMT) :
>> I've pushed an updated live-boot (live-persist doesn't need any
>> changes) into feature/persistence, awaiting the above change.
>> Tests of live-persist from the command-line was successful, so I'm
>> confident this should work. In addition my build used live-config
>> 3.0~a35-1 (currently in Debian unstable), and I think we should
>> settle on that version as 3.0~a36-1 and up intriduce stuff that
>> possibly causes some breakage.
> Given >= 3.0~a36-1 will likely be uploaded to sid soon, we should
> put the ~a35-1 binary package into our Git repository so that it is
> given precedence.
This was not done. Have we any clue whether live-config >= 3.0~a36-1
will, or won't, be uploaded to sid before we build Tails 0.11?
>> Surprisingly, we still use live-config-sysvinit 2.0.15-1. We really
>> should've bumped it to the matching version of live-config, but
>> since nothing seemed to fail during our extensive testing last
>> month, I suppose we should stay to not risk introducing any
>> breakage. I'm quite positive that version is completely incompatible
>> with live-config >= 3.0~a36-1.
> Only minor changes happened in live-config-sysvinit between 2.0.15-1
> and 3.0~a35-1, so this should be OK. Starting with 3.0~a36-1, we
> should really have matching live-config and live-config-sysvinit
> versions. Did you take any step so that we think to do so post-0.11?
I just did:
[devel 6606492]
Fetch live-config-sysvinit from sid so that it matches live-config version.
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
