On Tue, 26 Jul 2005 22:23:10 +0200, Eric Heintzmann <[EMAIL PROTECTED]> said:
> I co-maintain the GNUstep Core packages for more than 2 years, and I
> spend a lot of time to find a solution to these problems by moving
> files accordingly to FHS, and by symlinking some directories. After
> several
* Eric Heintzmann <[EMAIL PROTECTED]> writes:
> Since there is no other maintainer to try to make these packages FHS
> compliant, should GNUstep be removed from Debian ?
Speaking on behalf of the tiny Bulgarian GNUstep community I would
like to ask you (and RMs as well) not to remove GNUstep from
Hi,
Actually, there are in Debian (sarge, etch, sid) more than 50 packages
that are parts of the GNUstep Environment. But there is a big issue with
all of them: none are FHS compliant.
The development of GNUstep started a long time before the birth of the
File Hierarchy Standard, and since they i
Kurt Roeckx <[EMAIL PROTECTED]> wrote:
> On Tue, Jul 26, 2005 at 11:45:18AM +0200, Frank Küster wrote:
>>
>> The number of packages build-depending on tetex (directly or indirectly
>> via a build-dep on some conversion tool like debiandoc-sgml) is really
>> big, and we will not be able to check t
On Tue, Jul 26, 2005 at 11:45:18AM +0200, Frank Küster wrote:
>
> The number of packages build-depending on tetex (directly or indirectly
> via a build-dep on some conversion tool like debiandoc-sgml) is really
> big, and we will not be able to check this all by hand.
Doing just build tests for a
On Tue, Jul 26, 2005 at 10:14:15AM +0200, Frank K?ster wrote:
> a) libkpathsea: It has a new soname, and I have not checked at all
>whether this causes problems in compiling other packages. I do not
>expect, however, big problems with that because of two reasons: First
>of all, only a
Andreas Barth <[EMAIL PROTECTED]> wrote:
> * Frank Küster ([EMAIL PROTECTED]) [050726 14:45]:
>> Matthias Klose <[EMAIL PROTECTED]> wrote:
>>
>> > please make sure, that tetex-bin builds on all architectures.
>
>> Does all also mean amd64 now? If yes, is there a machine I can access
>> to te
* Frank Küster ([EMAIL PROTECTED]) [050726 15:04]:
> Andreas Barth <[EMAIL PROTECTED]> wrote:
>
> > * Frank Küster ([EMAIL PROTECTED]) [050726 14:45]:
> >> Matthias Klose <[EMAIL PROTECTED]> wrote:
> >>
> >> > please make sure, that tetex-bin builds on all architectures.
> >
> >> Does all als
Matthias Klose <[EMAIL PROTECTED]> wrote:
> please make sure, that tetex-bin builds on all architectures.
Does all also mean amd64 now? If yes, is there a machine I can access
to test it?
TIA, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
* Frank Küster ([EMAIL PROTECTED]) [050726 14:45]:
> Matthias Klose <[EMAIL PROTECTED]> wrote:
>
> > please make sure, that tetex-bin builds on all architectures.
> Does all also mean amd64 now? If yes, is there a machine I can access
> to test it?
If you upload to experimental, it should wo
On Tue, Jul 26, 2005 at 12:45:48AM +0100, Luke Kenneth Casson Leighton wrote:
> On Mon, Jul 25, 2005 at 03:51:22PM -0700, Matt Taggart wrote:
> > It would probably be a good idea to record what ought to work in any given
> > release and maybe have an ongoing idea what it should be. The answer migh
Andreas Barth <[EMAIL PROTECTED]> wrote:
> * Frank K?ster ([EMAIL PROTECTED]) [050726 12:34]:
>> Andreas Barth <[EMAIL PROTECTED]> wrote:
>> > Currently, we have (at least) two large transitions at our hands:
>> > 1. gcc-4.0/glibc
>> > 2. xorg
>> >
>> > I really would be happy if we can avoid that
* Frank Küster ([EMAIL PROTECTED]) [050726 13:17]:
> Andreas Barth <[EMAIL PROTECTED]> wrote:
> > * Frank K?ster ([EMAIL PROTECTED]) [050726 12:34]:
> >> Andreas Barth <[EMAIL PROTECTED]> wrote:
> >> > Currently, we have (at least) two large transitions at our hands:
> >> > 1. gcc-4.0/glibc
> >> >
Andreas Barth writes:
> * Frank K?ster ([EMAIL PROTECTED]) [050726 12:34]:
> > Andreas Barth <[EMAIL PROTECTED]> wrote:
> > > Currently, we have (at least) two large transitions at our hands:
> > > 1. gcc-4.0/glibc
> > > 2. xorg
> > >
> > > I really would be happy if we can avoid that tetex becomes
* Frank K?ster ([EMAIL PROTECTED]) [050726 12:34]:
> Andreas Barth <[EMAIL PROTECTED]> wrote:
> > Currently, we have (at least) two large transitions at our hands:
> > 1. gcc-4.0/glibc
> > 2. xorg
> >
> > I really would be happy if we can avoid that tetex becomes part of any
> > of these transition
On Tue, 26 Jul 2005 09:45, Luke Kenneth Casson Leighton wrote:
> On Mon, Jul 25, 2005 at 03:51:22PM -0700, Matt Taggart wrote:
> > It would probably be a good idea to record what ought to work in any
> > given release and maybe have an ongoing idea what it should be. The
> > answer might be archite
Andreas Barth <[EMAIL PROTECTED]> wrote:
> That sounds good, thanks.
>
>> b) More severely, tetex-bin is a build-dependency of many packages.
>>While I think that our packages do not contain major bugs, I would be
>>surprised if the upgrade did not reveal bugs in packages that use it,
>>
On Tuesday 26 July 2005 02:06, Steve Langasek wrote:
> I believe Joey Hess is the person who has the best handle on what the
> actual minimum requirements are for installing sarge. Joey, do you
> have anything we could add to the sarge release notes for this, if it's
> not already in there?
The d
On Tue, Jul 26, 2005 at 10:14:15AM +0200, Frank Küster wrote:
> b) More severely, tetex-bin is a build-dependency of many packages.
>While I think that our packages do not contain major bugs, I would be
>surprised if the upgrade did not reveal bugs in packages that use it,
>causing some
Hi Frank,
* Frank K?ster ([EMAIL PROTECTED]) [050726 10:30]:
> with the next upload (scheduled for today) of teTeX-3.0 to experimental,
> I think we have only cosmetic issues left before we can upload it to
> unstable.
That sounds good, thanks.
> b) More severely, tetex-bin is a build-dependency
Dear release team,
with the next upload (scheduled for today) of teTeX-3.0 to experimental,
I think we have only cosmetic issues left before we can upload it to
unstable. Before doing this, however, I'd like to notify you, so that
you have a chance to yell out "no!". There are two problem areas
21 matches
Mail list logo
