On Jan 22, 2008 1:51 AM, Lucas Nussbaum wrote:
> On 21/01/08 at 13:53 +0100, Michael Bienia wrote:
> > On 2008-01-20 23:19:58 +0100, Lucas Nussbaum wrote:
> > > I'm not 100% sure it's a good idea, but what about doing the same for
> > > packages which aren't a new upstream release? If the Debian ma
On 21/01/08 at 13:53 +0100, Michael Bienia wrote:
> On 2008-01-20 23:19:58 +0100, Lucas Nussbaum wrote:
> > I'm not 100% sure it's a good idea, but what about doing the same for
> > packages which aren't a new upstream release? If the Debian maintainer
> > uploaded a new debian-specific version, it
On 2008-01-20 23:19:58 +0100, Lucas Nussbaum wrote:
> I'm not 100% sure it's a good idea, but what about doing the same for
> packages which aren't a new upstream release? If the Debian maintainer
> uploaded a new debian-specific version, it's likely to be a bug-fixing
> upload. It might be harder
On 20/01/08 at 18:43 +0100, Martin Pitt wrote:
> Hi,
>
> Wouter Stomp [2008-01-19 21:13 +0100]:
> > Currently the automatic import of new packages from debian stops at
> > the debianimportfreeze, which is very early in the release schedule.
> > After that, sync requests have to be filed and acknow
Hi,
Wouter Stomp [2008-01-19 21:13 +0100]:
> Currently the automatic import of new packages from debian stops at
> the debianimportfreeze, which is very early in the release schedule.
> After that, sync requests have to be filed and acknowledged, which is
> a lot of unneccessary work I think and c
On Jan 19, 2008 9:13 PM, Wouter Stomp <[EMAIL PROTECTED]> wrote:
> Currently the automatic import of new packages from debian stops at
> the debianimportfreeze,
A small clarification: by new I mean new as in not previously in the
archives, not newer versions.
Wouter.
--
Ubuntu-devel-discuss mai
