[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Broken Potato Packages??? Build Daemon?



On Tue, Nov 07, 2000 at 05:11:23PM +0100, Alain Schroeder wrote:
> I just wanted to install some stuff on my PowerPC System (Power Mac
> 8200) and I had to recognize a lot of broken Packages. I just compiled
> two manually and I had absolutly _no_ problem doing it (gnome-print -
> breaks at least gnumeric and gnumeric breaks task-gnome-apps, librep5 -
> needed for sawmill).

READ the mailing list archives!  Please!

librep5 was the result of an ftpadmin screwup.  It will be fixed when
2.2r1 is released.

I do not remember the problem with gnome-print, but it was nontrivial. 
Just because a package "seems to compile fine" does not mean it is
correct - there are also, for instance, problems with build-time
dependencies.  I think gnome-print was one of these.

Also, bear in mind, you are running stable.  No more changes are
occuring for stable at this point, until 2.2r1, and very few then.

i.e., most of these will not be fixed in stable.  librep should be an
exception.

> There is no netscape-base-47, so that the packages netscape and
> communicator are broken. Mozilla is broken, because there is no libnspr
> 
> lftp ftp.debian.org:/debian/dists/potato/main/binary-powerpc> find | grep M14
> web/mozilla_M14-2.deb
> lftp ftp.debian.org:/debian/dists/potato/main/binary-powerpc> 

I don't think there's netscape binary packages either.

I have no idea why libnspr is missing.  It exists in unstable.  If it
bugs you, sorry, use unstable.

I'm amazed we got potato out the door at all.  I'm not worrying over a
comparatively small number of broken packages - and M14 is unstable
enough on powerpc to be unusable, anyway.

Dan

/--------------------------------\  /--------------------------------\
|       Daniel Jacobowitz        |__|        SCS Class of 2002       |
|   Debian GNU/Linux Developer    __    Carnegie Mellon University   |
|         dan@debian.org         |  |       dmj+@andrew.cmu.edu      |
\--------------------------------/  \--------------------------------/



Reply to: