Bug#879786: apt-secure man page needs to provide useful pointers for Release file info changes

2019-07-07 Thread Jan Braun
Package: apt Version: 1.8.2 Followup-For: Bug #879786 Dear Maintainer, I've had to spend far too much time to figure this out due the release yesterday. I'm running apt-get, and apt-get tells me nothing except | E: The repository 'http://security.debian.org testing/updates Release' no longer

Bug#879786: apt-secure man page needs to provide useful pointers for Release file info changes

2018-11-07 Thread Jesse Hathaway
> IMO, the right answer would be to run "apt update" and confirm the > change when asked. I find it strange to recommend another tool, when there is a flag to confirm the change with apt-get. If the intent is to deprecate using apt-get interactively entirely, then that should be done at a more

Bug#879786: apt-secure man page needs to provide useful pointers for Release file info changes

2018-11-07 Thread Julian Andres Klode
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 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

Bug#879786: apt-secure man page needs to provide useful pointers for Release file info changes

2018-11-07 Thread Jesse Hathaway
On Wed, Nov 7, 2018 at 12:12 PM Julian Andres Klode 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'

Bug#879786: apt-secure man page needs to provide useful pointers for Release file info changes

2018-11-07 Thread Julian Andres Klode
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

Bug#879786: apt-secure man page needs to provide useful pointers for Release file info changes

2018-11-07 Thread Jesse Hathaway
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

Bug#879786: apt-secure man page needs to provide useful pointers for Release file info changes

2018-07-24 Thread Yuri D'Elia
Package: apt Version: 1.6.3 Followup-For: Bug #879786 I second that apt-secure should mention the use of "apt" and, in detail, "apt-get --allow-releaseinfo-change" as well (pointing to apt-get for more details on the various finger-graned flags) since the manpage of apt(1) doesn't include any

Bug#879786: apt-secure man page needs to provide useful pointers for Release file info changes

2017-10-25 Thread Julian Andres Klode
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): >

Bug#879786: apt-secure man page needs to provide useful pointers for Release file info changes

2017-10-25 Thread js jb
nks,--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 a

Bug#879786: apt-secure man page needs to provide useful pointers for Release file info changes

2017-10-25 Thread js
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. For this I have