that
mutt-0.58.0-i386.deb is available but I can't find it (let alone install
it (let alone install it with dselect))!!
I also would like to keep my installation up-to-date with whatever is in
'bo-updates'; is there a way to do it with dselect?
btw: dselect is GREAT!!! congratulation
, but just one plain Packages.gz file
> in bo-updates/
So it would be even simpler!? So let's do it! Who can do it?
--
Lukas Eppler (godot)
http://www.fear.ch
> Hi!
>
> I may be wrong, but:
>
> When bo-updates had the same structure as stable, non-free and contrib,
> one could in fact use dselect to install the bo-updates, just by typing
>
> Enter space seperated list of distributions to get
> [stable non-free contrib]:
Hi!
I may be wrong, but:
When bo-updates had the same structure as stable, non-free and contrib,
one could in fact use dselect to install the bo-updates, just by typing
Enter space seperated list of distributions to get
[stable non-free contrib]: stable non-free contrib bo-updates
This would
Hi,
I am wondering when all those useful packages in bo-updates will be merged
into bo. I've seeing them for quite a while but I don't want to install
in our production servers (running 1.3.1) anything that is untested.
Debian 1.3.1 was released more than one month ago and I haven&
Carlo U Segre writes:
> One thing that strikes me about the change in the organization of the
> stable tree is that I have seen no simple instructions on how to make use
> of the updates in the bo-updates driectory since they are not linked to a
> version of the stable tree.
manoj
--- Start of forwarded message ---
First, there is an easy way with the current stable version of dselect
to determine what effect the packages in bo-updates will have on the
typical system. When dselect asks for a local directory of packages,
simply give it the directory where your bo
Hi,
>>"Eloy" == Eloy A Paris <[EMAIL PROTECTED]> writes:
Eloy> I think THIS IS THE PROBLEM with the new scheme: there is not a
Eloy> separate directory where you can get all the updates separately,
Eloy> you have to go to the stable directory because updates are
Eloy> merged directly into the main
at I have
Carlo> seen no simple instructions on how to make use of the updates
Carlo> in the bo-updates driectory since they are not linked to a
Carlo> version of the stable tree.
Right. Those packages have not been released yet. They are
release candidates. When they are released, it
Syrus Nemat-Nasser <[EMAIL PROTECTED]> wrote:
: In addition, the packages in bo-updates are for use at the user's
: discretion--they have not been formally accepted as updates to the stable
: distribution AFAIK.
I think THIS IS THE PROBLEM with the new scheme: there is not a separat
dates in the bo-updates driectory since they are not
> linked to a version of the stable tree.
>
> There has been some mention of using dpkg-ftp but one still has to tell
> dselect where to find the information about the packages and if they are
> not in the stable tree, they will no
Hello All:
I have been following the discussion of the past few days with some
interest. One thing that strikes me about the change in the organization
of the stable tree is that I have seen no simple instructions on how to
make use of the updates in the bo-updates driectory since they are not
Todd Harper <[EMAIL PROTECTED]> wrote:
: I would say that bo-updates is a holding tank for packages intended
: to become part of Debian-1.3.2 when it gets released. Consider it
: the "unstable" part of "stable" until the testing group gives those
: packages its bless
> > do not show up automatically with dselect. Apparently, bo-updates is
> > not intended to be in the dselect tree unless the user incorporates it
> > by hand?
>
>I've wondered about what exactly bo-updates is too, along with
> if/when/how one should install
On Thu, 24 Jul 1997 11:49:15 -0400, Igor Grobman <[EMAIL PROTECTED]> said:
>
> The packages in bo-updates are there for testing by everyone, namely
> the testing group, [...]
I'd be glad to help test these packages, but downloading and installing them
by hand is a hassle
> I was notified this morning about the recent CIAC security announcment
> on ld.so. I went to my Debian mirror and found that the fix was
> already available under bo-updates directory. I *thought* that since
> my system was up to date [i.e., v 1.3.1 + ] that I probably already
&
On Thu, 24 Jul 1997, James D. Freels wrote:
> do not show up automatically with dselect. Apparently, bo-updates is
> not intended to be in the dselect tree unless the user incorporates it
> by hand?
I've wondered about what exactly bo-updates is too, along with
if/when/how one
I was notified this morning about the recent CIAC security announcment
on ld.so. I went to my Debian mirror and found that the fix was
already available under bo-updates directory. I *thought* that since
my system was up to date [i.e., v 1.3.1 + ] that I probably already
had the fix incorporated
I have a question about the bo-updates subdirectory. Now, I know that bo
is supposed to be stable and relatively unchanging, but what is the purpose
of the bo-updates subdirectory?
I take it that it contains updates to the bo packages, but how can one
integrate this into deselect, or even
Hola,
On Mon, 30 Jun 1997, Antonio M. Roldan wrote:
> I've upgraded to xfree3.3 using the packages located in "bo-updates"
> and found the following error messages when installing scalable fonts:
>
>
On Mon, 30 Jun 1997, Antonio M. Roldan wrote:
: I've upgraded to xfree3.3 using the packages located in "bo-updates"
: and found the following error messages when installing scalable fonts:
[error sniffed]
: Has somoene suffered this problem?
I didn't experience thi
I've upgraded to xfree3.3 using the packages located in "bo-updates"
and found the following error messages when installing scalable fonts:
---
# dpkg -i xfntscl_3.3-3_all.deb
(Reading database ... 23014 files
22 matches
Mail list logo
