Re: RFS: lives
On Fri, Jul 31, 2009 at 08:59:27AM +0100, Harry Rickards wrote: Then 17 minutes later I got another email from the Archive Administrator at 23:04 saying: Rejected: lives_1.0.0-3.dsc refers to lives_1.0.0.orig.tar.gz, but I can't find it in the queue or in the pool. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. Is that something I've done wrong or something you've done wrong? It's my fault, I forgot to include the orig.tar.gz. -- Robert Millan The DRM opt-in fallacy: Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: lives
On Fri, Jul 31, 2009 at 04:27:42PM +0100, Harry Rickards wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Robert Millan wrote: On Fri, Jul 31, 2009 at 08:59:27AM +0100, Harry Rickards wrote: Then 17 minutes later I got another email from the Archive Administrator at 23:04 saying: Rejected: lives_1.0.0-3.dsc refers to lives_1.0.0.orig.tar.gz, but I can't find it in the queue or in the pool. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. Is that something I've done wrong or something you've done wrong? It's my fault, I forgot to include the orig.tar.gz. Okay. Again, thanks for uploading. In the emails I've got from the Archive Administrator, it's always saying amd64. Does the packaging system build an i386 deb as well (and if not, would it be possible for you to upload one)? It's automated, see http://www.debian.org/devel/buildd/ -- Robert Millan The DRM opt-in fallacy: Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: lives
On Thu, Jul 30, 2009 at 03:22:06PM +0100, Harry Rickards wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear mentors, I am looking for a sponsor for my package lives. * Package name: lives Version : 1.0.0-3 Upstream Author : Gabriel Finch salsa...@xs4all.nl * URL : http://livs.sourceforge.net * License : GPLv3 Section : graphics It builds these binary packages: libweed-dev - Development library for inclusion of plugins into LiVES libweed0 - Runtime library for inclusion of plugins into LiVES lives - Linux Video Editing System lives-data - Data files for LiVES The package appears to be lintian clean (with --pedantic). The package can be found on mentors.debian.net: - - URL: http://mentors.debian.net/debian/pool/main/l/lives - - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - - dget http://mentors.debian.net/debian/pool/main/l/lives/lives_1.0.0-3.dsc I would be glad if someone uploaded this package for me. Hi, This one still has the two problems I pointed out. -- Robert Millan The DRM opt-in fallacy: Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: lives
On Thu, Jul 30, 2009 at 04:05:06PM +0100, Harry Rickards wrote:
Hi,
This one still has the two problems I pointed out.
To version a dependency you just use (= ${source:Version}) after it in
debian/control right? Because that's what I've done. And I've upgraded
debian/rules to automatically do the dh_foo stuff with dh $@, so I
haven't actually got any of the dh_foo commands in there. Are you sure
you downloaded 1.0.0-3?
I'm sorry, I checked the wrong dir by mistake.
1.0.0-3 looks fine to me. I'm uploading it.
--
Robert Millan
The DRM opt-in fallacy: Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all.
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: lives
On Wed, Jul 29, 2009 at 02:00:26PM +0100, Harry Rickards wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear mentors,
I am looking for a sponsor for my package lives (based on the old,
non-lintian clean packages at http://sid.ethz.ch/debian/lives/nyu/).
* Package name: lives
Version : 1.0.0-1
Upstream Author : Gabriel Finch salsa...@xs4all.nl
* URL : http://lives.sourceforge.net
* License : GPLv3
Section : graphics
It builds these binary packages:
libweed-dev - Development library for inclusion of plugins into LiVES
libweed0 - Runtime library for inclusion of plugins into LiVES
lives - Linux Video Editing System
lives-data - Data files for LiVES
The package appears to be lintian clean.
The upload would fix these bugs: 247337
The package can be found on mentors.debian.net:
- - URL: http://mentors.debian.net/debian/pool/main/l/lives
- - Source repository: deb-src http://mentors.debian.net/debian unstable
main contrib non-free
- - dget
http://mentors.debian.net/debian/pool/main/l/lives/lives_1.0.0-1.dsc
I would be glad if someone uploaded this package for me.
Hi,
The libweed0 dependency in lives should be versioned (= ${source:Version}).
Also, never use -a for debhelper. -a just means it may fail gratuitously
in some situations, disabling portability. Use the non-broken -s instead.
--
Robert Millan
The DRM opt-in fallacy: Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all.
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
gathering debconf information from another package
** Please CC your reply, i'm not subscribed **
Hello,
I need to obtain debconf information from my postinst
with db_get from a package that isn't of mine.
do I need to set a pre-depends on it or is it enough
with a depends?
thanks!
--
Robert Millan Debian GNU/Hurd user
zeratul2 wanadoo eshttp://getyouriso.dyndns.org/
GPG ID C8D6942C
237F 8688 C2E5 BC64 E152 97B4 FB28 D41B C8D6 942C
Free Dmitry Sklyarov! http://www.freesklyarov.org
Join us in civil disobedience and distribute DeCSS!!
/*efdtt.c Author: Charles M. Hannum [EMAIL PROTECTED]*/
/*Length: 434 bytes (excluding unnecessary newlines)*/
/*Usage is: cat title-key scrambled.vob | efdtt clear.vob */
/*title-key can be read from the DVD by css-auth. (see livid.org)*/
#define m(i)(x[i]^s[i+84])
unsigned char x[5],y,s[2048];main(n){for(read(0,x,5);read(0,s,n=2048);write(1,s
,n))if(s[y=s[13]%8+20]/16%4==1){int i=m(1)17^256+m(0)8,k=m(2)0,j=m(4)17^m(3)9^k
*2-k%8^8,a=0,c=26;for(s[y]-=16;--c;j*=2)a=a*2^i1,i=i/2^j124;for(j=127;++jn
;c=cy)c+=y=i^i/8^i4^i12,i=i8^y17,a^=a14,y=a^a*8^a6,a=a8^y9,k=s
[j],k=7Wo~'G_\216[k7]+2^cr3sfw6v;*k+/n.[k4]*2^k*257/8,s[j]=k^(kk*234)
*6^c+~y;}}
strange errors with unofficial kernel module
Hello,
I maintain the plex86 package which includes a custom kernel module I
provide make-kpkg scripts to build on the users' host.
The module's always worked fine. however, i get this errors when loading
it:
*** Unresolved symbols in /lib/modules/2.4.16/misc/plex86.o
Warning: loading /lib/modules/2.4.16/misc/plex86.o will taint the kernel:
no license
Anyone can help? I know the first is something with depmod, but i have no
further idea.
For the second, Plex86's license is LGPL. where can i specify it so that
insmod knows?
Thanks
--
Robert Millan Debian GNU/Hurd user
zeratul2 wanadoo eshttp://getyouriso.dyndns.org/
GPG ID C8D6942C
237F 8688 C2E5 BC64 E152 97B4 FB28 D41B C8D6 942C
Free Dmitry Sklyarov! http://www.freesklyarov.org
Join us in civil disobedience and distribute DeCSS!!
/*efdtt.c Author: Charles M. Hannum [EMAIL PROTECTED]*/
/*Length: 434 bytes (excluding unnecessary newlines)*/
/*Usage is: cat title-key scrambled.vob | efdtt clear.vob */
/*title-key can be read from the DVD by css-auth. (see livid.org)*/
#define m(i)(x[i]^s[i+84])
unsigned char x[5],y,s[2048];main(n){for(read(0,x,5);read(0,s,n=2048);write(1,s
,n))if(s[y=s[13]%8+20]/16%4==1){int i=m(1)17^256+m(0)8,k=m(2)0,j=m(4)17^m(3)9^k
*2-k%8^8,a=0,c=26;for(s[y]-=16;--c;j*=2)a=a*2^i1,i=i/2^j124;for(j=127;++jn
;c=cy)c+=y=i^i/8^i4^i12,i=i8^y17,a^=a14,y=a^a*8^a6,a=a8^y9,k=s
[j],k=7Wo~'G_\216[k7]+2^cr3sfw6v;*k+/n.[k4]*2^k*257/8,s[j]=k^(kk*234)
*6^c+~y;}}
Re: Applicant w/ package
On Sun, 04 Nov 2001 16:26:20 Martin Michlmayr wrote: * Roland Mas [EMAIL PROTECTED] [20011104 16:08]: Maybe it would be worth listing it on the can't be packaged page at URL:http://www.debian.org/devel/wnpp/unable-to-package? you must be confused. the patent problems are only affecting the opendivx codec. I spoke with the maintainer about this problem, the opendivx codec is just not going into the mplayer package. the program itself is GPL regarding the technical issues, the main problem was that mplayer uses higher CPU optimizations on compilation. This can be solved by including a part of the sources in the binary package and building them in postinst or even by building many mplayer-* packages. this is a hard package, Dariush Pietrzak [EMAIL PROTECTED] has done a great job making it work. please don't trash it and reassign that entry to ITP. thanks, -- -- Robert Millan Debian GNU/Hurd user zeratul2 wanadoo eshttp://getyouriso.dyndns.org/ -- GPG ID C8D6942C 237F 8688 C2E5 BC64 E152 97B4 FB28 D41B C8D6 942C -- Some words for my friends Carnivore and Echelon -- FBI CIA NSA Assault Bomb Terrorism Jihad Allah Ossama Bin Laden Saddam Hussein Handgun Assault Plane Crash Pentagon World Trade Center Whitehouse President Bush Putin Twin Towers Air Force One USA America DeCCS RIAA BSA piracy illegal drugs heroin Big Brother is watching you defcon nuclear holocaust world war arabian afghanistan cryptography PGP GPG crack RSA algorithm Chechnya OMON Spetsnaz T-72 Merkava M1A1 Abrams Chieftain Challenger Turret Apache Missiles Skinheads troopers Kazakhstan Muhhamed Atta --- Put this in your signature and join us in confusing the Big Brother -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Applicant w/ package
On Sun, 04 Nov 2001 16:26:20 Martin Michlmayr wrote: * Roland Mas [EMAIL PROTECTED] [20011104 16:08]: Maybe it would be worth listing it on the can't be packaged page at URL:http://www.debian.org/devel/wnpp/unable-to-package? you must be confused. the patent problems are only affecting the opendivx codec. I spoke with the maintainer about this problem, the opendivx codec is just not going into the mplayer package. the program itself is GPL regarding the technical issues, the main problem was that mplayer uses higher CPU optimizations on compilation. This can be solved by including a part of the sources in the binary package and building them in postinst or even by building many mplayer-* packages. this is a hard package, Dariush Pietrzak [EMAIL PROTECTED] has done a great job making it work. please don't trash it and reassign that entry to ITP. thanks, -- -- Robert Millan Debian GNU/Hurd user zeratul2 wanadoo eshttp://getyouriso.dyndns.org/ -- GPG ID C8D6942C 237F 8688 C2E5 BC64 E152 97B4 FB28 D41B C8D6 942C -- Some words for my friends Carnivore and Echelon -- FBI CIA NSA Assault Bomb Terrorism Jihad Allah Ossama Bin Laden Saddam Hussein Handgun Assault Plane Crash Pentagon World Trade Center Whitehouse President Bush Putin Twin Towers Air Force One USA America DeCCS RIAA BSA piracy illegal drugs heroin Big Brother is watching you defcon nuclear holocaust world war arabian afghanistan cryptography PGP GPG crack RSA algorithm Chechnya OMON Spetsnaz T-72 Merkava M1A1 Abrams Chieftain Challenger Turret Apache Missiles Skinheads troopers Kazakhstan Muhhamed Atta --- Put this in your signature and join us in confusing the Big Brother
warning in Plex86
Hello, In the README file of the Plex86 program, you can find the following warning: ,-. | IMPORTANT NOTICE| |-| | This code is EXTREMELY EXPERIMENTAL, and may well result in a | | SYSTEM CRASH, and who knows what other ill effects. RUN THIS | | SOFTWARE AT YOUR OWN RISK. As a precaution, do not attempt to | | run this software on a system with important data on it, and| | make liberal use of the sync command! Expect to have to use| | the power button. | `-' Should this warning determine that this software should stay in 'unstable' and not get into 'testing' untill they make a stable release? If so, who should i contact about that matter? Also, should i make a postinst script that prints that message to ensure the user knows he/she is installing dangerous software? BTW, if anyone is already working on Plex86 please notice me ASAP. I haven't started yet. -- Robert Millan Debian GNU (Hurd) user zeratul2 wanadoo es http://getyouriso.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
warning in Plex86
Hello, In the README file of the Plex86 program, you can find the following warning: ,-. | IMPORTANT NOTICE| |-| | This code is EXTREMELY EXPERIMENTAL, and may well result in a | | SYSTEM CRASH, and who knows what other ill effects. RUN THIS | | SOFTWARE AT YOUR OWN RISK. As a precaution, do not attempt to | | run this software on a system with important data on it, and| | make liberal use of the sync command! Expect to have to use| | the power button. | `-' Should this warning determine that this software should stay in 'unstable' and not get into 'testing' untill they make a stable release? If so, who should i contact about that matter? Also, should i make a postinst script that prints that message to ensure the user knows he/she is installing dangerous software? BTW, if anyone is already working on Plex86 please notice me ASAP. I haven't started yet. -- Robert Millan Debian GNU (Hurd) user zeratul2 wanadoo es http://getyouriso.org/
sponsor distributed-net-pproxy
Hello, I've packaged a new version of the orphaned package distributed-net-pproxy, i'd make a Non-Maintainer Update myself but I'm not yet a Debian Developer. Anyone could sponsor my package and make the NMU? please contact me directly if you're interested -i'm not subscribed- and i'll send you the files. Regards, -- Robert Millan Debian GNU (Hurd) user zeratul2 wanadoo es http://getyouriso.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#102149: How can I reproduce this bug?
On Tue, 7 Aug 2001 01:33:49 -0300, Nicol=E1s Lichtmaier [EMAIL PROTECTED] wrote: I can't access that file with other FTP clients either. Could you provide me with an accessible URL which reproduces this. Can you still reproduce this with wget 1.7? Thanks hello, i'm (sigh) the reporter of this bug. Now i realize i was wrong about it and i'm very sorry. The matter is that i checked that URL with other clients *before* having problems with wget, and i attributed that to a bug in wget rather than what really was: the URL was moved and is no longer ftp://ftp.fsn.hu/pub/CDROM-Images/debian-unofficial/hurd-main.iso but ftp://ftp.fsn.hu/pub/CDROM-Images/debian-unofficial/hurd/hurd-main.iso. Never thought about the possibility of an URL change, I'm very sorry for messing this up and apologise for the inconvenience. -- Robert Millan Debian GNU (Hurd) user zeratul2 wanadoo es http://getyouriso.org/
Re: Re: Re: Re: missing file in my package
Thank you for the information. I don't have time at the moment but i'm going to learn about DH_COMPAT 2 and 3, specially when DH_COMPAT 1 is deprecated. I promise that next time i build a package for esms, i'm going to use DH_COMPAT 2 or 3. Anyhow, the actual package i made works and i'd like it to be uploaded as soon as possible (lets see if it's in time to get into woody). Could you do the NMU? thanks, -- Robert Millan Debian GNU (Hurd) user zeratul2 wanadoo es http://getyouriso.org/ On Mon, 9 Jul 2001 15:54:00 +0200, Eric Van Buggenhaut [EMAIL PROTECTED] wrote: This is how you could track the problem (say you want to know more about DH_COMPAT) : [eric@femto:~]$ grep -r DH_COMPAT /usr/share/doc/* /usr/share/doc/debhelper/TODO:* DH_COMPAT 1. Can be removed once all packages are seen to be using 2 or /usr/share/doc/debhelper/examples/rules.indep:export DH_COMPAT=3 /usr/share/doc/debhelper/examples/rules:export DH_COMPAT=3 /usr/share/doc/debhelper/examples/rules.multi2:export DH_COMPAT=3 /usr/share/doc/debhelper/examples/rules.multi:export DH_COMPAT=3 /usr/share/doc/maint-guide/maint-guide.html/ch-dreq.html: 10 export DH_COMPAT=1 [eric@femto:~]$ - First line offers me to look at /usr/share/doc/debhelper/TODO : Deprecated: * DH_COMPAT 1. Can be removed once all packages are seen to be using 2 or higher. I won't hold my breath. - Next lines suggest that DH_COMPAT is strongly tied to debhelper, so [eric@femto:~]$ man debhelper [...] Debhelper compatability levels From time to time, major non-backwards-compatible changes need to be made to debhelper, to keep it clean and well- designed as needs change and its author gains more experi- ence. To prevent such major changes from breaking existing packages, the DH_COMPAT environment variable was intro- duced. DH_COMPAT may be set to a number, to determine which major revision of debhelper should be used. There are currently 3: V1 Setting DH_COMPAT=1 (or leaving it unset) causes deb- helper to act in compatability mode. It will use debian/tmp as the package tree directory for the first binary package listed in the control file, while using debian/package for all other packages listed in the control file. This mode is deprecated. [etc.] Please keep this thread Cc'd on [EMAIL PROTECTED] Other people would be interested in following it as well as there might be other people on the list who could answer your question too. -- Eric VAN BUGGENHAUT [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: Re: Re: missing file in my package
Thank you for the information. I don't have time at the moment but i'm going to learn about DH_COMPAT 2 and 3, specially when DH_COMPAT 1 is deprecated. I promise that next time i build a package for esms, i'm going to use DH_COMPAT 2 or 3. Anyhow, the actual package i made works and i'd like it to be uploaded as soon as possible (lets see if it's in time to get into woody). Could you do the NMU? thanks, -- Robert Millan Debian GNU (Hurd) user zeratul2 wanadoo es http://getyouriso.org/ On Mon, 9 Jul 2001 15:54:00 +0200, Eric Van Buggenhaut [EMAIL PROTECTED] wrote: This is how you could track the problem (say you want to know more about DH_COMPAT) : [EMAIL PROTECTED]:~]$ grep -r DH_COMPAT /usr/share/doc/* /usr/share/doc/debhelper/TODO:* DH_COMPAT 1. Can be removed once all packages are seen to be using 2 or /usr/share/doc/debhelper/examples/rules.indep:export DH_COMPAT=3 /usr/share/doc/debhelper/examples/rules:export DH_COMPAT=3 /usr/share/doc/debhelper/examples/rules.multi2:export DH_COMPAT=3 /usr/share/doc/debhelper/examples/rules.multi:export DH_COMPAT=3 /usr/share/doc/maint-guide/maint-guide.html/ch-dreq.html: 10 export DH_COMPAT=1 [EMAIL PROTECTED]:~]$ - First line offers me to look at /usr/share/doc/debhelper/TODO : Deprecated: * DH_COMPAT 1. Can be removed once all packages are seen to be using 2 or higher. I won't hold my breath. - Next lines suggest that DH_COMPAT is strongly tied to debhelper, so [EMAIL PROTECTED]:~]$ man debhelper [...] Debhelper compatability levels From time to time, major non-backwards-compatible changes need to be made to debhelper, to keep it clean and well- designed as needs change and its author gains more experi- ence. To prevent such major changes from breaking existing packages, the DH_COMPAT environment variable was intro- duced. DH_COMPAT may be set to a number, to determine which major revision of debhelper should be used. There are currently 3: V1 Setting DH_COMPAT=1 (or leaving it unset) causes deb- helper to act in compatability mode. It will use debian/tmp as the package tree directory for the first binary package listed in the control file, while using debian/package for all other packages listed in the control file. This mode is deprecated. [etc.] Please keep this thread Cc'd on [EMAIL PROTECTED] Other people would be interested in following it as well as there might be other people on the list who could answer your question too. -- Eric VAN BUGGENHAUT [EMAIL PROTECTED]
Re: Re: [zeratul2@wanadoo.es: Bug#102811: grub: cannot access newer ext2 filesystems]
On Wed, 11 Jul 2001 00:17:43 +0200 (CEST), Santiago Vila [EMAIL PROTECTED] wrote: Robert Bihlmeyer wrote: (b) it's dubious whether another potato point release will be done at all. How can you be so certain about the dubiousness of that? :-) We should consider *all* the possibilities, including (but not limited to) that the release of woody will be delayed and there will be more potato point releases. hello, I'd like to suggest renaming it to grub1 or something and moving the woody version to potato, so we still have the chance to use both of them. regards, -- Robert Millan Debian GNU (Hurd) user zeratul2 wanadoo es http://getyouriso.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: [zeratul2@wanadoo.es: Bug#102811: grub: cannot access newer ext2 filesystems]
On Wed, 11 Jul 2001 00:17:43 +0200 (CEST), Santiago Vila [EMAIL PROTECTED] wrote: Robert Bihlmeyer wrote: (b) it's dubious whether another potato point release will be done at all. How can you be so certain about the dubiousness of that? :-) We should consider *all* the possibilities, including (but not limited to) that the release of woody will be delayed and there will be more potato point releases. hello, I'd like to suggest renaming it to grub1 or something and moving the woody version to potato, so we still have the chance to use both of them. regards, -- Robert Millan Debian GNU (Hurd) user zeratul2 wanadoo es http://getyouriso.org/
missing file in my package
Hello, I'm having some trouble in packaging a program called esms. It only consists of a single binary-all (perl) file that must go on /usr/bin/esms. The problem is that the package is created without it, here's a snapshot of an alienized package: bash-2.03$ tar -xvzf esms-0.9.0-2.tgz ./ ./usr/ ./usr/bin/ ./usr/share/ ./usr/share/doc/ ./usr/share/doc/esms/ ./usr/share/doc/esms/copyright ./usr/share/doc/esms/changelog.Debian.gz bash-2.03$ Here is the (IMHO) relevant part of my debian/rules file: install: build dh_testdir dh_testroot dh_clean -k dh_installdirs # Add here commands to install the package into debian/tmp. install -d debian/tmp/usr/bin install -m755 -o root -g root `pwd`/esms `pwd`/debian/tmp/usr/bin/esms If i missed some information let me know and i'll post it here. Thanks, -- Robert MillanDebian GNU (Hurd) user zeratul2 wanadoo eshttp://getyouriso.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: missing file in my package
On Sun, 08 Jul 2001 13:25:50 +0100, [EMAIL PROTECTED] (Colin Watson) wrote: You aren't using DH_COMPAT=2 or 3, are you? When that is set, the various debhelper commands (like dh_installdocs, which is installing your documentation, and dh_builddeb, which calls dpkg to construct the ..deb itself) use debian/package-name rather than debian/tmp. heh. as i remember, i was told to use DH_COMPAT=2 by someone who uses debian/package-name instead of debian/tmp :). thank you, -- Robert MillanDebian GNU (Hurd) user zeratul2 wanadoo eshttp://getyouriso.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
sponsor package
Hello, I've packaged esms (esms.sourceforge.net), anyone could sponsor it? thanks, -- Robert MillanDebian GNU (Hurd) user zeratul2 wanadoo eshttp://getyouriso.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: Makefile.in
On Sun, 8 Jul 2001 12:51:31 -0400, [EMAIL PROTECTED] wrote: Use the --prefix=/usr option to ./configure Then when running 'make install' do this instead: 'make install prefix=/path/to/temporary/directory' On Sun, 8 Jul 2001 13:08:57 -0400, Steve M. Robbins [EMAIL PROTECTED] wrote: Also, set --mandir=/usr/share/man and --infodir=/usr/share/info, if applicable. And if you're installing things in /etc, set --sysconfdir=/etc. In general: don't be afraid to run ./configure --help nor to read the INSTALL file! i'm sorry, i forgot to say i don't want to install it but to make a package :) will changing the prefix = @prefix@ line to prefix = /usr do? --Makefile.in SHELL = @SHELL@ srcdir = @srcdir@ top_srcdir = @top_srcdir@ VPATH = @srcdir@ prefix = @prefix@ exec_prefix = @exec_prefix@ bindir = @bindir@ sbindir = @sbindir@ libexecdir = @libexecdir@ datadir = @datadir@ sysconfdir = @sysconfdir@ sharedstatedir = @sharedstatedir@ localstatedir = @localstatedir@ libdir = @libdir@ infodir = @infodir@ mandir = @mandir@ includedir = @includedir@ oldincludedir = /usr/include --- thanks, -- Robert MillanDebian GNU (Hurd) user zeratul2 wanadoo eshttp://getyouriso.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: missing file in my package
On Mon, 9 Jul 2001 01:04:49 +0200, Eric Van Buggenhaut [EMAIL PROTECTED] wrote: What DH_COMPAT are you using ? I was using DH_COMPAT=2 as you told me in another question, now i've been told that when using the debian/tmp directory i need DH_COMPAT=1 (i noticed you are using debian/package_name directory). So don't worry it's working right now and i've finally made the package. Regards, -- Robert Millan Debian GNU (Hurd) user zeratul2 wanadoo es http://getyouriso.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
missing file in my package
Hello, I'm having some trouble in packaging a program called esms. It only consists of a single binary-all (perl) file that must go on /usr/bin/esms. The problem is that the package is created without it, here's a snapshot of an alienized package: bash-2.03$ tar -xvzf esms-0.9.0-2.tgz ./ ./usr/ ./usr/bin/ ./usr/share/ ./usr/share/doc/ ./usr/share/doc/esms/ ./usr/share/doc/esms/copyright ./usr/share/doc/esms/changelog.Debian.gz bash-2.03$ Here is the (IMHO) relevant part of my debian/rules file: install: build dh_testdir dh_testroot dh_clean -k dh_installdirs # Add here commands to install the package into debian/tmp. install -d debian/tmp/usr/bin install -m755 -o root -g root `pwd`/esms `pwd`/debian/tmp/usr/bin/esms If i missed some information let me know and i'll post it here. Thanks, -- Robert MillanDebian GNU (Hurd) user zeratul2 wanadoo eshttp://getyouriso.org/
Re: Re: missing file in my package
On Sun, 08 Jul 2001 13:25:50 +0100, [EMAIL PROTECTED] (Colin Watson) wrote: You aren't using DH_COMPAT=2 or 3, are you? When that is set, the various debhelper commands (like dh_installdocs, which is installing your documentation, and dh_builddeb, which calls dpkg to construct the ..deb itself) use debian/package-name rather than debian/tmp. heh. as i remember, i was told to use DH_COMPAT=2 by someone who uses debian/package-name instead of debian/tmp :). thank you, -- Robert MillanDebian GNU (Hurd) user zeratul2 wanadoo eshttp://getyouriso.org/
sponsor package
Hello, I've packaged esms (esms.sourceforge.net), anyone could sponsor it? thanks, -- Robert MillanDebian GNU (Hurd) user zeratul2 wanadoo eshttp://getyouriso.org/
Makefile.in
Hello,
I'm modifiing a Makefile.in to got rid of the /usr/local but i have some
doubts.
Makefile.in
SHELL = @SHELL@
srcdir = @srcdir@
top_srcdir = @top_srcdir@
VPATH = @srcdir@
prefix = @prefix@
exec_prefix = @exec_prefix@
bindir = @bindir@
sbindir = @sbindir@
libexecdir = @libexecdir@
datadir = @datadir@
sysconfdir = @sysconfdir@
sharedstatedir = @sharedstatedir@
localstatedir = @localstatedir@
libdir = @libdir@
infodir = @infodir@
mandir = @mandir@
includedir = @includedir@
oldincludedir = /usr/include
--Makefile (after running ./configure)
SHELL = /bin/sh
srcdir = .
top_srcdir = .
prefix = /usr/local
exec_prefix = ${prefix}
bindir = ${exec_prefix}/bin
sbindir = ${exec_prefix}/sbin
libexecdir = ${exec_prefix}/libexec
datadir = ${prefix}/share
sysconfdir = ${prefix}/etc
sharedstatedir = ${prefix}/com
localstatedir = ${prefix}/var
libdir = ${exec_prefix}/lib
infodir = ${prefix}/info
mandir = ${prefix}/man
includedir = ${prefix}/include
oldincludedir = /usr/include
--
Looking at the Makefile* (relevant parts below), I believe that changing the
prefix line
to prefix = /usr will solve the problem for some files but others won't have
a place to go,
for example, the /usr/etc dir does not exist.
What should i do?
thanks,
--
Robert MillanDebian GNU (Hurd) user
zeratul2 wanadoo eshttp://getyouriso.org/
Re: Re: Makefile.in
On Sun, 8 Jul 2001 12:51:31 -0400, [EMAIL PROTECTED] wrote: Use the --prefix=/usr option to ./configure Then when running 'make install' do this instead: 'make install prefix=/path/to/temporary/directory' On Sun, 8 Jul 2001 13:08:57 -0400, Steve M. Robbins [EMAIL PROTECTED] wrote: Also, set --mandir=/usr/share/man and --infodir=/usr/share/info, if applicable. And if you're installing things in /etc, set --sysconfdir=/etc. In general: don't be afraid to run ./configure --help nor to read the INSTALL file! i'm sorry, i forgot to say i don't want to install it but to make a package :) will changing the prefix = @prefix@ line to prefix = /usr do? --Makefile.in SHELL = @SHELL@ srcdir = @srcdir@ top_srcdir = @top_srcdir@ VPATH = @srcdir@ prefix = @prefix@ exec_prefix = @exec_prefix@ bindir = @bindir@ sbindir = @sbindir@ libexecdir = @libexecdir@ datadir = @datadir@ sysconfdir = @sysconfdir@ sharedstatedir = @sharedstatedir@ localstatedir = @localstatedir@ libdir = @libdir@ infodir = @infodir@ mandir = @mandir@ includedir = @includedir@ oldincludedir = /usr/include --- thanks, -- Robert MillanDebian GNU (Hurd) user zeratul2 wanadoo eshttp://getyouriso.org/
Re: Re: Re: Makefile.in
On Sun, 8 Jul 2001 15:06:31 -0400, Steve M. Robbins [EMAIL PROTECTED] wrote: Making a package involves installing it! You had better re-read the packaging manual. The New Maintainer's Guide http://www.debian.org/doc/maint-guide/ is quite good. But the maint-guide tells me to modify the Makefile.in file, in order to build the package with dpkg-buildpackage -rfakeroot later. I'd like to create a source package so i can compile it later for specific archs, does this procedure create a source package too? thank you, -- Robert MillanDebian GNU (Hurd) user zeratul2 wanadoo eshttp://getyouriso.org/
Re: Re: missing file in my package
On Mon, 9 Jul 2001 01:04:49 +0200, Eric Van Buggenhaut [EMAIL PROTECTED] wrote: What DH_COMPAT are you using ? I was using DH_COMPAT=2 as you told me in another question, now i've been told that when using the debian/tmp directory i need DH_COMPAT=1 (i noticed you are using debian/package_name directory). So don't worry it's working right now and i've finally made the package. Regards, -- Robert Millan Debian GNU (Hurd) user zeratul2 wanadoo es http://getyouriso.org/
Re: Re: Change of package name or command name.
On Thu, 28 Jun 2001 17:11:13 +0200, Roland Mas [EMAIL PROTECTED] wrote: Richard Braakman (2001-06-28 18:00:46 +0300) : On Thu, Jun 28, 2001 at 07:08:33AM +0900, Yooseong Yang wrote: Yes. poEdit is a horrible name. Command names should be all lowercase. What item in Debian Policy? you mean policy 2.3.1 or something? It's not in Debian Policy, it's a Unix tradition going back 30 years. One single letter: X :-) hey X is not in POSIX standards, and you must agree that every traditional unix command out there is lowercase. how bout poedit2? -- Robert MillanDebian GNU user zeratul2 wanadoo eshttp://getyouriso.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
error when building package
Hello,
when i run dpkg-buildpackage -rfakeroot to create a package, i get the following
error:
dpkg-deb: parse error, in file `debian/esms/DEBIAN/control' near line 6 package `esms':
`Depends' field, missing package name, or garbage where package name expected
dh_builddeb: command returned error code
while my debian/esms/DEBIAN/control file looks correct:
Package: esms
Version: 0.8.5-1
Section: comm
Priority: optional
Architecture: i386
Depends: ,perl-base, libwww-perl
Suggests: fortune
Installed-Size: 44
Maintainer: Robert Millan [EMAIL PROTECTED]
Description: [...]
[...]
and so does my debian/control file:
Source: esms
Section: comm
Priority: optional
Maintainer: Robert Millan [EMAIL PROTECTED]
Standards-Version: 3.0.1
Package: esms
Architecture: any
Depends: ${shlibs:Depends}, perl-base, libwww-perl
Suggests: fortune
Description: [...]
[...]
note that i have tried putting perl-base, libwww-perl before ${shlibs:Depends} to
avoid that strange comma and yet didn't work.
--
Robert MillanDebian GNU user
zeratul2 wanadoo eshttp://getyouriso.org/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Advocate/Sponsor
Do you mean an advocate? When you submit your appliance to join debian, an advocate geographically near will contact you for meeting. You need to meet him/her to prove your identity so debian allows you to join the community. see http://nm.debian.org/ for more info. -- Robert MillanDebian GNU user zeratul2 wanadoo eshttp://getyouriso.org/
Re: Re: Change of package name or command name.
On Thu, 28 Jun 2001 17:11:13 +0200, Roland Mas [EMAIL PROTECTED] wrote: Richard Braakman (2001-06-28 18:00:46 +0300) : On Thu, Jun 28, 2001 at 07:08:33AM +0900, Yooseong Yang wrote: Yes. poEdit is a horrible name. Command names should be all lowercase. What item in Debian Policy? you mean policy 2.3.1 or something? It's not in Debian Policy, it's a Unix tradition going back 30 years. One single letter: X :-) hey X is not in POSIX standards, and you must agree that every traditional unix command out there is lowercase. how bout poedit2? -- Robert MillanDebian GNU user zeratul2 wanadoo eshttp://getyouriso.org/
binary-all packaging
Hello, I'm on my first package. The upstream people provide just a perl script which should go to /usr/bin. I'm reading the instructions of the maintainer's guide (/usr/share/doc/maint-guide/) and all the steps and examples are desgned for creatinga binary package from a source tarball. I've tried to configure this file myself, but when i issue the command 'dpkg-buildpackage -rfakeroot' i always get the same error: dpkg-genchanges: failure: cannot read files list file: No such file or directory What am i doing wrong? I guess i have a problem in my rules file. just in case i post it here too: --./debian/rules #!/usr/bin/make -f # Sample debian/rules that uses debhelper. # GNU copyright 1997 to 1999 by Joey Hess. # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 # This is the debhelper compatability version to use. export DH_COMPAT=1 build: clean: install: dh_testdir dh_testroot # Add here commands to install the package into debian/tmp. mkdir -p `pwd`/debian/tmp/usr/bin /bin/cp `pwd`/esms `pwd`/debian/tmp/usr/bin/ # Build architecture-independent files here. binary-indep: build install # We have nothing to do by default. # Build architecture-dependent files here. binary-arch: build install binary: binary-indep binary-arch .PHONY: build clean binary-indep binary-arch binary install --EOF thanks-- Robert MillanDebian GNU user zeratul2 wanadoo eshttp://getyouriso.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
binary-all packaging
Hello, I'm on my first package. The upstream people provide just a perl script which should go to /usr/bin. I'm reading the instructions of the maintainer's guide (/usr/share/doc/maint-guide/) and all the steps and examples are desgned for creatinga binary package from a source tarball. I've tried to configure this file myself, but when i issue the command 'dpkg-buildpackage -rfakeroot' i always get the same error: dpkg-genchanges: failure: cannot read files list file: No such file or directory What am i doing wrong? I guess i have a problem in my rules file. just in case i post it here too: --./debian/rules #!/usr/bin/make -f # Sample debian/rules that uses debhelper. # GNU copyright 1997 to 1999 by Joey Hess. # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 # This is the debhelper compatability version to use. export DH_COMPAT=1 build: clean: install: dh_testdir dh_testroot # Add here commands to install the package into debian/tmp. mkdir -p `pwd`/debian/tmp/usr/bin /bin/cp `pwd`/esms `pwd`/debian/tmp/usr/bin/ # Build architecture-independent files here. binary-indep: build install # We have nothing to do by default. # Build architecture-dependent files here. binary-arch: build install binary: binary-indep binary-arch .PHONY: build clean binary-indep binary-arch binary install --EOF thanks-- Robert MillanDebian GNU user zeratul2 wanadoo eshttp://getyouriso.org/
