Re: What happen if I start following stable after upgrading to unstable?

[kamaraju kusumanchi]

On Sat, Oct 7, 2017 at 9:25 AM, Mostafa Shahverdy <most...@mostafa.info> wrote:
> Few while ago I tried upgrading to unstable and I could update all my packages
> successfully. Now I'm going to use stable version. I am following only
> stable repository and each time I hit `apt-get dist-upgrade` it
> successfully upgrades few packages.
>
> Is this a safe way to stick with stable?
>

If your idea is to eventually track stable if and when buster becomes
stable, then your approach is fine.

One side note: If you put "stable" in /etc/apt/sources.list, apt will
try to "upgrade" the packages to whatever is the current stable
version. Currently that is Stretch and it will be buster after the
next release etc., If you put "buster" in /etc/apt/sources.list, apt
will try to track the buster release irrespective of whether it is
currently stable or testing.

raju
-- 
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

Re: What happen if I start following stable after upgrading to unstable?

[Daniel Keast]

On Sun, Oct 08, 2017 at 06:30:03AM +0330, Mostafa Shahverdy wrote:
> > Yes. I am assuming you made a new stable installation, you have not
> > just changed the repository from unstable to stable. That will most
> > definitely not work.
> > 
> > Are you asking why only a few packages are upgraded, compared to
> > unstable?
> > 
> > Stable should not need many upgrades. In unstable, package versions are
> > frequently upgraded, most of the software has bugs, and sometimes the
> > entire architecture of a linked group of programs is changed.
> > 
> > In general, software versions in stable do not change, except for web
> > browsers and anti-virus software. Security bugs are fixed, though not
> > normally functional bugs. Debian stable is often used in servers, where
> > a change of behaviour due to a bug being fixed may cause worse problems
> > than the bug did. 
> > 
> > The whole purpose of stable is to be an unchanging platform, as far as
> > is possible. That means that the software versions are largely frozen
> > months before release, and will never change. If you need fairly
> > up-to-date software all the time, then stable is not the correct
> > distribution to use, either testing or unstable are more appropriate.
> > 
> I know that my packages are ahead at the moment, but what about the
> future?  My question is can I get updates in the future? For example the time
> that the `buster` becomes stable, can I securely update/upgrade? 
> This is my personal PC.
> -- 
> Regards,
> Mostafa Shahverdy 

Why not just use Buster? What your saying will probably work, but in the
meantime you'll have a broken insecure system.

https://wiki.debian.org/DontBreakDebian#Don.27t_make_a_FrankenDebian

Buster probably wont become stable until about 2019.

-- 
Daniel Keast,
Hatherleigh, UK

Re: What happen if I start following stable after upgrading to unstable?

[deloptes]

Mostafa Shahverdy wrote:

> I believe unstable was `buster` and my current installed packages are
> from `buster`. I know that most my packages are ahead, but what about
> like 10 month from now that `buster` becomes stable?
cat /etc/debian_version
9.1
is stretch

I would suggest keep the name buster in apt/source - it will not make
difference when it will become stable. Do regular apt-get update/upgrade.

regards

Re: What happen if I start following stable after upgrading to unstable?

[Mostafa Shahverdy]

> It is not exactly clear what "while ago" means. For example if you were
> using unstable=stretch when stable=jessie and then switched to stable, when
> stable=stretch it sounds reasonable.
> If it is not the case, which is not very likely as you still get updates,
> the versions of the packages will be higher than the one available in the
> repository, so it is strange that you even get updates. I would not expect
> such to be offered.
> 
I believe unstable was `buster` and my current installed packages are
from `buster`. I know that most my packages are ahead, but what about
like 10 month from now that `buster` becomes stable? 
-- 
Regards,
Mostafa Shahverdy 


signature.asc
Description: PGP signature

Re: What happen if I start following stable after upgrading to unstable?

[Mostafa Shahverdy]

> Yes. I am assuming you made a new stable installation, you have not
> just changed the repository from unstable to stable. That will most
> definitely not work.
> 
> Are you asking why only a few packages are upgraded, compared to
> unstable?
> 
> Stable should not need many upgrades. In unstable, package versions are
> frequently upgraded, most of the software has bugs, and sometimes the
> entire architecture of a linked group of programs is changed.
> 
> In general, software versions in stable do not change, except for web
> browsers and anti-virus software. Security bugs are fixed, though not
> normally functional bugs. Debian stable is often used in servers, where
> a change of behaviour due to a bug being fixed may cause worse problems
> than the bug did. 
> 
> The whole purpose of stable is to be an unchanging platform, as far as
> is possible. That means that the software versions are largely frozen
> months before release, and will never change. If you need fairly
> up-to-date software all the time, then stable is not the correct
> distribution to use, either testing or unstable are more appropriate.
> 
I know that my packages are ahead at the moment, but what about the
future?  My question is can I get updates in the future? For example the time
that the `buster` becomes stable, can I securely update/upgrade? 
This is my personal PC.
-- 
Regards,
Mostafa Shahverdy 


signature.asc
Description: PGP signature

Re: What happen if I start following stable after upgrading to unstable?

[deloptes]

Mostafa Shahverdy wrote:

> Few while ago I tried upgrading to unstable and I could update all my
> packages successfully. Now I'm going to use stable version. I am following
> only stable repository and each time I hit `apt-get dist-upgrade` it
> successfully upgrades few packages.
> 
> Is this a safe way to stick with stable?
> 

It is not exactly clear what "while ago" means. For example if you were
using unstable=stretch when stable=jessie and then switched to stable, when
stable=stretch it sounds reasonable.
If it is not the case, which is not very likely as you still get updates,
the versions of the packages will be higher than the one available in the
repository, so it is strange that you even get updates. I would not expect
such to be offered.

We usually do for regular updating

apt-get update
apt-get upgrade

not dist-upgrade

With stable doing so you can be 99.9% sure that it will work. At least
from my experience from the past 10+y. Note however that if you work on
production environment in case libc and friends get updated reboot or
restart of services is required to load newer libc ... 

You've got the response by Joe, where is explained what the purpose of
stable is.

regards

Re: What happen if I start following stable after upgrading to unstable?

[Joe]

On Sat, 7 Oct 2017 19:55:22 +0330
Mostafa Shahverdy <most...@mostafa.info> wrote:

> Few while ago I tried upgrading to unstable and I could update all my
> packages successfully. Now I'm going to use stable version. I am
> following only stable repository and each time I hit `apt-get
> dist-upgrade` it successfully upgrades few packages. 
> 
> Is this a safe way to stick with stable?
> 

Yes. I am assuming you made a new stable installation, you have not
just changed the repository from unstable to stable. That will most
definitely not work.

Are you asking why only a few packages are upgraded, compared to
unstable?

Stable should not need many upgrades. In unstable, package versions are
frequently upgraded, most of the software has bugs, and sometimes the
entire architecture of a linked group of programs is changed.

In general, software versions in stable do not change, except for web
browsers and anti-virus software. Security bugs are fixed, though not
normally functional bugs. Debian stable is often used in servers, where
a change of behaviour due to a bug being fixed may cause worse problems
than the bug did. 

The whole purpose of stable is to be an unchanging platform, as far as
is possible. That means that the software versions are largely frozen
months before release, and will never change. If you need fairly
up-to-date software all the time, then stable is not the correct
distribution to use, either testing or unstable are more appropriate.

-- 
Joe

Re: What happen if I start following stable after upgrading to unstable?

[Mostafa Shahverdy]

Any kind of help is already appreciated :)

On Sat, Oct 07, 2017 at 07:55:21PM +0330, Mostafa Shahverdy wrote:
> Few while ago I tried upgrading to unstable and I could update all my packages
> successfully. Now I'm going to use stable version. I am following only
> stable repository and each time I hit `apt-get dist-upgrade` it
> successfully upgrades few packages. 
> 
> Is this a safe way to stick with stable?
> 
> -- 
> Regards,
> Mostafa Shahverdy <http://www.mostafa.info/pgp>



-- 
Regards,
Mostafa Shahverdy <http://www.mostafa.info/pgp>


signature.asc
Description: PGP signature

What happen if I start following stable after upgrading to unstable?

[Mostafa Shahverdy]

Few while ago I tried upgrading to unstable and I could update all my packages
successfully. Now I'm going to use stable version. I am following only
stable repository and each time I hit `apt-get dist-upgrade` it
successfully upgrades few packages. 

Is this a safe way to stick with stable?

-- 
Regards,
Mostafa Shahverdy <http://www.mostafa.info/pgp>


signature.asc
Description: PGP signature

Re: upgrading to unstable

[Frank Copeland]

On 19 May 05 15:04:10 GMT, Alberto Bert [EMAIL PROTECTED] wrote:

 after reading the FAQ at:

 http://www.people.cornell.edu/pages/kk288/debian_choosing_distribution.html

 I'm upgrading from sarge to unstable...

After reading this I'm not convinced to do the same. The main argument
for preferring unstable over testing appears to be that when testing
breaks, it can take longer to fix than unstable. While this is true,
it's not a showstopper because you can always install the fixed
packages from unstable and wait for testing to catch up.

Testing is almost-but-not-quite bleeding-edge and that's good enough
for me.

 I'm pretty scared, so it would be nice to have some help from the
 list...

If you are scared, then don't do it...

 In doing it I'm using aptitude. I just saied it to U all the Upgrade
 packages, then I'm upgrading (it's downloading...)

... but it's a bit late now ;-)

 Is there anything else I should do?

Give yourself plenty of time to sort out any issues that crop up
unexpectedly. I doubt you will have many, the difference between
testing and unstable really isn't that great.

The real challenge is upgrading stable to testing/unstable. I've done
this a few times now and I always do it in stages, especially on
servers. First upgrade the tools used to perform the upgrade, ie -
apt-* and dpkg. Then upgrade each major service (web server,
mail-transport-agent, etc) individually. Don't forget the kernel; going
from 2.4.* to 2.6.* has some major implications especially for a
desktop. Once everything important is working properly, do a final
dist-upgrade to finish the job.

*Always* pay special attention to the feedback from the package
management system. It's a good idea to run (the equivalent of) 
'apt-get -us dist-upgrade' before each major step just to see what it
proposes to do next.

-- 
Frank Copeland
Home Page: URL:http://thingy.apana.org.au/~fjc/ 
Not the Scientology Home Page: URL:http://xenu.apana.org.au/ntshp/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: upgrading to unstable

[Rogério Brito]

On May 20 2005, Frank Copeland wrote:
 Testing is almost-but-not-quite bleeding-edge and that's good enough for
 me.

Furthermore, more people should be using testing at any time to see if it
has any bugs that would prevent it from being released. Remember: testing
was/is meant to be next to a releaseable state at any time. In other words,
it is called testing for a reason.

And, besides that, it is rock-solid, especially near release dates, when it
gets the attention of developers.

Cheers,

-- 
Rogério Brito : [EMAIL PROTECTED] : http://www.ime.usp.br/~rbrito
Homepage of the algorithms package : http://algorithms.berlios.de
Homepage on freshmeat:  http://freshmeat.net/projects/algorithms/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

upgrading to unstable

[Alberto Bert]

Hi,

after reading the FAQ at:

http://www.people.cornell.edu/pages/kk288/debian_choosing_distribution.html

I'm upgrading from sarge to unstable...

I'm pretty scared, so it would be nice to have some help from the
list...

In doing it I'm using aptitude. I just saied it to U all the Upgrade
packages, then I'm upgrading (it's downloading...)

Is there anything else I should do?

Thanks,
Alberto


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: upgrading to unstable

[Ernst Doubt]

Alberto Bert wrote:
Hi,
after reading the FAQ at:
http://www.people.cornell.edu/pages/kk288/debian_choosing_distribution.html
I'm upgrading from sarge to unstable...
I'm pretty scared, so it would be nice to have some help from the
list...
In doing it I'm using aptitude. I just saied it to U all the Upgrade
packages, then I'm upgrading (it's downloading...)
Is there anything else I should do?

I'd have installed apt-listbugs prior, but it's not a guarantee against 
breakage (though it does allow you to possibly prevent some buggy 
packages from being installed).

good luck,
~c

Thanks,
Alberto


--
Be not afraid of your own subjectivity, just streamline its flow ;)
- Youlian Troyanov
gpg key fingerprint = 4C29 C87D BF94 26D8 94D4  94E1 67CD F26D 0A66 3D1A
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: upgrading to unstable

[Frank Van Damme]

On Thu, 19 May 2005 11:16:29 -0400
Ernst Doubt [EMAIL PROTECTED] wrote:

 I'd have installed apt-listbugs prior, but it's not a guarantee against 
 breakage (though it does allow you to possibly prevent some buggy 
 packages from being installed).

Apt-listbugs still gives me errors even with packages from sarge. So
prepare for a LOT of error reports if you upgrade to sid!

-- 
Frank Van Damme


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: upgrading to unstable

[Colin]

Alberto Bert wrote:
 Hi,
 
 after reading the FAQ at:
 
 http://www.people.cornell.edu/pages/kk288/debian_choosing_distribution.html
 
 I'm upgrading from sarge to unstable...
 
 I'm pretty scared, so it would be nice to have some help from the
 list...

If you're scared about upgrading to unstable, then I wouldn't do it.
Unstable (sid) can break unexpectedly and you'll have to manually fix it
when it does.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: upgrading to unstable

[Paul Johnson]

On Thursday May 19 2005 8:04 am, Alberto Bert wrote:
 Hi,

 after reading the FAQ at:

 http://www.people.cornell.edu/pages/kk288/debian_choosing_distribut
ion.html

 I'm upgrading from sarge to unstable...

 I'm pretty scared, so it would be nice to have some help from the
 list...

Right now seems to be a good time to jump in, nothing really broken at 
the moment based on what I use.

 In doing it I'm using aptitude. I just saied it to U all the
 Upgrade packages, then I'm upgrading (it's downloading...)

u is update the list, once you do that, make sure it's not complaining 
about broken packages and make sure it's not doing anything too 
strange.  Then let it rip with g.


-- 
Paul Johnson
Email and Instant Messenger (Jabber): [EMAIL PROTECTED]
http://ursine.ca/~baloo/


pgpbSQg65HuRB.pgp
Description: PGP signature

problem with foomatic-db upgrading to unstable

[Sebastian Canagaratna]

Hi:

 I burned two dvd's  this week of the unstable distribution. I was
 upgrading from testing but ran into trouble with foomati-db,
 foomatic-bin and similar packages because of some dependency problem. 
 I see from google that last year people had had trouble with this, but
 my office machine works OK ( in was installed last year end of
 December).  I don't seem to be able to run apt-get dselect-upgrade,
 and twenty odd programs have not been upgraded. HOw does one twll
 apt-get to forget the foomatic and upgrade as much as it can? I have
 tried everything as I know: apt-get -f install, apt-get -f dist-upgrade
 etc, but nothing seems to worK.  How does one proceed? I have not seen
 any answer with  google.


 Thanks.

 Sebastian


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: pinning: Upgrading to unstable via gui, from testing.

[Colin Watson]

On Thu, Sep 25, 2003 at 04:47:40PM -0500, Mike Mestnik wrote:
 I'm using pinning and I can't find ought how to use dselect to select
 packages that should track unstable.  I would also like to select
 packages that, if able, should track testing/stable.
 
 Is there another gui that might deal better with pinning?

dselect predates pinning and doesn't do it. (Good - I'd rather it
didn't! Certainly mixing stable and unstable is strictly for the
extremely brave, and defeats the point of running stable unless you're
very careful ...)

Try aptitude, which I think handles it.

Cheers,

-- 
Colin Watson  [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

pinning: Upgrading to unstable via gui, from testing.

[Mike Mestnik]

I'm using pinning and I can't find ought how to use dselect to select
packages that should track unstable.  I would also like to select
packages that, if able, should track testing/stable.
Is there another gui that might deal better with pinning?

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

error while upgrading stable-unstable

[Attila Csosz]

Hi,

I'm trying to upgrade from stable to unstable but I've got the followin 
error message:

E: Internal Error, Could not perform immediate configuration (2) on libpam0g

How to solve this?
I've tried the apt-get -f install and the force-loopbreak option but 
nothing happened.

Thanks
Attila




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: error while upgrading stable-unstable

[David Fokkema]

On Sun, Jul 06, 2003 at 01:56:02PM +0200, Attila Csosz wrote:
 Hi,
 
 I'm trying to upgrade from stable to unstable but I've got the followin 
 error message:
 
 E: Internal Error, Could not perform immediate configuration (2) on libpam0g
 
 How to solve this?
 I've tried the apt-get -f install and the force-loopbreak option but 
 nothing happened.

This _exact_ problem has already been addressed two or three times.
Maybe more. The problem occuring while upgrading from stable to unstable
has already been addressed once. They're in the archives. Really.

1. You can try upgrading first to testing and then to unstable. It is
   reported once that this works.

2. You can search the archives and read the dozen or so suggestions to
   deal with the internal error.

HTH,

David


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: error while upgrading stable-unstable

[Chris Metzler]

On Sun, 06 Jul 2003 13:56:02 +0200
Attila Csosz [EMAIL PROTECTED] wrote:

 Hi,
 
 I'm trying to upgrade from stable to unstable but I've got the followin 
 error message:
 
 E: Internal Error, Could not perform immediate configuration (2) on
 libpam0g
 
 How to solve this?
 I've tried the apt-get -f install and the force-loopbreak option but 
 nothing happened.

You could start by doing a search on the archives of this mailing list for
all the other times this has come up in the last two weeks.  I went to

http://lists.debian.org/search.html

and searched the archives of this mailing list for the last week and found
this immediately:

http://lists.debian.org/debian-user/2003/debian-user-200307/msg00588.html

You may also find this to be of use:

http://www.catb.org/~esr/faqs/smart-questions.html

-c


-- 
Chris Metzler   [EMAIL PROTECTED]
(remove snip-me. to email)

As a child I understood how to give; I have forgotten this grace since I
have become civilized. - Chief Luther Standing Bear


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Upgrading from unstable to stable

[JZidar]

Hello! I'm running Woody Unstable/TEsting and I would like to upgrade to
stable. Do I haave to modify my sources.list file and run apt-get upgrade
and the then apt-get install or there more things that have to be dealt
with?

Thanx guys.

JZidar

There is no spoon.

Fill with mingled cream and amber,
I will drain that glass again.
Such hilarious visions clamber
Through the chambers of my brain.
Quaintest thoughts--queerest fancies,
Come to life and fade away:
I am drinking ale today.
(Edgar Allan Poe)



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Upgrading from unstable to stable

[Nicolas Kratz]

On Mon, Jun 09, 2003 at 11:25:22AM +0200, JZidar wrote:
 Hello! I'm running Woody Unstable/TEsting and I would like to upgrade to
 stable. Do I haave to modify my sources.list file and run apt-get upgrade
 and the then apt-get install or there more things that have to be dealt
 with?

There is no such thing as Woody Unstable/Testing. Woody is an alias
for stable. Furthermore, going from unstable to stable is a DOWNgrade.

Read http://www.debian.org/releases/ for clarification.

HTH,
Nick

-- 
x--x
| The greatest woes of the programmer? |
|  Serotonine deficiency, caffeine deprivation and the |
| unbearable roar of the birds.|
|--|
| Nicolas Kratz [EMAIL PROTECTED] [EMAIL PROTECTED] |
x--x


pgp0.pgp
Description: PGP signature

RE: Upgrading from unstable to stable

[Willem-Jan Meijer]

JZidar mailto:[EMAIL PROTECTED] schreef op maandag 9 juni 2003 11:25:

 Hello! I'm running Woody Unstable/TEsting and I would like to upgrade
 to stable. Do I haave to modify my sources.list file and run apt-get
 upgrade and the then apt-get install or there more things that have
 to be dealt with?   
 
 Thanx guys.
 
 JZidar
 
 There is no spoon.
 
 Fill with mingled cream and amber,
 I will drain that glass again.
 Such hilarious visions clamber
 Through the chambers of my brain.
 Quaintest thoughts--queerest fancies,
 Come to life and fade away:
 I am drinking ale today.
 (Edgar Allan Poe)

If you want back to stable, you are actuallly downgrading your system, you 
are going back to older bug-free packages. I tried it too 3 months ago but 
I couldn't do the trick.

My sources.lists:

deb http://http.us.debian.org/debian stable main contrib non-free
deb http://security.debian.org/ stable/updates main contrib non-free

I don't know your experience with debian, my experience isn't very
big ;) but you can google around for this or search the mailing list
archive.

Good Luck,

-WJ

Windows: Where do you want to go today?
MacOS:   Where do you want to be tomorrow?
Linux:   Are you coming or what?



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Upgrading from unstable to stable

[Colin Watson]

On Mon, Jun 09, 2003 at 12:27:40PM +0200, Nicolas Kratz wrote:
 On Mon, Jun 09, 2003 at 11:25:22AM +0200, JZidar wrote:
  Hello! I'm running Woody Unstable/TEsting and I would like to upgrade to
  stable. Do I haave to modify my sources.list file and run apt-get upgrade
  and the then apt-get install or there more things that have to be dealt
  with?
 
 There is no such thing as Woody Unstable/Testing.

But there was before woody became stable, which I think is what JZidar
is talking about.

