| 1 |
mini-buildd (2.3.1) unstable; urgency=medium |
| 2 |
|
| 3 |
With 2.2.x, mini-buildd no longer uses ``numix-icon-theme`` |
| 4 |
but provides a custom icon theme (in |
| 5 |
``/usr/lib/python3/dist-packages/mini_buildd/static/icons``). |
| 6 |
|
| 7 |
Until version 2.2.2, this change was not properly handled, |
| 8 |
causing the symlink to just stay and the new custom icon |
| 9 |
theme to be installed to the ``numix-icon-theme`` package |
| 10 |
path on upgrade. |
| 11 |
|
| 12 |
Version 2.2.2 fixes this. However, if you had 2.2.0|1 installed |
| 13 |
previously, you may end with cruft files in |
| 14 |
``/usr/share/icons/Numix/32`` that will not be handled by dpkg. |
| 15 |
|
| 16 |
You may want to remove these superfluous files manually. |
| 17 |
|
| 18 |
-- Stephan Sürken <[email protected]> Sun, 23 Jun 2024 08:57:44 +0200 |
| 19 |
|
| 20 |
mini-buildd (2.1.11) experimental; urgency=medium |
| 21 |
|
| 22 |
Support for deprecated ``<host>:<port>`` endpoint syntax has been |
| 23 |
removed for good. You will need to update all command line arguments |
| 24 |
(like ``-E,--http-endpoint``) or values in models (like in |
| 25 |
``Daemon.ftpd_bind``, ``Remote``) now if not already done. |
| 26 |
|
| 27 |
-- Stephan Sürken <[email protected]> Mon, 11 Dec 2023 18:26:22 +0100 |
| 28 |
|
| 29 |
mini-buildd (2.1.6) experimental; urgency=medium |
| 30 |
|
| 31 |
Deprecated ``-v,--verbose,-q,--quiet`` options are now gone |
| 32 |
for good (for all python-based command line tools). You really |
| 33 |
now need to remove them or replace by resp. ``-l,--log-level`` |
| 34 |
option. |
| 35 |
|
| 36 |
Deprecated ``-W,--httpd-bind`` option of ``mini-buildd`` is |
| 37 |
now gone for good. You really now need to remove them or replace |
| 38 |
by resp. ``-E,--http-endpoint`` option. |
| 39 |
|
| 40 |
-- Stephan Sürken <[email protected]> Fri, 15 Sep 2023 14:24:07 +0200 |
| 41 |
|
| 42 |
mini-buildd (1.9.111) unstable; urgency=medium |
| 43 |
|
| 44 |
While 2.0.x should be fully upgradeable from 1.0.x w/o any changes |
| 45 |
required, please see the manual's ``roadmap`` document for a |
| 46 |
checklist of higly recommended post upgrade maintenance. |
| 47 |
|
| 48 |
-- Stephan Sürken <[email protected]> Mon, 19 Dec 2022 07:25:31 +0100 |
| 49 |
|
| 50 |
mini-buildd (1.0.5) unstable; urgency=medium |
| 51 |
|
| 52 |
This version upgrade unfortunately requires some manual |
| 53 |
maintenance: |
| 54 |
|
| 55 |
(1) "sudo chroot workaround" removed: |
| 56 |
|
| 57 |
This version removes the "sudo workaround" for the per-build |
| 58 |
chroot setup (as the resp. bug #608840 in 'sbuild' is now |
| 59 |
fixed). |
| 60 |
|
| 61 |
You must RE-CREATE ALL CHROOTS ONCE NOW to get rid of the |
| 62 |
workaround's '/etc/sudoers' file in chroots, which imposes a |
| 63 |
potential security risk. |
| 64 |
|
| 65 |
FWIW: These chroots will all be automatically disabled in the |
| 66 |
next 'check' run (which automatically is done weekly). All |
| 67 |
1.0.x versions will still remove the '/etc/sudoers' in |
| 68 |
snapshots prior to builds (i.e., you keep the same level of |
| 69 |
security as before even if you do nothing until the chroot is |
| 70 |
actually disabled). |
| 71 |
|
| 72 |
To re-create chroots, enter the web configuration frontend as |
| 73 |
'admin' user, and first run 'Remove' and then 'PCA' on each |
| 74 |
chroot instance. |
| 75 |
|
| 76 |
(2) Updated default snippets for eatmydata 82: |
| 77 |
|
| 78 |
The new eatmydata 82 (sid/jessie) breaks the old eatmydata |
| 79 |
shell snippet (which is automatically added for newly created |
| 80 |
Distributions to the -- otherwise freely configurable -- |
| 81 |
distribution's "chroot setup script"). |
| 82 |
|
| 83 |
This breakage usually only means eatmydata is not enabled in |
| 84 |
builds (which may dramatically increase your build times), and |
| 85 |
ugly error messages in build logs. |
| 86 |
|
| 87 |
To update the snippet, enter the web configuration frontend as |
| 88 |
'admin' user, and fix up (or entirely remove) the snippet for |
| 89 |
each distribution instance from "Chroot setup options/Chroot |
| 90 |
setup script" (for your cut&paste pleasure, an updated snippet |
| 91 |
is shown there in the example script). |
| 92 |
|
| 93 |
Note that you also need to 'PCA' all depending repositories |
| 94 |
afterwards. |
| 95 |
|
| 96 |
-- Stephan Sürken <[email protected]> Wed, 22 Oct 2014 14:01:36 +0000 |
| 97 |
|
| 98 |
mini-buildd (1.0.0) unstable; urgency=low |
| 99 |
|
| 100 |
An 0.8.x (mini-dinstall/flat/multipackage) repository is |
| 101 |
_not_ automatically migrated into the new 1.0 |
| 102 |
(reprepro/pool/migration) one. If you have upgraded from |
| 103 |
0.8.x, your complete "old" repository will still be accessible |
| 104 |
like before (you can not build for it anymore, though). |
| 105 |
|
| 106 |
It's recommendend to just keep the old repository (located in |
| 107 |
'$HOME/rep/*') as-is, and use it as "Source" in your new |
| 108 |
(replacing) 1.0.x setup (located in '$HOME/repositories/*'). |
| 109 |
|
| 110 |
In case you actually want to migrate your packages, please |
| 111 |
check out the resp. Admin Manual section: |
| 112 |
|
| 113 |
http://localhost:8066/doc/admin.html#migrate-packages-from-0-8-x |
| 114 |
|
| 115 |
-- Stephan Sürken <[email protected]> Thu, 23 Oct 2014 11:11:44 +0000 |