Cycle preventing removal

2004-03-08 Thread Nathanael Nerode
* cl-uncommonsql can't be removed because it breaks cl-local-time-db * cl-local-time-db is from the cl-local-time source package (only in testing) * cl-local-time can't be removed because it breaks cl-metadata * cl-metadata is from the cl-uncommonsql source package in testing We appear to have dea

Re: Bug#236957: new upstream version is available

2004-03-08 Thread James Troup
Colin Watson <[EMAIL PROTECTED]> writes: > On Mon, Mar 08, 2004 at 08:32:01PM -0500, Daniel Jacobowitz wrote: >> On Tue, Mar 09, 2004 at 10:10:33AM +0900, Atsuhito Kohda wrote: >> > Package: ncurses >> > Version: 5.3.20030719-5 >> > Severity: wishlist >> > >> > Hi maintainer, >> > >> > In ftp://

Re: Bug#236957: new upstream version is available

2004-03-08 Thread Colin Watson
On Mon, Mar 08, 2004 at 08:32:01PM -0500, Daniel Jacobowitz wrote: > On Tue, Mar 09, 2004 at 10:10:33AM +0900, Atsuhito Kohda wrote: > > Package: ncurses > > Version: 5.3.20030719-5 > > Severity: wishlist > > > > Hi maintainer, > > > > In ftp://ftp.gnu.org/gnu/ncurses/ you can find > > 5.4 versio

Re: Bug#236957: new upstream version is available

2004-03-08 Thread Daniel Jacobowitz
On Tue, Mar 09, 2004 at 10:10:33AM +0900, Atsuhito Kohda wrote: > Package: ncurses > Version: 5.3.20030719-5 > Severity: wishlist > > Hi maintainer, > > In ftp://ftp.gnu.org/gnu/ncurses/ you can find > 5.4 version. > > Please package the latest one as possible as you can. > We need especially li

Re: Why is package X not in testing yet?

2004-03-08 Thread Colin Watson
On Mon, Mar 08, 2004 at 10:21:56PM +0100, Richard B. Kreckel wrote: > On Sat, 6 Mar 2004, Colin Watson wrote: > > Richard, do you read debian-release? If not, it would be helpful if you > > had a Mail-Followup-To: header or similar saying so. > > In other free software ecosystems it is customary t

Re: Why is package X not in testing yet?

2004-03-08 Thread Richard B. Kreckel
On Sat, 6 Mar 2004, Colin Watson wrote: [...] > Richard, do you read debian-release? If not, it would be helpful if you > had a Mail-Followup-To: header or similar saying so. In other free software ecosystems it is customary to CC the poster when replying. Even if he/she is known to be the list a

Re: status of postgresql for sarge?

2004-03-08 Thread Kurt Roeckx
On Mon, Mar 08, 2004 at 02:58:07PM +, Oliver Elphick wrote: > > In order to cure this, we need to change the woody package, either to > force it to do a dump in the prerm or to save all the shared libraries > it needs to go with its binaries for use by the new package's postinst. Afaik, It's

Re: status of postgresql for sarge?

2004-03-08 Thread Martin Schulze
Oliver Elphick wrote: > In order to cure this, we need to change the woody package, either to > force it to do a dump in the prerm or to save all the shared libraries > it needs to go with its binaries for use by the new package's postinst. > > Even then, there will be problems for those who don't

Re: status of postgresql for sarge?

2004-03-08 Thread Oliver Elphick
On Mon, 2004-03-08 at 10:15, Martin Schulze wrote: > Re new upstream package, it would be *very* nice if you would be able > to test and smoothen the upgrade path from woody-pg to sarge-pg (sid-pg) > as well. I've done a release upgrade before which resulted in a complete > desaster with the daemo

Re: Packages in final: for several days

2004-03-08 Thread Colin Watson
On Mon, Mar 08, 2004 at 03:15:39PM +0100, Björn Stenberg wrote: > Colin Watson wrote: > > Yep. Every day update_out.py calculates new Packages files for > > non-US/testing, but they never actually get applied to the testing suite > > in the non-US database. > > Right, but how come that is affectin

Re: Packages in final: for several days

2004-03-08 Thread Björn Stenberg
Colin Watson wrote: > Yep. Every day update_out.py calculates new Packages files for > non-US/testing, but they never actually get applied to the testing suite > in the non-US database. Right, but how come that is affecting packages which have already moved out of non-US, such as gutenbook? I can

Re: Packages in final: for several days

2004-03-08 Thread Colin Watson
On Mon, Mar 08, 2004 at 02:56:37PM +0100, Björn Stenberg wrote: > Colin Watson wrote: > > In other words, they're in both main and non-US. non-US isn't running at > > the moment; please ignore weirdnesses related to it. > > Ok. So basically all packages that are still listed in the (outdate) > non

Re: Packages in final: for several days

2004-03-08 Thread Björn Stenberg
Colin Watson wrote: > In other words, they're in both main and non-US. non-US isn't running at > the moment; please ignore weirdnesses related to it. Ok. So basically all packages that are still listed in the (outdate) non-US archive are held back because of it? I just want to be able to print s

Re: Packages in final: for several days

2004-03-08 Thread Colin Watson
On Mon, Mar 08, 2004 at 02:38:09PM +0100, Björn Stenberg wrote: > Colin Watson wrote: > > On Wed, Mar 03, 2004 at 11:16:15AM +0100, Björn Stenberg wrote: > > > I saved update_output.txt from yesterday and compared it to todays' > > > file. It turns out several packages are in the final: line for bo

Re: Packages in final: for several days

2004-03-08 Thread Björn Stenberg
Colin Watson wrote: > On Wed, Mar 03, 2004 at 11:16:15AM +0100, Björn Stenberg wrote: > > I saved update_output.txt from yesterday and compared it to todays' > > file. It turns out several packages are in the final: line for both > > days. gutenbook and pgpgpg are two examples. > > They're in non-

Re: status of postgresql for sarge?

2004-03-08 Thread Martin Schulze
Oliver Elphick wrote: > On Sun, 2004-03-07 at 00:19, Colin Watson wrote: > > > According to Oliver (the primary maintainer) there will be a new > > > bugfix upstream release soon, which would be a good opportunity to > > > upload an updated package. > > > > It would be very nice to have this upda