Bug#679853: general: Too much downtime during a big dist-upgrade - avoidable with snapshots
 

* Vincent Danjean <vdanjean.ml@free.fr>, 2012-07-02, 10:19:

python-support also create symlink/compile bytecode in /var


FWIW, python-support hasn't been using /var since 2009:

$ ls -ld /var/lib/python-support
lrwxrwxrwx 1 root root 18 Jun 5 16:15 /var/lib/python-support -> /usr/lib/pymodules

--
Jakub Wilk


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120702083048.GA8788@jwilk.net">http://lists.debian.org/20120702083048.GA8788@jwilk.net

Bug#679853: general: Too much downtime during a big dist-upgrade - avoidable with snapshots
 

On 02/07/12 15:27, Alexander E. Patrakov wrote:
> The quoted solution is easier and it
> seems to work well enough. But for some reason, freedesktop folks
> invented this for desktop systems:
> http://fedoraproject.org/wiki/Features/OfflineSystemUpdates .

I think you mean "Fedora folks". freedesktop.org and Fedora are not
synonymous :-)

S


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4FF1BCD3.50900@debian.org">http://lists.debian.org/4FF1BCD3.50900@debian.org

Bug#679853: general: Too much downtime during a big dist-upgrade - avoidable with snapshots
 

]] Wouter Verhelst

> Yes, freedesktop people have given up on many useful things, which is a
> shame in my opinion (consider the fact that dbus can't be restarted on a
> running system without causing breakage).

There's no «freedesktop people». fdo is a set of fairly loosely
associated projects.

> That doesn't necessarily need to mean that Debian can't do the right
> thing, though. If indeed restart after upgrade becomes the default, then
> that could fix some similar issues. Mean time, if "short downtime"
> really is important to you, there's a workaround: don't upgrade all your
> packages with dist-upgrade, but upgrade the important packages (Apache
> and MySQL in your example) plus their dependencies first (so the list of
> packages being upgraded is much smaller, and the time between "things go
> down" and "things are up again"), and *then* do a dist-upgrade
> (upgrading everything else).

If you need short down-time, you should be using multiple hosting
locations and such anyway, so just take one host out of rotation,
upgrade it with reboots and whatnot, re-rotate it. Repeat for all the
other hosts.

--
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87bojxzy8l.fsf@xoog.err.no">http://lists.debian.org/87bojxzy8l.fsf@xoog.err.no