Re: Julian Andres Klode
> Default Acquire::AllowReleaseInfoChange::Suite to "true"
>
> Closes: #931566
Thanks!
Christoph
On Mon, Apr 19, 2021 at 06:31:48PM +0200, Julien Cristau wrote:
> Can we defer these until after the AllowReleaseInfoChange change is
> out, please?
Done. I uploaded 1.8.2.3 with that one change as requested, and created a
pu bug for it.
--
debian developer - deb.li/jak | jak-linux.org - free
On Mon, Apr 19, 2021 at 06:28:05PM +0200, Julian Andres Klode wrote:
> On Mon, Apr 19, 2021 at 06:08:23PM +0200, Julien Cristau wrote:
> > On Mon, Apr 19, 2021 at 06:01:18PM +0200, Julian Andres Klode wrote:
> > > I see. Nobody pinged me since then, but it is indeed fixed in the
> > > 1.8.5 stable
On Mon, Apr 19, 2021 at 06:08:23PM +0200, Julien Cristau wrote:
> On Mon, Apr 19, 2021 at 06:01:18PM +0200, Julian Andres Klode wrote:
> > I see. Nobody pinged me since then, but it is indeed fixed in the
> > 1.8.5 stable update that at least one release team member was
> > not exited about.
> >
On Mon, Apr 19, 2021 at 06:01:18PM +0200, Julian Andres Klode wrote:
> I see. Nobody pinged me since then, but it is indeed fixed in the
> 1.8.5 stable update that at least one release team member was
> not exited about.
>
> https://salsa.debian.org/apt-team/apt/-/compare/1.8.2.2...1.8.5
>
> So
On Mon, Apr 19, 2021 at 05:40:09PM +0200, Christoph Berg wrote:
> Re: Julian Andres Klode
> > > We're getting close to the release of bullseye and it has been brought
> > > to my attention that this bug is still unfixed in buster. Once we
> > > release bullseye, this bug is going to run havoc for
Re: Julian Andres Klode
> > We're getting close to the release of bullseye and it has been brought
> > to my attention that this bug is still unfixed in buster. Once we
> > release bullseye, this bug is going to run havoc for our buster users.
>
> That's not accurate. This is _only_ a problem for
On Sun, Apr 18, 2021 at 10:20:19PM +0200, Paul Gevers wrote:
> Hi Julian, David, SRM,
>
> On Mon, 8 Jul 2019 09:11:48 +0200 Christoph Berg wrote:
> > Fwiw, I think this needs fixing in buster, not just in unstable.
>
> We're getting close to the release of bullseye and it has been brought
> to
Hi Julian, David, SRM,
On Mon, 8 Jul 2019 09:11:48 +0200 Christoph Berg wrote:
> Fwiw, I think this needs fixing in buster, not just in unstable.
We're getting close to the release of bullseye and it has been brought
to my attention that this bug is still unfixed in buster. Once we
release
Re: Paul Wise 2019-09-02
<68737fa6fe19d3c2a71beadefbe69c661dd4d271.ca...@debian.org>
> I recently had a similar issue with the backports repos:
>
> E: Repository 'https://incoming.debian.org/debian-buildd
> buildd-stretch-backports-sloppy InRelease' changed its default priority for
>
On Sun, 7 Jul 2019 20:39:10 +0200 Christoph Berg wrote:
> I and #debian-devel in general were pretty surprised that our "buster"
> systems couldn't properly "apt-get update" anymore today:
I recently had a similar issue with the backports repos:
E: Repository
On Fri, Jul 12, 2019 at 04:52:36PM +0200, Julian Andres Klode wrote:
> On Tue, Jul 09, 2019 at 03:31:07PM +0200, David Kalnischkies wrote:
> > On Mon, Jul 08, 2019 at 12:19:36PM +0200, Julian Andres Klode wrote:
> > Anyway, that apt is enforcing the metadata isn't changing is a security
> >
On Tue, Jul 09, 2019 at 03:31:07PM +0200, David Kalnischkies wrote:
> On Mon, Jul 08, 2019 at 12:19:36PM +0200, Julian Andres Klode wrote:
> > Anyway, this was not my thing so I might be misrepresenting or missing
> > things :)
>
> First of all: I am happy that I still manage to "break the world"
Re: David Kalnischkies 2019-07-10 <20190710100502.yoe2umfxyiuglaw2@crossbow>
> http://deb.devuan.org/devuan/dists/stable/Release
> http://deb.devuan.org/merged/dists/stable/Release
>
> The two release pockets differ by Suite only.
Hi,
this bug is not about fixing problems that devuan and the
On Tue, Jul 09, 2019 at 06:52:58PM +0200, Julien Cristau wrote:
> I think overall what you're trying to do here (the whole "notify the
> user they're out of date" thing) does not belong in apt. IMO it belongs
> in higher level tools that are going to heavily depend on the use case
> and so
On Tue, Jul 9, 2019 at 15:55:02 +0200, Christoph Berg wrote:
> Re: David Kalnischkies 2019-07-09 <20190709133107.gvib2ibj6w36j447@crossbow>
> > A Release file can declare that it will "soon" change its the value of
> > a field to foo and apt clients can notify users about this so
>
> Fwiw, I
Re: David Kalnischkies 2019-07-09 <20190709133107.gvib2ibj6w36j447@crossbow>
> A) For a user with "debian stable" in sources.list the change of the
> Codename from buster to bullseye is a giant leap which should not
> be done carelessly or even automatically in the background.
I agree that
On Mon, Jul 08, 2019 at 12:19:36PM +0200, Julian Andres Klode wrote:
> Anyway, this was not my thing so I might be misrepresenting or missing
> things :)
First of all: I am happy that I still manage to "break the world" (FSVO
world) – in other words that is "my thing" , but I mostly forgot about
On Mon, Jul 08, 2019 at 11:50:49AM +0200, Julien Cristau wrote:
> On Mon, Jul 8, 2019 at 11:41:55 +0200, Julian Andres Klode wrote:
>
> > On Mon, Jul 08, 2019 at 10:17:27AM +0200, Julien Cristau wrote:
> > > Control: severity -1 serious
> > >
> > > On Mon, Jul 08, 2019 at 09:11:48AM +0200,
On Mon, Jul 8, 2019 at 11:41:55 +0200, Julian Andres Klode wrote:
> On Mon, Jul 08, 2019 at 10:17:27AM +0200, Julien Cristau wrote:
> > Control: severity -1 serious
> >
> > On Mon, Jul 08, 2019 at 09:11:48AM +0200, Christoph Berg wrote:
> > > Control: tags -1 buster sid
> > >
> > > Re: To
Re: Julian Andres Klode 2019-07-08 <20190708113658.ga10...@debian.org>
> We likely do not want to allow arbitrary changes of Suite. One
> option is to introduce a new field that specifies that the Suite
> field will change to something else soon, and a field to indicate
> release notes for that
On Mon, Jul 08, 2019 at 10:17:27AM +0200, Julien Cristau wrote:
> Control: severity -1 serious
>
> On Mon, Jul 08, 2019 at 09:11:48AM +0200, Christoph Berg wrote:
> > Control: tags -1 buster sid
> >
> > Re: To Debian Bug Tracking System 2019-07-07
> > <20190707183910.ga22...@msg.df7cb.de>
> > >
On Mon, Jul 08, 2019 at 11:19:28AM +0200, Andreas Beckmann wrote:
> Followup-For: Bug #931566
> Control: tag -1 experimental
>
> IMHO, the intention behind this change is good.
> The implementation was completely untested. Well, it's kind of hard to
> properly
Followup-For: Bug #931566
Control: tag -1 experimental
IMHO, the intention behind this change is good.
The implementation was completely untested. Well, it's kind of hard to
properly test such a change.
The documentation is not really helpful.
I initially thought this was caused by my rather
Control: severity -1 serious
On Mon, Jul 08, 2019 at 09:11:48AM +0200, Christoph Berg wrote:
> Control: tags -1 buster sid
>
> Re: To Debian Bug Tracking System 2019-07-07
> <20190707183910.ga22...@msg.df7cb.de>
> > Please consider setting Acquire::AllowReleaseInfoChange::Suite "true";
>
>
Control: tags -1 buster sid
Re: To Debian Bug Tracking System 2019-07-07
<20190707183910.ga22...@msg.df7cb.de>
> Please consider setting Acquire::AllowReleaseInfoChange::Suite "true";
Fwiw, I think this needs fixing in buster, not just in unstable.
Christoph
Package: apt
Version: 1.8.1
Severity: important
Hi,
I and #debian-devel in general were pretty surprised that our "buster"
systems couldn't properly "apt-get update" anymore today:
+ apt-get update
Get:1 http://mirror.hetzner.de/debian/packages buster InRelease [118 kB]
Get:2
28 matches
Mail list logo
