Your message dated Sat, 12 Jan 2019 19:55:32 +0100
with message-id <20190112185532.j2gpllmsppjkd...@jarry.cc>
and subject line Re: Bug#919078: buildbot: upgrading a buildmaster from 0.8
fails the hard way
has caused the Debian Bug report #919078,
regarding buildbot: upgrading a buildmaster from 0.8 fails the hard way
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
919078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919078
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: buildbot
Version: 1.6.0-1
Severity: normal
Dear Maintainer,
when I try to upgrade from stretch to buster a system with buildbot installed
and a buildmaster service configured:
apt update && apt dist-upgrade
after upgrading to buildbot 1.x it tries to configure it, but the buildmaster
service fails to start therefore apt stops the hard way (with a broken install)
to make the buster migration run smooth, it would be great if buildbot on
upgrading from 0.8 to 1.x were to:
1) disable the service, so that apt can complete the dist-upgrade command
2) prominently display a message that the upgrade from buildbot 0.8 to 1.x
requires manual actions:
- fix the buildmaster config syntax
- wipe the DB
- invoke buildbot upgrade-master /var/lib/buildbot/masters/xxx
- and manually re-enable builmaster service
see:
http://docs.buildbot.net/latest/manual/upgrading/nine-upgrade.html#upgrading-to-nine
3) point out that in buster we don't have the buildbot Web Status widget
anymore, and suggest a workaround
Thanks !
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8),
LANGUAGE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages buildbot depends on:
ii python3-buildbot 1.6.0-1
buildbot recommends no packages.
buildbot suggests no packages.
-- Configuration Files:
/etc/default/buildmaster changed [not included]
/etc/init.d/buildmaster changed [not included]
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.7.0-2
Hi Paolo,
Thank you for your bug report.
2019-01-12, Paolo Greppi:
> to make the buster migration run smooth, it would be great if buildbot on
> upgrading from 0.8 to 1.x were to:
> 1) disable the service, so that apt can complete the dist-upgrade command
> 2) prominently display a message that the upgrade from buildbot 0.8 to 1.x
> requires manual actions:
> - fix the buildmaster config syntax
> - wipe the DB
> - invoke buildbot upgrade-master /var/lib/buildbot/masters/xxx
> - and manually re-enable builmaster service
> see:
> http://docs.buildbot.net/latest/manual/upgrading/nine-upgrade.html#upgrading-to-nine
> 3) point out that in buster we don't have the buildbot Web Status widget
> anymore, and suggest a workaround
All this should be fixed in the latest release which was uploaded to
unstable yesterday. It should be available in buster in a few days.
See the git log for more details:
https://salsa.debian.org/python-team/applications/buildbot/commits/debian/master
--
Robin
--- End Message ---
