Lucas Nussbaum writes:
> It is likely that other tools and scripts are affected. And there might
> also be some affected packages (debmirror? APT proxies?).
Certainly not debmirror. That alway had to cope with Arch:all packages
being listed in each archs Packages file and the same version in
sta
On Tue, 15 Dec 2009, Andreas Tille wrote:
> On Sun, Dec 13, 2009 at 06:32:56PM -0800, Don Armstrong wrote:
> > There have always been possible to have several versions of the same
> > binary package in the same suite (for different archit
On Sun, Dec 13, 2009 at 06:32:56PM -0800, Don Armstrong wrote:
> There have always been possible to have several versions of the same
> binary package in the same suite (for different architectures) so this
> shouldn't come as a shock to anyone.
But in this case the different versions of one packa
On 11964 March 1977, Lucas Nussbaum wrote:
> The result of that change is that the structure of the Sources and
> Packages files have changed: before, there was only one version of each
> source or binary package in each suite (unstable, testing, stable). There
> can now be several versions of the
On Mon, 14 Dec 2009, Lucas Nussbaum wrote:
> The result of that change is that the structure of the Sources and
> Packages files have changed: before, there was only one version of
> each source or binary package in each suite (unstable, testing,
> stable). There can now be several versions of the
This one time, at band camp, Lucas Nussbaum said:
> So, where should we go from there? Our options are:
> - find & fix all the occurences of the problem ASAP. Please report it
> if you notice strange things about version numbers or other data
> that possibly comes from Sources/Packages.
> - ask
Hi,
Ftpmasters have done a change that possibly has very large side effects.
>From d-d-a:
> Tracking arch all packages
> --
> #246992 asked us to not delete arch all packages before the
> corresponding (if any) arch any packages are available for all
> architectures. Examp
7 matches
Mail list logo
