Re: proper config for specific pks upgrade from stable to testing

On Vi, 24 iul 20, 16:21:28, daggs wrote: > > > Sent: Friday, July 24, 2020 at 12:13 PM > > From: "Andrei POPESCU" > > > > With only these pins the rest of testing is priority 500, same as > > stable. Probably not what you want. > > so I need to demote the rest of testing is priority to below 500

Re: proper config for specific pks upgrade from stable to testing

Greetings Andrei, > Sent: Friday, July 24, 2020 at 12:13 PM > From: "Andrei POPESCU" > To: debian-user@lists.debian.org > Subject: Re: proper config for specific pks upgrade from stable to testing > > On Vi, 24 iul 20, 08:37:52, daggs wrote: > > Greeting

Re: proper config for specific pks upgrade from stable to testing

On Vi, 24 iul 20, 08:37:52, daggs wrote: > Greetings, > > I want to upgrade these specific pkgs from stable to testing: > libvirt-clients/stable,now 5.0.0-4+deb10u1 amd64 [installed,upgradable to: > 6.4.0-2] > libvirt-daemon-system/stable,now 5.0.0-4+deb10u1 amd64 [installed,upgradable > to: 6.4

proper config for specific pks upgrade from stable to testing

Greetings, I want to upgrade these specific pkgs from stable to testing: libvirt-clients/stable,now 5.0.0-4+deb10u1 amd64 [installed,upgradable to: 6.4.0-2] libvirt-daemon-system/stable,now 5.0.0-4+deb10u1 amd64 [installed,upgradable to: 6.4.0-2] libvirt-daemon/stable,now 5.0.0-4+deb10u1 amd64 [

Re: Upgrade from stable to testing hosed my server

Well, after some poking around I finally solved the problem 1. The onboard nic was not dead, just a little confused. 2. The problem was in /etc/fstab in this line //192.168.25.105/orca /home/share cifs file_mode=0644,dir_mode=0755,uid=1000,gid=1000,rw00 I found these errors in the logs

Re: Upgrade from stable to testing hosed my server

On 01/24/2013 05:51 PM, Mark Phillips wrote: Peter, Can I access the log if I boot the machine with a live cd of some kind? Mark Hello Mark, read the release notes first and think about what you did wrong. I do not know how you proceed with the upgrade, but yes there are paths like these:

Re: Upgrade from stable to testing hosed my server

On 01/24/2013 02:30 PM, Mark Phillips wrote: I used aptitude to upgrade a headless server from Debian stable to Debian testing. The upgrade did not generate any error messages, but when I rebooted I could not ssh into the box (connection refused) nor do I get any output on a monitor I attache

Upgrade from stable to testing hosed my server

I used aptitude to upgrade a headless server from Debian stable to Debian testing. The upgrade did not generate any error messages, but when I rebooted I could not ssh into the box (connection refused) nor do I get any output on a monitor I attached to the box (no signal). Apache does not appear to

Re: upgrade-report: errors from squeeze tar unpacking packages from testing (Re: Upgrade from stable to testing problem)

> This sounds reminiscent of . > It would be a serious bug, except the necessary version of tar had been in > squeeze for more than a year already. What version of tar were you > using when you ran into this? (/var/log/dpkg.log should say.) What > error message di

upgrade-report: errors from squeeze tar unpacking packages from testing (Re: Upgrade from stable to testing problem)

Hi Hans, Hans-J. Ullrich wrote: > some weeks ago I made a fresh instrallation on a notebook with debian/stable. > > Well, then I started a aptitiude full-upgrade, but it did not work. I found > out, the reason for it, was, that the installed version of tar could not > unpack the packages of deb

Upgrade from stable to testing problem

Hi all, some weeks ago I made a fresh instrallation on a notebook with debian/stable. Well, then I started a aptitiude full-upgrade, but it did not work. I found out, the reason for it, was, that the installed version of tar could not unpack the packages of debian/testing. I could fix this, b

Re: upgrade from stable to testing

Antoine Solomon wrote: if i used the nvidia drivers from their website, would this conflict with deb pkg sys? On 11/23/05, *Rafal Czlonka* <[EMAIL PROTECTED] > wrote: > Could anyone point me to information on upgrading from stable to testing.? > The

Re: upgrade from stable to testing

On Wed, Nov 23, 2005 at 01:27:12PM -0500, Antoine Solomon wrote: > if i used the nvidia drivers from their website, would this conflict with > deb pkg sys? No, why should it? -- Rafal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTE

Re: upgrade from stable to testing

if i used the nvidia drivers from their website, would this conflict with deb pkg sys?  On 11/23/05, Rafal Czlonka <[EMAIL PROTECTED]> wrote: > Could anyone point me to information on upgrading from stable to testing.?> The reason I ask is because I have a nvidia graphics card and unable to load>

Re: upgrade from stable to testing

> Could anyone point me to information on upgrading from stable to testing.? > The reason I ask is because I have a nvidia graphics card and unable to load > X. # apt-get update && apt-get dist-upgrade BTW you don't need to upgrade the system to be able to use X. -- Rafal -- To UNSUBSCRIBE,

Re: upgrade from stable to testing

On Wed, Nov 23, 2005 at 12:45:24PM -0500, Antoine Solomon wrote: > hello, > > Could anyone point me to information on upgrading from stable to testing.? > The reason I ask is because I have a nvidia graphics card and unable to load > X. Which card? Is it possible for you to grab just the updated

upgrade from stable to testing

hello, Could anyone point me to information on upgrading from stable to testing.?  The reason I ask is because I have a nvidia graphics card and unable to load X.  -- Antoine W. Solomon Jr.

Re: dist-upgrade from stable to testing

On Tue, Aug 14, 2001 at 12:20:57AM -0600, Phil Reardon wrote: > On Monday 13 August 2001 11:36 pm, John Galt wrote: > > mkdir /etc/exim then rerun apt-get dist-upgrade... You won't have to > > re-download the 166M, BTW. > > > > On Mon, 13 Aug 2001, Phil Reardon wrote: > > >After apt-get update, ap

Re: dist-upgrade from stable to testing

On Monday 13 August 2001 11:36 pm, John Galt wrote: > mkdir /etc/exim then rerun apt-get dist-upgrade... You won't have to > re-download the 166M, BTW. > > On Mon, 13 Aug 2001, Phil Reardon wrote: > >After apt-get update, apt-get dist-upgrade to testing, I got a successful > >download of 166 MB. B

Re: dist-upgrade from stable to testing

mkdir /etc/exim then rerun apt-get dist-upgrade... You won't have to re-download the 166M, BTW. On Mon, 13 Aug 2001, Phil Reardon wrote: >After apt-get update, apt-get dist-upgrade to testing, I got a successful >download of 166 MB. But during the install/config, I saw this message: > >mv: cann

dist-upgrade from stable to testing

After apt-get update, apt-get dist-upgrade to testing, I got a successful download of 166 MB. But during the install/config, I saw this message: mv: cannot create regjular file '/etc/exim/exim.conf' ; No such file or directory. dpkg: error processing /var/cach/apt/archives/exim_3.31-1_i386.d

Re: dist-upgrade from stable to testing: circular dependency

Try installing both packages at once from dpkg. If that won't work then you get to now learn the joys of "forcing" packages into your system. run dpkg --force-help I won't tell you which one to use because it's best if you read the help and then make an informed decision about "forcing" your "dep

dist-upgrade from stable to testing: circular dependency

The debian-testing archive doesn't have any messages since April, so I presume this is the correct list. I changed sources.list from stable to testing, used dselect to do what is presumably the equivalent of apt-get update, then did apt-get dist-upgrade, which failed with an error message. perl: