On Tue, Aug 12, 2003 at 04:40:42PM -0700, Eric Winger wrote:
> Ok, I've managed to create a .deb package, experimented with putting
> things in the rules file, installed my package locally. Learned a little
> about purge and kind of have the gist of what y'all have been trying to
> pound into my
On Tue, Aug 12, 2003 at 04:40:42PM -0700, Eric Winger wrote:
> I've modified the postinst.ex file, but my commands aren't being
> executed. And the Debian New Maintainers' Guide says I shouldn't do this
> (add to maintainer scripts) yet. So that tells me I should be putting my
> configuration co
On Tue, Aug 12, 2003 at 04:40:42PM -0700, Eric Winger wrote:
> Any ideas? Or is the postinst.ex file correct, and i may be not writing
> the script correctly. I just added:
>
> cp myFile /hardcoded path/
> ./path/myFile (wishing to run that file)
.ex stands for example. remove the .ex.
I sugges
On Tue, Aug 12, 2003 at 11:53:27AM -0700, Eric Winger wrote:
> Colin Watson wrote:
> >That's correct except that you want "non-free" there, not "free".
> >(Ever think you'd hear a Debian developer say that?)
>
> would it be sacreligious to ask why sources are kept in non-free?
I think one of us
Ok, I've managed to create a .deb package, experimented with putting
things in the rules file, installed my package locally. Learned a little
about purge and kind of have the gist of what y'all have been trying to
pound into my head.
But now I've run into a problem. For my first package, which
Eric Winger wrote:
> would it be sacreligious to ask why sources are kept in non-free?
You are asking an obvious question and the answer is the obvious one.
The sources are in non-free because they are not free. Look at the
copyrights of any of the packages in non-free and you will see that
they
Eric Winger <[EMAIL PROTECTED]> writes:
> ok, I've managed to make a .deb file & a big ol tarball. Questions:
> * I thought that the .deb file would end up containing all of my
> * files, but the only thing that could possible hold my source is the
> * big tarball that dpkg-buildpackage built for
After e-mailing the current maintainer several times over the last
month, and recieving no reply I have cleaned up my package for the new
upstream version og HMMER. The packages are almost linda + lintian
clean, the only complaints are that the *-pvm programs (which aren't
used by the user, they a
oops, shouldn't have posted so soon. I found the dpkg -i .deb option.
I'll work through that. sorry
Matthew Palmer wrote:
On Mon, Aug 11, 2003 at 04:16:31PM -0700, Eric Winger wrote:
> thx to all for the responses. I'm slowly making progress here. Could
> someone distinguish the configuration
ok, I've managed to make a .deb file & a big ol tarball. Questions:
* I would like to test install this package but not go through the
apt-get stuff, because i believe it goes to sources.list etc. Is there a
simple way to simulate this load to see if my commands run successfully?
Or even load
Eric Winger <[EMAIL PROTECTED]> writes:
> Ahh, this brings up a point that has bothered me about debian. Well
> actually in this case, two points.
>
> * all the deb-src entries i tried to add to my sources.list give me
> * errors when I try to get the source. What is the url for sources?
> * This
Colin Watson wrote:
That's correct except that you want "non-free" there, not "free".
(Ever think you'd hear a Debian developer say that?)
would it be sacreligious to ask why sources are kept in non-free?
I found it easiest (years ago) to read the sources.list(5) man page and
learn how th
On Ter, 2003-08-12 at 14:38, Eric Winger wrote:
> * all the deb-src entries i tried to add to my sources.list give me
> errors when I try to get the source. What is the url for sources? This
> is my latest attempt:
>
> deb-src ftp://ftp.debian.org/debian testing main contrib free
My sources.lis
On Tue, Aug 12, 2003 at 10:38:06AM -0700, Eric Winger wrote:
> Matthew Palmer wrote:
> >The easiest way for packages in the actual archive is to run 'apt-get
> >source '. That'll download the sources and unpack them into
> >the current directory.
>
> Ahh, this brings up a point that has bothered
Matthew Palmer wrote:
The easiest way for packages in the actual archive is to run 'apt-get
source
'. That'll download the sources and unpack them into the
current
directory.
Ahh, this brings up a point that has bothered me about debian. Well
actually in this case, two points.
* all the
Hi,
This is my third or fourth attempt to find a sponsor for the
python-albatross package. So far, I've been contacted by one developer
who was interested in sponsoring the package; he never replied to my
reply, however, so I assume he has other things to do at the moment.
Meanwhile, I'm continuin
> Will the packaging tools complain if you have no copyright file, too? I
> know it's necessary for uploading, of course, and I'm sure lintian would
> have a right whinge, but will (eg) debhelper scripts have a complain, to
> your knowledge?
Nope. Neither dpkg-* nor debhelper will complain. (Tried
Hi all,
I am preparing new Debian packages for CMS Midgard.
My idea is to let users manage with their databases and hosts
with debconf and dpkg instead of writing one config and postinst
for setup and updates and another one tools for managing existing
ones in a future. So simply I would like to
Hello!
I'd like to maintain package with game 'Neverball' and am looking for a
Sponsor (and an Advocate when I prove to be a worthy Applicant :-)
Package description:
Neverball is a colorful 3D arcade game in which you tilt the floor to
roll the ball through the obstacle course before time runs o
Hello!
I'd like to maintain package with game 'Neverball' and am looking for a
Sponsor (and an Advocate when I prove to be a worthy Applicant :-)
Package description:
Neverball is a colorful 3D arcade game in which you tilt the floor to
roll the ball through the obstacle course before time runs o
On Fri, 8 Aug 2003 00:32:37 -0700
Steve Lamb <[EMAIL PROTECTED]> wrote:
> Description: Parity Archive v2
> This utility applies the data-recover capability concepts of RAID-like
> systems to individual and multiple files. It is most commonly used in
> the posting and recovery of multipart archi
Peter Nome <[EMAIL PROTECTED]> writes:
> On a woody base install, I'm getting lots of post-installation script errors,
> like this:
>
> # dpkg -i sed_3.02-8_i386.deb
> (Reading database ... 6623 files and directories currently installed.)
> Preparing to replace sed 3.02-8 (using sed_3.02-8_i386.
Peter Nome <[EMAIL PROTECTED]> schrieb:
> On a woody base install, I'm getting lots of post-installation script errors,
> like this:
>
> # dpkg -i sed_3.02-8_i386.deb
> (Reading database ... 6623 files and directories currently installed.)
> Preparing to replace sed 3.02-8 (using sed_3.02-8_i386.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On a woody base install, I'm getting lots of post-installation script errors,
like this:
# dpkg -i sed_3.02-8_i386.deb
(Reading database ... 6623 files and directories currently installed.)
Preparing to replace sed 3.02-8 (using sed_3.02-8_i386.deb) ...
/var/lib/dpkg/info/sed.prerm: line 9: 65
25 matches
Mail list logo
