Bug#879786: apt-secure man page needs to provide useful pointers for Release file info changes
On Wed, Nov 07, 2018 at 12:21:01PM -0600, Jesse Hathaway wrote:
> On Wed, Nov 7, 2018 at 12:12 PM Julian Andres Klode <jak@debian.org> wrote:
> >
> > On Wed, Nov 07, 2018 at 10:50:05AM -0600, Jesse Hathaway wrote:
> > > Just ran into this issue with chrome package from Google:
> > >
> > > E: Repository 'http://dl.google.com/linux/chrome/deb stable
> > > Release' changed its 'Origin' value from 'Google, Inc.' to 'Google
> > > LLC'
> > > N: This must be accepted explicitly before updates for this
> > > repository can be applied. See apt-secure(8) manpage for details.
> > >
> > > Rather than adding information to apt-secure's man page, I think it
> > > would be more helpful to output the command the user needs to accept
> > > the change:
> > >
> > > E: Repository 'http://dl.google.com/linux/chrome/deb stable
> > > Release' changed its 'Origin' value from 'Google, Inc.' to 'Google
> > > LLC'
> > > N: If you would like to accept this change, please rerun apt-get
> > > update with the `--allow-releaseinfo-change` flag
> >
> > If you run it interactive, you get asked directly, and don't need
> > the flag. Just recommending the flag is probably not a good idea,
> > as it makes people add them to update scripts without thinking.
>
> What do you mean by running interactively? I ran `apt-get update` in
> my terminal and I was not prompted, it just showed those error
> messages.
Oh, you might have to use apt instead of apt-get.
> I also don't see why showing the flag is not helpful, that
> was the only way I was able to confirm the change?
IMO, the right answer would be to run "apt update" and confirm the
change when asked.
--
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer i speak de, en
Reply to: