[Pkg-privacy-maintainers] Updating snowflake to 2.10.1 in Debian
    Nilesh Patra 
    nilesh at iki.fi
       
    Fri Oct 17 20:36:20 BST 2025
    
    
  
On 07/10/25 6:16 am, Yifei Zhan wrote:
> On Monday, October 6, 2025 8:19:37 PM Coordinated Universal Time Nilesh Patra 
> wrote:
>> Hi meskio, anarcat,
>>
>> I noticed that snowflake is at 2.10.1 in salsa but it does not actually
>> build due to multiple issues.
>>
>> I packaged all (but one -- I need to coordinate w someone else for the
>> upload) missing B-D, uploaded to NEW and fixed all the build+test issues
>> and finally built snowflake locally.
> 
> Thanks for working on this!
> 
>>
>> Additionally, would you consider to see if this (locally built on my
>> machine) deb [1] works for you?
> 
> The client component works on my machine with bridgeline from the Tor Browser. 
> I can test snowflake-proxy later.
Thanks for checking.
I can't test this personally. All deps are in new. Once they are in, all that
is left is to just do an upload (I think dh_missing needs to be overriden as
I did not get a response to my earlier email about sqscreds but that's the only
additional work remaining).
Since you are able to run it, may I ask you to do an upload once the deps are in the
archive?
I can grant you DM permissions if you want.
> As we are discussing snowflake packaging, I'd like to know your opinion on 
> merging (at least the golang packages) the privacy team with the golang team, 
> and converting to a single debian/ namespace on salsa. The golang team is more 
> active and we can use some help from the golang team.
It may make more sense to move it to go team instead. There are very few people
in the privacy team who ever made commits to this package so we can grant them
individual access should they like.
The problem with Debian namespace is that only DDs have commit access there (and
others are granted access on a need basis) and realistically the possibility of
anyone from go team would ever look at that repo on debian/ namespace is tiny.
But I don't have much of an opinion here. Do as you deem fit.
> Prior discussions and context:
> https://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/2025/005009.html
CC'ing Simon as it was their suggestion.
-- 
Best,
Nilesh
    
    
More information about the Pkg-privacy-maintainers
mailing list