Actually the english version of "man apt-get" in the case of "upgrade"
writes the following:
upgrade
upgrade is used to install the newest versions of all
packages currently installed on the system from the sources enumerated
in /etc/apt/sources.list. Packages currently
i
On Thu 24 Oct 2024 at 13:19:13 (-0400), Daniel Roberts wrote:
> I've run into this a few times over the years and it can be a headache to
> resolve.
>
> Passing a package name to "apt-get update" results in the response "E: The
> update command takes no arguments". However, passing a package name
Hello,
I've run into this a few times over the years and it can be a headache to
resolve.
Passing a package name to "apt-get update" results in the response "E: The
update command takes no arguments". However, passing a package name to
"apt-get upgrade" results in the argument being ignored and a
Daniel Roberts composed on 2024-10-24 13:19 (UTC-0400):
> I've run into this a few times over the years and it can be a headache to
> resolve.
> Passing a package name to "apt-get update" results in the response "E: The
> update command takes no arguments". However, passing a package name to
> "a
Hello Daniel,
# man apt-get
(german translation) doesn't tell anything else. apt-get upgrade
upgrades ALL installed packages.
Kind regards
Frank
Daniel Roberts:
Hello,
I've run into this a few times over the years and it can be a headache
to resolve.
Passing a package name to "apt-get
There is a new package in Backports:
https://packages.debian.org/search?keywords=telegram-desktop&searchon=names§ion=all&suite=buster-backports
On Sun, Feb 13, 2022 at 10:48 AM Kilo Byte wrote:
> hi debian team,
> the telegram-desktop is outdated in the repo.
> pls try to update it asap
> regard
hi debian team,
the telegram-desktop is outdated in the repo.
pls try to update it asap
regards
Am 28.04.2015 um 03:29 schrieb Bill Baker:
> That's what I thought at first, too. But when I ran 'apt-get remove
> consolekit', it didn't report any dependencies. I expected to see a
> list as long as my arm, but nope.
consolekit is pretty much unused in jessie. There are only very few
packages
On 04/27/2015 09:26 PM, The Wanderer wrote:
> On 04/27/2015 at 09:19 PM, Bill Baker wrote:
>
>> On a whim, I decided to see what would happen if I uninstalled
>> consolekit. Lo and behold, after uninstalling it, I was able to
>> upgrade the kernel normally and run a normal upgrade. Thanks to
>> e
On 04/27/2015 at 09:19 PM, Bill Baker wrote:
> On a whim, I decided to see what would happen if I uninstalled
> consolekit. Lo and behold, after uninstalling it, I was able to
> upgrade the kernel normally and run a normal upgrade. Thanks to
> everyone who offered help. Replying to your respons
On a whim, I decided to see what would happen if I uninstalled
consolekit. Lo and behold, after uninstalling it, I was able to upgrade
the kernel normally and run a normal upgrade. Thanks to everyone who
offered help. Replying to your responses helped me think through this.
--
To UNSUBSCRIBE,
Am 28.04.2015 um 01:43 schrieb The Wanderer:
> On 04/27/2015 at 07:15 PM, Bill Baker wrote:
>> Here is the output from sudo apt-get install linux-image-586:
>>
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> You might want to run 'apt-get
On 04/27/2015 at 07:15 PM, Bill Baker wrote:
> On 04/27/2015 07:05 PM, The Wanderer wrote:
>>
>> A few thoughts:
>>
>> 1. Is there a reason why you need 'apt-get -f install packagename'?
>> Does it error out if you just run 'apt-get install packagename'?
>
> I used -f because the output suggest
On 04/27/2015 07:04 PM, Michael Biebl wrote:
>
> Have you rebooted, using that kernel?
> What does uname -r say?
I have rebooted, but the new kernel has not installed. Here is uname -r:
2.6.32-5-486
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscr
On 04/27/2015 07:05 PM, The Wanderer wrote:
>
> A few thoughts:
>
> 1. Is there a reason why you need 'apt-get -f install packagename'? Does
> it error out if you just run 'apt-get install packagename'?
I used -f because the output suggested I use it.
> 2. What happens if you try to install linux
On 04/27/2015 at 06:57 PM, Bill Baker wrote:
> On 04/27/2015 06:23 PM, Michael Biebl wrote:
>
>> Am 28.04.2015 um 00:05 schrieb Bill Baker:
>>> Anyone have any ideas on what I can try next?
>>>
>> First upgrade your kernel to the wheezy version (reboot) and everything
>> will be fine.
>>
>> Dist-
Am 28.04.2015 um 00:57 schrieb Bill Baker:
> On 04/27/2015 06:23 PM, Michael Biebl wrote:
>> Am 28.04.2015 um 00:05 schrieb Bill Baker:
>>> Over the weekend, I upgraded my headless ssh server from wheezy to jessie.
>>> It's an older computer, built in the year 2000 with an AMD-K6 processor.
>>> Una
On 04/27/2015 06:23 PM, Michael Biebl wrote:
> Am 28.04.2015 um 00:05 schrieb Bill Baker:
>> Over the weekend, I upgraded my headless ssh server from wheezy to jessie.
>> It's an older computer, built in the year 2000 with an AMD-K6 processor.
>> Uname -a returns the following:
>>
>> Linux shunnel
Am 28.04.2015 um 00:05 schrieb Bill Baker:
> Over the weekend, I upgraded my headless ssh server from wheezy to jessie.
> It's an older computer, built in the year 2000 with an AMD-K6 processor.
> Uname -a returns the following:
>
> Linux shunnel 2.6.32-5-486 #1 Mon Feb 25 00:22:26 UTC 2013 i586 G
Over the weekend, I upgraded my headless ssh server from wheezy to jessie.
It's an older computer, built in the year 2000 with an AMD-K6 processor.
Uname -a returns the following:
Linux shunnel 2.6.32-5-486 #1 Mon Feb 25 00:22:26 UTC 2013 i586 GNU/Linux
Since upgrading, whenever I try to do an a
Am 11.01.2014 14:15, schrieb Brian:
> You could do
>
>apt-get --reinstall install -o Dpkg::Options::"--force-confask"
>
> to force a conffile prompt.
>
> What happens?
>
I'm being asked which version of the configuration file I would like to
see used. Great. Your suggestion also helped me
On 2014-01-11 13:20 +0100, Malte Forkel wrote:
> Am 11.01.2014 11:53, schrieb Dominique Dumont:
>> Did you change the content of the conffile in the package ?
>> (i.e. the content of the *delivered* configuration file between package
>> version n and version n-1)
>>
> No. The configuration file
On Sat 11 Jan 2014 at 13:21:06 +0100, Malte Forkel wrote:
> Am 11.01.2014 12:02, schrieb Brian:
> >
> > Ckeck that the file in question is a conffile:
> >
> >dpkg --status
> >
> It's a conffile.
You could do
apt-get --reinstall install -o Dpkg::Options::"--force-confask"
to force a
Am 11.01.2014 12:02, schrieb Brian:
>
> Ckeck that the file in question is a conffile:
>
>dpkg --status
>
It's a conffile.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lis
Am 11.01.2014 11:53, schrieb Dominique Dumont:
> Did you change the content of the conffile in the package ?
> (i.e. the content of the *delivered* configuration file between package
> version n and version n-1)
>
No. The configuration file did not change between versions.
Is dpkg smart enough
On Sat 11 Jan 2014 at 11:04:08 +0100, Malte Forkel wrote:
> I have a question regarding the handling of locally modified conffiles
> on package upgrades.
>
> When I installed a new version of a self-written native package, I
> noticed that I was not asked whether I wanted to keep or replace a
> c
On Saturday 11 January 2014 11:04:08 Malte Forkel wrote:
> What might I be missing?
Did you change the content of the conffile in the package ?
(i.e. the content of the *delivered* configuration file between package
version n and version n-1)
signature.asc
Description: This is a digitally sig
Hello,
I have a question regarding the handling of locally modified conffiles
on package upgrades.
When I installed a new version of a self-written native package, I
noticed that I was not asked whether I wanted to keep or replace a
configuration file that I had modified locally. After the upgrad
On Ma, 01 oct 13, 13:56:32, Bob Proulx wrote:
> Chris Bannister wrote:
> > Vincent Lefevre wrote:
> > > During important upgrades such as locales, I avoid doing things
> > > like starting an xterm... Usually, already running applications
> >
> > You do system upgrades WITH X running? :(
>
> One o
On 2013-09-30 04:03:54 +1300, Chris Bannister wrote:
> On Sat, Sep 28, 2013 at 03:45:01PM +0200, Ralf Mardorf wrote:
> > On Sun, 2013-09-29 at 01:15 +1200, Chris Bannister wrote:
> > > On Tue, Sep 24, 2013 at 02:20:39AM +0200, Vincent Lefevre wrote:
> > > >
> > > > During important upgrades such a
Chris Bannister wrote:
> Vincent Lefevre wrote:
> > During important upgrades such as locales, I avoid doing things
> > like starting an xterm... Usually, already running applications
>
> You do system upgrades WITH X running? :(
One of my machines is an Unstable Sid system as a desktop. I am us
On Sat, Sep 28, 2013 at 03:45:01PM +0200, Ralf Mardorf wrote:
> On Sun, 2013-09-29 at 01:15 +1200, Chris Bannister wrote:
> > On Tue, Sep 24, 2013 at 02:20:39AM +0200, Vincent Lefevre wrote:
> > >
> > > During important upgrades such as locales, I avoid doing things
> > > like starting an xterm...
On Sun, 2013-09-29 at 01:15 +1200, Chris Bannister wrote:
> On Tue, Sep 24, 2013 at 02:20:39AM +0200, Vincent Lefevre wrote:
> >
> > During important upgrades such as locales, I avoid doing things
> > like starting an xterm... Usually, already running applications
>
> You do system upgrades WITH
On Tue, Sep 24, 2013 at 02:20:39AM +0200, Vincent Lefevre wrote:
>
> During important upgrades such as locales, I avoid doing things
> like starting an xterm... Usually, already running applications
You do system upgrades WITH X running? :(
If there is a problem with the upgrade of X, you could
On 2013-09-23 14:11:31 -0600, Bob Proulx wrote:
> Vincent Lefevre wrote:
> > When packages are upgraded (e.g. locales), cron scripts can given
> > errors. Is it possible to lock (delay) them during a package upgrade?
> > Shouldn't this be done by default?
>
>
Vincent Lefevre wrote:
> When packages are upgraded (e.g. locales), cron scripts can given
> errors. Is it possible to lock (delay) them during a package upgrade?
> Shouldn't this be done by default?
I have noticed this at times too. When I am doing a full system
upgrade from ma
When packages are upgraded (e.g. locales), cron scripts can given
errors. Is it possible to lock (delay) them during a package upgrade?
Shouldn't this be done by default?
--
Vincent Lefèvre - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.v
On Thu, 09 Aug 2012 12:44:08 -0500, hvw59601 wrote:
> I would like to be notified when package linux-source-3.2 (3.2.23-1) in
> Sid gets upgraded. Is that possible? I can look of course and find out,
> but it would be more interesting to be notified. I normally run wheezy
> which is still at 3.2.2
On Jo, 09 aug 12, 12:44:08, hvw59601 wrote:
> Hi,
>
> I would like to be notified when package linux-source-3.2 (3.2.23-1)
> in Sid gets upgraded. Is that possible? I can look of course and
> find out, but it would be more interesting to be notified. I
> normally run wheezy which is still at 3.2.2
Hi,
I would like to be notified when package linux-source-3.2 (3.2.23-1) in
Sid gets upgraded. Is that possible? I can look of course and find out,
but it would be more interesting to be notified. I normally run wheezy
which is still at 3.2.21-3.
Hugo
--
To UNSUBSCRIBE, email to debian-use
@lists.debian.org
Subject: How to reverse a package upgrade?
Debian / testing
Hi,
Upgraded "suversion" package to the latest in debian/testing, that is,
version:
1.4.0-5 . Once upgrade was completed, it became clear that I should have
stuck
with the old version of subversion packag
On Sun, Oct 29, 2006 at 07:58:58PM -0800, rds wrote:
> Is the old version of the package still available in "testing"? And if not, is
> there a way to rollback to a previous verson of the package? I'm using
> aptitude
You want to take a look at http://snapshot.debian.net/ - although
bear in m
Debian / testing
Hi,
Upgraded "suversion" package to the latest in debian/testing, that is, version:
1.4.0-5 . Once upgrade was completed, it became clear that I should have stuck
with the old version of subversion package, the old version was version
1.3.2-5, I think.
So, now it's highly desir
Hi all,
To upgrade the package, I have two way:
"aptitude update" and then "aptitude upgrade",
or "aptitude update" and then "aptitude dist-upgrade".
So what is main difference between the two parameters
"upgrade" and "dist-upgrade" for command "aptitude"? and which is
recommended on
On Tuesday 13 July 2004 10:16 am, Reid Priedhorsky wrote:
> I suppose Googling may help. The man page on Debian is not so helpful.
Not very helpful at all. I get it now. Thanks.
--
Michael McIntyre Silvan <[EMAIL PROTECTED]>
Linux fanatic, and certified Geek; registered Linux user #2
On Tue, 13 Jul 2004 09:30:18 +0200, Silvan wrote:
>
>> Also look into the tput program. You tell it what you want (bold,
>> green, etc.) and it outputs appropriate magic for your current
>> terminal.
>
> Sounds interesting, but any syntax examples? I couldn't make heads or
> tails of it.
Here'
> It's a matter of a 3-way merge, as cvs does it. The three files are:
> 1) Old package version original config file
> 2) New package version config file
> 3) The installed config file (with your changes).
>
> This would mean changing dpkg to keep pristine copies of installed
> conffiles (fi
Once upon a time Silvan said...
>
> It would be cool if this process could use a CVS-style merge instead. I
> wonder how hard it would be to do this in practice?
>
> I guess it's not such a simple matter as merging two source files, really.
It's a matter of a 3-way merge, as cvs does it. The
On Monday 12 July 2004 06:31 pm, Monique Y. Mudama wrote:
> > remote, etc. It helps when you have as many different terminal
> > sessions open at one time as I do.
>
> Great minds must think alike ... root is red for me, too =)
Hard to argue with that. Great minds indeed. :)
Incidentally, on
> Also look into the tput program. You tell it what you want (bold, green,
> etc.) and it outputs appropriate magic for your current terminal.
Sounds interesting, but any syntax examples? I couldn't make heads or tails
of it.
--
Michael McIntyre Silvan <[EMAIL PROTECTED]>
Linux fanati
On Tue, 13 Jul 2004 01:10:06 +0200, Monique Y. Mudama wrote:
>
> > Wow, how could you do that? Can you share your code with us? I use
> > colored xterms to distinguish those -- easier to do. :-)
>
> In my root .bashrc I have this:
>
> export PS1='\e[31;1m\h:\w\$\e[0m '
Also look into the tput p
On 2004-07-10, * Tong* penned:
> On Sat, 10 Jul 2004 00:55:08 -0400, Silvan wrote:
>
>> anyway. One thing I've done to help me keep track of where I am is
>> to use colorized prompts. Red is root, cyan is local user, purple is
>> local user with developer environment variables, green is remote,
>
On 2004-07-10, Silvan penned:
>
> One thing I've done to help me keep track of where
> I am is to use colorized prompts. Red is root, cyan is local user,
> purple is local user with developer environment variables, green is
> remote, etc. It helps when you have as many different terminal
> sessio
On Fri, Jul 09, 2004 at 10:31:02AM -0400, Ken Long wrote:
> I have a question that I hope someone can help me with.
>
> As some background, we had a problem where every once in a very long
> while, someone (usually me O:) ) would get a little ahead of themselves
> and issue a shutdown command to s
> > use colorized prompts. Red is root, cyan is local user, purple is local
> > user with developer environment variables, green is remote, etc. It
> > helps when you have as many different terminal sessions open at one time
> > as I do.
>
> Wow, how could you do that? Can you share your code wi
On Sat, 10 Jul 2004 00:55:08 -0400, Silvan wrote:
> anyway. One thing I've done to help me keep track of where I am is to use
> colorized prompts. Red is root, cyan is local user, purple is local user
> with developer environment variables, green is remote, etc. It helps when
> you have as m
> /sbin/shutdown file, or better yet, redirect the new /sbin/shutdown file
> to /sbin/shutdown.real instead? Is that possible?
You already have the answer you seek about dpkg-divert. It works well.
While your problem is certainly solved, I thought I'd throw out a suggestion
anyway. One thing
Ken Long wrote:
I have a question that I hope someone can help me with.
As some background, we had a problem where every once in a very long
while, someone (usually me O:) ) would get a little ahead of themselves
and issue a shutdown command to shut down the system they were logged in
on. Problem
--- Ken Long <[EMAIL PROTECTED]> wrote:
> So, I had this bright idea to replace shutdown with a script that
> would take an additional parameter of the hostname of the system. The
> script would then check the hostname given on the commandline against
> the hostname of the system it was bein
On Fri, 09 Jul 2004 10:31:02 -0400
Ken Long <[EMAIL PROTECTED]> wrote:
> So, here is my question. How can I make it so that if I upgrade the
> sysvinit package on a system, it will either just not touch the
> /sbin/shutdown file, or better yet, redirect the new /sbin/shutdown
> file to /sbin/shu
I have a question that I hope someone can help me with.
As some background, we had a problem where every once in a very long
while, someone (usually me O:) ) would get a little ahead of themselves
and issue a shutdown command to shut down the system they were logged in
on. Problem was, the person
Le dimanche 4 Avril 2004 16:43, Colin Watson a écrit :
>
> Don't remove all of them, then. From update-rc.d(8):
>
>If any files /etc/rcrunlevel.d/[SK]??name already exist then
>update-rc.d does nothing. This is so that the system adminis-
>trator can rearrange the l
gt; > The problem is that after each deamon package upgrade, the symlinks are
> > created again. I heard about some hacks to avoid this, but I thinks we
> > need a cleaner policy to manage this, like a file where there are
> > symlinks which can be upgrade for example.
> >
&
On Sun, Apr 04, 2004 at 03:44:48PM +0200, jjluza wrote:
> For some reason, I need to remove some symlinks to daemon in rc?.d. I launh
> such a deamon from another place by running manually /etc/init.d/daemon
> start.
> The problem is that after each deamon package upgrade, the
jjluza wrote:
Dear people,
For some reason, I need to remove some symlinks to daemon in rc?.d. I launh
such a deamon from another place by running manually /etc/init.d/daemon
start.
The problem is that after each deamon package upgrade, the symlinks are
created again. I heard about some hacks
Dear people,
For some reason, I need to remove some symlinks to daemon in rc?.d. I launh
such a deamon from another place by running manually /etc/init.d/daemon
start.
The problem is that after each deamon package upgrade, the symlinks are
created again. I heard about some hacks to avoid this
Ivan Nestlerode wrote:
Hello debian-user,
I'm running Debian unstable and I would like to revert one package
upgrade that I did earlier this week.
I upgraded to version 0.6.1-5 of mozilla-firebird. After some testing
and attempts to do basic things with bookmarks, I've found it much
Hello debian-user,
I'm running Debian unstable and I would like to revert one package
upgrade that I did earlier this week.
I upgraded to version 0.6.1-5 of mozilla-firebird. After some testing
and attempts to do basic things with bookmarks, I've found it much too buggy
(the bugs ar
Sent: Friday, September 27, 2002 11:20 PM
Subject: Re: 1Re: eth0 problem after kernal package upgrade
> "Neal" == Neal Pollock <[EMAIL PROTECTED]> writes:
>
> Neal> a... I found the driver in
> Neal> /lib/modules/2.4.18-k7/kernel/drivers/net/
&g
"Neal" == Neal Pollock <[EMAIL PROTECTED]> writes:
Neal> a... I found the driver in
Neal> /lib/modules/2.4.18-k7/kernel/drivers/net/
>> "eth0: Macronix 98715 PMAC rev 37 at 0xd400,
>> 00:80:C6:EA:C0:69, IRQ 4 eth0: EEPROM default media type
>> 10baseT. via-rhine.c:v
"Neal" == Neal Pollock <[EMAIL PROTECTED]> writes:
Neal> Thanks Shayamal. I have the following lines from 'dmesg' on
Neal> 2.2.20 kernel:
Neal> "eth0: Macronix 98715 PMAC rev 37 at 0xd400,00:80:C6:EA:C0:69, IRQ 4
Neal> eth0: EEPROM default media type 10baseT.
Neal> via-
.0.1 12/14/2000"
>
> How can I discern the name of the driver module for 2.4.18 from this?
>
> Neal.
> - Original Message -
> From: "Shyamal Prasad" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, September 27, 2002 9:22 AM
for 2.4.18 from this?
Neal.
- Original Message -
From: "Shyamal Prasad" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 27, 2002 9:22 AM
Subject: Re: eth0 problem after kernal package upgrade
> "Neal" == Neal Pollock <[EMAIL
"Neal" == Neal Pollock <[EMAIL PROTECTED]> writes:
Neal> Thanks for the repsonse, here's my details:
Neal> http://members.rogers.com/npollock1/sysinfo.txt
Neal,
I think the only thing you missed there is the kind of NIC you
have. If you don't know this look in the output of 'lspci'
Thanks for the repsonse, here's my details:
http://members.rogers.com/npollock1/sysinfo.txt
Neal.
- Original Message -
From: "nate" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 26, 2002 2:46 PM
Subject: Re: eth0 problem after kern
"Neal" == Neal Pollock <[EMAIL PROTECTED]> writes:
Neal> i recently upgraded my kernel from 2.2.20 to 2.4.18 using a
Neal> kernel image via dselect. Unfortunately when I boot the new
Neal> kernel i cannot establish an internet connection. Am I
Neal> correct in assuming that
Neal Pollock said:
> i recently upgraded my kernel from 2.2.20 to 2.4.18 using a kernel image
> via dselect. Unfortunately when I boot the new kernel i cannot establish
> an internet connection. Am I correct in assuming that i need to to
> check:
>
> a) eth0 is properly configured
> b) dhcpclien
Neal Pollock wrote:
> i recently upgraded my kernel from 2.2.20 to 2.4.18 using a kernel image via
> dselect. Unfortunately when I boot the new kernel i cannot establish an
> internet connection. Am I correct in assuming that i need to to check:
>
> a) eth0 is properly configured
> b) dhcpclien
i recently upgraded my kernel from 2.2.20 to 2.4.18 using a kernel image via
dselect. Unfortunately when I boot the new kernel i cannot establish an
internet connection. Am I correct in assuming that i need to to check:
a) eth0 is properly configured
b) dhcpclient obtained an IP
inorder to tro
Hi!
Printing with apsfilter does not work for me any longer after
doing my regular package upgrade in woody. I have noticed that
lpr, libcups2 and some other printing related packages have changed.
The printer does receive data, but is not able to handle it.
It seems like that the data that is
On 26-Oct-2001 Mark Morshedi wrote:
> using my Official CDROM as the source I tried to add packages using
> APT-get. I issued the command but after initial set of instruction
> and the rest of usuall text, the process comes back and tells me that
> ""Dbconf" is in web mode GOTO HTTP://localhost:8
using my Official CDROM as the source I tried to add packages using
APT-get. I issued the command but after initial set of instruction
and the rest of usuall text, the process comes back and tells me that
""Dbconf" is in web mode GOTO HTTP://localhost:8001". Anyone know
what this mean and where
You probably won't have to do anything special. What is the 'fairly
common source' you speak of?
A month ago, I upgraded from potato (stable) to woody (testing, and
soon to be stable). In potato, my KDE 2.1 packages came from
kde.tdyc.com. The KDE packages are part of woody, so I only had on
On Thu, 6 Sep 2001, Greg Wiley wrote:
> Good day all-
>
> On a Debian Potato, I am using KDE 2.1 packages that
> are, obviously, not part of Potato but are from a fairly
> common source.
If you are using stuff Ivan Moore has done...
> Since KDE 2.2 is slated for inclusion in the upcoming
> Debia
On 2001.09.06 19:03 Greg Wiley wrote:
> Good day all-
>
> On a Debian Potato, I am using KDE 2.1 packages that
> are, obviously, not part of Potato but are from a fairly
> common source.
>
> Since KDE 2.2 is slated for inclusion in the upcoming
> Debian release, what is the best way to prepare
Good day all-
On a Debian Potato, I am using KDE 2.1 packages that
are, obviously, not part of Potato but are from a fairly
common source.
Since KDE 2.2 is slated for inclusion in the upcoming
Debian release, what is the best way to prepare for the
upgrade? I cannot assume that the new packages
Hi,
too funny! Right after I posted this I upgraded to exim 3.02. AFTER the upgrade
dselect gave me this message:
Important! Exim configuration file format has changed!
==
Your old configuration file has been renamed to /etc/exim.conf-pre-v3. An
Hi,
one thing I would like to see is some kind of "warning" when a package that can
be upgraded using dselect if the upgrade means the software needs to be
majorly reconfigured after the upgrade.
An example would be if for instance program-x could be upgraded and
/etc/program-x.conf would have t
88 matches
Mail list logo
