On Wed, Jul 30, 2003 at 05:39:59PM -0500, Steve Langasek wrote:
> On Wed, Jul 30, 2003 at 05:05:24PM -0500, Drew Scott Daniels wrote:
> > I'm using sourceforge's compile farm and I'd like to know how to use it to
> > compile packages for unstable. They use woody. I also have an account on
> > HP's
On Wed, Jul 30, 2003 at 10:23:14PM -0400, Neil Roeth wrote:
> I maintain a package that provides a shared library, libosp3c102. The files
> /usr/share/locale/{ja,fr,de,sv}/LC_MESSAGES/sp.mo are part of the package.
> However, they are also part of the package that provided the older version of
>
On Wed, Jul 30, 2003 at 10:23:14PM -0400, Neil Roeth wrote:
> I maintain a package that provides a shared library, libosp3c102. The files
> /usr/share/locale/{ja,fr,de,sv}/LC_MESSAGES/sp.mo are part of the package.
> However, they are also part of the package that provided the older version of
> t
I maintain a package that provides a shared library, libosp3c102. The files
/usr/share/locale/{ja,fr,de,sv}/LC_MESSAGES/sp.mo are part of the package.
However, they are also part of the package that provided the older version of
the same shared library, libosp2. When I try to install libosp3c102
On Wed, Jul 30, 2003 at 10:23:14PM -0400, Neil Roeth wrote:
> I maintain a package that provides a shared library, libosp3c102. The files
> /usr/share/locale/{ja,fr,de,sv}/LC_MESSAGES/sp.mo are part of the package.
> However, they are also part of the package that provided the older version of
>
On Wed, Jul 30, 2003 at 10:23:14PM -0400, Neil Roeth wrote:
> I maintain a package that provides a shared library, libosp3c102. The files
> /usr/share/locale/{ja,fr,de,sv}/LC_MESSAGES/sp.mo are part of the package.
> However, they are also part of the package that provided the older version of
> t
I maintain a package that provides a shared library, libosp3c102. The files
/usr/share/locale/{ja,fr,de,sv}/LC_MESSAGES/sp.mo are part of the package.
However, they are also part of the package that provided the older version of
the same shared library, libosp2. When I try to install libosp3c102
On Wed, Jul 30, 2003 at 05:05:24PM -0500, Drew Scott Daniels wrote:
> I'm using sourceforge's compile farm and I'd like to know how to use it to
> compile packages for unstable. They use woody. I also have an account on
> HP's testdrive systems.
> Is there any reasonably easy way to do this? I kno
On Wed, Jul 30, 2003 at 05:05:24PM -0500, Drew Scott Daniels wrote:
> I'm using sourceforge's compile farm and I'd like to know how to use it to
> compile packages for unstable. They use woody. I also have an account on
> HP's testdrive systems.
Bad idea. Your packages' first point of entry is uns
I'm using sourceforge's compile farm and I'd like to know how to use it to
compile packages for unstable. They use woody. I also have an account on
HP's testdrive systems.
Is there any reasonably easy way to do this? I know that the buildd's can
take care of it, but I'd like to be able to do this
On Thu, Jul 31, 2003 at 06:13:26AM +1000, Aníbal Monsalve Salazar wrote:
> On Wed, Jul 30, 2003 at 17:42 +0200, Julien Barnier wrote:
> > 2) The package seems correct, lintian doesn't give any message anymore.
> > But dpkg-buildpackage didn't generate an "orig.tar.gz" and a
> > "diff.tar.gz" files,
Lucas Wall <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>I read the Debian Policy and didn't installed documentation in
> "/usr/lib". What I did was move the html manual out of the main program
> install dir and place it in "/usr/share/doc", but the w
On Wed, Jul 30, 2003 at 05:05:24PM -0500, Drew Scott Daniels wrote:
> I'm using sourceforge's compile farm and I'd like to know how to use it to
> compile packages for unstable. They use woody. I also have an account on
> HP's testdrive systems.
> Is there any reasonably easy way to do this? I kno
On Wed, Jul 30, 2003 at 05:05:24PM -0500, Drew Scott Daniels wrote:
> I'm using sourceforge's compile farm and I'd like to know how to use it to
> compile packages for unstable. They use woody. I also have an account on
> HP's testdrive systems.
Bad idea. Your packages' first point of entry is uns
On Wed, Jul 30, 2003 at 17:42 +0200, Julien Barnier wrote:
> 2) The package seems correct, lintian doesn't give any message anymore.
> But dpkg-buildpackage didn't generate an "orig.tar.gz" and a
> "diff.tar.gz" files, but only a "tar.gz". Is it because I didn't change
> anything in the source code
I'm using sourceforge's compile farm and I'd like to know how to use it to
compile packages for unstable. They use woody. I also have an account on
HP's testdrive systems.
Is there any reasonably easy way to do this? I know that the buildd's can
take care of it, but I'd like to be able to do this
On Thu, Jul 31, 2003 at 06:13:26AM +1000, Aníbal Monsalve Salazar wrote:
> On Wed, Jul 30, 2003 at 17:42 +0200, Julien Barnier wrote:
> > 2) The package seems correct, lintian doesn't give any message anymore.
> > But dpkg-buildpackage didn't generate an "orig.tar.gz" and a
> > "diff.tar.gz" files,
Lucas Wall <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>I read the Debian Policy and didn't installed documentation in "/usr/lib".
> What I did was move the html manual out of the main program install dir and place it
> in "/usr/share/doc", but the w
On Wed, Jul 30, 2003 at 17:42 +0200, Julien Barnier wrote:
> 2) The package seems correct, lintian doesn't give any message anymore.
> But dpkg-buildpackage didn't generate an "orig.tar.gz" and a
> "diff.tar.gz" files, but only a "tar.gz". Is it because I didn't change
> anything in the source code
On 30.07.03 10:02 Frank Küster wrote:
Andreas Metzler <[EMAIL PROTECTED]> schrieb:
Tagging them as "fixed,woody" sounds wrong to me, they'll be listed as
"closed in NMU" and will probably be rereported again.
Oh, does tagging "fixed" automatically result in that?
Yes, bugs listed on http:/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package is now lintian clean, the description has been fixed and the
changelog entry added.
K.
> -Original Message-
> From: Aníbal Monsalve Salazar [mailto:[EMAIL PROTECTED]
> Sent: Wednesd
* Julien Barnier <[EMAIL PROTECTED]> [030730 17:40]:
> 2) The package seems correct, lintian doesn't give any message anymore.
> But dpkg-buildpackage didn't generate an "orig.tar.gz" and a
> "diff.tar.gz" files, but only a "tar.gz". Is it because I didn't change
> anything in the source code ?
dp
> Have you checked if the wmxmms in xmms package isn't the same as
> your WMxmms dockapp?
Yes, and it is a different dockapp, much more complete in my opinion.
In fact this WMxmms dockapp is closer to the wmusic dockapp.
Otherwise, the problem would have been solved...
Julien
On 30.07.03 10:02 Frank Küster wrote:
Andreas Metzler <[EMAIL PROTECTED]> schrieb:
Tagging them as "fixed,woody" sounds wrong to me, they'll be listed as
"closed in NMU" and will probably be rereported again.
Oh, does tagging "fixed" automatically result in that?
Yes, bugs listed on http://bugs.d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I read the Debian Policy and didn't installed documentation in
"/usr/lib". What I did was move the html manual out of the main program install
dir and place it in "/usr/share/doc", but the web UI links to the manual so I
placed a symbolic l
* Julien Barnier ([EMAIL PROTECTED]) wrote:
> Hello,
>
> As an exercise, I am trying to make my first Debian package using a
> Windowmaker dockapp called WMxmms. I think I almost succeeded to produce
> something that works, but I have three little questions.
>
> 1) I have a (boring) naming proble
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package is now lintian clean, the description has been fixed and the changelog
entry added.
K.
> -Original Message-
> From: Aníbal Monsalve Salazar [mailto:[EMAIL PROTECTED]
> Sent: Wednesd
Hello,
As an exercise, I am trying to make my first Debian package using a
Windowmaker dockapp called WMxmms. I think I almost succeeded to produce
something that works, but I have three little questions.
1) I have a (boring) naming problem. The program is called WMxmms
version 0.1.4, but I read
* Julien Barnier <[EMAIL PROTECTED]> [030730 17:40]:
> 2) The package seems correct, lintian doesn't give any message anymore.
> But dpkg-buildpackage didn't generate an "orig.tar.gz" and a
> "diff.tar.gz" files, but only a "tar.gz". Is it because I didn't change
> anything in the source code ?
dp
> Have you checked if the wmxmms in xmms package isn't the same as
> your WMxmms dockapp?
Yes, and it is a different dockapp, much more complete in my opinion.
In fact this WMxmms dockapp is closer to the wmusic dockapp.
Otherwise, the problem would have been solved...
Julien
--
To UNSUBSCRI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I read the Debian Policy and didn't installed documentation in "/usr/lib".
What I did was move the html manual out of the main program install dir and place it
in "/usr/share/doc", but the web UI links to the manual so I placed a symbolic li
* Julien Barnier ([EMAIL PROTECTED]) wrote:
> Hello,
>
> As an exercise, I am trying to make my first Debian package using a
> Windowmaker dockapp called WMxmms. I think I almost succeeded to produce
> something that works, but I have three little questions.
>
> 1) I have a (boring) naming proble
Hello,
As an exercise, I am trying to make my first Debian package using a
Windowmaker dockapp called WMxmms. I think I almost succeeded to produce
something that works, but I have three little questions.
1) I have a (boring) naming problem. The program is called WMxmms
version 0.1.4, but I read
On Wed, Jul 30, 2003 at 08:20:15PM +1000, An?bal Monsalve Salazar wrote:
> On Wed, Jul 30, 2003 at 04:14 -0300, Lucas Wall wrote:
> > Will the bug tracking system parse the whole file or just the changes
> > list for the latest version?
>
> You shouldn't change the log of the previous versions any
On Wed, Jul 30, 2003 at 04:14 -0300, Lucas Wall wrote:
> Ok... Description fixed. I have some questions about the other two
> items.
>
> Ah... I updated lintian to testing and notice several errors. I'll
> fix them. I used to have one which I was not sure about. Lintian
> complains that symbolic l
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Wed, Jul 30, 2003 at 08:20:15PM +1000, An?bal Monsalve Salazar wrote:
> On Wed, Jul 30, 2003 at 04:14 -0300, Lucas Wall wrote:
> > Will the bug tracking system parse the whole file or just the changes
> > list for the latest version?
>
> You shouldn't change the log of the previous versions any
On Wed, Jul 30, 2003 at 04:14 -0300, Lucas Wall wrote:
> Ok... Description fixed. I have some questions about the other two
> items.
>
> Ah... I updated lintian to testing and notice several errors. I'll
> fix them. I used to have one which I was not sure about. Lintian
> complains that symbolic l
Andreas Metzler <[EMAIL PROTECTED]> schrieb:
>
> Tagging them as "fixed,woody" sounds wrong to me, they'll be listed as
> "closed in NMU" and will probably be rereported again.
Oh, does tagging "fixed" automatically result in that? As far as I
understood, a NMU is one possibility, but not the onl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ok... Description fixed. I have some questions about the other two
items.
Ah... I updated lintian to testing and notice several errors. I'll fix
them. I used to have one which I was not sure about. Lintian complains that
symbolic l
#include
* Matej Cepl [Mon, Jul 28 2003, 03:11:29PM]:
> Hi,
>
> I have created a package for vimoutliner. Is there anybody who would
> like to sponsor me?
>
>Package: vimoutliner
>Status: install ok installed
>Priority: optional
>Section: editors
>Installed-Size: 204
>Mai
On Tue, Jul 29, 2003 at 15:57 -0300, Lucas Wall wrote:
> Hi!
>
> I'm looking for a sponsor. I have the following package ready for
> examination:
>
> POPFile is an email classification tool with a Naive Bayes classifier,
> a POP3 proxy and a web interface. It runs on most platforms and with
> mo
Andreas Metzler <[EMAIL PROTECTED]> schrieb:
>
> Tagging them as "fixed,woody" sounds wrong to me, they'll be listed as
> "closed in NMU" and will probably be rereported again.
Oh, does tagging "fixed" automatically result in that? As far as I
understood, a NMU is one possibility, but not the onl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ok... Description fixed. I have some questions about the other two items.
Ah... I updated lintian to testing and notice several errors. I'll fix them. I
used to have one which I was not sure about. Lintian complains that symbolic lin
#include
* Matej Cepl [Mon, Jul 28 2003, 03:11:29PM]:
> Hi,
>
> I have created a package for vimoutliner. Is there anybody who would
> like to sponsor me?
>
>Package: vimoutliner
>Status: install ok installed
>Priority: optional
>Section: editors
>Installed-Size: 204
>Mai
46 matches
Mail list logo
