On Jan 19, 2008 9:13 PM, Wouter Stomp <wouterstomp@gmail.com> 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 mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

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 causes packages for which no
> requests are filed not to be in ubuntu, while they could have been.
> Would it be possible to automatically sync new packages in debian
> unstable until featurefreeze (or even later)?

Technically this is not a problem at all.

For discussing/changing the policy I'd recommend you to raise this
with the Technical Board.

</officialy speaking>

My own opinion: I tend to agree. It would steamline the job of
requesters and archive admins, and completely new packages are mostly
harmless. Since universe already has a magnitude more packages that
MOTUs can handle, it doesn't make the maintainability situation
significantly worse, eases source package renaming/lost build deps,
etc.

Martin

--
Martin Pitt http://www.piware.de
Ubuntu Developer http://www.ubuntu.com
Debian Developer http://www.debian.org
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

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 acknowledged, which is
> > a lot of unneccessary work I think and causes packages for which no
> > requests are filed not to be in ubuntu, while they could have been.
> > Would it be possible to automatically sync new packages in debian
> > unstable until featurefreeze (or even later)?
>
> Technically this is not a problem at all.
>
> For discussing/changing the policy I'd recommend you to raise this
> with the Technical Board.
>
> </officialy speaking>
>
> My own opinion: I tend to agree. It would steamline the job of
> requesters and archive admins, and completely new packages are mostly
> harmless. Since universe already has a magnitude more packages that
> MOTUs can handle, it doesn't make the maintainability situation
> significantly worse, eases source package renaming/lost build deps,
> etc.

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 to automatize, but still...
--
| Lucas Nussbaum
| lucas@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr GPG: 1024D/023B3F4F |
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

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 to automatize, but still...

The new revision might introduce a versioned build-dependency on an
other package with a new upstream version and we would either have to
complete the transition or undo the change.

Michael

--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

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's likely to be a bug-fixing
> > upload. It might be harder to automatize, but still...
>
> The new revision might introduce a versioned build-dependency on an
> other package with a new upstream version and we would either have to
> complete the transition or undo the change.

Ok ; but, it isn't much harder to import new debian-specific versions
provided that they are still installable and buildable in Ubuntu.
--
| Lucas Nussbaum
| lucas@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr GPG: 1024D/023B3F4F |

--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

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 maintainer
> > > uploaded a new debian-specific version, it's likely to be a bug-fixing
> > > upload. It might be harder to automatize, but still...
> >
> > The new revision might introduce a versioned build-dependency on an
> > other package with a new upstream version and we would either have to
> > complete the transition or undo the change.
>
> Ok ; but, it isn't much harder to import new debian-specific versions
> provided that they are still installable and buildable in Ubuntu.

It's precisely that test that makes it a manual process. For the
most part, until feature freeze, any package that builds, installs,
and doesn't break anything is suitable for sync, and several people
watch the variation and request syncs to reduce variance. The
downside of the manual process is that some packages do not get needed
attention. After feature freeze, the RC bug checker is used to try to
get all RC bugs closed in Debian also closed in Ubuntu, perhaps from a
sync, maybe a merge, and sometimes pulling minimal patches to address
the specific issue from the Debian package and adding them to the
exisitng Ubuntu package.

I believe the solution to this is more hands and more eyes. On
the other hand, if there were sufficient resources available to
autobuild all Debian updates for non-modified packages against Ubuntu
and automate the installation/upgrade/removal testing, this could be a
source of sync candidates (although it may still be nice to have a
human check to make sure nothing went wrong).

--
Emmet HIKORY

--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss