> "Ganesan" == Ganesan Rajagopal <[EMAIL PROTECTED]> writes:
> Hi,
> I am currently in the NM queue. I am looking for a sponsor to upload
> packages for OpenSLP. My experimental packages are available at
> ftp://openslp.sourceforge.net:/pub/openslp/CVS. These sources are based on
> a curren
On Wed, Feb 07, 2001 at 05:43:51PM +, James Troup wrote:
> Julian Gilbey <[EMAIL PROTECTED]> writes:
>
> > > I have packaged vpopmail and put it into main section of Debian. Then
> > > somebody reported that it depends on qmail and hence it should be moved
> > > From mail to contrib/mail. I
On Wed, Feb 07, 2001 at 05:43:51PM +, James Troup wrote:
> Julian Gilbey <[EMAIL PROTECTED]> writes:
>
> > > I have packaged vpopmail and put it into main section of Debian. Then
> > > somebody reported that it depends on qmail and hence it should be moved
> > > From mail to contrib/mail. I
>>"Aubin" == Aubin Paul <[EMAIL PROTECTED]> writes:
Aubin> Hmm... I'm actually quite familiar with CVS (we use it extensively at
Aubin> work) So, the idea would be that I'd keep the pristine sources in a
Aubin> branch, apply my changes in a 'version' and maintain the debian/ stuff
Aubin> in an
On Wed, 7 Feb 2001, peter karlsson wrote:
> Well, also there is the endian problem. I don't know how 1.4 debs ended
> up on these machines, because I have a check in configure that
> disallows compiles on big-endian machines (since the datastructures are
> defined as little-endian, and I haven't
Christopher C. Chimelis:
> If it were something like GNAT, where we cannot build it on Alpha at
> all without pre-existing binaries (which don't exist for
> alpha-linux), then I would say omit Alpha.
Well, also there is the endian problem. I don't know how 1.4 debs ended
up on these machines, bec
>>"Aubin" == Aubin Paul <[EMAIL PROTECTED]> writes:
Aubin> Hmm... I'm actually quite familiar with CVS (we use it extensively at
Aubin> work) So, the idea would be that I'd keep the pristine sources in a
Aubin> branch, apply my changes in a 'version' and maintain the debian/ stuff
Aubin> in a
On Wed, 7 Feb 2001, peter karlsson wrote:
> Well, also there is the endian problem. I don't know how 1.4 debs ended
> up on these machines, because I have a check in configure that
> disallows compiles on big-endian machines (since the datastructures are
> defined as little-endian, and I haven't
On Wed, 7 Feb 2001, peter karlsson wrote:
> So basically, I should change "Architecture: any" to specifically not
> list alpha (and other platforms lacking Qt)?
H...I would say no, personally, only because it's a compiler problem
which is likely to be fixed eventually. If it were something
Julian Gilbey <[EMAIL PROTECTED]> writes:
> > I have packaged vpopmail and put it into main section of Debian. Then
> > somebody reported that it depends on qmail and hence it should be moved
> > From mail to contrib/mail. I tried to upload fixed packages, but Debian
> > installer rejected those
Christopher C. Chimelis:
> If it were something like GNAT, where we cannot build it on Alpha at
> all without pre-existing binaries (which don't exist for
> alpha-linux), then I would say omit Alpha.
Well, also there is the endian problem. I don't know how 1.4 debs ended
up on these machines, be
Christopher C. Chimelis:
> Alpha has serious gcc/g++ problems with Qt 2.2, so don't expect an alpha
> upload for quite some timejust fyi :-)
So basically, I should change "Architecture: any" to specifically not
list alpha (and other platforms lacking Qt)?
--
\\//
peter - http://www.softwolv
On Wed, 7 Feb 2001, peter karlsson wrote:
> So basically, I should change "Architecture: any" to specifically not
> list alpha (and other platforms lacking Qt)?
H...I would say no, personally, only because it's a compiler problem
which is likely to be fixed eventually. If it were something
On Wed, Feb 07, 2001 at 04:54:10PM +0100, Ondrej Sury wrote:
>
> Hello,
>
> I have packaged vpopmail and put it into main section of Debian. Then
> somebody reported that it depends on qmail and hence it should be moved
> From mail to contrib/mail. I tried to upload fixed packages, but Debian
>
Hello,
I have packaged vpopmail and put it into main section of Debian. Then
somebody reported that it depends on qmail and hence it should be moved
From mail to contrib/mail. I tried to upload fixed packages, but Debian
installer rejected those new packages. Now I don't know how to solve this
Julian Gilbey <[EMAIL PROTECTED]> writes:
> > I have packaged vpopmail and put it into main section of Debian. Then
> > somebody reported that it depends on qmail and hence it should be moved
> > From mail to contrib/mail. I tried to upload fixed packages, but Debian
> > installer rejected thos
In Tue, 6 Feb 2001 19:18:24 -0500 Jimmy cum veritate scripsit :
> Hi. I would like to play around with some program and try to come up
> with a
> .deb for it, in order to learn how to do it. I'd like it to be
> reasonably
> simple, but I'd also like not to be duplicating work that's already been
>
Christopher C. Chimelis:
> Alpha has serious gcc/g++ problems with Qt 2.2, so don't expect an alpha
> upload for quite some timejust fyi :-)
So basically, I should change "Architecture: any" to specifically not
list alpha (and other platforms lacking Qt)?
--
\\//
peter - http://www.softwol
On Wed, Feb 07, 2001 at 04:54:10PM +0100, Ondrej Sury wrote:
>
> Hello,
>
> I have packaged vpopmail and put it into main section of Debian. Then
> somebody reported that it depends on qmail and hence it should be moved
> From mail to contrib/mail. I tried to upload fixed packages, but Debian
Hello,
I have packaged vpopmail and put it into main section of Debian. Then
somebody reported that it depends on qmail and hence it should be moved
From mail to contrib/mail. I tried to upload fixed packages, but Debian
installer rejected those new packages. Now I don't know how to solve thi
Hmm... I'm actually quite familiar with CVS (we use it extensively at
work) So, the idea would be that I'd keep the pristine sources in a
branch, apply my changes in a 'version' and maintain the debian/ stuff
in another branch? Sounds good, but I've usually just made my changes,
made a diff, and pa
In Tue, 6 Feb 2001 19:18:24 -0500 Jimmy cum veritate scripsit :
> Hi. I would like to play around with some program and try to come up
> with a
> .deb for it, in order to learn how to do it. I'd like it to be
> reasonably
> simple, but I'd also like not to be duplicating work that's already been
hi all
i have a problem with bug #78232 which i don't figure out how to solve.
it is the assle of the -rpath parameter. lintian is reporting this
warning against my curl binary package and i'm not understanding how
to make it shut up.
lintian doesn't provide any information regarding this warnin
Hmm... I'm actually quite familiar with CVS (we use it extensively at
work) So, the idea would be that I'd keep the pristine sources in a
branch, apply my changes in a 'version' and maintain the debian/ stuff
in another branch? Sounds good, but I've usually just made my changes,
made a diff, and p
hi all
i have a problem with bug #78232 which i don't figure out how to solve.
it is the assle of the -rpath parameter. lintian is reporting this
warning against my curl binary package and i'm not understanding how
to make it shut up.
lintian doesn't provide any information regarding this warni
Aubin Paul <[EMAIL PROTECTED]> wrote:
> 2) If I make a bug-fix, and submit it upstream, do I have to wait
> for the upstream version to apply my fix, or can I just apply it
> myself. (In one of my packages, there were some GTK warnings, so I
> fixed those, and sent a patch to the upstream guy, but
26 matches
Mail list logo
