Uploading packages
Hi, I made a package (sound-recorder_0.04-1_i386.deb). This is to be my first upload. My question is: Its a direct-to-disk recorder and contains: record (no cdrom support), cdrom-record and play-sample Can i use this name (same as tar-ball) for the package or do you need it to be the same as the binary (ELF) and therefore be 3 separate packages?? I used sound/extra as section/priority, is this correct?? Where do i upload it. /home/Debian/ftp/private/project/Incoming because of the freeze of hamm (so in other words is this slink). Thanks, Bart Format: 1.5 Date: Fri, 22 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-recorder (0.04-1) unstable; urgency=low . * Initial Release. Files: 5824419994f26be6e8e701b38e636423 645 sound extra sound-recorder_0.04-1.dsc 6ea74b1981f950f828c93d8210ca41c9 23781 sound extra sound-recorder_0.04.orig.tar.gz 19d9fbc4f88346ffa50a38cbd9de836d 1529 sound extra sound-recorder_0.04-1.diff.gz 533f4688a45b2a7f02d55e339d534b43 25160 sound extra sound-recorder_0.04-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Uploading packages
---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'm a bit scared to ask, because I don't want to start a thread, but are > these the names of the executables? > Yes they are... > The reason I ask is becasue it is depreciated to use dictionary words, > because of namespace wasting... well, especially "record" seems to be too > general. > > Comments? > I guess you are right. Any good alternative names are welcome. I have uploaded the package already. This means what... Bart -- ---- B. Warmerdam GNU/Debian Linux [EMAIL PROTECTED] http://www.xs4all.nl/~bartw -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Question on segv dpkg wrt links in man/man1
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. Is this a problem with dpkg or do i try to reorder the man dir in the archive (with tar flags)??? When manually copying this file and installing all is well. Thanks, B. Example: drwxr-xr-x root/root 0 1998-11-22 19:46 usr/man/man1/ lrwxrwxrwx root/root 0 1998-11-22 19:46 usr/man/man1/extract.1.gz -> csound.1.gz lrwxrwxrwx root/root 0 1998-11-22 19:46 usr/man/man1/extractor.1.gz -> csound.1.gz lrwxrwxrwx root/root 0 1998-11-22 19:46 usr/man/man1/het_export.1.gz -> csound.1.gz lrwxrwxrwx root/root 0 1998-11-22 19:46 usr/man/man1/het_import.1.gz -> csound.1.gz -rw-r--r-- root/root 1531 1998-11-22 18:25 usr/man/man1/csound.1.gz lrwxrwxrwx root/root 0 1998-11-22 19:46 usr/man/man1/envelope.1.gz -> csound.1.gz lrwxrwxrwx root/root 0 1998-11-22 19:46 usr/man/man1/lpc_export.1.gz -> csound.1.gz lrwxrwxrwx root/root 0 1998-11-22 19:46 usr/man/man1/scot.1.gz -> csound.1.gz -- B. Warmerdam GNU/Debian Linux [EMAIL PROTECTED], [EMAIL PROTECTED] (Keyid: 10A0FDD1)
Re: Question on segv dpkg wrt links in man/man1
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 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. Is this a problem with dpkg or do i > > try > > to reorder the man dir in the archive (with tar flags)??? When manually > > copying this file and installing all is well. > > There were problems a while ago when the lchown syscall was added to the > linux kernel but the numbers were messed up so the "chown" command would try > and chown what the symlinked pointed to rather than the symlink itself. > > What kernel are you on, and are you using recent versions of (mentioning all > programs ): dpkg, tar, libc6, libc5, fileutils. > Kernel 1.2.128 on Alpha 164SX Slink/Sid ii dpkg1.4.0.24 Package maintenance system for Debian ii tar 1.12-6 GNU tar ii libc6.1 2.0.7u-5 The GNU C library version 2 (run-time un libc5(no description available) ii fileutils 3.16-5.3 GNU file management utilities. IIRC lchown was a problem with older kernels and not the development ones. A newer libc solves lchown as well. I guess my situation is different from the one you are suggesting... But if I were sure I wouldn't be asking this question, so correct me if i'm wrong :) Thanks, B. -- B. Warmerdam GNU/Debian Linux [EMAIL PROTECTED], [EMAIL PROTECTED] (Keyid: 10A0FDD1)
Re: couple quick questions
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 stuff :-) > > > > Learning troff is not hard, though. man(7) tells you all you need to know. > > Is there a manpage template or DTD or something similar for use > with emacs in nroff mode? > Maybe you could also look into pod. This is a language that comes with perl and produces manpages quite easy. See the pod manual page. (pod2html, pod2latex, pod2man, pod2text) HTH, B. -- B. Warmerdam GNU/Debian Linux [EMAIL PROTECTED], [EMAIL PROTECTED] (Keyid: 10A0FDD1)
Re: How to recover the debian/ dir
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: 'dpkg-source -x myutil_1.0-1.dsc' B. -- B. Warmerdam GNU/Debian Linux [EMAIL PROTECTED], [EMAIL PROTECTED] (Keyid: 10A0FDD1)
Re: question about porting...
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 will compile/work on say m68k, hurd, sparc platforms. The port ppl check if it compiles and check buildlogs. > So...I upload them under a "any" clause, the m68k,sparc,etc ppl suck them up, > compile them on their systems and (?) . Do they test them out or do they > just upload them into the distribution and wait to see if anyone who uses them > finds problems in them? Some packages are easy to test but others don't. Eg you don't set up a list-server every time you compile it. Checking is the least you can do though. > > If there is a problem, who is responsible for fixing it? (ie,) if say > rrlogind > has problems on sparc systems, who handles this? if it were i386 it would be > me > in conjunction with the author, but since I don't have access to a sparc > debian > system I can only assume it's not me but rather the person who is doing the > porting. If the bug is port specific, mention it on the port list or contact the uploader of your package (if you can trace him). Most likely they solve it for you and send the patch. If it's a source question i386 should suffer as well and you have to step in :) > > Are my conclusions pretty much correct? > > Is there a way for me to have access to debian (sparc/hurd/m68k/etc...) > systems > to do porting on so that this responsibility layes with me? > There are net-connected systems. Be aware that all ports have their specific problems!! B. -- B. Warmerdam GNU/Debian Linux [EMAIL PROTECTED], [EMAIL PROTECTED] (Keyid: 10A0FDD1)
Re: No diff created when buidlng mountapp!
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 source.tar.gz with version -2. I used > the command build to do that whis was probably wrong? > Everything else wase made correctly, so for future > versions: What did I wrong and, if I create a .diff > in the next version does dpkg know on which of the source-packages > this should be applied. Hi Olaf, You forgot to put the source.orig.tar.gz in directory .. If the original tarball is there only the diff is created and on -1 the orig.tar.gz has to be uploaded as well. All other Debian versions only need the diff. B. -- B. Warmerdam GNU/Debian Linux [EMAIL PROTECTED], [EMAIL PROTECTED] (Keyid: 10A0FDD1)
Re: Upgrading to a new upstream maintainer version
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 the changelog... ? > > * unpack the new upstream version [snip] Or use uupdate and let this program do all the work while you relax in you chair watching your computer doing all the labour instead of you ;-) Cheers, B. dpkg --print-avail devscripts Package: devscripts [snip snip] will need transferring - uupdate: Integrate upstream changes into a source package - uscan: Scan upstream sites for new releases of packages [snip snip] -- B. Warmerdam GNU/Debian Linux [EMAIL PROTECTED], [EMAIL PROTECTED] (Keyid: 10A0FDD1)
Re: arch specific details and autobuilder.
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.
Re: characters in X-application replaced with boxes :(
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.
Re: arch specific details and autobuilder.
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 UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: characters in X-application replaced with boxes :(
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 UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
