[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #31130 [Applications/Tor Browser]: Use Debian 10 for our Android container images



#31130: Use Debian 10 for our Android container images
--------------------------------------+--------------------------------
 Reporter:  gk                        |          Owner:  tbb-team
     Type:  defect                    |         Status:  needs_revision
 Priority:  Medium                    |      Milestone:
Component:  Applications/Tor Browser  |        Version:
 Severity:  Normal                    |     Resolution:
 Keywords:  tbb-rbm                   |  Actual Points:
Parent ID:  #31127                    |         Points:  0.5
 Reviewer:                            |        Sponsor:
--------------------------------------+--------------------------------

Comment (by boklm):

 Replying to [comment:6 sisbell]:

 > > >
 > > > The above commit works fine for openjdk-8. When I attempted to add
 pinning I would get some dependency errors and I didn't see any advantage
 to making this more complicated.
 > >
 > > No pinning means that we are not using Debian buster, but Debian
 testing, which is not what we want (and not a good idea for reproducible
 builds as this distribution is changing a lot all the time). From the
 error it looks like `openjdk-8-jre` and `openjdk-8-jdk-headless` need to
 be added to the pinning configuration too.
 >
 > I had tried pinning the openjdk-8-jre and openjdk-8-headless but got the
 same result, they were missing.

 Maybe the pinning configuration was wrong. But hard to say without seeing
 the actual configuration that was used, and how the openjdk package was
 installed.

 If pinning is too complicate, an other option is to download and install
 the openjdk packages without using apt. In any case, adding the testing
 repository without pinning is not an option, as that just means we're
 using Debian testing and not buster.


 > >
 > > I also think we should not do this configuration in `projects
 /debootstrap-image/config`, but only in the containers that we use for
 android builds, for example by doing it in `var/pre_pkginst` in
 `rbm.conf`.
 >
 > I can move the apt sources change to rbm.conf. Assuming I don't modify
 the pre script in the debootstrap config for the android specific build,
 how is the # Bug 29158 going to be handled? Is this related to stretch or
 to the ubuntu version? Can it be removed now?

 buster was released after `DSA 4371-1`, so it is not affected by this
 issue.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/31130#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs