Re: KDE 3.1.4 Status Update -- 20031021
The current[1] status of KDE in sid is below. Hopefully the buildds will catch up soon then I can upload a new kdelibs. Is there really any reason to wait for them to catch up?
Re: KDE 3.1.4 Status Update -- 20031021
On Wed, Oct 22, 2003 at 01:54:51AM -0400, Nathanael Nerode wrote: > >The current[1] status of KDE in sid is below. Hopefully the buildds > >will catch up soon then I can upload a new kdelibs. > > Is there really any reason to wait for them to catch up? Well until kdelibs is built on all archs other KDE packages won't be compilable. I am considering making kdelibs-data arch: any due to this fact. Chris
Re: Group maintainership
On Oct 20, 2003 at 17:09, Ben Burton praised the llamas by saying: > > > I can see arguments for group maintainership of core material such as > qt, kdelibs, etc, and I have no problem whatsoever with that. However, > because this is a good solution for large core packages does not mean > it needs to be imposed upon smaller or non-core packages. > > And of course it's neither pleasant nor necessary to have one's > character called into question for resisting this imposition. I have no problem with kdesdk etc remaining maintained by just yourself. I did not expect this to be taken as a hijacking and I hope no-one else had that intention. One thing I will say is that it would be useful to have your input on packaging and policy regarding the core KDE and Qt stuff as you are probably the biggest user of them, but then I don;t see a need for you to hand over any control in order to do this. -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. pgpmpUtwZtQBW.pgp Description: PGP signature
Re: KDE 3.1.4 Status Update - 20031020
On Mon, Oct 20, 2003 at 05:10:14PM -0500, Chris Cheney wrote: > The current[1] status of KDE in sid is below. Hopefully the buildds will > catch up soon then I can upload a new kdelibs. I am not sure if mips is > ever going to be in good shape since it appears the buildd admin doesn't > care to maintain it... I'm not sure that waiting for buildds before uploading new packages is really good at this stage. If you're waiting for a particular version of kdelibs to upload kdebase, for example, then it would be better just to add a versioned build-dep to kdebase. Those can be ignored pretty efficiently by the buildds until a new version is available, and in the meantime testing can proceed by users and by other buildds. kdebase is really getting urgent. :( Cheers, -- Colin Watson [EMAIL PROTECTED]
Re: KDE 3.1.4 Status Update - 20031020
On Wed, Oct 22, 2003 at 06:11:31AM -0500, Colin Watson wrote: > On Mon, Oct 20, 2003 at 05:10:14PM -0500, Chris Cheney wrote: > > The current[1] status of KDE in sid is below. Hopefully the buildds will > > catch up soon then I can upload a new kdelibs. I am not sure if mips is > > ever going to be in good shape since it appears the buildd admin doesn't > > care to maintain it... > I'm not sure that waiting for buildds before uploading new packages is > really good at this stage. If you're waiting for a particular version of > kdelibs to upload kdebase, for example, then it would be better just to > add a versioned build-dep to kdebase. That's not the problem. the problem is that kdelibs-dev package depends on exact kdelibs4 version, and the new kdelibs-dev is binary-all and thus gets into the archive before kdelibs is compiled on that specific platform. Personally I think we should just upload all new kde packages and drop any archs that are inable[1] to get kdelibs compiled in a reasonable timeframe. [1] http://buildd.debian.org/build.php?arch=mips&pkg=kdelibs&ver=4:3.1.4-2 > kdebase is really getting urgent. :( -- Riku Voipio|[EMAIL PROTECTED] | kirkkonummentie 33 |+358 40 8476974 --+-- 02140 Espoo| | dark> A bad analogy is like leaky screwdriver |
Orphaning Packages
I have orphaned the following packages for anyone interested in adopting them: arts hdparm jasper jfsutils kdeadmin kdebase kdegraphics kdelibs kdenetwork kdepim kdeutils libboulder-perl libcflow-perl libconfigreader-perl libhtml-table-perl libnet-patricia-perl libusb meta-kde usbutils Thanks, Chris Cheney signature.asc Description: Digital signature
Re: Orphaning Packages
On Wed, Oct 22, 2003 at 01:10:02PM -0500, Chris Cheney wrote: > I have orphaned the following packages for anyone interested in adopting > them: > > arts > kdeadmin > kdebase > kdegraphics > kdelibs > kdenetwork > kdepim > kdeutils > meta-kde > > Thanks, > Chris Cheney If nobody objects, I can take over resposibility for these packages and do my best to get them ready for release. I, however, will also try to establish the maintainer group in order to avoid events like the one described above in the future. -- .''`. Martin Loschwitz Debian GNU/Linux developer : :' : [EMAIL PROTECTED][EMAIL PROTECTED] `. `'` http://www.madkiss.org/people.debian.org/~madkiss/ `- Use Debian GNU/Linux 3.0! See http://www.debian.org/ signature.asc Description: Digital signature
Re: KDE 3.1.4 Status Update - 20031020
On Wed, Oct 22, 2003 at 08:05:06PM +0300, Riku Voipio wrote: > On Wed, Oct 22, 2003 at 06:11:31AM -0500, Colin Watson wrote: > > On Mon, Oct 20, 2003 at 05:10:14PM -0500, Chris Cheney wrote: > > > The current[1] status of KDE in sid is below. Hopefully the > > > buildds will catch up soon then I can upload a new kdelibs. I am > > > not sure if mips is ever going to be in good shape since it > > > appears the buildd admin doesn't care to maintain it... > > > > I'm not sure that waiting for buildds before uploading new packages > > is really good at this stage. If you're waiting for a particular > > version of kdelibs to upload kdebase, for example, then it would be > > better just to add a versioned build-dep to kdebase. > > That's not the problem. the problem is that kdelibs-dev package > depends on exact kdelibs4 version, and the new kdelibs-dev is > binary-all and thus gets into the archive before kdelibs is compiled > on that specific platform. Oh, that should be equally not a problem. If kdelibs-dev can't be installed then the buildds will just defer the build for a while; that's perfectly normal and not something that should delay maintenance work. Cheers, -- Colin Watson [EMAIL PROTECTED]
