Hi, I'm in search of a sponsor for python-itools. You will find the
administrativa afterwards.
Note this package has quite a long story, and the "Initial Release"
changelog entry is kind of lost at the bottom. Hopefully, this means the
project is active.
Thank you in advance!
repository pool
Hi, I'm in search of a sponsor for python-itools. You will find some
administrativa afterwards.
This is a first step to finally close #204120 after a year and a half,
and being able to package latest upstreams of Localizer.
If things go well, why not being myself the DD for these packages in th
Eduardo M KALINOWSKI a écrit :
What about the case in which the upstream maintainer is the Debian
maintainer? I create packages for a piece of sofware I've written.
That's my case (well...) and I decided to apply the "Separation of
Concerns" paradigm: software development and packaging are differ
Lucas Di Pentima a écrit :
I see that the source package control file must be in
"debian/control", and the binary control file must be in
"DEBIAN/control"...am I right? they are different directories? I didn't
knew that.
that DEBIAN directory is the one generated in a binary package, where
the
martin f krafft wrote:
also sprach Hervé Cauwelier <[EMAIL PROTECTED]> [2005.03.10.1219 +0100]:
I guess you should just copy it to debian/etc//config.d
debian//etc//config.d
Oops, yes!
Remember to ask Debhelper to create this folder by adding a line
in your dirs file.
or a `mkdir -p -m755` call to
Charles Majola wrote:
Hi all
I need help with this: how do I add configuration files to a debian
package.
I want to add files to /etc/package-name/config.d
I guess you should just copy it to debian/etc//config.d
Remember to ask Debhelper to create this folder by adding a line in your
dirs file.
Rakotomandimby (R12y) Mihamina wrote:
Hello.
I did not make a backup copy of my "rules" file, and I edited it like a
pig.
I would like to do it again but with a clean "rules" file.
Have you generated a package yet? If so, you will find it inside the
.diff.gz file.
If you don't have diff.gz file, it
Hi,
For a source package I'm preparing (first step of a RFP for another), I
have a problem with the -doc binary package.
Due to a bug in the upstream tarball preparation, a couple of files are
missing and prevent the PS manual from being compiled, and as a
consequence, the PDF and HTML versions. Th
Lucas Wall wrote:
Even if you wrote the program its a good idea to keep the debian
packaging scripts separate and don't make a native package. Basicaly you
provide the orig tarball without the debian subdir and put it in the
diff files.
Is there some litterature about this choice? I hesitated a
9 matches
Mail list logo
