Hi,
I just adopted a package which is nothing but a Perl script. Previous
maitainer built it using
Architecture: any
when it had to be
Architecture: all
(correct me if I'm wrong)
Now that I'm uploading a new version of package with correct Architecture, should I
On Mon, 26 Nov 2001, Eric Van Buggenhaut wrote:
I just adopted a package which is nothing but a Perl script. Previous
maitainer built it using
Architecture: any
when it had to be
Architecture: all
(correct me if I'm wrong)
Now that I'm uploading a new version of package
Title: Untitled Document
On 28-Nov-2001 Gustavo Noronha Silva wrote:
Hello all,
I adopted a package, koth, and wanted to change its build process.
For that I needed to change its orig.tar.gz, now dinstall is
rejecting to overwrite it, I'd like to know what I need to do,
upstream is not releasing anything for
Hello,
I have seen packages change their package names to include a version
number. Reading the policy, there is little guidance on this subject.
It would seem that's what Epochs are designed for. However I am aware
there could be reasons for wanting to change the package name. One
reason
Hi!
I am trying to add icons to the menu entries for the Siag suite, but I
am having problems getting the icons to be recognized. I have this in
the menu file:
?package(xsiag): needs=X11 section=Apps/Math \
title=Siag longtitle=Siag Office Scheme-in-a-Grid \
command=/usr/bin/siag
On 28-Nov-2001 peter karlsson wrote:
Hi!
I am trying to add icons to the menu entries for the Siag suite, but I
am having problems getting the icons to be recognized. I have this in
the menu file:
?package(xsiag): needs=X11 section=Apps/Math \
title=Siag longtitle=Siag Office
I'm the maintainer of the libming packages.
Libming has Python bindings, so i made a package python2-ming.
The Python policy has changed now, and Python 2.1 is now the default
python, so it might be good to rename my package to python-ming?
This is a binary package, the source package remains
On Wed, Nov 28, 2001 at 11:50:11AM -0800, Grant Bowman wrote:
Hello,
I have seen packages change their package names to include a version
number. Reading the policy, there is little guidance on this subject.
It would seem that's what Epochs are designed for. However I am aware
there
Sean 'Shaleh' Perry:
looks like every other icon entry:
Exactly. That is why I am confused.
--
\\//
peter - http://www.softwolves.pp.se/
Statement concerning unsolicited e-mail according to Swedish law:
http://www.softwolves.pp.se/peter/reklampost.html
--
To UNSUBSCRIBE, email to
Thank you Julian for that complete summary. I can't think of any other
questions or scenarios to ask about.
Regards,
--
-- Grant Bowman [EMAIL PROTECTED]
* Julian Gilbey [EMAIL PROTECTED] [011128 16:06]:
(1) libdb: Shared library packages have the major
Hi,
I just adopted a package which is nothing but a Perl script. Previous
maitainer built it using
Architecture: any
when it had to be
Architecture: all
(correct me if I'm wrong)
Now that I'm uploading a new version of package with correct Architecture,
should I ask
On Mon, 26 Nov 2001, Eric Van Buggenhaut wrote:
I just adopted a package which is nothing but a Perl script. Previous
maitainer built it using
Architecture: any
when it had to be
Architecture: all
(correct me if I'm wrong)
Now that I'm uploading a new version of package
On Mon, Nov 26, 2001 at 01:46:20PM -0500, Joey Hess wrote:
Adam Heath wrote:
Never build a full release from the cvs work directory. Always cvs export
to
another directory first.
Doing test builds from the cvs work dir is fine. But do final releases
from a
temp dir. Sometimes,
Hello all,
I adopted a package, koth, and wanted to change its build process.
For that I needed to change its orig.tar.gz, now dinstall is
rejecting to overwrite it, I'd like to know what I need to do,
upstream is not releasing anything for now...
btw, the modifications I did were untarring
On 28-Nov-2001 Gustavo Noronha Silva wrote:
Hello all,
I adopted a package, koth, and wanted to change its build process.
For that I needed to change its orig.tar.gz, now dinstall is
rejecting to overwrite it, I'd like to know what I need to do,
upstream is not releasing anything for
Sean 'Shaleh' Perry [EMAIL PROTECTED] writes:
On 28-Nov-2001 Gustavo Noronha Silva wrote:
Hello all,
I adopted a package, koth, and wanted to change its build process.
For that I needed to change its orig.tar.gz, now dinstall is
rejecting to overwrite it, I'd like to know what I need
Hello,
I have seen packages change their package names to include a version
number. Reading the policy, there is little guidance on this subject.
It would seem that's what Epochs are designed for. However I am aware
there could be reasons for wanting to change the package name. One
reason
Hi!
I am trying to add icons to the menu entries for the Siag suite, but I
am having problems getting the icons to be recognized. I have this in
the menu file:
?package(xsiag): needs=X11 section=Apps/Math \
title=Siag longtitle=Siag Office Scheme-in-a-Grid \
command=/usr/bin/siag
On 28-Nov-2001 peter karlsson wrote:
Hi!
I am trying to add icons to the menu entries for the Siag suite, but I
am having problems getting the icons to be recognized. I have this in
the menu file:
?package(xsiag): needs=X11 section=Apps/Math \
title=Siag longtitle=Siag Office
I'm the maintainer of the libming packages.
Libming has Python bindings, so i made a package python2-ming.
The Python policy has changed now, and Python 2.1 is now the default
python, so it might be good to rename my package to python-ming?
This is a binary package, the source package remains
On Wed, Nov 28, 2001 at 11:50:11AM -0800, Grant Bowman wrote:
Hello,
I have seen packages change their package names to include a version
number. Reading the policy, there is little guidance on this subject.
It would seem that's what Epochs are designed for. However I am aware
there
22 matches
Mail list logo
