Planned patches for Core Update 152 and handling location filter issues in Core Update 151 (was: Re: Upcoming Core Update 151)

Planned patches for Core Update 152 and handling location filter issues in Core Update 151 (was: Re: Upcoming Core Update 151)

[Peter Müller]

[-- Attachment #1: Type: text/plain, Size: 2785 bytes --]

Hello Michael, hello *,

I am currently working on a new version of the Tor add-on, which should be done in
a couple of hours and can IMHO safely be merged in Core Update 152. :-)

Regarding Core Update 151 (hence the location list CC'ed): Are you planning to include
your commits made to libloc today and yesterday into this update as well? Or are those
not necessary on the client-side and we ship them with a new version of libloc?

Speaking about the location database: My understanding of handling bugs #12499 to #12501
is currently the following:

1. We continue to generate location databases using the extended sources.
2. A fix for the location filter issue (#12499) is already included in Core Update 151.
3. As soon as we feel confident about the inetnum patchset I submitted the other day
   (i. e. after some successful Q/A testing), we release a new version of libloc and
   publish databases in a new fashion (inetnum data where we have it, and extended
   sources otherwise).

>From my point of view, the last step will break systems still running on Core Update 150
and having the location filter enabled. Those should not be too much, but since we can
never be sure, we could

1. Urge all users to install Core Update 151 as fast as possible once it has been released.
2. Give them some time (2 weeks, maybe longer) until we switch to the new database format.
3. Prohibit location downloads from user-agents we can correlate to Core Update 150 systems
   left over. This requires Core Update 151 systems to come with a different user-agent.

Is this procedure fine? Or am I missing something?

Thanks, and best regards,
Peter Müller


> Hello,
> 
> So since Core Update 151 has been available for testing for a while and because we have received a lot of positive feedback, we are planning a release quite soon.
> 
> This also means that Core Update 152 is ready to be closed for any further changes. We will soon merge it into master unless somebody has some urgent changes that need to be included in it. Please raise your hand now.
> 
> Everyone have a lovely weekend.
> 
> Best,
> -Michael
> 
>> On 2 Oct 2020, at 16:51, Michael Tremer <michael.tremer(a)ipfire.org> wrote:
>>
>> Hello everyone,
>>
>> I have been in charge of merging together Core Update 151.
>>
>> I would like to accept patches until (and including Monday). After that I would like to close it and only accept any fixes for newly introduced bugs.
>>
>> If anyone has anything urgent, please let me know. Otherwise everything else will be merged into Core Update 152.
>>
>> Thank you all for your hard work on this Core Update. It has a large number of contributors which makes me happy :)
>>
>> Have a lovely weekend,
>> -Michael
>