-- 
Colin Watson  [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Upgrading from unstable to stable

[Colin Watson]

On Mon, Jun 09, 2003 at 11:25:22AM +0200, JZidar wrote:
 Hello! I'm running Woody Unstable/TEsting and I would like to upgrade
 to stable. Do I haave to modify my sources.list file and run apt-get
 upgrade and the then apt-get install or there more things that have to
 be dealt with?

That should be fine depending on how far pre-woody your installation is,
except that you probably mean:

  apt-get update (or better 'dselect update' so that dpkg's available
  file is up to date)
  apt-get dist-upgrade

-- 
Colin Watson  [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: upgrading to unstable KDE

[Paul Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, Apr 03, 2003 at 11:17:28PM +0800, Arne Goetje wrote:
 Ok, now it works. I upgraded all dependency packages for kmail to the latest 
 versions, although kmail doesn't 'require' it. I don't know which one of 
 them did the trick, but now it works.

Are you using apt pinning?  If so, this is a prime example of why the
developers tell you *not* to do this unless you have a fairly firm
understanding of what's going on and are willing to track at least the
announcements for all versions involved.  Really, pinning was only
intended for advanced users running stable that needed a couple
packages from newer versions and thus is not necissarily a reliable
substitute tracking just one version.

- -- 
 .''`. Baloo Ursidae [EMAIL PROTECTED]
: :'  :proud Debian admin and user
`. `'`
  `-  Debian - when you have better things to do than fix a system
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+jVf9J5vLSqVpK2kRAqmgAJ9Fon+5ZvqGZ1wTWWxtBdbPUpICWQCgkk03
VPdigN1zrEQoee6FIdzzYBM=
=Wjlu
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: upgrading to unstable KDE

[Arne Goetje]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 Are you using apt pinning?  If so, this is a prime example of why the
 developers tell you *not* to do this unless you have a fairly firm
 understanding of what's going on and are willing to track at least the
 announcements for all versions involved.  Really, pinning was only
 intended for advanced users running stable that needed a couple
 packages from newer versions and thus is not necissarily a reliable
 substitute tracking just one version.

yes, I am using apt pinning. And I think I am an experienced user...
I also run stable as main source and have testing and unstable pinned. The 
only applications that are from unstable are KDE and the dependencies.
I had it too often that a package from unstable was broken and left my 
system unusable. That's why I use stable as main source and upgrade single 
packages when I need them.
In aptitude this is relative easy. I think this issue with kmail happened 
because I had the packages from the original kde mirrors installed and 
switched to the unstable packages now, because I needed some unstable 
versions of some gnome software that conflicted with the kde packages. this 
was because the kde packages from the kde site use libfam0 and libqt3-mt. 
These conflict with gnome2 in unstable.

Cheers
Arne
- -- 
Arne Goetje [EMAIL PROTECTED] 
(Spam catcher.  Address might change in future!)
PGP/GnuPG key: 1024D/685D1E8C
Fingerprint: 2056 F6B7 DEA8 B478 311F  1C34 6E9F D06E 685D 1E8C
Key available at wwwkeys.pgp.net.   Encrypted e-mail preferred.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+jWoSbp/QbmhdHowRAkaOAKDFQ16jLCWEhkHgS+5iV4IL8Ex3JACaAv8Q
UWgXduAnSavLNXDM1bEU4MY=
=4NcO
-END PGP SIGNATURE-


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: upgrading to unstable KDE

[ronin2]

Great, thanks.

I read the thread.

Kevin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: upgrading to unstable KDE

[Arne Goetje]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thursday 03 April 2003 11:47, Leo Spalteholz wrote:
 On April 2, 2003 03:33 am, Paul Johnson wrote:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1
 
  On Wed, Apr 02, 2003 at 07:06:58PM +0800, Arne Goetje wrote:
   when did you upgrade? I tried it on saturday with the deb from
   ftp.debian.org. 3.1.1-1 AFAIK...
 
  That's the version installed here...4:3.1.1-1...

 Same here.  Kmail has been working beautifully here ever since it got
 into sid.  And just as well before from the maintainer's site before
 it got into sid..

Ok, now it works. I upgraded all dependency packages for kmail to the latest 
versions, although kmail doesn't 'require' it. I don't know which one of 
them did the trick, but now it works.

Cheers
Arne
- -- 
Arne Goetje [EMAIL PROTECTED] 
(Spam catcher.  Address might change in future!)
PGP/GnuPG key: 1024D/685D1E8C
Fingerprint: 2056 F6B7 DEA8 B478 311F  1C34 6E9F D06E 685D 1E8C
Key available at wwwkeys.pgp.net.   Encrypted e-mail preferred.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE+jFCQbp/QbmhdHowRAp3WAJ9VN/ZkkcjFHk5a9vaLJ1UjRG7ZkACg4oz4
Mo3fuPGvXxi+Nbv2j5iRqh0=
=ORxZ
-END PGP SIGNATURE-


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: upgrading to unstable KDE

[Levi Waldron]

On April 1, 2003 06:11 pm, Noah Meyerhans wrote:
 You'll probably have much better luck using the unofficial native woody
 packages of KDE 3.1.  See http://www.apt-get.org/, which will refer you
 to:
 deb http://download.us.kde.org/pub/kde/stable/latest/Debian/ woody main

Thanks everyone for the apt-pinning warnings, and for this alternate tip.  I 
installed KDE 3.1 from this source, with just some minor setbacks.  gdm 
didn't seem to recognize kde3 upon logging out of kde after the reinstall, 
but setting kdm as the default display manager and rebooting got me in.

-- 
We don't see the world as it is, we see the world as we are.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: upgrading to unstable KDE

[Paul Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, Apr 01, 2003 at 05:20:44PM -0500, Levi Waldron wrote:
 I'm running Woody right now, but am tempted to dselect-upgrade KDE to the 
 3.10 in unstable (because of the improvements to kmail).  Any thoughts 
 on the potential pain/painlessness of this upgrade, before I try it?  If 
 there's a fair chance of having to spend a lot of time fixing a broken 
 system, I'll just wait for it to arrive in testing.

I think it's linked to a newer libc than is in woody.  Upgrading KDE
would result in upgrading libc, which results in upgrading...hmm,
could someone tell me what isn't dependant on libc again?

- -- 
 .''`. Baloo Ursidae [EMAIL PROTECTED]
: :'  :proud Debian admin and user
`. `'`
  `-  Debian - when you have better things to do than fix a system
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+iqP3J5vLSqVpK2kRAjklAJ41JIqttS+9C2bKR61+ofwZE26yQgCfdwVt
uuOae6LXMO5K4QGHFeVwvDI=
=O0rE
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: upgrading to unstable KDE

[Colin Watson]

On Wed, Apr 02, 2003 at 12:48:55AM -0800, Paul Johnson wrote:
 On Tue, Apr 01, 2003 at 05:20:44PM -0500, Levi Waldron wrote:
  I'm running Woody right now, but am tempted to dselect-upgrade KDE
  to the 3.10 in unstable (because of the improvements to kmail).  Any
  thoughts on the potential pain/painlessness of this upgrade, before
  I try it?  If there's a fair chance of having to spend a lot of time
  fixing a broken system, I'll just wait for it to arrive in testing.
 
 I think it's linked to a newer libc than is in woody.  Upgrading KDE
 would result in upgrading libc, which results in upgrading...hmm,
 could someone tell me what isn't dependant on libc again?

Nothing much apart from documentation, but you've got it the wrong way
round; the only thing that libc6 depends on is libdb1-compat, plus it
conflicts with earlier versions of some packages. Upgrading libc6
doesn't require you to upgrade everything that depends on it.

Cheers,

-- 
Colin Watson  [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: upgrading to unstable KDE

[Rob VanFleet]

On Tue, Apr 01, 2003 at 05:20:44PM -0500, Levi Waldron wrote:
 I'm running Woody right now, but am tempted to dselect-upgrade KDE to the 
 3.10 in unstable (because of the improvements to kmail).  Any thoughts 
 on the potential pain/painlessness of this upgrade, before I try it?  If 
 there's a fair chance of having to spend a lot of time fixing a broken 
 system, I'll just wait for it to arrive in testing.

I ran a dist-upgrade to unstable a couple of weeks ago and it went
pretty smoothly, but YMMV.  I've found that you stand less of a chance
of things going wrong with a small number of packages to start with and
then installing them once you're fully in unstable.  My starting stable
setup consisted of base, C/C++ dev, X and blackbox.  I usually take the
machine from stable to testing, then testing to unstable.  Last I
checked some KDE packages in unstable were uninstallable, but by
grabbing individual packages I got everything I needed.  In other words,
trying to install the 'kde' metapackage failed, but installing kdebase,
the browing throug the results of 'apt-cache search kde | less' I managed
to get everything else.  KDE3.1 seems to be in a pretty nice working
state in unstable at the moment.

That being said, you'll probably run into a few false starts during the
dist-upgrade - few conflicting packages that need to be tweaked manually
or temporarily removed with dpkg (sometimes using some sort of --force).
Once you get the hang of it, unstable transitions aren't so bad, but
having a small amont of packages to upgrade as well as some experience
massaging the packages to get out of dist-upgrade problems (most of
the time a --fix-missing will do the trick) helps.

So if I haven't given you enough mixed messages, just do it when you
have some time on your hands, and if your system is at all mission
critical - don't do it at all.

Rob


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: upgrading to unstable KDE

[Arne Goetje]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday 02 April 2003 16:48, Paul Johnson wrote:
 On Tue, Apr 01, 2003 at 05:20:44PM -0500, Levi Waldron wrote:
  I'm running Woody right now, but am tempted to dselect-upgrade KDE to
  the 3.10 in unstable (because of the improvements to kmail).  Any
  thoughts on the potential pain/painlessness of this upgrade, before I
  try it?  If there's a fair chance of having to spend a lot of time
  fixing a broken system, I'll just wait for it to arrive in testing.

 I think it's linked to a newer libc than is in woody.  Upgrading KDE
 would result in upgrading libc, which results in upgrading...hmm,
 could someone tell me what isn't dependant on libc again?

The libc is not that problem. The major problem is, that kmail in sid is 
unusable in the moment. However the sid version of KDE3.1.1 is compiled 
with two different libraries than the original KDE packages. This is 
because the original KDE packages conflict with Gnome2 in sid. So, if you 
don't use any Gnome2 apps, use the original packages from the KDE mirror 
instead of the sid version. If you use any Gnome2 packages, wait until the 
package maintainer has fixed the bug in kmail.

Cheers
Arne

- -- 
Arne Goetje [EMAIL PROTECTED] 
(Spam catcher.  Address might change in future!)
PGP/GnuPG key: 1024D/685D1E8C
Fingerprint: 2056 F6B7 DEA8 B478 311F  1C34 6E9F D06E 685D 1E8C
Key available at wwwkeys.pgp.net.   Encrypted e-mail preferred.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+iq3rbp/QbmhdHowRAr28AKCjBvTNWlPDkP0NsEx/OdfJGQc8/ACffYPJ
p0uKQm5zOIn1BawK7r3ACvs=
=EKw6
-END PGP SIGNATURE-


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: upgrading to unstable KDE

[Bob Proulx]

Paul Johnson wrote:
 I think it's linked to a newer libc than is in woody.  Upgrading KDE
 would result in upgrading libc, which results in upgrading...hmm,
 could someone tell me what isn't dependant on libc again?

First off you need to have graphviz from unstable, backported is fine
and works for me, the woody version has segfault problems.  Then the
following is a really cool feature of apt-cache.  Insert your favorite
program in the place of the libc6 example.

  dotty (apt-cache dotty libc6)

While reading the man page for apt-cache I found it produces dotty
output.  It is a graphical dependency diagram of what packages depend
upon what other packages.  Way cool.

Bob


pgp0.pgp
Description: PGP signature

Re: upgrading to unstable KDE

[Paul Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wed, Apr 02, 2003 at 05:31:23PM +0800, Arne Goetje wrote:
 The libc is not that problem. The major problem is, that kmail in sid is 
 unusable in the moment. 

Really?  I'm pretty sure that was recently fixed.  I just checked,
kmail runs on my box...I'm running sid, and the kmail and kde
installed are from sid...

- -- 
 .''`. Baloo Ursidae [EMAIL PROTECTED]
: :'  :proud Debian admin and user
`. `'`
  `-  Debian - when you have better things to do than fix a system
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+irwyJ5vLSqVpK2kRAoRKAKCEP/z6kRCK2AQMzk8vCpVmTFjwcgCfYTBa
qootz5BOoH62p2tl6sbZPZk=
=63Mw
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: upgrading to unstable KDE

[Paul Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wed, Apr 02, 2003 at 03:12:32AM -0600,  Rob VanFleet wrote:
 That being said, you'll probably run into a few false starts during the
 dist-upgrade - few conflicting packages that need to be tweaked manually
 or temporarily removed with dpkg (sometimes using some sort of --force).
 Once you get the hang of it, unstable transitions aren't so bad, but
 having a small amont of packages to upgrade as well as some experience
 massaging the packages to get out of dist-upgrade problems (most of
 the time a --fix-missing will do the trick) helps.

I'd also go re-read the long The Myth of Apt Pinning thread that ran
a while back.  One of the DDs speaks out against pinning, essentially
considering it harmful.  Consider yourself warned if you *really* want
to run a frankendistro.

- -- 
 .''`. Baloo Ursidae [EMAIL PROTECTED]
: :'  :proud Debian admin and user
`. `'`
  `-  Debian - when you have better things to do than fix a system
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+ir1PJ5vLSqVpK2kRAlm2AKCe190Sw21TKz6iIhS6EqDI+VlKmACdFLoL
TrR/zTXbh5EBJCj6nUkFo+s=
=60/g
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: upgrading to unstable KDE

[Arne Goetje]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday 02 April 2003 18:32, Paul Johnson wrote:
 On Wed, Apr 02, 2003 at 05:31:23PM +0800, Arne Goetje wrote:
  The libc is not that problem. The major problem is, that kmail in sid
  is unusable in the moment.

 Really?  I'm pretty sure that was recently fixed.  I just checked,
 kmail runs on my box...I'm running sid, and the kmail and kde
 installed are from sid...

when did you upgrade? I tried it on saturday with the deb from 
ftp.debian.org. 3.1.1-1 AFAIK...
If you have already a newer version running I'll try again.

Cheers
Arne

- -- 
Arne Goetje [EMAIL PROTECTED] 
(Spam catcher.  Address might change in future!)
PGP/GnuPG key: 1024D/685D1E8C
Fingerprint: 2056 F6B7 DEA8 B478 311F  1C34 6E9F D06E 685D 1E8C
Key available at wwwkeys.pgp.net.   Encrypted e-mail preferred.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+isRSbp/QbmhdHowRApBMAKCuuOe8R36oKCjLQSO0h8Njj8ER9QCg2iw8
phT+oFvMBG0WEbZLzswUaV0=
=jYt4
-END PGP SIGNATURE-


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: upgrading to unstable KDE

[Paul Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wed, Apr 02, 2003 at 07:06:58PM +0800, Arne Goetje wrote:
 when did you upgrade? I tried it on saturday with the deb from 
 ftp.debian.org. 3.1.1-1 AFAIK...

That's the version installed here...4:3.1.1-1...

- -- 
 .''`. Baloo Ursidae [EMAIL PROTECTED]
: :'  :proud Debian admin and user
`. `'`
  `-  Debian - when you have better things to do than fix a system
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+isqAJ5vLSqVpK2kRAjQZAJwJMkgGpSVVtU4/OK8q3EjPvCdTtACgoT5D
SspaOISrW5l2mtUmDhFOraQ=
=2Wy2
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: upgrading to unstable KDE

[ronin2]

On Wed, 2 Apr 2003 02:37:03 -0800
Paul Johnson [EMAIL PROTECTED] wrote:

 I'd also go re-read the long The Myth of Apt Pinning thread that ran
 a while back.  One of the DDs speaks out against pinning, essentially
 considering it harmful.  Consider yourself warned if you *really* want
 to run a frankendistro.

Was that on this list or another.

I tried searching the archives back to last April and didn't see it.

Kevin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: upgrading to unstable KDE

[Paul Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wed, Apr 02, 2003 at 09:14:26AM -0500, [EMAIL PROTECTED] wrote:
 Was that on this list or another.

I'm pretty sure it was.  I remember having to use thread-delete on it
after I got tired of it...I recall it being a rather long thread.

- -- 
 .''`. Baloo Ursidae [EMAIL PROTECTED]
: :'  :proud Debian admin and user
`. `'`
  `-  Debian - when you have better things to do than fix a system
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+iv2GJ5vLSqVpK2kRAqDYAJ9+zjcvIdyiOdYVcUxwDoOYt6tCfgCgzcwD
RxRLEHR/PXV98t8+Odsi4ug=
=OmaQ
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

RE: upgrading to unstable KDE

[Irish, Jon D BAE SYSTEMS]

Levi,
I've been using it for 2 weeks now without any issues whatsoever.

Jon

-Original Message-
From: Levi Waldron [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 01, 2003 4:21 PM
To: [EMAIL PROTECTED]
Subject: upgrading to unstable KDE


I'm running Woody right now, but am tempted to dselect-upgrade KDE to the 
3.10 in unstable (because of the improvements to kmail).  Any thoughts 
on the potential pain/painlessness of this upgrade, before I try it?  If 
there's a fair chance of having to spend a lot of time fixing a broken 
system, I'll just wait for it to arrive in testing.

Thanks,
Levi


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: upgrading to unstable KDE

[Brian Nelson]

[EMAIL PROTECTED] writes:

 On Wed, 2 Apr 2003 02:37:03 -0800
 Paul Johnson [EMAIL PROTECTED] wrote:

 I'd also go re-read the long The Myth of Apt Pinning thread that ran
 a while back.  One of the DDs speaks out against pinning, essentially
 considering it harmful.  Consider yourself warned if you *really* want
 to run a frankendistro.

 Was that on this list or another.

http://lists.debian.org/debian-devel/2003/debian-devel-200301/msg01644.html

-- 
I don't know half of you half as well as I should like; and I like less
than half of you half as well as you deserve.


pgp0.pgp
Description: PGP signature

Re: upgrading to unstable KDE

[Rob French]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Any thought of using the KDE3.1 for woody from KDE?

apt-get sources.list line:

deb http://download.us.kde.org/pub/kde/stable/latest/Debian/ woody main
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+i3fPajFD3wrWXs8RAvWVAJ4ykD/z0GNN30wVNsyDZ6cdLfi4/ACfTgGL
xVKnTrJxmqb4k8f2imvWNo4=
=7NJo
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: upgrading to unstable KDE

[Leo Spalteholz]

On April 2, 2003 03:33 am, Paul Johnson wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On Wed, Apr 02, 2003 at 07:06:58PM +0800, Arne Goetje wrote:
  when did you upgrade? I tried it on saturday with the deb from
  ftp.debian.org. 3.1.1-1 AFAIK...

 That's the version installed here...4:3.1.1-1...

Same here.  Kmail has been working beautifully here ever since it got 
into sid.  And just as well before from the maintainer's site before 
it got into sid..  

leo


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: upgrading to unstable KDE

[Paul Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wed, Apr 02, 2003 at 08:49:37AM -0800, Brian Nelson wrote:
 http://lists.debian.org/debian-devel/2003/debian-devel-200301/msg01644.html

That's the one.  I remember it spilling over into debian-user, though
oddly enough it doesn't show that in the archives.

- -- 
 .''`. Baloo Ursidae [EMAIL PROTECTED]
: :'  :proud Debian admin and user
`. `'`
  `-  Debian - when you have better things to do than fix a system
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+i9dMJ5vLSqVpK2kRAgDLAJoDimdU4BwmhXPL4KSWfRa7rx3rfACgwls8
ZvuIZToz4Zmr2V3yFSeX9DY=
=Esgt
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

upgrading to unstable KDE

[Levi Waldron]

I'm running Woody right now, but am tempted to dselect-upgrade KDE to the 
3.10 in unstable (because of the improvements to kmail).  Any thoughts 
on the potential pain/painlessness of this upgrade, before I try it?  If 
there's a fair chance of having to spend a lot of time fixing a broken 
system, I'll just wait for it to arrive in testing.

Thanks,
Levi


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: upgrading to unstable KDE

[Noah Meyerhans]

On Tue, Apr 01, 2003 at 05:20:44PM -0500, Levi Waldron wrote:
 I'm running Woody right now, but am tempted to dselect-upgrade KDE to the 
 3.10 in unstable (because of the improvements to kmail).  Any thoughts 
 on the potential pain/painlessness of this upgrade, before I try it?  If 
 there's a fair chance of having to spend a lot of time fixing a broken 
 system, I'll just wait for it to arrive in testing.

You'll probably have much better luck using the unofficial native woody
packages of KDE 3.1.  See http://www.apt-get.org/, which will refer you
to:
deb http://download.us.kde.org/pub/kde/stable/latest/Debian/ woody main

noah

-- 
 ___
| Web: http://web.morgul.net/~frodo/
| PGP Public Key: http://web.morgul.net/~frodo/mail.html 


pgp0.pgp
Description: PGP signature

Re: 404 Not Found when upgrading to unstable - next morning

[Eric Smith]

According to Andras BALI on Mon, Nov 12, 2001 at 11:13:29PM +0100:
 On Mon, Nov 12, 2001 at 10:43:34PM +0100, Eric Smith wrote:
 
  Err http://ftp.nl.debian.org unstable/main binutils 2.11.92.0.10-3
404 Not Found
 
 The reason is:
 
 $ ncftpls ftp://ftp.nl.debian.org/debian/ | head -1
 Archive-Update-in-Progress-open.hands.com
 $

Its still marked this way.

 
 The archive is just being updated, therefore it may happen that the
 Packages file is new, but the new files it refers to are not yet
 downloaded. Check back later.
 

This morning things are _slightly_ better viz.

Should I force it to continue - how?

apt-get --fix-missing  dist-upgrade 
Reading Package Lists... 0%Reading Package Lists... 100%Reading Package 
Lists... Done
Building Dependency Tree... 0%Building Dependency Tree... 0%Building Dependency 
Tree... 3%Building Dependency Tree... 50%Building Dependency Tree... 
50%Building Dependency Tree... 59%Building Dependency Tree... 72%Building 
Dependency Tree... 86%Building Dependency Tree... 98%Building Dependency 
Tree... Done
Calculating Upgrade... Done
The following packages will be REMOVED:
  python-base 
The following NEW packages will be installed:
  autoconf2.13 autotools-dev bonobo console-common debconf-utils defoma 
dict-gcide gcc-3.0-base gnome-pim groff-base gs gs-common
  gsfonts host html2text ifupdown ipchains ipppd isdnlog isdnlog-data 
isdnutils-base isdnutils-xtools isdnvboxclient
  isdnvboxserver klogd libbonobo2 libbz2-1.0 libcap1 libcupsys2 libdb3 libdns4 
libefs1 libesmtp5 libexpat1 libgal15 libgal17
  libgc6 libgcc1 libgdk-pixbuf-gnome2 libgdk-pixbuf2 libgimpprint1 libgmp3 
libgnomeprint-bin libgnomeprint-data libgnomeprint15
  libgtkhtml18 libisc3 liblcms libldap2 libltdl3 liblwres1 libmagick5 
libmysqlclient10 libnetpbm9 liboaf0 libpcre3 libpspell4
  librep9 libsasl7 libscrollkeeper0 libssl0.9.6 libstdc++3 libttf2 libungif4g 
libwmf0.2-1 libxml2 mysql-common net-tools
  netkit-inetd netkit-ping oaf perl-doc portmap powertweak-extra powertweak-gtk 
powertweak-text powertweakd python python2.1
  scrollkeeper tcl8.3 xutils 
The following packages have been kept back
  w3m 
302 packages upgraded, 82 newly installed, 1 to remove and 1  not upgraded.
Need to get 8927kB/188MB of archives. After unpacking 143MB will be used.
Do you want to continue? [Y/n] 

Do you want to continue? [Y/n]
Err http://ftp.nl.debian.org unstable/main python2.1 2.1.1-4
  404 Not Found [IP: 195.129.111.9 80]
Err http://ftp.nl.debian.org unstable/main python 2.1.1-4
  404 Not Found [IP: 195.129.111.9 80]
Get:1 http://ftp.nl.debian.org unstable/main libfreetype6 2.0.5-2 [182kB]
Get:2 http://ftp.nl.debian.org unstable/main libgnomeprint-bin 0.32-1 [20.6kB]
Get:3 http://ftp.nl.debian.org unstable/main libgnomeprint-data 0.32-1 [201kB]
Get:4 http://ftp.nl.debian.org unstable/main libgnomeprint15 0.32-1 [207kB]
Get:5 http://ftp.nl.debian.org unstable/main binutils 2.11.92.0.10-3 [1278kB]
Err http://ftp.nl.debian.org unstable/main procmail 3.21.2001.3.23pre-1
  404 Not Found [IP: 195.129.111.9 80]
Err http://ftp.nl.debian.org unstable/main mysql-common 3.23.43-4
  404 Not Found [IP: 195.129.111.9 80]
Err http://ftp.nl.debian.org unstable/main libmysqlclient10 3.23.43-4
  404 Not Found [IP: 195.129.111.9 80]
Get:6 http://ftp.nl.debian.org unstable/main dhcp 2.0pl5-6.2 [202kB]
Err http://ftp.nl.debian.org unstable/main libwine 0.0.20011108-2
  404 Not Found [IP: 195.129.111.9 80]
Err http://ftp.nl.debian.org unstable/main wine-doc 0.0.20011108-2
  404 Not Found [IP: 195.129.111.9 80]
Fetched 2091kB in 21s (99.5kB/s)
Failed to fetch 
http://ftp.nl.debian.org/debian/pool/main/p/python2.1/python2.1_2.1.1-4_i386.deb
  404 Not Found [IP: 195.129.111.9 80]
Failed to fetch 
http://ftp.nl.debian.org/debian/pool/main/p/python2.1/python_2.1.1-4_all.deb  
404 Not Found [IP: 195.129.111.9 80]
Failed to fetch 
http://ftp.nl.debian.org/debian/pool/main/p/procmail/procmail_3.21.2001.3.23pre-1_i386.deb
  404 Not Found [IP: 195.129.111.9 80]
Failed to fetch 
http://ftp.nl.debian.org/debian/pool/main/m/mysql/mysql-common_3.23.43-4_all.deb
  404 Not Found [IP: 195.129.111.9 80]
Failed to fetch 
http://ftp.nl.debian.org/debian/pool/main/m/mysql/libmysqlclient10_3.23.43-4_i386.deb
  404 Not Found [IP: 195.129.111.9 80]
Failed to fetch 
http://ftp.nl.debian.org/debian/pool/main/w/wine/libwine_0.0.20011108-2_i386.deb
  404 Not Found [IP: 195.129.111.9 80]
Failed to fetch 
http://ftp.nl.debian.org/debian/pool/main/w/wine/wine-doc_0.0.20011108-2_i386.deb
  404 Not Found [IP: 195.129.111.9
80]
Unable to correct missing packages.
E: Aborting Install.

thanx
-- 
Eric Smith

Re: 404 Not Found when upgrading to unstable - next morning

[Colin Watson]

On Tue, Nov 13, 2001 at 09:24:07AM +0100, Eric Smith wrote:
 According to Andras BALI on Mon, Nov 12, 2001 at 11:13:29PM +0100:
  The archive is just being updated, therefore it may happen that the
  Packages file is new, but the new files it refers to are not yet
  downloaded. Check back later.
 
 This morning things are _slightly_ better viz.
 
 Should I force it to continue - how?

I'd pick another mirror for now. From what you've posted, it looks like
ftp.nl is having problems. Archive maintenance happens around 20:00 GMT,
lasts for a couple of hours, and then the mirrors update; by the next
morning GMT all primary mirrors should easily have synced.

-- 
Colin Watson  [EMAIL PROTECTED]

404 Not Found when upgrading to unstable

[Eric Smith]

I am upgrading as follows:

deb http://ftp.nl.debian.org/debian/ unstable main non-free contrib
deb http://ftp.nl.debian.org/debian-non-US unstable/non-US main non-free contrib

I tried to install firstly debconf and apt-options and got this:

Err http://ftp.nl.debian.org unstable/main binutils 2.11.92.0.10-3
  404 Not Found
Get:17 http://ftp.nl.debian.org unstable/main cpp 2:2.95.4-8 [3282B]
Get:18 http://ftp.nl.debian.org unstable/main cpp-2.95 1:2.95.4-0.011006 [128kB]
Get:19 http://ftp.nl.debian.org unstable/main g++ 2:2.95.4-8 [1186B]
Get:20 http://ftp.nl.debian.org unstable/main g++-2.95 1:2.95.4-0.011006 
[1028kB]
Get:21 http://ftp.nl.debian.org unstable/main gcc 2:2.95.4-8 [3278B]
Get:22 http://ftp.nl.debian.org unstable/main gcc-2.95 1:2.95.4-0.011006 [951kB]
Get:23 http://ftp.nl.debian.org unstable/main libstdc++2.10-dev 
1:2.95.4-0.011006 [301kB]
Get:24 http://ftp.nl.debian.org unstable/main libc6-dev 2.2.4-5 [2352kB]
Get:25 http://ftp.nl.debian.org unstable/main locales 2.2.4-5 [3337kB]
Get:26 http://ftp.nl.debian.org unstable/main apt-utils 0.5.4 [173kB]
Get:27 http://ftp.nl.debian.org unstable/main libdb2-util 2:2.7.7.0-2 [107kB]
Get:28 http://ftp.nl.debian.org unstable/main libdps1 4.1.0-9 [156kB]
Err http://ftp.nl.debian.org unstable/main libfreetype6 2.0.5-2
  404 Not Found
Get:29 http://ftp.nl.debian.org unstable/main xlib6g 4.1.0-9 [47.1kB]


Then tried to install login and got this:

cherry# apt-get install login
Reading Package Lists... Done
Building Dependency Tree... Done
The following extra packages will be installed:
  binutils cpp cpp-2.95 debconf dialog g++ g++-2.95 gcc gcc-2.95 libc6 
libc6-dev libdb2 libdb2-util libdps1 libfreetype6 libgtk1.2
  libncurses5 libperl5.6 libpopt0 libstdc++2.10-dev libstdc++2.10-glibc2.2 
libxaw6 libxaw7 locales perl perl-5.005 perl-5.005-base
  perl-5.005-suid perl-base perl-modules perl-suid whiptail xbase-clients 
xfree86-common xlib6g xlibs
The following packages will be REMOVED:
  xpm4g
The following NEW packages will be installed:
  cpp-2.95 g++-2.95 gcc-2.95 libdps1 libfreetype6 libperl5.6 
libstdc++2.10-glibc2.2 libxaw6 libxaw7 perl perl-modules perl-suid
  xlibs
24 packages upgraded, 13 newly installed, 1 to remove and 299 not upgraded.
Need to get 1569kB/21.6MB of archives. After unpacking 13.2MB will be used.
Do you want to continue? [Y/n]
Get:1 http://ftp.nl.debian.org unstable/main login 2902-8 [110kB]
Err http://ftp.nl.debian.org unstable/main binutils 2.11.92.0.10-3
  404 Not Found
Err http://ftp.nl.debian.org unstable/main libfreetype6 2.0.5-2
  404 Not Found
Fetched 110kB in 2s (46.6kB/s)
Failed to fetch 
http://ftp.nl.debian.org/debian/pool/main/b/binutils/binutils_2.11.92.0.10-3_i386.deb
  404 Not Found
Failed to fetch 
http://ftp.nl.debian.org/debian/pool/main/f/freetype/libfreetype6_2.0.5-2_i386.deb
  404 Not Found
E: Unable to fetch some archives, maybe try with --fix-missing?

What solecism have I committed?

If I wanted to make a CD first to mound with apt-cdrom. what would I make
the root of the CD?

Thanx

--
Eric Smith

Re: 404 Not Found when upgrading to unstable

[Andras BALI]

On Mon, Nov 12, 2001 at 10:43:34PM +0100, Eric Smith wrote:

 Err http://ftp.nl.debian.org unstable/main binutils 2.11.92.0.10-3
   404 Not Found

The reason is:

$ ncftpls ftp://ftp.nl.debian.org/debian/ | head -1
Archive-Update-in-Progress-open.hands.com
$

The archive is just being updated, therefore it may happen that the
Packages file is new, but the new files it refers to are not yet
downloaded. Check back later.

-- 
BALI, Andra's  GPG keyID: 78560E1C
[EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]

Upgrading to unstable.. debconf probs

[William Leese]

Hi all,

I just dist-upgraded to unstable from woody and i am running into a few 
problems. The cause of these problems seem to be because i cant get debconf 
configured and set-up.

This is what i get:

dpkg: dependency problems prevent configuration of lilo:
 lilo depends on debconf (= 0.2.26); however:
  Package debconf is not configured yet.
dpkg: error processing lilo (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of console-common:
 console-common depends on debconf (= 0.5); however:
  Package debconf is not configured yet.
dpkg: error processing console-common (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of console-data:
 console-data depends on debconf (= 0.5); however:
  Package debconf is not configured yet.
 console-data depends on console-common; however:
  Package console-common is not configured yet.
dpkg: error processing console-data (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of console-tools:
 console-tools depends on console-common; however:
  Package console-common is not configured yet.
 console-tools depends on debconf (= 0.5); however:
  Package debconf is not configured yet.
dpkg: error processing console-tools (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 debconf
 lilo
 console-common
 console-data
 console-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)


So, debconf isnt configured so i get these errors. I tried dpkg --configure 
debconf but to no avail, output on that:


Setting up debconf (0.9.10) ...
dpkg: error processing debconf (--configure):
 subprocess post-installation script returned error exit status 10
Errors were encountered while processing:
 debconf


This doesnt help me much. Anyone who can help me with this?


William

Re: Upgrading to unstable.. debconf probs

[Joey Hess]

William Leese wrote:
 Setting up debconf (0.9.10) ...
 dpkg: error processing debconf (--configure):
  subprocess post-installation script returned error exit status 10
 Errors were encountered while processing:
  debconf
 
 
 This doesnt help me much. Anyone who can help me with this?

That version is out of date, upgrade to the newer version in unstable.

-- 
see shy jo

Re: Upgrading to unstable.. debconf probs [solved]

[William Leese]

On Wednesday 07 March 2001 01:22, Joey Hess wrote:
 William Leese wrote:
  Setting up debconf (0.9.10) ...
  dpkg: error processing debconf (--configure):
   subprocess post-installation script returned error exit status 10
  Errors were encountered while processing:
   debconf
  
 That version is out of date, upgrade to the newer version in unstable.

done. took awhile till the mirror i was using caughtup with ftp.debian.org

cheers,

William

Dangers in upgrading to unstable?

[Colin Cashman]

I recently installed Debian on my laptop, but some of the programs I was 
planning on using exist only in unstable (for instance,
Enlightenment 0.16.5).

What are the dangers in upgrading my system to run unstable? What issues am I 
likely to face if I do upgrade the whole thing to
unstable? Would it simply be better to download the specific unstable packages 
I want and otherwise stick with simply running
stable?

Thanks in advance!

Colin

Re: Dangers in upgrading to unstable?

[Andrei Ivanov]

I've upgraded to unstable over a period of time.libc first, then
X yesterday. Its been pretty stable so far, but you never know, you may
run into some upgrade problems with your hardware (took me a while to get
the X upgraded properly so it was usable).
Overall you should be alright, I think.
Andrei

--
First there was Explorer...
Then came Expedition.
This summer
Coming to a street near you..
Ford Exterminator.
--
Andrei Ivanov
http://arshes.dyndns.org
[EMAIL PROTECTED]
12402354
--

Re: Dangers in upgrading to unstable?

[Preben Randhol]

Colin Cashman [EMAIL PROTECTED] wrote on 01/02/2001 (16:35) :
 I recently installed Debian on my laptop, but some of the programs I
 was planning on using exist only in unstable (for instance,
 Enlightenment 0.16.5).

Are you sure you want Enlightenment? It eats a lot of memory... 
 
 What are the dangers in upgrading my system to run unstable? What
 issues am I likely to face if I do upgrade the whole thing to
 unstable? Would it simply be better to download the specific unstable
 packages I want and otherwise stick with simply running stable?

I wouldn't do it unless you really know what you are doing. Upgrade to
testing in stead of unstable, you may end up with a lot of broken
packages with unstable (not to say that this couldn't happen with
testing). Then upgrade the packages you want but which is only
in unstable, by hand.

-- 
Preben Randhol -- http://www.pvv.org/~randhol/ --
+---+ There was, I think, never any reason to  believe in any innate
| ! |  superiority of the male, except his superior muscle.
+---+  -- Bertrand Russell, Ideas That Have Harmed Mankind (1950)

Re: Dangers in upgrading to unstable?

[Colin Cashman]

 Are you sure you want Enlightenment? It eats a lot of memory...

It's the one I'm most familiar with, and my laptop has 128MB of memory + 256MB 
swap, so I'm not /overly/ concerned about the memory
usage.

However, after having read about some of the other window manglers, I'm 
probably going to put on Blackbox and maybe Sawfish and/or
IceWM to see which one I like the best.

 I wouldn't do it unless you really know what you are doing. Upgrade to
 testing in stead of unstable, you may end up with a lot of broken
 packages with unstable (not to say that this couldn't happen with
 testing). Then upgrade the packages you want but which is only
 in unstable, by hand.

I see! Thanks for the advice!

Re: Dangers in upgrading to unstable?

[David B . Harris]

To quote Colin Cashman [EMAIL PROTECTED],
# I recently installed Debian on my laptop, but some of the programs I
was planning on using exist only in unstable (for instance,
# Enlightenment 0.16.5).

If you only want a limited number of newer packages(I'd say less than 20
or 30), you can do the following to get the newer package for your
Potato system:

1) Temporarily add a deb-src line in your sources.list pointing to
unstable.
2) 'apt-get source package'
3) Go into the newly created directory, and run, as root,
'dpkg-buildpackage -uc -b'
4) In the directory above the newly created directory(probably where you
ran 'apt-get source package', you'll have new binary .deb(s), made for
Potato.
5) Comment out your unstable deb-src line in sources.list.
6) Lather, rinse, repeat :)
 
# What are the dangers in upgrading my system to run unstable? What
issues am I likely to face if I do upgrade the whole thing to
# unstable? Would it simply be better to download the specific unstable
packages I want and otherwise stick with simply running
# stable?

Now, I've been running Sid for a while now(I was using Woody before
that). I can say that my system is really quite stable. Very few things
segfault on me, everything compiles well, it's really quite a pleasure
:)

However, sometimes the upgrade itself causes problems. For instance, I
see a lot of people coming in to #debian on irc.openprojects.net with
perl installation problems - only when they're upgrade to Woody/Sid,
though. I didn't get that problem, so I don't know the solution, but
it's a good example.

Also, you should be familiar with system recovery. You should have a
rescue disk, with anything you might need to get your system up and
running. For example, a broken LILO package made it into Sid a while
back, and over-wrote some people's lilo.conf, without a backup. Some
people's systems were even unbootable after that. Not a good thing :)

And, lastly, if you're using Sid(unstable), you'll likely not get any
sympathy if a new package breaks stuff. You're using unstable Debian,
after all :) Expect hiccups and maybe even worse.

David Barclay Harris, Clan Barclay
Aut agere, aut mori. (Either action, or death.)

dictd is not restarted after upgrading from unstable?

[Shaul Karl]

It seems to me that dictd is not restarted after upgrading, although it might 
be that installing dict-web1913 for the first time is the cause. In any case, 
I am quite sure there is a problem after using some dict relating package from 
unstable.
Did anybody has encountered this or has more info?
I have restarted dictd myself. If someone will tell me what to look for I will 
look for more info.

Upgrading to unstable

[Brian Skreeg]

Upgrading to unstable used to be easy. Login, get list, choose
yer kit, install. Play. Lovely.
The current unstable tree seems impossible to me to upgrade to without
horrid dependancy stuff creeping in everywhere. My main problem seems
to be with lib6g+ (or something similar), tk4.2 (I have tk42) , tk7.6
(I have tk76) and stuff like that. Choosing just a simple thing like
tkirc for upgrading results in a large mangled mess of dependancy
conflicts. Anyone got any suggestions for getting started in this tree?


Ozzy,
   __ _ _
  /  \ \ \ 
 / / / / / |-Brian SkreegIRC:_Ozzy-|
 \__/  \ \ |-Lead guitarist extraordinaire-|
\__/_/ |-I don't look like two zombies-|


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Upgrading to unstable

[dpk]

This reason why it is more difficult is that when upgrading from stable -
unstable: you are upgrading from libc5 - libc6.  Have you followed the steps
in the mini-HOWTO for this?  You can find it at:
  ftp://ftp.debian.org/pub/debian/doc/libc5-libc6-Mini-HOWTO.html.tar.gz

Thanks,
Dennis
--
dpk [EMAIL PROTECTED], Systems/Network |  work: 353.4844
Division of Engineering Computing Services |  page: 222.5875

On Thu, 8 Jan 1998, Brian Skreeg wrote:

 
   Upgrading to unstable used to be easy. Login, get list, choose
 yer kit, install. Play. Lovely.
 The current unstable tree seems impossible to me to upgrade to without
 horrid dependancy stuff creeping in everywhere. My main problem seems
 to be with lib6g+ (or something similar), tk4.2 (I have tk42) , tk7.6
 (I have tk76) and stuff like that. Choosing just a simple thing like
 tkirc for upgrading results in a large mangled mess of dependancy
 conflicts. Anyone got any suggestions for getting started in this tree?
 
 
 Ozzy,
__ _ _
   /  \ \ \ 
  / / / / / |-Brian SkreegIRC:_Ozzy-|
  \__/  \ \ |-Lead guitarist extraordinaire-|
 \__/_/ |-I don't look like two zombies-|
 
 
 --
 TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
 [EMAIL PROTECTED] . 
 Trouble?  e-mail to [EMAIL PROTECTED] .
 


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .