On 2015-09-13, Paul van der Vlis <p...@vandervlis.nl> wrote: > Op 12-09-15 om 22:21 schreef Liam O'Toole: >> On 2015-09-11, Paul van der Vlis <p...@vandervlis.nl> wrote: >>> Op 09-09-15 om 23:43 schreef Liam O'Toole: >>>> On 2015-09-09, Paul van der Vlis <p...@vandervlis.nl> wrote: >>>>> Op 09-09-15 om 12:20 schreef Liam O'Toole: >>>>> >>>>>> If you use flashplayer-mozilla from deb-multimedia, then you get updates >>>>>> automatically. >>>>> >>>>> When you use cron, you get updates automatically too. See my other post. >>>> >>>> I saw that, thanks. I prefer to manage updates through APT. Each to his >>>> own. >>> >>> You prefer to get updates from a place, what gave many problems in the past. >>> >>>>>> Conflicts are avoided by pinning the deb-multimedia repository. >>>>> >>>>> I think this is complex to do right. >>>>> >>>>> My experience: deb-multimedia in sources.list gives problems. >>>>> See: https://wiki.debian.org/DebianMultimedia/FAQ#Common_issues >>>>> >>>>> When I need a package from deb-multimedia, I use wget and dpkg. >>>> >>>> I've been using Flash from deb-multimedia for years without issue (on >>>> stable releases, I grant you). I use the following pinning: >>>> >>>> Package: * >>>> Pin: release o=Unofficial Multimedia Packages >>>> Pin-Priority: 100 >>> >>> I don't know what this is doing, do you? >> >> Yes. When a package is available in both debian and deb-multimedia, the >> former is always preferred. > > And when an update of a package depends on a package what's newer then > what's available in Debian?
In those circumstances the update is held back. -- Liam
