headers
Matt Zimmerman | 12 Aug 2005 21:45
Favicon

Resyncing the archive with the seed lists

As many of you know, the correct archive component for a given package is
determined by way of the "seed" lists[0].  However, changes to the seeds and
package dependencies do not automatically cause packages to move to a
different component.  This would be unpredictable, and so it is a manual
process.  We have a tool called "anastacia" which examines the archive and
compares it to the output of germinate[1].  The archive administrators
examine this, and make decisions about what to move and when.

At release time, this list needs to be EMPTY.  It's very long right now, so
this is a good time to review it and process as many packages as we can.

For new source packages which are requested in main, either via seeds or
package dependencies, we look for a main inclusion report at
https://wiki.ubuntu.com/UbuntuMainInclusionQueue .  If one exists and has
been reviewed, then the package can be promoted to main.  Otherwise, it is
deferred.

For new binary packages which are requested in main, whose source is already
in main, these are generally approved unless the characteristics of the new
binary package are significantly different (e.g., a security-sensitive
component such as a network server, new dependencies, etc.).

For packages in main which are no longer requested, we should discuss
whether it is appropriate to move them to universe, or add them to a seed.
Generally, if we are supporting the source package anyway, it is preferable
to have all of the binaries in the same component unless there is a good
reason to split it.  Generally, -dev, -dbg and -doc packages from sources in
main should be added to the supported seed.

The current status of this process is published twice per hour here:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Matthias Klose | 15 Aug 2005 14:11
Favicon

Re: Resyncing the archive with the seed lists

Matt Zimmerman wrote:

>  Source and binary promotions to main
>  ------------------------------------
> 
>  o atlas3: atlas3-base
>    [Reverse-Depends: python2.4-numarray]
> 
> 	python2.4-numarray [main] wants atlas3, but atlas3 has no main
> 	inclusion report.  Matthias?

fixed python2.4-numarray and python2.4-meric-ext to prefer 
lapack3/refblas3, which already is in main. needs sync from incoming 
(Aug 15).

>  o ispell-fo: aspell-fo
>    [Reverse-Depends: language-support-fo]
> 
> 	Missing report

Are explicit reports needed for each dictionary?

>  o language-support-fo: language-support-fo
>    [Reverse-Depends: Supported seed]
> 
> 	Pending report for ispell-fo dependency

sorting out the aspell dependencies with Martin.

>  o sox: sox
(Continue reading)

Permalink | Reply | 0 comments |
headers
Martin Pitt | 15 Aug 2005 10:25
Favicon
Gravatar

Re: Resyncing the archive with the seed lists

Hi!

Matt Zimmerman [2005-08-12 12:45 -0700]:
>  o gtk-qt-engine: gtk2-engines-gtk-qt
>    [Reverse-Depends: Desktop seed]
> 
> 	UbuntuMainInclusionQueue says: Request retracted, gtk-qt-engine has
> 	big problems with Cairo GTK currently, jriddell 2005-08-04
> 
> 	If this is no longer a candidate, it needs to be moved from the
> 	seeds

I could not find it in the seeds, so I assume you already removed it.

>  o ispell-fo: aspell-fo
>    [Reverse-Depends: language-support-fo]
> 
>  o language-support-fo: language-support-fo
>    [Reverse-Depends: Supported seed]
> 
> 	Pending report for ispell-fo dependency

Some language support packages are still uninstallable, I'll sort that
out soon and will also review the remaining packages.

> 
>  o qdbm: libqdbm-dev libqdbm11
>    [Reverse-Depends: libqdbm-dev]
>    [Reverse-Build-Depends: bogofilter]
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Adam Conrad | 15 Aug 2005 13:55
Gravatar

Re: Resyncing the archive with the seed lists

Martin Pitt wrote:
> 
>> o wwwconfig-common: wwwconfig-common
>>   [Reverse-Depends: moodle]
>>
>>	Missing report (should probably be avoided in moodle; Adam, please
>>	confirm)
> 
> 
> The intention of this package really makes sense, I would like to take
> a look at it and evaluate it. Unfortunately my Debian activities were
> quiet nonexistant recently (ENOTIME)... Something like this package is
> required for web applications anyway, and Sean Finney did quite good
> work on it AFAIK.

Sean hasn't touched wwwconfig-common, actually, he's been proposing and
trying to write a replacement that's actually policy compliant and
doesn't mess willy-nilly with other packages' conffiles.
wwwconfig-common, while a validly useful idea, is horribly implemented
and can cause a large number of hard-to-diagnose problems.  If there's
any way that moodle can be made to not require it, yet still install
cleanly, this would really be preferable.

