On Thu, Apr 26, 2001 at 02:54:14PM +0530, Viral wrote:
> Hi,
>
> I am packaging a single binary package, vcdimager. The binary it contains
> is called vcdrip.
>
> My question is, that for such simple packages, is it a good idea for the
> name of the binary to coincide with the name of the package
On Thu, Apr 26, 2001 at 02:54:14PM +0530, Viral wrote:
> Hi,
>
> I am packaging a single binary package, vcdimager. The binary it contains
> is called vcdrip.
>
> My question is, that for such simple packages, is it a good idea for the
> name of the binary to coincide with the name of the packag
> Welcome !
Thanks to you and to everyone who answered my questions. Once the mail
got through the arcane of the Internet I got quick replies.
> There is no fooling, this is exactly what you should do. Debian
> native packages are for instance the debian package tools. In almost
> all situations
On Thu, 26 Apr 2001, Wolfgang Sourdeau wrote:
> paragraph 6.4.1 it is mentionned that the archive maintainer will
> chose the appropriate category for a package. Does this mean that one
> should take arrangement with him before uploading the package (so as
Most just peruse the archive, find the ca
On Thu, Apr 26, 2001 at 04:07:38PM -0400, Wolfgang Sourdeau wrote:
> The dh_installchangelogs doesn't accept a ChangeLog parameter when the
> package is a native debian package. However, the GNU HaliFAX project
> is (as its name implies) an official GNU project, which besides other
> things, mean
On Thu, Apr 26, 2001 at 04:21:21PM -0400, Wolfgang Sourdeau wrote:
>
> I am the author of the GNU HaliFAX viewer and I have pre-packaged it
> for Debian GNU/Linux. I have been a maintainer since Saturday and
Welcome !
>
> In http://www.debian.org/doc/developers-reference/ch-upload.en.html,
> par
Hi,
I am the author of the GNU HaliFAX viewer and I have pre-packaged it
for Debian GNU/Linux. I have been a maintainer since Saturday and
although my packaging seemed correct to my applicant manager I still
have a few questions for which I have no answer.
In http://www.debian.org/doc/developers
Hi,
I am the author of the GNU HaliFAX viewer and I have pre-packaged it
for Debian GNU/Linux. I have been a maintainer since Saturday and
although my packaging seemed correct to my applicant manager I still
have a few questions for which I have no answer.
In http://www.debian.org/doc/developers
> Welcome !
Thanks to you and to everyone who answered my questions. Once the mail
got through the arcane of the Internet I got quick replies.
> There is no fooling, this is exactly what you should do. Debian
> native packages are for instance the debian package tools. In almost
> all situations
On Thu, 26 Apr 2001, Wolfgang Sourdeau wrote:
> paragraph 6.4.1 it is mentionned that the archive maintainer will
> chose the appropriate category for a package. Does this mean that one
> should take arrangement with him before uploading the package (so as
Most just peruse the archive, find the c
On Thu, Apr 26, 2001 at 04:07:38PM -0400, Wolfgang Sourdeau wrote:
> The dh_installchangelogs doesn't accept a ChangeLog parameter when the
> package is a native debian package. However, the GNU HaliFAX project
> is (as its name implies) an official GNU project, which besides other
> things, mean
On Thu, Apr 26, 2001 at 04:21:21PM -0400, Wolfgang Sourdeau wrote:
>
> I am the author of the GNU HaliFAX viewer and I have pre-packaged it
> for Debian GNU/Linux. I have been a maintainer since Saturday and
Welcome !
>
> In http://www.debian.org/doc/developers-reference/ch-upload.en.html,
> pa
Hi,
I am the author of the GNU HaliFAX viewer and I have pre-packaged it
for Debian GNU/Linux. I have been a maintainer since Saturday and
although my packaging seemed correct to my applicant manager I still
have a few questions for which I have no answer.
In http://www.debian.org/doc/developer
Hi,
I am the author of the GNU HaliFAX viewer and I have pre-packaged it
for Debian GNU/Linux. I have been a maintainer since Saturday and
although my packaging seemed correct to my applicant manager I still
have a few questions for which I have no answer.
In http://www.debian.org/doc/developer
David Spreen <[EMAIL PROTECTED]> writes:
> Is it possible to get fast _all_ lidspackages out of testing and
> unstable?
Packages are removed by filing bugs against the "ftp.debian.org"
pseudo-package. That's not necessarily fast, however. I don't get why
there's so much urgency, though ...
> So
On Thu, Apr 26, 2001 at 12:49:38AM -0600, Jeremy wrote:
> Hi
>
> Has any one seen this error before when tring to su??
>
> su: Authentication service cannot retrieve authentication info.
Hi Jeremy!
Please can you
(a) Post this to -user, not to -mentors: if you read the description
of the v
David Spreen <[EMAIL PROTECTED]> writes:
> Is it possible to get fast _all_ lidspackages out of testing and
> unstable?
Packages are removed by filing bugs against the "ftp.debian.org"
pseudo-package. That's not necessarily fast, however. I don't get why
there's so much urgency, though ...
> So
On Thu, Apr 26, 2001 at 12:49:38AM -0600, Jeremy wrote:
> Hi
>
> Has any one seen this error before when tring to su??
>
> su: Authentication service cannot retrieve authentication info.
Hi Jeremy!
Please can you
(a) Post this to -user, not to -mentors: if you read the description
of the
Hi,
I am packaging a single binary package, vcdimager. The binary it contains
is called vcdrip.
My question is, that for such simple packages, is it a good idea for the
name of the binary to coincide with the name of the package ? Then, if a
person installs a package, she knows what is the name o
Hi,
I am packaging a single binary package, vcdimager. The binary it contains
is called vcdrip.
My question is, that for such simple packages, is it a good idea for the
name of the binary to coincide with the name of the package ? Then, if a
person installs a package, she knows what is the name
I'm trying to do my part to take a load off the porters by ensuring my
package compiles on all available architectures. However, I'm running
into questions:
1. It seems the only machine with chroots available is vore. What about
builds on architectures other than sparc?
2. Even on vore in the u
Hi
Has any one seen this error before when tring to su??
su: Authentication service cannot retrieve authentication info.
Thanks
Jeremy
<>
I'm trying to do my part to take a load off the porters by ensuring my
package compiles on all available architectures. However, I'm running
into questions:
1. It seems the only machine with chroots available is vore. What about
builds on architectures other than sparc?
2. Even on vore in the
23 matches
Mail list logo
