In building debian packages,why do you require root privileges and so we
have to use fakeroot..?
On Mon, Jul 21, 2008 at 12:04 PM, Reema Shah [EMAIL PROTECTED] wrote:
In building debian packages,why do you require root privileges and so we
have to use fakeroot..?
fakeroot is not necessary now with new dpkg.
--
Cheers,
Kartik Mistry | 0xD1028C8D | IRC: kart_
Blogs:
* Kartik Mistry [EMAIL PROTECTED] [080721 09:25]:
On Mon, Jul 21, 2008 at 12:04 PM, Reema Shah [EMAIL PROTECTED] wrote:
In building debian packages,why do you require root privileges and so we
have to use fakeroot..?
fakeroot is not necessary now with new dpkg.
Reading through the
On Fri Jul 18 04:25, Sveinung Kvilhaugsvik wrote:
http://mentors.debian.net/debian/pool/main/l/libnanoxml2-java/libnanoxml2-java_2.2.3.dfsg-1.dsc
I've had a look at this and it looks pretty good, except you have:
Suggests: nanoxml2-doc
but the package name is libnanoxml2-java-doc.
Other
On Mon, Jul 21, 2008 at 10:06:27AM +0900, Osamu Aoki wrote:
In License, you have:
LGPL-2+ can also be treated as version 2.1 of GNU Lesser General Public
License. On Debian systems, the complete text may be found in
/usr/share/common-licenses/LGPL-2.1.
LGPL-2+ can also be treated as version
Hi,
I am looking for sponsors to upload new upstream versions of sclapp and
pytagsfs. These updates build the following binary packages (with the said
changes):
python-sclapp (0.5.2-1) - framework for Python command-line applications
* New upstream release
+ sclapp.txt is now licensed
Hello!
Thank you for your feedback.
I've had a look at this and it looks pretty good, except you have:
Suggests: nanoxml2-doc
but the package name is libnanoxml2-java-doc.
Fixed.
By the way, should the copyright text from dh_helper be included in
debian/rules like it is now? (Lintian did
OK, I am attempting to package up redmine and need some general
pointers. I'm going through the New Maintainers Guide tutorial and
have run into a few things that I need clarification on.
1) Is there any type of automated way to extract license info from a
series of files? I am using a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Richard Hurt wrote:
OK, I am attempting to package up redmine and need some general
pointers. I'm going through the New Maintainers Guide tutorial and have
run into a few things that I need clarification on.
1) Is there any type of automated
On 07/21/2008 03:20 PM, Richard Hurt wrote :
OK, I am attempting to package up redmine and need some general
pointers. I'm going through the New Maintainers Guide tutorial and have
run into a few things that I need clarification on.
1) Is there any type of automated way to extract license
On Mon Jul 21 14:37, Sveinung Kvilhaugsvik wrote:
By the way, should the copyright text from dh_helper be included in
debian/rules like it is now? (Lintian did not warn me about it so I
assumed it was OK)
Yeah, that's fine, and possibly required.
- Is it safe to do as I have done in
On Mon Jul 21 00:57, Damien Raude-Morvan wrote:
I've just uploaded a new version to mentors.debian.net, you should dget that.
Looks good, I've uploaded
Matt
--
Matthew Johnson
signature.asc
Description: Digital signature
Vincent Bernat a écrit :
OoO En cette matinée ensoleillée du mardi 08 juillet 2008, vers 09:54,
Vincent Legout [EMAIL PROTECTED] disait :
* Package name: gimmix
Version : 0.4.3-1
Upstream Author : Priyank M. Gosalia
* URL : http://gimmix.berlios.de/
*
After spending a bit of time with licensecheck and a some command
line friends I now have a debian/copyright file that conforms to the
proposed CopyrightFormat. The problem is that weighing in @ 388
lines, it is huge! It turns out that while most of the files in
redmine are GPL they have
OoO Pendant le journal télévisé du lundi 21 juillet 2008, vers 20:58,
Vincent Legout [EMAIL PROTECTED] disait :
I'm away for two weeks. I won't be able to answer.
I have uploaded your package. Thanks for your contribution!
--
Avoid multiple exits from loops.
- The Elements of
OoO En ce début de soirée du lundi 21 juillet 2008, vers 21:11, Richard
Hurt [EMAIL PROTECTED] disait :
Should I just combine the similar (same person) copyrights into a
single one covering all the years or am I supposed to list each one
separately?
Personnaly, I would merge them.
Also,
- Is it safe to do as I have done in debian/origCleaner.sh (using one
more parameter than uscan passes to tell set the tempdir from
get-orgi-source) or do I risk that uscan adds parameters without
notice? (If adding is the only risk I could pass the tempdir by the
second parameter instead and
Reema Shah [EMAIL PROTECTED] writes:
In building debian packages,why do you require root privileges and
so we have to use fakeroot..?
The manpage for 'fakeroot(1)' gives the answer:
fakeroot runs a command in an environment wherein it appears to
have root privileges for file
Dear mentors,
I am looking for a sponsor for my package libenglab.
* Package name: libenglab
Version : 0.2.2-1
Upstream Author : BugFest Team [EMAIL PROTECTED]
* URL : http://englab.sf.net
* License : GPLv2
Section : libs
It builds these binary
Dear mentors,
I am looking for a sponsor for the new version 0.1.c-1
of the Debian package ttylog, which I am adopting.
The program can be used to print everything that comes in
from a serial port to stdout. The device and the baud rate
can be specified on the command line.
It builds this
20 matches
Mail list logo
