In agreement with the current maintainer, I intend to take over the
scsh Debian package. scsh is a Scheme implementation tuned for writing
shell scripts. I have already prepared a package that closes most open
bugs. Here's the changelog:
scsh (0.6.4-1) unstable; urgency=low
* New upstream relea
Hi, folks.
I have a reworked version of facturalux package and I'd like you to upload it,
because I'm not yet a Debian Developer (expecting since 1029337800).
The upload is important because it fixes a pair of issues, one regarding to
gcc-3.3 compiling and other correcting an usability bug.
Yo
Eric Winger <[EMAIL PROTECTED]> writes:
> So, two questions:
>
> * Is this a reasonable way to maintain our internal packages - ie a
> seperate archive? Or is there a better way.
Its realy easy for small repositories (say <100 packages so this
applies to you) but you need proper management script
Hi again,
still no definit sponsor.
I started a tiny webpage on alioth: http://debix.alioth.debian.org/
Enjoy.
Mrvn
> Hi,
>
> I'm looking for a sponsor for 2 packages (debix and debix-imager), who
> would have guessed. :)
>
> Debix-imager
>
>
> Debix-imager is a setuid b
Eric Winger (2003-08-20 16:05:33 -0700) :
> So, two questions:
>
> * Is this a reasonable way to maintain our internal packages - ie a
> seperate archive? Or is there a better way.
It's the best way I've found.
> * If this is the most reasonable way, where is the information on
> building/mainta
Christopher W. Curtis wrote:
A quick google for "apt repository howto", besides pulling up a
surprising number of links about RPMs, also brings up these two:
http://www.debian.org/doc/manuals/repository-howto/repository-howto.html
Thanks to everyone for their responses. This link has prove
On Thu, Aug 21, 2003 at 02:40:27PM +0200, Roland Mas wrote:
> Eric Winger (2003-08-20 16:05:33 -0700) :
>
> > So, two questions:
> >
> > * Is this a reasonable way to maintain our internal packages - ie a
> > seperate archive? Or is there a better way.
>
> It's the best way I've found.
>
> > * I
hi everyone,
i have a simple question: when am i to close bugs? once the bug is fixed
in *one* version in the debian archive (unstable) or once it is fixed in
*all*?
the bts docs say as soon as a fixed version is in the archive, but there
are a lot of open bugs tagged "fixed". and imho it would m
Probably a simple question. But I've created a local repository. Figured
out how dput moved packages into the archive. Worked through
atp-ftparchive and created a Packages.gz file, got sources-list to point
at my archive correctly.
But when I do a
apt-get install spinelli (spinelli is my packa
On Thu, Aug 21, 2003 at 03:40:50PM +0200, Robert Lemmen wrote:
> hi everyone,
> i have a simple question: when am i to close bugs? once the bug is fixed
> in *one* version in the debian archive (unstable) or once it is fixed in
> *all*?
> the bts docs say as soon as a fixed version is in the arch
Eric Winger wrote:
But when I do a
apt-get install spinelli (spinelli is my package)
I get this message.
E: Package spinelli has no installation candidate
I assume the 'apt-get update' succeeded;
Try apt-cache policy spinelli
Also - look at your packages file and make sure the File: header po
On Thu, Aug 21, 2003 at 03:40:50PM +0200, Robert Lemmen wrote:
> i have a simple question: when am i to close bugs? once the bug is fixed
> in *one* version in the debian archive (unstable) or once it is fixed in
> *all*?
Right now, just close it when it's fixed in unstable. A better mechanism
is
Forgot to mention that I got this after doing apt-get update:
Ign file: binary/ Release
Reading Package Lists... Done
Building Dependency Tree... Done
I thought that the first line might have been ok because I'm not doing
any pinning. Maybe that was a bad assumption.
apt-cache policy spinelli
Eric Winger <[EMAIL PROTECTED]> writes:
> Probably a simple question. But I've created a local
> repository. Figured out how dput moved packages into the
> archive. Worked through atp-ftparchive and created a Packages.gz file,
> got sources-list to point at my archive correctly.
>
>
> But when I
> Forgot to mention that I got this after doing apt-get update:
>
> Ign file: binary/ Release
> Reading Package Lists... Done
> Building Dependency Tree... Done
>
> I thought that the first line might have been ok because I'm not doing
> any pinning. Maybe that was a bad assumption.
>
> apt-cache p
Hi, folks.
I have a reworked version of facturalux package and I'd like you to upload it,
because I'm not yet a Debian Developer (expecting since 1029337800).
The upload is important because it fixes a pair of issues, one regarding to
gcc-3.3 compiling and other correcting an usability bug.
Yo
Eric Winger <[EMAIL PROTECTED]> writes:
> So, two questions:
>
> * Is this a reasonable way to maintain our internal packages - ie a
> seperate archive? Or is there a better way.
Its realy easy for small repositories (say <100 packages so this
applies to you) but you need proper management script
Hi again,
still no definit sponsor.
I started a tiny webpage on alioth: http://debix.alioth.debian.org/
Enjoy.
Mrvn
> Hi,
>
> I'm looking for a sponsor for 2 packages (debix and debix-imager), who
> would have guessed. :)
>
> Debix-imager
>
>
> Debix-imager is a setuid b
Eric Winger (2003-08-20 16:05:33 -0700) :
> So, two questions:
>
> * Is this a reasonable way to maintain our internal packages - ie a
> seperate archive? Or is there a better way.
It's the best way I've found.
> * If this is the most reasonable way, where is the information on
> building/mainta
Christopher W. Curtis wrote:
A quick google for "apt repository howto", besides pulling up a
surprising number of links about RPMs, also brings up these two:
http://www.debian.org/doc/manuals/repository-howto/repository-howto.html
Thanks to everyone for their responses. This link has proved ver
On Thu, Aug 21, 2003 at 02:40:27PM +0200, Roland Mas wrote:
> Eric Winger (2003-08-20 16:05:33 -0700) :
>
> > So, two questions:
> >
> > * Is this a reasonable way to maintain our internal packages - ie a
> > seperate archive? Or is there a better way.
>
> It's the best way I've found.
>
> > * I
hi everyone,
i have a simple question: when am i to close bugs? once the bug is fixed
in *one* version in the debian archive (unstable) or once it is fixed in
*all*?
the bts docs say as soon as a fixed version is in the archive, but there
are a lot of open bugs tagged "fixed". and imho it would m
Probably a simple question. But I've created a local repository. Figured
out how dput moved packages into the archive. Worked through
atp-ftparchive and created a Packages.gz file, got sources-list to point
at my archive correctly.
But when I do a
apt-get install spinelli (spinelli is my packag
On Thu, Aug 21, 2003 at 03:40:50PM +0200, Robert Lemmen wrote:
> hi everyone,
> i have a simple question: when am i to close bugs? once the bug is fixed
> in *one* version in the debian archive (unstable) or once it is fixed in
> *all*?
> the bts docs say as soon as a fixed version is in the arch
Eric Winger wrote:
But when I do a
apt-get install spinelli (spinelli is my package)
I get this message.
E: Package spinelli has no installation candidate
I assume the 'apt-get update' succeeded;
Try apt-cache policy spinelli
Also - look at your packages file and make sure the File: header points
On Thu, Aug 21, 2003 at 03:40:50PM +0200, Robert Lemmen wrote:
> i have a simple question: when am i to close bugs? once the bug is fixed
> in *one* version in the debian archive (unstable) or once it is fixed in
> *all*?
Right now, just close it when it's fixed in unstable. A better mechanism
is
Forgot to mention that I got this after doing apt-get update:
Ign file: binary/ Release
Reading Package Lists... Done
Building Dependency Tree... Done
I thought that the first line might have been ok because I'm not doing
any pinning. Maybe that was a bad assumption.
apt-cache policy spinelli re
Eric Winger <[EMAIL PROTECTED]> writes:
> Probably a simple question. But I've created a local
> repository. Figured out how dput moved packages into the
> archive. Worked through atp-ftparchive and created a Packages.gz file,
> got sources-list to point at my archive correctly.
>
>
> But when I
> Forgot to mention that I got this after doing apt-get update:
>
> Ign file: binary/ Release
> Reading Package Lists... Done
> Building Dependency Tree... Done
>
> I thought that the first line might have been ok because I'm not doing
> any pinning. Maybe that was a bad assumption.
>
> apt-cache p
29 matches
Mail list logo