Who is trying to get moodle seeded to main, and can they contact me and
see if perhaps we can work together to sort it out to not require
wwwconfig-common?

... Adam
(Continue reading)

Permalink | Reply | 0 comments |
headers
Thom May | 15 Aug 2005 17:39
Favicon

Re: Resyncing the archive with the seed lists

* Adam Conrad (adconrad <at> 0c3.net) wrote :
> Martin Pitt wrote:
> > 
> >> o wwwconfig-common: wwwconfig-common
> 
> Sean hasn't touched wwwconfig-common, actually, he's been proposing and
> trying to write a replacement that's actually policy compliant and
> doesn't mess willy-nilly with other packages' conffiles.
> wwwconfig-common, while a validly useful idea, is horribly implemented
> and can cause a large number of hard-to-diagnose problems.  If there's
> any way that moodle can be made to not require it, yet still install
> cleanly, this would really be preferable.
> 
Definitely agree with Adam here; I spent some time ripping wwwconfig-common
out of main during the hoary timescale and it was definitely the right
decision.
Cheers,
-Thom
Permalink | Reply | 0 comments |
headers
Matt Zimmerman | 17 Aug 2005 05:29
Favicon

Re: Resyncing the archive with the seed lists

On Mon, Aug 15, 2005 at 02:11:07PM +0200, Matthias Klose wrote:

> Matt Zimmerman wrote:
> 
> > o ispell-fo: aspell-fo
> >   [Reverse-Depends: language-support-fo]
> >
> >	Missing report
> 
> Are explicit reports needed for each dictionary?

If it is a new source package to enter main, then yes, it needs a report.

> 
> > o language-support-fo: language-support-fo
> >   [Reverse-Depends: Supported seed]
> >
> >	Pending report for ispell-fo dependency
> 
> sorting out the aspell dependencies with Martin.

This is still pending, any update?

> > o sox: sox
> >   [Reverse-Depends: isdnvboxclient]
> >
> >	Missing report
> 
> we should drop isdnutils, and keep isdnutils-base, ipppd, isdnlog, 
> isdnutils-doc, isdnutils-xtools
(Continue reading)

Permalink | Reply | 0 comments |
headers
Matt Zimmerman | 17 Aug 2005 05:31
Favicon

Re: Resyncing the archive with the seed lists

On Mon, Aug 15, 2005 at 10:25:42AM +0200, Martin Pitt wrote:

> Matt Zimmerman [2005-08-12 12:45 -0700]:
> >  o libdb3-util                                                           {db3}
> > 
> > 	Is this worth seeding?  We still have packages which use db3
> > 	databases.
> 
> Certainly not a big deal since the source is in main anyway.

Please seed it if you haven't already.

> >  o tdsodbc                                                           {freetds}
> > 
> > 	Its source and dependencies are already in main; should probably be
> > 	seeded.  Thoughts?
> 
> Doesn't look scary security-wise, no CANs. No objection.

Please seed if you haven't already.

> >  o ocaml-native-compilers                                              {ocaml}
> > 
> > 	Anyone know anything about ocaml?
> 
> A bit, since I maintain a package written in Ocaml, and I dealt with
> it in my university time. Ocaml programs are usually compiled into
> bytecode and are interpreted by ocaml-base, but for number crunching
> apps you can speed them up a bit by compiling it natively. Not more or
> less critical than ocaml-base, but usually bytecode is enough.
(Continue reading)

Permalink | Reply | 0 comments |
headers
bugzilla-daemon | 25 Aug 2005 17:57

[Bug 8586] swsusp fails after automatic kernel upgrade

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=8586
Ubuntu | acpi-support

mdz <at> ubuntu.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kernel-team <at> lists.ubuntu.com

------- Additional Comments From mdz <at> ubuntu.com  2005-08-25 16:57 UTC -------
(In reply to comment #4)
> On kernel upgrades, we probably need to drop something that'll disable
> hibernate. Matt, what's the best way to deal with this?

I mailed you a script which tries to heuristically determine if we'll be using a
different kernel on the next boot.  Your sentence above gave me an idea for how
to improve it even further:

Kernel upgrades already drop a file in /var/lib/update-notifier/user.d to
indicate to the user that they should reboot.  Unfortunately, I think it's dated
based on the timestamp in the .deb, and not when it is installed, but perhaps it
could still be useful

--

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
(Continue reading)

Permalink | Reply | 0 comments |

Gmane