Thanks Bob,
BP> Even if you think you only tweaked X if this is your behavior there
BP> must have been some other change to the boot sequence. Because
BP> changing X would not affect boot. (And if I were changing X I would
BP> not have rebooted personally because they are not related.)
No, I ag
debian wrote:
> I've just upgraded my "store" machine (behind my firewall) from
> woody to sarge and my firewall following the instructions. The
> store machine rebooted fine at first but then, after some tweaks to
> X, I rebooted again and the boot is hanging at "LI".
Even if you think you only
I've just upgraded my "store" machine (behind my firewall) from woody to sarge
and my
firewall following the instructions. The store machine rebooted fine
at first but then, after some tweaks to X, I rebooted again and the
boot is hanging at "LI". I can get into the machine with a woody boot
CD
On 8/2/05, Brian Kimsey-Hickman <[EMAIL PROTECTED]> wrote:
> Just upgraded a Debian box to Sarge and my Samba shares don't seem to
> work quite the same. This box should be using Domain Authentication
> and I successfully rejoined the domain with a net join command but the
> only people that can o
Hi Brian,
Brian Kimsey-Hickman schreef:
> Just upgraded a Debian box to Sarge and my Samba shares don't seem to
> work quite the same. This box should be using Domain Authentication
> and I successfully rejoined the domain with a net join command but the
> only people that can open share are ones
Hello!
Im have to configure sarge pam system for authenticate via windows
PDC of the network. Before, on woody, I installed libpam_smb and it
provided the /lib/security/pam_smb_auth.so file, which did what I
need. Well, sarge has not libpam_smb pack. So, how to do this on
sa
Just upgraded a Debian box to Sarge and my Samba shares don't seem to
work quite the same. This box should be using Domain Authentication
and I successfully rejoined the domain with a net join command but the
only people that can open share are ones that have user account on the
device and on the
On Sat, Jul 23, 2005 at 04:16:26PM +0200, Felix Natter wrote:
> hi,
>
> I'm trying to upgrade from woody to sarge by following the release notes,
> which state that I should first upgrade to sarge's aptitude.
>
> However, when I do this, aptitude tries to update glibc and a lot of
> other package
hi,
I'm trying to upgrade from woody to sarge by following the release notes,
which state that I should first upgrade to sarge's aptitude.
However, when I do this, aptitude tries to update glibc and a lot of
other packages, and the point of first upgrading aptitude was to
get better resolution of
Hello. I'm trying to upgrade the system from woody to sarge. Followed the
steps in the Debian release notes for sarge
(http://www.debian.org/releases/sarge/i386/release-notes/index.en.html):
that is:
- edit sources.list
- apt-get update
- aptitude install aptitude
- aptitude install doc-base
- ap
> I'm not sure you want to be running the 386 kernel.
> Try installing one the amd kernels, perhaps the 2.6.8-2-k7 kernel-image.
>
> You could also try resetting your bios back to defaults.
>
I've tried the following with no success:
resetting bios settings
"apm=power-off" in lilo.conf
installing
On Monday 27 June 2005 22:22, Mark Fletcher wrote:
> Hi
>
> I recently (last week) upgraded from woody to sarge
> using aptitude. First off much to my surprise X
> windows appeared to survive the upgrade although my
> KDE was shot.
>
> Removing and re-installing GDM (which I use to launch
> X) solv
> I'm not sure you want to be running the 386 kernel.
> Try installing one the amd kernels, perhaps the 2.6.8-2-k7 kernel-image.
Tried that - got endless reboots. I assume that the k7 kernel won't run on
a k6. Nor will the 686 kernel. I managed to compile a k6 kernel, but got
the same problem
On Mon, Jun 27, 2005 at 08:27:43AM -0500, Kent West wrote:
> Mark Fletcher wrote:
>
> >BUT -- now X is shot. If I try to start X either using
> >GDM or startx, it starts up but then... my monitor
> >goes into power saving mode!!! And nothing can get it
> >to come out of it other than Ctrl-Alt-F1,
Quoting Robert S <[EMAIL PROTECTED]>:
I recently upgraded my system to Sarge, and upgraded my kernel. I have a
rather antiquated AMD K6 running on a K6BV3+/66 mobo (AT form factor).
If I issue the "reboot" command, everything shuts down, until "rebooting"
appears, but then nothing happens. I
Mark Fletcher wrote:
>BUT -- now X is shot. If I try to start X either using
>GDM or startx, it starts up but then... my monitor
>goes into power saving mode!!! And nothing can get it
>to come out of it other than Ctrl-Alt-F1, login as
>root (without being able to see what I am doing) then
>shutdo
Hi
I recently (last week) upgraded from woody to sarge
using aptitude. First off much to my surprise X
windows appeared to survive the upgrade although my
KDE was shot.
Removing and re-installing GDM (which I use to launch
X) solved that problem. However over the following
days it gradually beca
I recently upgraded my system to Sarge, and upgraded my kernel. I have a
rather antiquated AMD K6 running on a K6BV3+/66 mobo (AT form factor).
If I issue the "reboot" command, everything shuts down, until "rebooting"
appears, but then nothing happens. I need to do a hard reboot to restart my
On Sat, Jun 25, 2005 at 12:39:01PM -0400, Hendrik Boom wrote:
> On Sat, Jun 25, 2005 at 12:11:23PM -0400, Hendrik Boom wrote:
>
> I certainly *never* asked xdm to be held back, nor icewm, yet
> when I started an interactive aptitude session just now,
> they were on the list of held-back packages,
On Sat, Jun 25, 2005 at 12:11:23PM -0400, Hendrik Boom wrote:
> On Fri, Jun 24, 2005 at 11:58:15PM -0400, Hendrik Boom wrote:
> > On Fri, Jun 24, 2005 at 05:21:01PM -0700, Mark Fletcher wrote:
> > > Hi
> > >
> > > Got a problem with KDE after upgrading woody to sarge.
> > > I am running the i386 d
On Sat, Jun 25, 2005 at 12:41:12PM +, Petri Varsa wrote:
> I had the exact same problem ... except I use kdm. You must have a lot more
> patience than myself. It only took me a few hours before I decided to just
> back up all of my data and re-install everything. :-)
This is actually the sec
On Fri, Jun 24, 2005 at 11:58:15PM -0400, Hendrik Boom wrote:
> On Fri, Jun 24, 2005 at 05:21:01PM -0700, Mark Fletcher wrote:
> > Hi
> >
> > Got a problem with KDE after upgrading woody to sarge.
> > I am running the i386 distribution. For historical
> > reasons I will get around to sorting out o
On Saturday 25 June 2005 12:58, Hendrik Boom wrote:
> On Fri, Jun 24, 2005 at 05:21:01PM -0700, Mark
Fletcher wrote:
> > Hi
> >
> > Got a problem with KDE after upgrading woody to
> > sarge. I am running the i386 distribution. For
> > historical reasons I will get around to sorting out
> > one of
On Saturday 25 June 2005 17:58, Mark Fletcher wrote:
> --- Kent West <[EMAIL PROTECTED]> wrote:
> > Mark Fletcher wrote:
> > >Got a problem with KDE after upgrading woody to
> >
> > sarge.
> >
> >
> >
> >
> > >However on login, the X server appears to shut
> > > down (and gdm promptly re-starts it
> > Is it just KDE? Try a different wm/environment.
for me, the problem existed with xdm, and kdm. I didn't try gdm. All
other window managers worked fine. Just the kde enviroment would fail
on startup.
> > Is it just from gdm? What happens if you kill gdm
> > and try "startx"?
With startx, ot
I had the exact same problem ... except I use kdm. You must have
a lot more patience than myself. It only took me a few hours
before I decided to just back up all of my data and re-install
everything. :-)
With a fresh install, KDE works just fine.
-petri
On 6/25/05, Hendrik Boom <[EMAIL PROTE
--- Kent West <[EMAIL PROTECTED]> wrote:
> Mark Fletcher wrote:
>
> >Got a problem with KDE after upgrading woody to
> sarge.
> >
> >
>
>
> >However on login, the X server appears to shut down
> >(and gdm promptly re-starts it) -- so I log in and
> >after some flashing of screens for a seco
Mark Fletcher wrote:
>Got a problem with KDE after upgrading woody to sarge.
>
>
>However on login, the X server appears to shut down
>(and gdm promptly re-starts it) -- so I log in and
>after some flashing of screens for a second or two I
>find myself back at the login screen again.
>
>
Is
On Fri, Jun 24, 2005 at 05:21:01PM -0700, Mark Fletcher wrote:
> Hi
>
> Got a problem with KDE after upgrading woody to sarge.
> I am running the i386 distribution. For historical
> reasons I will get around to sorting out one of these
> days, I run gdm then select a KDE session at login.
>
> My
Hi
Got a problem with KDE after upgrading woody to sarge.
I am running the i386 distribution. For historical
reasons I will get around to sorting out one of these
days, I run gdm then select a KDE session at login.
My X server has obviously survived the upgrade as gdm
starts OK on boot and presen
I have just upgraded from woody to sarge, including a kernel upgrade to
kernel 2.4.27-2-686. I have an old Adaptec 2940 card (which contains
another OS and is not used by debian). During the startup it seems to try
to load the SCSI driver several times then hangs. Removing the
/etc/rc2.d/xxx
On Sat, 11 Jun 2005 17:30:11 +0200, Hendrik Boom wrote:
> After 18 hours of upgrading on my very slow 100 MHz Pentium,
> it ended up producing an unending stream of
>
> multilog: warning: unable to write to /var/log/svscan/current. pausing: out
> of disk space
The few times I've run out of space
On Sat, Jun 11, 2005 at 07:00:31PM +0100, peter colton wrote:
> part is the use of aptitude with a dist-upgrade.
Isn't the lack of disk space the issue?
aptitude with a dist-upgrade will bring in all recommends which will eat
even more disk space!
suggest
1) apt-get upgrade
Watch packages do
On 06/12/05 22:43, Tom Allison wrote:
A thousand pardons.
It found version 10 that was replaced by version 11.
I was looking at version 11 being in use, not 10.
You're right, I'm wrong.
Sorry for the waste in bandwidth.
No problems. BTW, here is the command that I use with deborphan:
apt-get
Rogério Brito wrote:
On Jun 11 2005, Hendrik Boom wrote:
Will try again. But ... Is it possible to resume the broken upgrade?
Yes, it is. But besides the hint given by the previous poster, it would be
nice if you could purge some unneeded packages, install both debophan and
debfoster and re
Rogério Brito wrote:
On Jun 11 2005, Hendrik Boom wrote:
Will try again. But ... Is it possible to resume the broken upgrade?
Yes, it is. But besides the hint given by the previous poster, it would be
nice if you could purge some unneeded packages, install both debophan and
debfoster and re
On Sat, Jun 11, 2005 at 11:39:44PM +0200, Maurits van Rees wrote:
> On Sat, Jun 11, 2005 at 05:46:50PM -0400, Hendrik Boom wrote:
> > But I am still curious how reilient aptitude is to disasters like
> > disk-space shortage, and whether there is any way fo finding and
> > repairing the packages tha
On Sat, Jun 11, 2005 at 05:46:50PM -0400, Hendrik Boom wrote:
> But I am still curious how reilient aptitude is to disasters like
> disk-space shortage, and whether there is any way fo finding and
> repairing the packages that were damages or misconfigured as a result.
dpkg -l | grep -v ^ii
will
On Sat, Jun 11, 2005 at 08:37:24PM +0200, Maurits van Rees wrote:
> On Sat, Jun 11, 2005 at 04:46:22PM +0100, peter colton wrote:
> > did you clear var out for apt.
> > apt-get clean
> > apt-get autoclean
>
> I would vote for apt-get autoclean here. 'clean' removes all package
> files. 'autoc
On Sat, Jun 11, 2005 at 07:00:31PM +0100, peter colton wrote:
> On Saturday 11 June 2005 17:20, Hendrik Boom wrote:
> > On Sat, Jun 11, 2005 at 04:46:22PM +0100, peter colton wrote:
> > > On Saturday 11 June 2005 16:49, Hendrik Boom wrote:
> > > > After 18 hours of upgrading on my very slow 100 MHz
On Sat, Jun 11, 2005 at 04:46:22PM +0100, peter colton wrote:
> did you clear var out for apt.
> apt-get clean
> apt-get autoclean
I would vote for apt-get autoclean here. 'clean' removes all package
files. 'autoclean' only removes files that cannot be downloaded
anymore. So autoclean would k
On Jun 11 2005, Hendrik Boom wrote:
> Will try again. But ... Is it possible to resume the broken upgrade?
Yes, it is. But besides the hint given by the previous poster, it would be
nice if you could purge some unneeded packages, install both debophan and
debfoster and remove unneeded packages/li
On Saturday 11 June 2005 17:20, Hendrik Boom wrote:
> On Sat, Jun 11, 2005 at 04:46:22PM +0100, peter colton wrote:
> > On Saturday 11 June 2005 16:49, Hendrik Boom wrote:
> > > After 18 hours of upgrading on my very slow 100 MHz Pentium,
> > > it ended up producing an unending stream of
> > >
> >
On Sat, Jun 11, 2005 at 04:46:22PM +0100, peter colton wrote:
> On Saturday 11 June 2005 16:49, Hendrik Boom wrote:
> > After 18 hours of upgrading on my very slow 100 MHz Pentium,
> > it ended up producing an unending stream of
> >
> > multilog: warning: unable to write to /var/log/svscan/current.
On Saturday 11 June 2005 16:49, Hendrik Boom wrote:
> After 18 hours of upgrading on my very slow 100 MHz Pentium,
> it ended up producing an unending stream of
>
> multilog: warning: unable to write to /var/log/svscan/current. pausing: out
> of disk space
>
> The installation log file (made using
After 18 hours of upgrading on my very slow 100 MHz Pentium,
it ended up producing an unending stream of
multilog: warning: unable to write to /var/log/svscan/current. pausing: out of
disk space
The installation log file (made using script on another partition)
also contains complaints that othe
On (16/05/05 22:03), Mankuthimma wrote:
> > At the risk of being contrary, I recently (January) upgraded a couple of
> > servers from woody to sarge and it was pretty trivial - in fact I don't
> > recall having to do any reconfiguration other than answer some questions
> > during the upgrade.
> >
> At the risk of being contrary, I recently (January) upgraded a couple of
> servers from woody to sarge and it was pretty trivial - in fact I don't
> recall having to do any reconfiguration other than answer some questions
> during the upgrade.
>
> Given the supposed strength of Debian is that it
On (16/05/05 02:58), Simon Gloßner wrote:
> Hi,
>
> * Andy Hawkins <[EMAIL PROTECTED]> wrote:
> > Now that Sarge has entered freeze, I'm considering upgrading my Woody box to
> > it. This runs the firewall for my local network (connected via Ethernet
> > cable modem) handling mail (Exim v3 and fet
Hi,
* Andy Hawkins <[EMAIL PROTECTED]> wrote:
> Now that Sarge has entered freeze, I'm considering upgrading my Woody box to
> it. This runs the firewall for my local network (connected via Ethernet
> cable modem) handling mail (Exim v3 and fetchmail), news (newsstar and INN
> v2.3.2), web proxy e
Andy Hawkins wrote:
>Hi all,
>
>Now that Sarge has entered freeze, I'm considering upgrading my Woody box to
>it. This runs the firewall for my local network (connected via Ethernet
>cable modem) handling mail (Exim v3 and fetchmail), news (newsstar and INN
>v2.3.2), web proxy etc.
>
>Is the upgra
Hi all,
Now that Sarge has entered freeze, I'm considering upgrading my Woody box to
it. This runs the firewall for my local network (connected via Ethernet
cable modem) handling mail (Exim v3 and fetchmail), news (newsstar and INN
v2.3.2), web proxy etc.
Is the upgrade to Sarge relatively painle
et update && apt-get
> dist-upgrade, but I can't find what. Just changing "stable" to "sarge"
> or "testing" makes no difference. Anyway, thanx for ur help.
>
Try "woody sarge update apt-get sources list" into Google - the first
te
In /etc/sources.list, change any reference to `stable' (or `woody') to
`testing'.
Run
# apt-get update && apt-get dist-upgrade
Wait for it all to download & install, and you're set.
Eric Scott wrote:
Hey, sorry to ask this FAQ, I know I've done it before, but google is NO
help to me here.
What
Hey, sorry to ask this FAQ, I know I've done it before, but google is NO
help to me here.
What exactly do I do to upgrade from Woody to Sarge. I know i have to
plop something in sources.list, the do apt-get update && apt-get
dist-upgrade, but I can't find what. Just changing "stable" to "sarg
On 2004-11-18, Hugo Vanwoerkom <[EMAIL PROTECTED]> wrote:
> Felixk Karpfen wrote:
>> before plunging into an upgrade
>> via "apt-cdrom".
>>
>> I have used this routine successfully to add the "Debian 3.0R2" upgrade
>> disk to my successfully-installed "Debian 3.0R1"; but I blench at an
>> upgrad
On Sun, 21 Nov 2004 11:50:42 -0600, John J Waldeck <[EMAIL PROTECTED]> wrote:
> I was directed to file bug reports for installations of Woody
> (which failed with a P4 system), and Sarge (which failed on a P3 system
> and succeeded on a P4 system). My question is which package should I
> i
I was directed to file bug reports for installations of Woody
(which failed with a P4 system), and Sarge (which failed on a P3 system
and succeeded on a P4 system). My question is which package should I
indicate for the bug reports?
jjwdeck
_
Felixk Karpfen wrote:
Although this query may already have been answered several times in
recent postings, as a new arrival to Debian, I venture to check that I
have understood the docs correctly before plunging into an upgrade
via "apt-cdrom".
I have used this routine successfully to add the "Debi
Although this query may already have been answered several times in
recent postings, as a new arrival to Debian, I venture to check that I
have understood the docs correctly before plunging into an upgrade
via "apt-cdrom".
I have used this routine successfully to add the "Debian 3.0R2" upgrade
di
On Mon, Oct 18, 2004 at 09:44:03AM +, Alexis Huxley wrote:
> If you cannot get the X server running, or it just didn't start on its
> own at boot-time, then post the output from running 'X' from the console
> - all of it, exactly as it appears.
Or the more common "startx".
--
Carl Fink
On (18/10/04 09:40), Paul E Condon wrote:
> On Mon, Oct 18, 2004 at 12:39:47PM +0530, Vikas Rawal wrote:
> > I have been trying to install debian on a Compaq Deskpro EN for last one
> > week. I have tried both woody (stable) and sarge (testing). In both, the
> > x-windows configuration does not w
On Mon, Oct 18, 2004 at 12:39:47PM +0530, Vikas Rawal wrote:
> I have been trying to install debian on a Compaq Deskpro EN for last one
> week. I have tried both woody (stable) and sarge (testing). In both, the
> x-windows configuration does not work. In woody, installation went fine
> except th
why did it take 13 hours for you to download??? is JNU part of ernet?
if yes then, use the debian mirror at IIT Madras. here from university
of pune i downloaded the sarge in 20 mins at 625 Kb/s. the ernet is
really fast.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscr
> at the end nothing worked. I think the problem is again with x-windows.
>
> What does one do?
Start by explaining in a lot more detail what "nothing worked" means:
what commands did you run which didn't work?
If you cannot get the X server running, or it just didn't start on its
own at boot-t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I have been trying to install debian on a Compaq Deskpro EN for last one
> week. I have tried both woody (stable) and sarge (testing). In both, the
> x-windows configuration does not work. In woody, installation went fine
> except that none of the vi
I have been trying to install debian on a Compaq Deskpro EN for last one
week. I have tried both woody (stable) and sarge (testing). In both, the
x-windows configuration does not work. In woody, installation went fine
except that none of the video cards/monitor options there get x-windows
runni
I have been trying to install debian on a Compaq Deskpro EN for last one
week. I have tried both woody (stable) and sarge (testing). In both, the
x-windows configuration does not work. In woody, installation went fine
except that none of the video cards/monitor options there get x-windows
runni
somebody said:
>>>systems every day. I've been doing it on about 10 systems for about 2
>>>years, and haven't had a lot of trouble; indeed once my mail servers
>>> went
>>>down for a few hours for that reason, but my mail servers are always
>>> looking
>>>for an excuse to go down.
Use ssh-agent, a
Karsten M. Self wrote:
on Wed, May 19, 2004 at 08:07:46PM -0400, David Gaudine ([EMAIL PROTECTED]) wrote:
and if ththeresroblem with MTMTApgrade ?:)
True, now and then I have to count the subject lines to make sure all
systems are accounted for. But it's still better than logging in to all the
sys
on Wed, May 19, 2004 at 08:07:46PM -0400, David Gaudine ([EMAIL PROTECTED]) wrote:
> > and if ththeresroblem with MTMTApgrade ?:)
>
> True, now and then I have to count the subject lines to make sure all
> systems are accounted for. But it's still better than logging in to all the
> systems every
Colin Watson <[EMAIL PROTECTED]> wrote:
On Wed, May 19, 2004 at 10:19:29AM -0500, Michael Kahle wrote:
Wednesday, May 19, 2004 5:14 AM Colin Watson wrote:
I *strongly* recommend against upgrading by cron job. Just don't do
it; there are lots of ways it can break.
I have heard this m
> and if ththeresroblem with MTMTApgrade ?:)
True, now and then I have to count the subject lines to make sure all
systems are accounted for. But it's still better than logging in to all the
systems every day. I've been doing it on about 10 systems for about 2
years, and haven't had a lot of tro
--- David GaGaudinedadavidmemclaboconcordiaa> wrote:
> > I know that this is not recommended. But I often
> set up DeDebianachines
> > for "friends" who have virtually no clue
> whatsoever and no intentions
> > of changing this. The machines are obviously not
> very important but I
> > want to prov
> I know that this is not recommended. But I often set up Debian machines
> for "friends" who have virtually no clue whatsoever and no intentions
> of changing this. The machines are obviously not very important but I
> want to provide at least a minimal level of security because if I do not
> it w
>
> In my opinion semi-automaticaly updates sound scary
> itself...
>
> - Martin
I agree, and I never use it.
But still, even on manual updates , it can cause
problem.
cheers,
http://www.axeltabs.com/
__
axel
__
Do you Yahoo!?
SBC Ya
On Wed, May 19, 2004 at 01:59:28PM -0700, Ping Wing wrote:
> > Upgrades require interaction from time to time, such
> > as conffile merges.
> > Even with packages that use debconf, the defaults
> > you get with the
> > noninteractive frontend aren't always what you want.
>
> well but lets assume i
> Upgrades require interaction from time to time, such
> as conffile merges.
> Even with packages that use debconf, the defaults
> you get with the
> noninteractive frontend aren't always what you want.
well but lets assume i have little router ticking
somewhere. only sshd listening.
If I configu
> Every Debian init.d script that starts a daemon says
> something like
> "Starting web server: apache."
>
some processes take long time to finish.
slurpd hangs sometime mystically or takes long to
finish.
I think it could cause probelms if I start it again
before its done.
some scripts are ok
On Wednesday, May 19, 2004 10:42 AM Colin Watson wrote:
>On Wed, May 19, 2004 at 10:19:29AM -0500, Michael Kahle wrote:
>> Wednesday, May 19, 2004 5:14 AM Colin Watson wrote:
>>> I *strongly* recommend against upgrading by cron job. Just don't do
>>> it; there are lots of ways it can break.
>>
>>
Incoming from Michael Kahle:
> Wednesday, May 19, 2004 5:14 AM Colin Watson wrote:
> > I *strongly* recommend against upgrading by cron job. Just don't do
> > it; there are lots of ways it can break.
>
> I have heard this mentioned before. Could you elaborate? Why is this a
> problem? Please e
On Wed, May 19, 2004 at 10:19:29AM -0500, Michael Kahle wrote:
> Wednesday, May 19, 2004 5:14 AM Colin Watson wrote:
> > I *strongly* recommend against upgrading by cron job. Just don't do
> > it; there are lots of ways it can break.
>
> I have heard this mentioned before. Could you elaborate?
Wednesday, May 19, 2004 5:14 AM Colin Watson wrote:
> I *strongly* recommend against upgrading by cron job. Just don't do
> it; there are lots of ways it can break.
I have heard this mentioned before. Could you elaborate? Why is this a
problem? Please excuse my inexperience here.
Michael
--
On Wed, May 19, 2004 at 11:14:12AM +0100, Colin Watson wrote:
> > Ok, please forget _why_ I ask. The question remains - are the release
> > codenames equivalent to "stable"/"testing" in sources.list? I dont
>
> You can safely use the codenames.
Ok, thank you!
> > And Greg, please think of machin
On Tue, May 18, 2004 at 01:38:33PM -0700, Ping Wing wrote:
> frankly, the fact that debian puts 'stable' in source.list
> automatically is littlebit scaring. For example when sarge is new
> stable one day, and im doing another (semi-)automatic apt-get upgrade,
> theres good chance that this messe
On Wed, May 19, 2004 at 03:13:23AM +0200, Matthias Czapla wrote:
> On Tue, May 18, 2004 at 06:22:04PM -0400, Greg Folkert wrote:
> > On Tue, 2004-05-18 at 15:54, Matthias Czapla wrote:
> > > Can I safely use "woody" or "sarge" instead of stable and testing for
> > > the distribution specifier in /e
On Tue, May 18, 2004 at 01:38:33PM -0700, Ping Wing wrote:
> Matthias Czapla wrote:
> > Can I safely use "woody" or "sarge" instead of stable and testing
> > for the distribution specifier in /etc/apt/sources.list or can this
> > cause trouble? Im afraid of an unwanted upgrade to a new
> > distribu
> Sarge *SUDDENLY* becoming Stable. Don't make me
> laugh.
>
> We aren't even into freeze yet.
>
> When that happens, then you should maybe worry about
> that.
it doesnt matter when it happen.
I must read news every day, be prepared to change all
my sources.list when it happens?
thing is that
On Tue, May 18, 2004 at 06:22:04PM -0400, Greg Folkert wrote:
> On Tue, 2004-05-18 at 15:54, Matthias Czapla wrote:
> > Can I safely use "woody" or "sarge" instead of stable and testing for
> > the distribution specifier in /etc/apt/sources.list or can this cause
> > trouble? Im afraid of an unwant
On Tue, 2004-05-18 at 15:54, Matthias Czapla wrote:
> Can I safely use "woody" or "sarge" instead of stable and testing for
> the distribution specifier in /etc/apt/sources.list or can this cause
> trouble? Im afraid of an unwanted upgrade to a new distribution when
> testing suddenly becomes stabl
> Can I safely use "woody" or "sarge" instead of
> stable and testing for
> the distribution specifier in /etc/apt/sources.list
> or can this cause
> trouble? Im afraid of an unwanted upgrade to a new
> distribution when
> testing suddenly becomes stable.
yes you can and imho it makse very much s
Hi!
Can I safely use "woody" or "sarge" instead of stable and testing for
the distribution specifier in /etc/apt/sources.list or can this cause
trouble? Im afraid of an unwanted upgrade to a new distribution when
testing suddenly becomes stable.
Regards
Matthias
--
To UNSUBSCRIBE, email to [EM
Jerry Spicklemire wrote:
The following packages have unmet dependencies:
e2fsprogs: PreDepends: libblkid1 (>= 1.34-1) but it
is not installable
PreDepends: libss2 (>= 1.34-1) but it is
not installable
PreDepends: libuuid1 (>= 1.34-1) but it
is not installable
coreutils
Incoming from Jerry Spicklemire:
>
> Is there any way to back up in time to
> a state where sarge is complete, and
> therefore upgradable, even if it is
> in a less than ideal state? I can always
I'd suggest you backup /etc and $HOME and re-install, using
woody/stable sources.list. Then if y
Greetings Debian Gurus,
Well, I've learned a lot this week
about how Debian works in the real
world. Up to now I've just been
having a blissful run of beginner's
luck, it seems. The past five days
have seen me chasing down supposed
hardware incompatibilities, sifting
through partial, though
I just finished doing my first distro upgrade through apt, and after doing so I get
the same dependeny problems no matter what I'm trying to install. The out-put reads
as follows:
armagetron: Depends armagetron-common (=0.2.5.2.-3) but it is not going to be installed
Depends: libsdl-image
[EMAIL PROTECTED] wrote
...
> Reading Package Lists... Error!
> E: Dynamic MMap ran out of room
...
this means that apt hit a configured limit and cannot
allocate more memory --- preventing it from processing all
dependencies.
create a file /etc/apt/apt.conf with the line
APT::Cache-Limit
On Mon, Feb 09, 2004 at 01:37:09PM -0800, Roger Chrisman wrote:
> I use 'testing' instead of 'sarge' in /etc/sources.list.
>
> I understand 'testing' == 'sarge', but are they also interchangablely in
> sources.list in that way? Produce identical results?
This is what I understand from it:
Whe
09 February 2004 07:16, Werner Mahr:
> Why stable and unstable if you want Sarge (testing)?
> Try this in your sources.list:
>
> deb http://http.us.debian.org/debian sarge main contrib non-free
> deb http://non-us.debian.org/debian-non-US sarge/non-US main contrib\
> non-free
> deb http://security.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Montag, 9. Februar 2004 18:18 schrieb Adam Funk:
> > deb http://http.us.debian.org/debian sarge main contrib non-free
>
> What's the difference between using "sarge" and "testing", e.g.
>
> deb ftp://www.mirror.ac.uk/sites/ftp.debian.org/debian/ tes
1 - 100 of 156 matches
Mail list logo
