[Qa-jenkins-scm] [jenkins.debian.net] 02/02: reproducible Debian: i386 seems to be fine with stretch

[Holger Levsen]

This is an automated email from the git hooks/post-receive script.

holger pushed a commit to branch master
in repository jenkins.debian.net.

commit dfea843e7d9580cfbedeb783631ae2efce92e648
Author: Holger Levsen <holger at layer-acht.org>
Date:   Mon Jun 19 20:01:36 2017 +0200

    reproducible Debian: i386 seems to be fine with stretch
    
    Signed-off-by: Holger Levsen <holger at layer-acht.org>
---
 TODO4stretch-host-upgrades.txt | 40 +++++++++++++++++++++-------------------
 1 file changed, 21 insertions(+), 19 deletions(-)

diff --git a/TODO4stretch-host-upgrades.txt b/TODO4stretch-host-upgrades.txt
index b5fa608..9ac3e8e 100644
--- a/TODO4stretch-host-upgrades.txt
+++ b/TODO4stretch-host-upgrades.txt
@@ -1,33 +1,35 @@
-rough notes from upgrading pb-build2:
---------------------------------------
-check for changes in /etc/ssh/sshd_config - the currently running one is the one from jessie which doesnt 
-seem sufficient anymore… 
 
 
-had to do "sudo apt install linux-image-686-pae", to get kernel upgraded… huh? :)
--> add multiarch, needs to be added to update_jdn still…
-
-squid
------
-It seems the squid configuration moved from /etc/squid3 to /etc/squid.  postinst
-script takes care of moving the files, but we should eventually:
-1) move them in our git repo too
-2) delete /etc/squid3 from the hosts
-3) install squid instead of squid3 in update_jdn (once all hosts are upgraded) - that's going to mark the package as manually installed
-4) apt purge squid3
 
 problems
 --------
-no amd64 kernel for i386? manually done, needs to go into update_jdn
-pb6+16 are not running in the future anymore
+- none known
 
 todo for upgrades
 -----------------
 test jenkins-test-vm upgrade before doing jenkins
 	-> cucumber problems reported by fil
-resolve issues on pb2+6+12+16 :)
+resolve issues on pb2+6+12+16:
+	no amd64 kernel for i386? manually done, needs to go into update_jdn
+	compare sshd_config from stretch with the one we're using (from jessie)
 wait with upgrading armhf nodes until next week as vagrant has no time until then
 
+
+to be done once all hosts run stretch: squid
+--------------------------------------------
+It seems the squid configuration moved from /etc/squid3 to /etc/squid.  postinst
+script takes care of moving the files, but we should eventually:
+1) move them in our git repo too
+2) delete /etc/squid3 from the hosts
+3) install squid instead of squid3 in update_jdn (once all hosts are upgraded) - that's going to mark the package as manually installed
+4) apt purge squid3
+
+to be done once all hosts run stretch: sshd_config
+--------------------------------------------------
+/etc/ssh/sshd_config - the currently running one is the one from jessie, we should update_jdn to the one from stretch
+
+
 done for upgrades
 -----------------
-base upgrade of all i386 nodes, still need finishing touches as described above
+upgrade of all i386 nodes
+upgrade of jenkins-test-vm in progress

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/qa/jenkins.debian.net.git