Bas Wijnen <[EMAIL PROTECTED]> writes:
> On Fri, Dec 14, 2007 at 12:04:48PM -0800, Russ Allbery wrote:
>>> I think the best way is to include the license text in
>>> debian/copyright just like any other license that is not in
>>> common-licenses.
>> We probably don't really want to include a copy
On Sat, 15 Dec 2007, David Schulberg wrote:
Hi All,
Posted originally to debian-user and it was suggested I post here in
particular:
Have just set up Linda or I thought I had.
When I run 'linda package.deb' I get errors as follows:
debian:/home/david/Desktop/Downloads# linda checki
Hi All,
Posted originally to debian-user and it was suggested I post here in
particular:
>>
Have just set up Linda or I thought I had.
When I run 'linda package.deb' I get errors as follows:
debian:/home/david/Desktop/Downloads# linda checkinstall_1.6.1-1_i386.deb
Linda: Running
Dear mentors,
I am looking for a sponsor for my package "kmfl-keyboards-mywin".
* Package name: kmfl-keyboards-mywin
Version : 2.1.1-1
Upstream Author : Keith Stribley <[EMAIL PROTECTED]>
* URL :
http://www.thanlwinsoft.org/ThanLwinSoft/Downloads/#keyboards
* License
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gilles Filippini a écrit :
> Bas Wijnen a écrit :
>> This is because dupload checks its own log, and refuses to upload the
>> same file twice unless you force it with --force. You should probably
>> do this, and see if you get "file already exists" er
On Fri, Dec 14, 2007 at 10:21:41PM +0100, Basile STARYNKEVITCH wrote:
> Bas Wijnen wrote:
>>
>> RMS does this, in his attempts to move people to use the newest version
>> of the GPL. He has a point, but if Debian would fully agree with it, I
>> suppose we would relicense all GPL works as GPL versi
Bas Wijnen wrote:
RMS does this, in his attempts to move people to use the newest version
of the GPL. He has a point, but if Debian would fully agree with it, I
suppose we would relicense all GPL works as GPL version 3 or later when
possible.
I am not a lawyer (and you'll need a lawyer know
Hi,
On Fri, Dec 14, 2007 at 10:09:21PM +0100, Gilles Filippini wrote:
> I've uploaded yesterday to mentors.d.n a new release of my package nted.
> The upload seemed successful but I didn't received any confirmation mail
> and the package doesn't show up on the mentors.d.n web site.
>
> Here is th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I've uploaded yesterday to mentors.d.n a new release of my package nted.
The upload seemed successful but I didn't received any confirmation mail
and the package doesn't show up on the mentors.d.n web site.
Here is the trace of the upload acti
On Fri, Dec 14, 2007 at 12:04:48PM -0800, Russ Allbery wrote:
> > I think the best way is to include the license text in debian/copyright
> > just like any other license that is not in common-licenses.
>
> We probably don't really want to include a copy of the GPLv1 in every Perl
> package.
If th
On 14/12/2007, Dmitry E. Oboukhov wrote:
> I needed to test the building of one of my packages with gcc4.3.
> However it turns out that gcc-snapshot from unstable contains the
> critical bug, which makes impossible using it. At the same time the
> previous version of the gcc-snapshot deb-package ha
On Friday 14 December 2007, Dmitry E. Oboukhov wrote:
Hi,
> I needed to test the building of one of my packages with gcc4.3.
> However it turns out that gcc-snapshot from unstable contains the critical
> bug, which makes impossible using it. At the same time the previous
> version of the gcc-snap
On Fri, Dec 14, 2007 at 22:38:56 +0300, Dmitry E. Oboukhov wrote:
> I needed to test the building of one of my packages with gcc4.3.
> However it turns out that gcc-snapshot from unstable contains the critical
> bug, which makes impossible using it. At the same time the previous
> version of the g
Matthias Julius <[EMAIL PROTECTED]> writes:
> Russ Allbery <[EMAIL PROTECTED]> writes:
>> Agreed. I think debian/copyright should always refer to the exact
>> version of the GPL that the package says it's covered under and then
>> document whether only that version is permissable or whether the "
Matthias Julius <[EMAIL PROTECTED]> writes:
> Russ Allbery <[EMAIL PROTECTED]> writes:
>> Dave Ewart <[EMAIL PROTECTED]> writes:
>>> Yes, I do run lintian (and linda), but the spare machine I used to
>>> build the packages was running Lenny at the time I built them. It's
>>> now Sid ;-)
>> You c
I needed to test the building of one of my packages with gcc4.3.
However it turns out that gcc-snapshot from unstable contains the critical
bug, which makes impossible using it. At the same time the previous
version of the gcc-snapshot deb-package has been already deleted from
unstable.
As a resul
Dear mentors,
I am looking for a sponsor for my package "kmfl-keyboards-mywin".
* Package name: kmfl-keyboards-mywin
Version : 2.1.1-1
Upstream Author : Keith Stribley <[EMAIL PROTECTED]>
* URL :
http://www.thanlwinsoft.org/ThanLwinSoft/Downloads/#keyboards
* License
On Tue, Dec 11, 2007 at 09:37:07AM -0800, Doug Rintoul wrote:
> Ming Hua wrote:
>> Scim package is already set up to handle all_ALL, it just doesn't set it
s/Scim/im-switch/
>> to default (and it shouldn't). I believe no packages that currently use
>> im-switch change all_ALL by default.
> Can y
Hello Thibaut,
Thibaut Paumard <[EMAIL PROTECTED]> wrote:
> I'm packaging an interpreted language, Yorick, and a bunch of add-ons
> for that language.
>
> I'd like to provide a wrapper package that would depend on all the
> packages in this family present in main and suggest the one that is
Russ Allbery <[EMAIL PROTECTED]> writes:
> Agreed. I think debian/copyright should always refer to the exact version
> of the GPL that the package says it's covered under and then document
> whether only that version is permissable or whether the "or later" part is
> available. (The exception is
Russ Allbery <[EMAIL PROTECTED]> writes:
> Dave Ewart <[EMAIL PROTECTED]> writes:
>
>> Yes, I do run lintian (and linda), but the spare machine I used to build
>> the packages was running Lenny at the time I built them. It's now Sid
>> ;-)
>
> You can also pin lintian in particular to unstable on
Hello,
On Fri, 14 Dec 2007, iluvlinux wrote:
> but dpkg-buildpackage command asks for passphrase just before building the
> package (at dh_builddeb ). so how can i check it with lintian etc.
>
> Do you want that first i should build a package, check it and than use gpg
> separately for signing th
iluvlinux wrote:
> but dpkg-buildpackage command asks for passphrase just before building the
> package (at dh_builddeb ). so how can i check it with lintian etc.
You can sign it when dpkg-buildpackage asks you. Since you will have to be
actually there to do that you can then run lintian to check
hi
but dpkg-buildpackage command asks for passphrase just before building the
package (at dh_builddeb ). so how can i check it with lintian etc.
Do you want that first i should build a package, check it and than use gpg
separately for signing the package?
bye
Kapil Hari Paranjape wrote:
>
>
Hello,
On Fri, 14 Dec 2007, iluvlinux wrote:
> Storing your passphrase in a file or ENV variable is never "safe" as told in
> documents and by mentors.
True enough. Yet ...
> than here's what i found:
> gpg's default home dir is ~/.gunpg (you can change it using --homedir
> option, using this op
Hi,
On Friday 14 December 2007 00:37, Bas Wijnen wrote:
> On Thu, Dec 13, 2007 at 03:06:27PM +0100, Holger Levsen wrote:
> > And yes, if you refer to "the GPL" today, it certainly means GPL3.
> Not at all. Well, at least not completely. ;-) GNU GPL 3 itself says
> about this (section 14):
Wow,
Storing your passphrase in a file or ENV variable is never "safe" as told in
documents and by mentors.
but what if you want to enter the passphrase number of times or you want a
cron job or a script to do use gpg?
than here's what i found:
gpg's default home dir is ~/.gunpg (you can change it us
27 matches
Mail list logo
