On Wed, 12 Aug 1998, Paul Slootman wrote:
> Check out the archive for debian-alpha, an offer to debian developers
> who want to use an alpha was made (last week I think). Look for "Danny
> ter Haar".
> But maybe you want to get in touch with [EMAIL PROTECTED] (also check the
> archive!) ? He's th
On Fri, 2 Apr 1999, Mika Fischer wrote:
> > This is a possibility for at least m68k, powerpc and alpha (kullervo,
> > tervola and faure @ debian.org), but unless you specifically want to
> > or need to, I wouldn't bother.
>
> Na, I don't think I want to.
I don't blame you on this :-) I'm one o
On Fri, 7 May 1999, Peter S Galbraith wrote:
> Now it occurs to me that if I rebuild my package and bump up the
> debian version number, then other archs will need to rebuild too
> even thought I have not changed a thing in source.
> Is that the proper thing to do?
Yes. If you need to recompile
On Mon, 12 Jul 1999, chris mckillop wrote:
> So, in my efforts to be useful.
>
> I would like to help hunt out and squash some of the bugs currently
> listed on bugs.debian.org. However, it would seem that a little caution
> is in order. How should I approach submitting the fixes I
On Tue, 20 Jul 1999, Decklin Foster wrote:
> I filed a bug a long time ago against chimera about there being a new
> upstream version (a new patchlevel, really.) It's 79 days old and I
> haven't heard anything. I wish I could NMU it, but I am not a
> developer and do not have a verified PGP key.
On Wed, 21 Jul 1999, Decklin Foster wrote:
> I've been running the actual binary for several weeks with no problems
> (well, other than buggy layout, but that's another issue :-), and it
> went through the suggested upgrade/downgrade tests with no apparent
> problems for me. Thanks for uploading
On Thu, 22 Jul 1999, Decklin Foster wrote:
> Well, I've been running chimera 1.6/1.7 on an i386 for, hmmm, more
> than a year at least. This is been a combination of compiling from a
> tarball, using Debian's packages, and rolling my own. I haven't ever
> experienced anything like that, so I susp
On 5 Aug 1999 [EMAIL PROTECTED] wrote:
> I did some fixes and cleanup on the defrag package and have e2dump
> 64Bit clean and 2GB proff now, but still have some bugs left to
> fix. Also the defrag tells me that it can't find inode xxx, where xxx
> is way to big (probably a 64 Bit problem in defra
On 5 Aug 1999 [EMAIL PROTECTED] wrote:
> Could be, but I don't think so. I rather think that it reads a long
> instead of an __u32 and thus gets two __u32 into the long, which then
> is far to big.
Hehehe...that's typical :-) Wouldn't be the first time I've seen that
either.
C
On Wed, 8 Sep 1999, Christian T. Steigies wrote:
> I dont think the build demons will pick up non-main packages in the near
> future, but maybe we could have a quinn-diff running on contrib and the
> non-* directories, so that we at least know when something is not up to
> date. And somebody coul
On Thu, 9 Sep 1999, Adam Keys wrote:
> This is a GNOME applet that adds some pretty small icons to
> your panel, like Windows' QuickLaunch toolbar. They are smaller
> than the normal GNOME launchers so you can fit more on your panel.
> It can also be torn away from the panel and put elsewhere.
>
Nevermind...tarball wasn't on ftp, but was via http.
It compiles and runs nicely on the Alpha :-) Very nice! I'll have to
start using this one soon :-)
I don't see anything wrong with it. It installed and purged very cleanly
and seems to do everything it needs to (hell, the lintian report on
Oh, FYI, if you upload the same (-3) revision of the package, let me know
and I'll upload my Alpha deb for it as well.
C
On Fri, 24 Sep 1999, Paul Harris wrote:
> ok i forgot to ask: i can compile for i386, but whats the deal with the
> other platforms? how can i test vrweb on those even if i have no access to
> a machine?
I can check it on Alpha, but it may be a few days. Let me know where I
can compile the sour
On Sat, 25 Sep 1999, Paul Harris wrote:
> could I also please ask Christopher to attempt to build it on his Alpha
> (mmm wish i had access ;). also if anyone has access to a platform other
> than an i386 (i have that), could i get them to please check it out?
I took the Alpha down today (am movi
On Mon, 10 Jan 2000, Holger Eitzenberger wrote:
> * Platform is only i386 for now. This is likely to change in the
> future.
Is this due to i386-specific asm code or is this package just untested on
other archs? If it's C or C++, I'll take a stab at patching it for Alpha,
but if it's asm
On Sun, 11 Jun 2000, Jimmy O'Regan wrote:
> I have a couple of packages done and available at
> http://lit.compsoc.com/~jimregan/debian/
>
> I was wondering if someone could check them out, and maybe sponsor them?
No time to sponsor, but I did test out a few so far on Alpha...comments
below. I
On Sat, 10 Jun 2000, Christopher C. Chimelis wrote:
> > name: gnut
> > desc: Command line gnutella client
> > license: GPL
>
> Didn't get to check the package too much, but did check the
> software. Seems to have problems when finding an interface on Alpha
>
On Sun, 11 Jun 2000, Christopher C. Chimelis wrote:
>
> On Sat, 10 Jun 2000, Christopher C. Chimelis wrote:
>
> > > name: gnut
> > > desc: Command line gnutella client
> > > license: GPL
> >
> > Didn't get to check the package too much, bu
On Sun, 11 Jun 2000, andreas palsson wrote:
> This might sound a little strange.
> If I would like to become a debian developer, but I don't have any
> package and maybe I just want to "help" others by testing packages,
> fixing bugs and suppling patches to the original maintainers.
>
> Is this
On 2 Aug 2000, Christian Marillat wrote:
> This is the 3th bugs against Helix package in our BTS.
>
> I close these bug without reading them.
>
> But for one I've some problem (bug 68343).
>
> This bug has been closed 2 times and reopen 2 times. Here is the latest
> reopen:
>
> What I need t
On 2 Aug 2000, Christian Marillat wrote:
> CCC> I'd forward it upstream, personally. In other words, file it as a bug
> CCC> with the Helix folk and mark it as forwarded in our BTS.
>
> I just discovered the Helix BTS.
Yeah, I had the URL ready in case you didn't have it yet.
> This problem i
On Sun, 27 Aug 2000, Cosimo Alfarano wrote:
> I've put 'Depends: libc6 (>= 2.1.2), libstdc++2.10, wish'
> Which is the best solution, let gocr depends on wish or
> make two packages (1 with only one small binary)?
Make sure not to hard-code the libc6 dependency (let dpkg-shlibdeps
handle it via
On Sun, 1 Oct 2000, Scott Dier wrote:
> Figures :)
>
> Thanks. I should have checked first.
>
> Well, my background right now is mostly systems administration and
> programming, anyone got a service or something console based that needs
> to be packaged? :)
I've got the beginnings of a netsai
On Sun, 1 Oct 2000, Scott Dier wrote:
> Looks like theres allready a netsaint package in woody...
Oops...I missed that. Thanks for catching this :-)
C
On Sat, 30 Sep 2000, Scott Dier wrote:
> I am also interested in packaging. This would be my first package. If
> noone comes out from before and jumps up and down about doing it, I
> would be interested in packaging sphinx.
If this is the sphinx that's a speech recognition library and utilitie
On Fri, 24 Nov 2000, zhaoway wrote:
> hi,
>
> i have a bug on compiling on m68k. i have no experience beyond i386.
> is there some guideline/step-by-step/tutorial on dealing with such
> bugs?
Not really, since every platform has its quirks. I don't have an m68k,
but perhaps I can help you thro
On Sun, 26 Nov 2000, Josip Rodin wrote:
> Yes, build daemons for i386, m68k, sparc, powerpc should be active.
> I'm not sure about the alpha one, but there's always Chris Chimelis :)
Hehehe...just call me Chris "build daemon" Chimelis :-) If dinstall puts
a package into the master archives, I b
On Wed, 7 Feb 2001, Junichi Uekawa wrote:
> So, if you had your package for 26 days, the possibility is that qt2.2
> hasn't been available on all arches when you had it installed.
>
> Have you tried looking at the build logs and its date ?
Alpha has serious gcc/g++ problems with Qt 2.2, so don
On Tue, 6 Feb 2001, Steve Langasek wrote:
> I've found that Qt builds surprisingly well if I use Compaq's cxx compiler.
> It might be nice if the qt packages were structured to allow rebuilding with
> different compilers, although having Qt Build-Depend on a non-free package is
> not a very good
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, 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 Sun, 11 Jun 2000, Jimmy O'Regan wrote:
> I have a couple of packages done and available at
> http://lit.compsoc.com/~jimregan/debian/
>
> I was wondering if someone could check them out, and maybe sponsor them?
No time to sponsor, but I did test out a few so far on Alpha...comments
below.
On Sat, 10 Jun 2000, Christopher C. Chimelis wrote:
> > name: gnut
> > desc: Command line gnutella client
> > license: GPL
>
> Didn't get to check the package too much, but did check the
> software. Seems to have problems when finding an interface on Alpha
&
On Sun, 11 Jun 2000, Christopher C. Chimelis wrote:
>
> On Sat, 10 Jun 2000, Christopher C. Chimelis wrote:
>
> > > name: gnut
> > > desc: Command line gnutella client
> > > license: GPL
> >
> > Didn't get to check the package too much, bu
On Sun, 11 Jun 2000, andreas palsson wrote:
> This might sound a little strange.
> If I would like to become a debian developer, but I don't have any
> package and maybe I just want to "help" others by testing packages,
> fixing bugs and suppling patches to the original maintainers.
>
> Is this
On 2 Aug 2000, Christian Marillat wrote:
> This is the 3th bugs against Helix package in our BTS.
>
> I close these bug without reading them.
>
> But for one I've some problem (bug 68343).
>
> This bug has been closed 2 times and reopen 2 times. Here is the latest reopen:
>
> What I need to
On 2 Aug 2000, Christian Marillat wrote:
> CCC> I'd forward it upstream, personally. In other words, file it as a bug
> CCC> with the Helix folk and mark it as forwarded in our BTS.
>
> I just discovered the Helix BTS.
Yeah, I had the URL ready in case you didn't have it yet.
> This problem
On Sun, 27 Aug 2000, Cosimo Alfarano wrote:
> I've put 'Depends: libc6 (>= 2.1.2), libstdc++2.10, wish'
> Which is the best solution, let gocr depends on wish or
> make two packages (1 with only one small binary)?
Make sure not to hard-code the libc6 dependency (let dpkg-shlibdeps
handle it vi
On Sat, 30 Sep 2000, Scott Dier wrote:
> I am also interested in packaging. This would be my first package. If
> noone comes out from before and jumps up and down about doing it, I
> would be interested in packaging sphinx.
If this is the sphinx that's a speech recognition library and utiliti
On Sun, 1 Oct 2000, Scott Dier wrote:
> Figures :)
>
> Thanks. I should have checked first.
>
> Well, my background right now is mostly systems administration and
> programming, anyone got a service or something console based that needs
> to be packaged? :)
I've got the beginnings of a netsa
On Sun, 1 Oct 2000, Scott Dier wrote:
> Looks like theres allready a netsaint package in woody...
Oops...I missed that. Thanks for catching this :-)
C
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Fri, 24 Nov 2000, zhaoway wrote:
> hi,
>
> i have a bug on compiling on m68k. i have no experience beyond i386.
> is there some guideline/step-by-step/tutorial on dealing with such
> bugs?
Not really, since every platform has its quirks. I don't have an m68k,
but perhaps I can help you thr
On Sun, 26 Nov 2000, Josip Rodin wrote:
> Yes, build daemons for i386, m68k, sparc, powerpc should be active.
> I'm not sure about the alpha one, but there's always Chris Chimelis :)
Hehehe...just call me Chris "build daemon" Chimelis :-) If dinstall puts
a package into the master archives, I
On Wed, 7 Feb 2001, Junichi Uekawa wrote:
> So, if you had your package for 26 days, the possibility is that qt2.2
> hasn't been available on all arches when you had it installed.
>
> Have you tried looking at the build logs and its date ?
Alpha has serious gcc/g++ problems with Qt 2.2, so do
On Tue, 6 Feb 2001, Steve Langasek wrote:
> I've found that Qt builds surprisingly well if I use Compaq's cxx compiler.
> It might be nice if the qt packages were structured to allow rebuilding with
> different compilers, although having Qt Build-Depend on a non-free package is
> not a very good
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, 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
48 matches
Mail list logo
