Hi!
I hope that I've selected the correct debian mailing list for this
question. But if not, I would appreciate if you could redirect properly.
I am just starting to learn about debian packaging with the goal of
creating debian packages for our systems. These would be proprietary
packages fo
lso (really really stupid question).. where do i get these sources for
the packages you guys mentioned?
Eric
Bernhard R. Link wrote:
* Eric Winger <[EMAIL PROTECTED]> [030807 21:54]:
> But in following the instructions in the doc it tells me to create some
> directories with my s
should have added that I also tried the fakeroot /debian/rules binary to
build the .deb, but it just told me that it didn't find a file on a line
that didn't exist in my /rules file.
eric
Winger, Eric wrote:
thx to all for the responses. I'm slowly making progress here
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
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
t for me. Does this seem correct?
thx,
Eric
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 section and how that applies to
> debian pa
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 distingu
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
this general type of question already. In
the meantime, I"ll keep browsing the docs I have. Hopefully, the kind of
questions I'm working on are clear. Because they effect things like
purge & remove steps too.
thx
Eric
Matthew Palmer wrote:
On Thu, Aug 07, 2003 at 12:54:08PM -
Goswin von Brederlow wrote:
Hi,
by the way, do you use "debuild" to build your package?
I'm using dpkg-buildpackage -rfakeroot
That way Debian will do some more checks before and after build like
build dependencies and lintian runs. Lintian will catch a lot of
little mistakes one can make
Ok, I got a few more things understood including what directories get
built inside of debian, etc. So I think I understand better what is
being installed where, so again, disregard the last email.
I've gotten a package to correctly deliver a .bin to a folder &
successfully run that on install.
After having spent some time this week learning the very basics about
debian packaging, I wrote a simple (~ 2 pages) tutorial for others in
our software group to follow. A simplistic step-by-step guide without a
lot of explanation. And it only covers loading necessary packages,
dh_make, dpkg-bu
Hi!
Continuing our investigation into debian packages, we'd like to be able
to create our own internal archive/repository for just our packages.
Then change our sources.list file to point at that and be able to use
the apt-get engines to update our code on any machine at any of our
facilities
Christopher W. Curtis wrote:
A quick google for "apt repository howto", besides pulling up a
surprising number of links about RPMs, also brings up these two:
http://www.debian.org/doc/manuals/repository-howto/repository-howto.html
Thanks to everyone for their responses. This link has prove
Probably a simple question. But I've created a local repository. Figured
out how dput moved packages into the archive. Worked through
atp-ftparchive and created a Packages.gz file, got sources-list to point
at my archive correctly.
But when I do a
apt-get install spinelli (spinelli is my packa
AIL PROTECTED]>
Architecture: i386
Version: 0.9
Filename: ./spinelli_0.9_i386.deb
Size: 131164
MD5sum: 9ef6eb14c9b242b5c76dbcd739a1034b
Description:
which has version 0.9
Eric
Christopher Curtis wrote:
Eric Winger wrote:
> But when I do a
> apt-get install spinelli (spinelli is my package)
[EMAIL PROTECTED] wrote:
What does the tree structure of your repository look like (where are the
packages , where is Packages.gz etc ) and where do you point to in
/etc/apt/sources.list ?
The directory structure of my archive looks like this:
~/archive/binary$ ls
Packages.gz spinelli
Matt Zimmerman wrote:
>
> deb file:///home/ewinger/archive binary/
These are incompatible. Either create Packages relative to archive (not
binary), or use
deb file:///home/ewinger/archive/binary ./
or such
--
- mdz
I tried using
deb file:///home/ewinger/archive/binary ./
&
moving the
Geert Stappers wrote:
I missed the architecture in your archive directory lay-out.
Architecture is something like 'alpha', 'powerpc'. or 'ia64'
[EMAIL PROTECTED]:/pub/debian/dists/sarge/main
$ pwd
/pub/debian/dists/sarge/main
[EMAIL PROTECTED]:/pub/debian/dists/sarge/main
$ ls
binary-alpha bi
Christopher Curtis wrote:
Eric: This is really very simple.
I think part of the problem, is that the original problem got lost. I'll
snip your comments, because I believe I understand and correctly have
implemented what you talked about. The problem is that for some reason,
I can't install
Got it! My package installed! Thank you Thank you Thank you everyone. I
think I was confusing the two types of repositories and how to access
them (automagic & simple - from the repository howto).
Sorry for delayed response.
Goswin von Brederlow wrote:
Luk Claes <[EMAIL PROTECTED]> writes:
Goswin von Brederlow wrote:
PS: carefull with File://, apt-get source will create links into the
mirror and debuild will then erase the files from the repository and
replace them when you rebuild.
I guess I don't follow the warnings enough to heed them.
I thought looking at the man page of de
In putting my packages to my local repository, I've encountered a number
of messages & questions.
When running dpkg-scanpackages I got this message:
! Package spinelli (filename pool/spinelli_0.9_i386.deb) is repeat;
ignored that one and using data from pool/spinelli_0.10_i386.deb !
I'm usin
The question, basically is this: "How does one have a .deb package which
replaces/overwrites files from another package (in this case a
dependency)?"
The specific example is this. We want to use autofs. For our turnkey
systems, we want to have our own little package, that "configures" the
aut
Geert Stappers wrote:
On Wed, Aug 27, 2003 at 04:36:22PM -0700, Eric Winger wrote:
> The question, basically is this: "How does one have a .deb package
which
> replaces/overwrites files from another package (in this case a
> dependency)?"
Dependency means that a package w
Jamie Wilkinson was heard to have trumpeted:
This one time, at band camp, Eric Winger wrote:
>I'm thinking there's got to be a "higher level" way of handling this
>type of scenario.
Firstly, you can't really Depend on and then Replace a package at the
same
ti
I decided to format my simple primer into a better format than just
text. If anyone would like a copy, feel free to ask.
On Thu, Aug 14, 2003 at 04:02:18PM -0700, Eric Winger wrote:
> After having spent some time this week learning the very basics about
> debian packaging, I wrote a simpl
Hi!
I hope that I've selected the correct debian mailing list for this
question. But if not, I would appreciate if you could redirect properly.
I am just starting to learn about debian packaging with the goal of
creating debian packages for our systems. These would be proprietary
packages for
lso (really really stupid question).. where do i get these sources for
the packages you guys mentioned?
Eric
Bernhard R. Link wrote:
* Eric Winger <[EMAIL PROTECTED]> [030807 21:54]:
> But in following the instructions in the doc it tells me to create some
> directories with my source
Goswin von Brederlow wrote:
Hi,
by the way, do you use "debuild" to build your package?
I'm using dpkg-buildpackage -rfakeroot
That way Debian will do some more checks before and after build like
build dependencies and lintian runs. Lintian will catch a lot of
little mistakes one can make lik
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 those
should have added that I also tried the fakeroot /debian/rules binary to
build the .deb, but it just told me that it didn't find a file on a line
that didn't exist in my /rules file.
eric
Winger, Eric wrote:
thx to all for the responses. I'm slowly making progress here
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 de
t for me. Does this seem correct?
thx,
Eric
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 section and how that applies to
> debian pa
this general type of question already. In
the meantime, I"ll keep browsing the docs I have. Hopefully, the kind of
questions I'm working on are clear. Because they effect things like
purge & remove steps too.
thx
Eric
Matthew Palmer wrote:
On Thu, Aug 07, 2003 at 12:54:08PM -
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
Ok, I got a few more things understood including what directories get
built inside of debian, etc. So I think I understand better what is
being installed where, so again, disregard the last email.
I've gotten a package to correctly deliver a .bin to a folder &
successfully run that on install.
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 distingu
Hi!
Continuing our investigation into debian packages, we'd like to be able
to create our own internal archive/repository for just our packages.
Then change our sources.list file to point at that and be able to use
the apt-get engines to update our code on any machine at any of our
facilities.
Christopher W. Curtis wrote:
A quick google for "apt repository howto", besides pulling up a
surprising number of links about RPMs, also brings up these two:
http://www.debian.org/doc/manuals/repository-howto/repository-howto.html
Thanks to everyone for their responses. This link has proved ver
Probably a simple question. But I've created a local repository. Figured
out how dput moved packages into the archive. Worked through
atp-ftparchive and created a Packages.gz file, got sources-list to point
at my archive correctly.
But when I do a
apt-get install spinelli (spinelli is my packag
gt;
Architecture: i386
Version: 0.9
Filename: ./spinelli_0.9_i386.deb
Size: 131164
MD5sum: 9ef6eb14c9b242b5c76dbcd739a1034b
Description:
which has version 0.9
Eric
Christopher Curtis wrote:
Eric Winger wrote:
> But when I do a
> apt-get install spinelli (spinelli is my package)
>
[EMAIL PROTECTED] wrote:
What does the tree structure of your repository look like (where are the
packages , where is Packages.gz etc ) and where do you point to in
/etc/apt/sources.list ?
The directory structure of my archive looks like this:
~/archive/binary$ ls
Packages.gz spinelli_0.9
Matt Zimmerman wrote:
>
> deb file:///home/ewinger/archive binary/
These are incompatible. Either create Packages relative to archive (not
binary), or use
deb file:///home/ewinger/archive/binary ./
or such
--
- mdz
I tried using
deb file:///home/ewinger/archive/binary ./
&
moving the conten
Geert Stappers wrote:
I missed the architecture in your archive directory lay-out.
Architecture is something like 'alpha', 'powerpc'. or 'ia64'
[EMAIL PROTECTED]:/pub/debian/dists/sarge/main
$ pwd
/pub/debian/dists/sarge/main
[EMAIL PROTECTED]:/pub/debian/dists/sarge/main
$ ls
binary-alpha binary
Christopher Curtis wrote:
Eric: This is really very simple.
I think part of the problem, is that the original problem got lost. I'll
snip your comments, because I believe I understand and correctly have
implemented what you talked about. The problem is that for some reason,
I can't install t
Got it! My package installed! Thank you Thank you Thank you everyone. I
think I was confusing the two types of repositories and how to access
them (automagic & simple - from the repository howto).
Sorry for delayed response.
Goswin von Brederlow wrote:
Luk Claes <[EMAIL PROTECTED]> writes:
Goswin von Brederlow wrote:
PS: carefull with File://, apt-get source will create links into the
mirror and debuild will then erase the files from the repository and
replace them when you rebuild.
I guess I don't follow the warnings enough to heed them.
I thought looking at the man page of debuil
In putting my packages to my local repository, I've encountered a number
of messages & questions.
When running dpkg-scanpackages I got this message:
! Package spinelli (filename pool/spinelli_0.9_i386.deb) is repeat;
ignored that one and using data from pool/spinelli_0.10_i386.deb !
I'm using
The question, basically is this: "How does one have a .deb package which
replaces/overwrites files from another package (in this case a
dependency)?"
The specific example is this. We want to use autofs. For our turnkey
systems, we want to have our own little package, that "configures" the
auto
Geert Stappers wrote:
On Wed, Aug 27, 2003 at 04:36:22PM -0700, Eric Winger wrote:
> The question, basically is this: "How does one have a .deb package
which
> replaces/overwrites files from another package (in this case a
> dependency)?"
Dependency means that a package w
Jamie Wilkinson was heard to have trumpeted:
This one time, at band camp, Eric Winger wrote:
>I'm thinking there's got to be a "higher level" way of handling this
>type of scenario.
Firstly, you can't really Depend on and then Replace a package at the
same
ti
I decided to format my simple primer into a better format than just
text. If anyone would like a copy, feel free to ask.
On Thu, Aug 14, 2003 at 04:02:18PM -0700, Eric Winger wrote:
> After having spent some time this week learning the very basics about
> debian packaging, I wrote a simpl
53 matches
Mail list logo
