Like I said I am probably over thinking.
Sent from my iPhone
> On Dec 11, 2016, at 4:00 AM, Andrey Rahmatullin wrote:
>
> On Sun, Dec 11, 2016 at 01:24:26AM -0700, Herminio Hernandez Jr wrote:
Let me try to clarify. Did my package use the code from upstream or the
code from the watc
On Sun, Dec 11, 2016 at 01:24:26AM -0700, Herminio Hernandez Jr wrote:
> > > Let me try to clarify. Did my package use the code from upstream or the
> > > code from the watch file to build.
> >
> > Please read how gbp works.
> > gbp uses the version from d/changelog to find the upstream tag which
On Sunday, December 11, 2016 1:20:05 PM MST Andrey Rahmatullin wrote:
> On Sun, Dec 11, 2016 at 01:16:21AM -0700, Herminio Hernandez Jr wrote:
> > Let me try to clarify. Did my package use the code from upstream or the
> > code from the watch file to build.
>
> Please read how gbp works.
> gbp use
On Sun, Dec 11, 2016 at 01:16:21AM -0700, Herminio Hernandez Jr wrote:
> Let me try to clarify. Did my package use the code from upstream or the code
> from the watch file to build.
Please read how gbp works.
gbp uses the version from d/changelog to find the upstream tag which it
then uses to recr
On Sunday, December 11, 2016 12:57:40 PM MST Andrey Rahmatullin wrote:
> On Sat, Dec 10, 2016 at 11:04:30PM -0700, Herminio Hernandez Jr wrote:
> > I have a question regarding packaging using git and the watch file in the
> > Debian directory. There is an open bug 794438 for the KDE Partition
> > M
On Sat, Dec 10, 2016 at 11:04:30PM -0700, Herminio Hernandez Jr wrote:
> I have a question regarding packaging using git and the watch file in the
> Debian directory. There is an open bug 794438 for the KDE Partition Manager.
> The current package is broken in Sid. In the thread it was mentioned
Dear Mentors,
I have a question regarding packaging using git and the watch file in the
Debian directory. There is an open bug 794438 for the KDE Partition Manager.
The current package is broken in Sid. In the thread it was mentioned that the
KDE Neon has a working package. When I pulled the gi
On Sat, Mar 27, 2010 at 08:24:05PM +0100, Wuttke, Joachim wrote:
> Thank you, Stanislav, for your helpful explanations.
>
> Regarding the name of the package:
> For many years the upstream project has been called "lmfit"
> (since the main application is curve fitting), but the shared
> library has
Thank you, Stanislav, for your helpful explanations.
Regarding the name of the package:
For many years the upstream project has been called "lmfit"
(since the main application is curve fitting), but the shared
library has been called "lmmin.so" (since the fundamental
mathematical operation is mini
On Sat, Mar 27, 2010 at 06:57:03PM +0100, Wuttke, Joachim wrote:
> One more question (which possibly elucidates my previous questions):
>
> The upstream project is structured as follows:
>
> lmfit/configure.ac
> lmfit/Makefile.am
> # ... and all the resulting autotools stuff
>
> lmfit/lib/ # con
On Sat, Mar 27, 2010 at 06:35:42PM +0100, Wuttke, Joachim wrote:
> Dear specialists,
>
> I need more help. Specifically, I am going to ask 3 questions.
>
> My debian directory is still messed up, as it has been from the beginning:
> either the automatic scripts are not ready to assist in generat
One more question (which possibly elucidates my previous questions):
The upstream project is structured as follows:
lmfit/configure.ac
lmfit/Makefile.am
# ... and all the resulting autotools stuff
lmfit/lib/ # contains library sources and the include file lmmin.h
lmfit/demo/ # contains applicat
Dear specialists,
I need more help. Specifically, I am going to ask 3 questions.
My debian directory is still messed up, as it has been from the beginning:
either the automatic scripts are not ready to assist in generating a
shared-library
package, or I used them in wrong way.
Here my control
On September 15, 2007 07:20:29 pm Peter wrote:
> If I post this question in the wrong list please tell me where to ask
> the question :)
>
> I created an update package and it install perfectly but for one thing.
> If I install an earlier version, my package won't show up as an update.
> It's the
Matthew Palmer wrote:
> On Sat, Sep 15, 2007 at 07:20:29PM -0400, Peter wrote:
>> If I post this question in the wrong list please tell me where to ask
>> the question :)
>>
>> I created an update package and it install perfectly but for one thing.
>> If I install an earlier version, my package wo
On Sat, Sep 15, 2007 at 07:20:29PM -0400, Peter wrote:
> If I post this question in the wrong list please tell me where to ask
> the question :)
>
> I created an update package and it install perfectly but for one thing.
> If I install an earlier version, my package won't show up as an update.
>
On 15/09/2007, Peter <[EMAIL PROTECTED]> wrote:
> If I post this question in the wrong list please tell me where to ask
> the question :)
>
>
> So what do I need to do to make my package be seen as an update?
First of all, I would ask you why you have 1: in the package version.
Usually that's add
If I post this question in the wrong list please tell me where to ask
the question :)
I created an update package and it install perfectly but for one thing.
If I install an earlier version, my package won't show up as an update.
It's the first time this has happened. I believe I know why it does
On 2006-11-14, Ritesh Raj Sarraf <[EMAIL PROTECTED]> wrote:
> How would I then add entry of the old changelog into the current knetstats
> package i.e. 1.6.2 ?
>
> I hope there is a proper way to tackle such situations.
apt-get install devscripts
man uupdate
it does exactly what you ask for.
/S
On Tue, Nov 14, 2006, Frank Küster wrote:
> > How would I then add entry of the old changelog into the current knetstats
> > package i.e. 1.6.2 ?
> If the diff.gz contains only files in the debian directory (i.e. your
> changes are organized in patches, or you don't have source changes),
> then you
On Tue, Nov 14, 2006 at 03:00:40PM +0530, Ritesh Raj Sarraf wrote:
> Hi,
Hello,
> My question is:
> Currently knentstats is at version 1.6.1.
> How would I repackage knetstats when version 1.6.2 is released ?
There are several ways. Personally, I just get the new upstream tarball,
unpack it, re
Ritesh Raj Sarraf <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I've package knetstats for Debian.
>
> Currently I ran dh_make and did the packaging. dh_make created the debian/
> subfolder and I did the necessary changes to build the package. All is fine
> till here.
>
> My question is:
> Currently knents
Hi,
I've package knetstats for Debian.
Currently I ran dh_make and did the packaging. dh_make created the debian/
subfolder and I did the necessary changes to build the package. All is fine
till here.
My question is:
Currently knentstats is at version 1.6.1.
How would I repackage knetstats when
Am Dienstag, den 29.08.2006, 15:54 -0400 schrieb Jean-Sebastien Pilon:
[..]
> > What's inside libpcap-ring1.install and libpcap-ring-dev.install? You
> > need to "copy" the files from debian/tmp to debian/$package
>
>
> # cat debian/libpcap-ring1.install
> usr/local/lib/lib*.so.*
>
> # cat deb
>
> Am Dienstag, den 29.08.2006, 12:44 -0400 schrieb Jean-Sebastien Pilon:
>
> > I am trying to create packages from sources for libpcap
> compiled with
> > the libpfring library. This compiles no problem. When I am packaging
> > though... there are the issues coming up Wink
> >
> > # fakeroot
Am Dienstag, den 29.08.2006, 12:44 -0400 schrieb Jean-Sebastien Pilon:
> I am trying to create packages from sources for libpcap compiled with
> the libpfring library. This compiles no problem. When I am packaging
> though... there are the issues coming up Wink
>
> # fakeroot debian/rules clean
>
Hello,
I am trying to create packages from sources for libpcap compiled with
the libpfring library. This compiles no problem. When I am packaging
though... there are the issues coming up Wink
# fakeroot debian/rules clean
# debian/rules build
# debian/rules binary
till now it's ok
i have 2 .d
See my recent message to -mentors and -devel, "Nonpublic shared
libraries." It sees that rpath could be used here because it is a
"private" library, not used by other packages. In the future, if that
changes, it will have to have a soname. For now, you could also just
install to /usr/lib/libSyno
Hi,
I am currently adopting synopsis, a source code documentation
tool specially suited for python, but also useable for
C and C++. I created a first package from the new upstream
version which is available at http://www.littletux.net/debian.
The package is not yet lintian clean, and this leads
Hi all,
I have upgraded the automake to 1.7.9 and that took care
of some the errors
but when i try to generate the Makefile through the configure
command it gives me an error saying saying that the script file is not
found which is mainboard.py .
Which i think due to a path that it did not fi
Hi all,
I have upgraded the automake to 1.7.9 and that took care
of some the errors
but when i try to generate the Makefile through the configure
command it gives me an error saying saying that the script file is not
found which is mainboard.py .
Which i think due to a path that it did not fi
On Thu, 19 Aug 2004 12:33:44 -0600
Amr Nasr <[EMAIL PROTECTED]> wrote:
> Makefile:18: *** missing separator (did you mean TAB instead of 8
> spaces?). Stop.
objective: dependencies
rules
These separators *must* be one tab keypress, not spaces. All of them.
Maybe your editor has
On Thu, Aug 19, 2004 at 12:33:44PM -0600, Amr Nasr wrote:
>hi all ,
>I have read the debian Maintainers' Guide for Creating debian Packages
>and i was following it for creation of the package and then when i run
>*dh_make* according to the instructions i get errors related to the
>Makefile that i
On Thu, 19 Aug 2004 12:33:44 -0600
Amr Nasr <[EMAIL PROTECTED]> wrote:
> Makefile:18: *** missing separator (did you mean TAB instead of 8
> spaces?). Stop.
objective: dependencies
rules
These separators *must* be one tab keypress, not spaces. All of them.
Maybe your editor has
On Thu, Aug 19, 2004 at 12:33:44PM -0600, Amr Nasr wrote:
>hi all ,
>I have read the debian Maintainers' Guide for Creating debian Packages
>and i was following it for creation of the package and then when i run
>*dh_make* according to the instructions i get errors related to the
>Makefile that i
hi all ,
I have read the debian Maintainers' Guide for Creating debian Packages
and i was following it for creation of the package and then when i run
dh_make according to the instructions i get errors related to
the Makefile that i have
modified as i am trying to install a script and get
hi all ,
I have read the debian Maintainers' Guide for Creating debian Packages
and i was following it for creation of the package and then when i run
dh_make according to the instructions i get errors related to
the Makefile that i have
modified as i am trying to install a script and get
On Thu, Aug 05, 2004 at 08:42:50AM -0700, Josh Lauricha wrote:
> On Thu 08/05/04 17:35, Brian Sutherland wrote:
> > Make sure that if the package is uninstalled, the cron job is
> > disabled?
>
> I'd do something like:
> # a bunch of lines for setting the command-line options or sourceing
> # /etc
On Thu, Aug 05, 2004 at 08:42:50AM -0700, Josh Lauricha wrote:
> On Thu 08/05/04 17:35, Brian Sutherland wrote:
> > Make sure that if the package is uninstalled, the cron job is
> > disabled?
>
> I'd do something like:
> # a bunch of lines for setting the command-line options or sourceing
> # /etc
Im stunned. Three answers in under an hour.
Thanks world.
--
Brian Sutherland
"There has got to be more to life than just being really,
really, really, ridiculously good-looking." -- Derek Zoolander
On 2004-08-05 Brian Sutherland <[EMAIL PROTECTED]> wrote:
> As my first foray into debian packaging, I want to create a
> package that installs a cron job to be run daily.
> My approach is to install a simple script into /etc/cron.daily/
> that calls a more complex script which I install into /usr
On Thu 08/05/04 17:35, Brian Sutherland wrote:
> As my first foray into debian packaging, I want to create a
> package that installs a cron job to be run daily.
>
> My approach is to install a simple script into /etc/cron.daily/
> that calls a more complex script which I install into /usr/bin/.
>
You are correct; see [1]. Make sure it checks for the existence of all
files it needs.
Cheers,
--
Justin
aptitude install iraf saods9 eclipse xpa sextractor x11iraf wcstools pyraf
http://www.justinpryzby.com/debian/
References
[1] http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.5
O
As my first foray into debian packaging, I want to create a
package that installs a cron job to be run daily.
My approach is to install a simple script into /etc/cron.daily/
that calls a more complex script which I install into /usr/bin/.
Will this be compliant with the FHS?
Make sure that if th
Im stunned. Three answers in under an hour.
Thanks world.
--
Brian Sutherland
"There has got to be more to life than just being really,
really, really, ridiculously good-looking." -- Derek Zoolander
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Conta
On 2004-08-05 Brian Sutherland <[EMAIL PROTECTED]> wrote:
> As my first foray into debian packaging, I want to create a
> package that installs a cron job to be run daily.
> My approach is to install a simple script into /etc/cron.daily/
> that calls a more complex script which I install into /usr
On Thu 08/05/04 17:35, Brian Sutherland wrote:
> As my first foray into debian packaging, I want to create a
> package that installs a cron job to be run daily.
>
> My approach is to install a simple script into /etc/cron.daily/
> that calls a more complex script which I install into /usr/bin/.
>
You are correct; see [1]. Make sure it checks for the existence of all
files it needs.
Cheers,
--
Justin
aptitude install iraf saods9 eclipse xpa sextractor x11iraf wcstools pyraf
http://www.justinpryzby.com/debian/
References
[1] http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.5
O
As my first foray into debian packaging, I want to create a
package that installs a cron job to be run daily.
My approach is to install a simple script into /etc/cron.daily/
that calls a more complex script which I install into /usr/bin/.
Will this be compliant with the FHS?
Make sure that if th
On Пнд, 2004-06-28 at 17:48 +0200, Laszlo 'GCS' Boszormenyi wrote:
> Delete them after 'make install' from debian/rules . You may tamper
> with the Makefile as well, but be it as a last resort, only if the 'make
> install' create big files/files after a long calculation etc, you got
> the idea.
O
On Mon, Jun 28, 2004 at 07:41:27PM +0400, Dan Korostelev wrote:
> Is it possible to make some files installed by 'make install' excluded
> from deb package???
Sure.
rm debian/package/blah/fasel
in debian/rules after make install.
cu andreas
* Dan Korostelev <[EMAIL PROTECTED]> [2004-06-28 19:41:27 +0400]:
> Is it possible to make some files installed by 'make install' excluded
> from deb package???
Delete them after 'make install' from debian/rules . You may tamper
with the Makefile as well, but be it as a last resort, only if the '
Is it possible to make some files installed by 'make install' excluded
from deb package???
--
Dan Korostelev <[EMAIL PROTECTED]>
On ÐÐÐ, 2004-06-28 at 17:48 +0200, Laszlo 'GCS' Boszormenyi wrote:
> Delete them after 'make install' from debian/rules . You may tamper
> with the Makefile as well, but be it as a last resort, only if the 'make
> install' create big files/files after a long calculation etc, you got
> the idea.
O
On Mon, Jun 28, 2004 at 07:41:27PM +0400, Dan Korostelev wrote:
> Is it possible to make some files installed by 'make install' excluded
> from deb package???
Sure.
rm debian/package/blah/fasel
in debian/rules after make install.
cu andreas
--
To UNSUBSCRIBE, email to [EMAIL PRO
* Dan Korostelev <[EMAIL PROTECTED]> [2004-06-28 19:41:27 +0400]:
> Is it possible to make some files installed by 'make install' excluded
> from deb package???
Delete them after 'make install' from debian/rules . You may tamper
with the Makefile as well, but be it as a last resort, only if the '
Is it possible to make some files installed by 'make install' excluded
from deb package???
--
Dan Korostelev <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Thu, Aug 07, 2003 at 12:54:08PM -0700, Eric Winger wrote:
> 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.
Nope, this is the right spot.
> My first steps are proving to be quite haltingly slow. I'm
On Fri, Aug 08, 2003 at 11:24:13AM +0100, Colin Watson wrote:
> On Fri, Aug 08, 2003 at 07:38:11PM +1000, Matthew Palmer wrote:
> > The things which absolutely have to be in a package in order to be
> > built are debian/rules and debian/control. debian/rules gives the
> > commands required to make
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 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
Hi,
by the way, do you use "debuild" to build your package?
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 like having *.ex files still in the
package. Listen to it.
MfG
Go
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
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 se
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.
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
I've been able to build a package, install it, get a postinst script to
run properly. Now, I'm at the point in my little test where
understanding where everything goes during install is important.
I'm moving away from using New Deb Maintainer docs and trying to follow
advice given in this forum
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
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
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
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. Could
someone distingui
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 t
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
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
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
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 packages for me (the eternal newbie).
There are several "configuration sections" yo
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
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
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
thx to all for the responses. I'm slowly making progress here. Could
someone distinguish the configuration section and how that applies to
debian packages for me (the eternal newbie).
I was under the impression that the configuration rules were what the
package would run after it was loaded. Ho
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.
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
I've been able to build a package, install it, get a postinst script to
run properly. Now, I'm at the point in my little test where
understanding where everything goes during install is important.
I'm moving away from using New Deb Maintainer docs and trying to follow
advice given in this foru
Hi,
by the way, do you use "debuild" to build your package?
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 like having *.ex files still in the
package. Listen to it.
MfG
Go
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
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
> 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
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 packages for me (the eternal newbie).
There are several "configuration sections" yo
1 - 100 of 173 matches
Mail list logo
