On Fri, Aug 10, 2001 at 05:48:49PM +1000, Drew Parsons wrote:
[ characters show as boxes in X ]
> Can anyone suggest how to best determine the cause of the problem?
Restart X. Helped for me numerous times for the same problem. BTW, does anyone
know why this is happening anyhow?
B.
On Fri, Aug 10, 2001 at 05:48:49PM +1000, Drew Parsons wrote:
[ characters show as boxes in X ]
> Can anyone suggest how to best determine the cause of the problem?
Restart X. Helped for me numerous times for the same problem. BTW, does anyone
know why this is happening anyhow?
B.
--
To UN
On Fri, Jun 01, 2001 at 12:08:58PM +0530, Viral wrote:
> Hi,
>
> Is there a page that tells about the arches that a package was successfully
> compiled for ? Problems etc ?
Maybe you want to look at http://buildd.debian.org. This is the closest I can
think of...
Cheers,
B.
On Fri, Jun 01, 2001 at 12:08:58PM +0530, Viral wrote:
> Hi,
>
> Is there a page that tells about the arches that a package was successfully
> compiled for ? Problems etc ?
Maybe you want to look at http://buildd.debian.org. This is the closest I can
think of...
Cheers,
B.
--
To UNSUBSCRIB
On Wed, Jun 23, 1999 at 12:53:30AM +0200, Christian Hammers wrote:
> On Tue, 22.06.99 13:55 +0200, Sami Dalouche wrote:
> > I've already packaged a deb of epkg but there's a new upstream maintainer
> > version.
> > Must I remake entirely the package or I have just to do anything that will
> > keep
On Mon, May 10, 1999 at 02:40:44PM +0200, Olaf Stetzer wrote:
> Hello again,
>
> just another question came up on my second package mountapp.
> Last week I uploaded version -2 of it and afterward recognised,
> that instead of building the i386 binary and creating the .diff
> it created another sou
On Wed, Apr 21, 1999 at 10:23:54AM -0700, Ivan E. Moore II wrote:
> (how do we know if packages we create work on other platforms?)
>
> (rrdhcp and rrlogin) are not. I build them on i386 systems and have no clue
> (other than the author saying they "should" work on other platforms) whether
> they
On Thu, Apr 15, 1999 at 11:40:24PM -0700, Adam Klein wrote:
> On Thu, Apr 15, 1999 at 04:47:04PM -0500, Jianming YOU wrote:
>
> Use 'ar x myutil_1.0-1.deb' to unpack the parts of the deb, and then use
> tar to extract the control files from control.tar.gz.
>
Better (at least easier) is: 'dpk
On Mon, Mar 15, 1999 at 10:50:07AM -0500, Bob Hilliard wrote:
> Richard Braakman <[EMAIL PROTECTED]> writes:
>
> > Randolph Chung wrote:
> > > what's the easiest way to write a manpage if i don't want to learn troff?
> > > :)
> >
> > Grab a manpage from a similar utility and fill in your own st
On Mon, Nov 23, 1998 at 08:21:08PM +, Adrian Bridgett wrote:
> On Sun, Nov 22, 1998 at 08:07:16PM +0100, Bart Warmerdam wrote:
> >
> > Hi,
> >
> > I have a question:
> >
> > I am currently working on a port on csound. In package csound all manu
Hi,
I have a question:
I am currently working on a port on csound. In package csound all manuals
are linked to csound.1.gz. In de archive the csound.1.gz is not the first
file to be extracted (see below). When installing a package when there is no
valid link, dpkg segfaults on chown.
---Reply on mail from Marcus Brinkmann about Uploading packages
> On Sat, May 23, 1998 at 02:27:26PM +0200, Bart Warmerdam wrote:
>
>> Its a direct-to-disk recorder and contains:
>> record (no cdrom support), cdrom-record and play-sample
>
> Hello Bart!
>
> I&#x
May 1998 20:04:37 +0200
Source: sound-recorder
Binary: sound-recorder
Architecture: source i386
Version: 0.04-1
Distribution: unstable
Urgency: low
Maintainer: Bart Warmerdam <[EMAIL PROTECTED]>
Description:
sound-recorder - Direct-to-disk recording and play-back programs.
Changes:
sound-re
13 matches
Mail list logo
