Thanks,
"BTW, your pinning and sources.list is extreme. That's not really a sensible
thing to do and can cause a lotof trouble. "
If you can be more explicit, I'd very much appreciate the feedback.
As it is, the pinning I use is to prevent unintentional changes to nvidia
drivers, linux kernel, and to block all ubuntu packages other than the 2 codecs
not available in debian.Plus block versions of some packages, like vivaldi
browser, that no longer work well with the latest codecs.
It there's a better way to achieve these goals, I'd very much like to learn
about it.
thanks,--jack
From: Julian Andres Klode <j...@debian.org>
To: js <em2ja...@yahoo.com>; 879...@bugs.debian.org
Sent: Wednesday, October 25, 2017 4:23 PM
Subject: Re: Bug#879786: apt-secure man page needs to provide useful pointers
for Release file info changes
On Wed, Oct 25, 2017 at 04:05:24PM -0400, js wrote:
> Package: apt
> Version: 1.5
> Severity: minor
>
> Dear Maintainer,
>
> ==============================================================================================
> I use only 2 packages from ubuntu (which are not available in debian):
> chromium-codecs-ffmpeg-extra, oxideqt-codecs-extra.
The first one does not make much sense, Debian's chromium should already
contain all codecs.
> For this I have the ubuntu repository in sources.list along with an
> apt_preferences file to allow
> only those 2 packages (with priority 476 < 500 for all debian).
>
> This recently gave these errors during apt-get update:
> W: Conflicting distribution: http://archive.ubuntu.com/ubuntu devel
>InRelease (expected devel but got bionic)
> N: Repository 'http://archive.ubuntu.com/ubuntu devel InRelease' changed its
>'Version' value from '17.10' to '18.04'
> E: Repository 'http://archive.ubuntu.com/ubuntu devel InRelease' changed its
>'Suite' value from 'artful' to 'bionic'
> E: Repository 'http://archive.ubuntu.com/ubuntu devel InRelease' changed its
>'Codename' value from 'artful' to 'bionic'
> N: This must be accepted explicitly before updates for this repository can
>be applied. See apt-secure(8) manpage for details.
>
> The apt-secure man page is of no help in resolving this (see bottom).
That's somewhat true. You likely want to use apt instead of apt-get, that would
ask
the question interactively. apt-get is mostly for scripting.
BTW, your pinning and sources.list is extreme. That's not really a sensible
thing to do and can cause a lot
of trouble. Also, well, it took me a minute to clean them out for the reply -
it can only delete one line
at a time :/
--
Debian Developer - deb.li/jak | jak-linux.org - free software dev
Ubuntu Core Developer
