Re: Upgrading with a low data cap

On Tue 09 Oct 2018 at 15:31:03 -, Dan Purgert wrote: > Richard Owlett wrote: > > On 10/09/2018 04:57 AM, Dan Purgert wrote: > >> Richard Owlett wrote: > >>> On 10/08/2018 06:23 PM, David wrote: > On Tue, 9 Oct 2018 at 06:25, Richard Owlett wrote: > > > > I have no LAN. > > >

Re: Upgrading with a low data cap

Richard Owlett wrote: > On 10/09/2018 04:57 AM, Dan Purgert wrote: >> Richard Owlett wrote: >>> On 10/08/2018 06:23 PM, David wrote: On Tue, 9 Oct 2018 at 06:25, Richard Owlett wrote: > > I have no LAN. > > I've a low cap. Using the word "cap" suggests that you have

Re: Upgrading with a low data cap

On 10/09/2018 04:57 AM, Dan Purgert wrote: Richard Owlett wrote: On 10/08/2018 06:23 PM, David wrote: On Tue, 9 Oct 2018 at 06:25, Richard Owlett wrote: I have no LAN. I've a low cap. Using the word "cap" suggests that you have an internet service provider. True How do you connect to

Re: Upgrading with a low data cap

On 10/08/2018 09:30 PM, Kenneth Parker wrote: Hello Richard.  I honor the help you have given to other users on this List.  Good work! On Mon, Oct 8, 2018 at 9:49 PM Richard Owlett > wrote: On 10/08/2018 06:23 PM, David wrote: > On Tue, 9 Oct 2018 at

Re: Upgrading with a low data cap

Richard Owlett wrote: > On 10/08/2018 06:23 PM, David wrote: >> On Tue, 9 Oct 2018 at 06:25, Richard Owlett wrote: >>> >>> I have no LAN. >>> >>> I've a low cap. >> >> Using the word "cap" suggests that you have an internet service provider. > > True >> >> How do you connect to that service

Re: Upgrading with a low data cap

On Mon 08 Oct 2018 at 21:39:49 +0100, Brian wrote: > On Mon 08 Oct 2018 at 15:32:52 -0500, Richard Owlett wrote: > > > On 10/08/2018 02:46 PM, Brian wrote: > > > On Mon 08 Oct 2018 at 14:24:49 -0500, Richard Owlett wrote: > > > > > > > On 10/08/2018 10:56 AM, David Wright wrote: > > > > > > >

Re: Upgrading with a low data cap

Hello Richard. I honor the help you have given to other users on this List. Good work! On Mon, Oct 8, 2018 at 9:49 PM Richard Owlett wrote: > On 10/08/2018 06:23 PM, David wrote: > > On Tue, 9 Oct 2018 at 06:25, Richard Owlett wrote: > >> > >> I have no LAN. > >> > >> I've a low cap. > > > >

Re: Upgrading with a low data cap

On 10/08/2018 06:23 PM, David wrote: On Tue, 9 Oct 2018 at 06:25, Richard Owlett wrote: I have no LAN. I've a low cap. Using the word "cap" suggests that you have an internet service provider. True How do you connect to that service provider? The same way as for decades via a "modem"

Re: Upgrading with a low data cap

On Tue, 9 Oct 2018 at 06:25, Richard Owlett wrote: > > I have no LAN. > > I've a low cap. Using the word "cap" suggests that you have an internet service provider. How do you connect to that service provider? What is the make and model of the equipment that provides the connection to that

Re: Upgrading with a low data cap

On Mon 08 Oct 2018 at 15:32:52 -0500, Richard Owlett wrote: > On 10/08/2018 02:46 PM, Brian wrote: > > On Mon 08 Oct 2018 at 14:24:49 -0500, Richard Owlett wrote: > > > > > On 10/08/2018 10:56 AM, David Wright wrote: > > > > > > > > That may well be, but the sooner you deploy some method of

Re: Upgrading with a low data cap

On 10/08/2018 02:46 PM, Brian wrote: On Mon 08 Oct 2018 at 14:24:49 -0500, Richard Owlett wrote: On 10/08/2018 10:56 AM, David Wright wrote: That may well be, but the sooner you deploy some method of reusing packages, the more you avoid exceeding your cap. I've a low cap. But I use even

Re: Upgrading with a low data cap

On Mon 08 Oct 2018 at 14:24:49 -0500, Richard Owlett wrote: > On 10/08/2018 10:56 AM, David Wright wrote: > > > > That may well be, but the sooner you deploy some method of reusing > > packages, the more you avoid exceeding your cap. > > I've a low cap. But I use even less and have built up a

Re: Upgrading with a low data cap

On Mon 08 Oct 2018 at 14:24:49 -0500, Richard Owlett wrote: > On 10/08/2018 10:56 AM, David Wright wrote: > > On Mon 08 Oct 2018 at 06:35:19 (-0500), Richard Owlett wrote: > > > [snip] > > > > I was under the impression that your networking consisted of > > > > point-to-point links via machines'

Re: Upgrading with a low data cap

On 10/08/2018 10:56 AM, David Wright wrote: On Mon 08 Oct 2018 at 06:35:19 (-0500), Richard Owlett wrote: [snip] I was under the impression that your networking consisted of point-to-point links via machines' USB ports. That effort is on hold [almost abandoned]. It's goal was primarily

Re: Upgrading with a low data cap

On Sun 07 Oct 2018 at 15:29:43 +0100, Brian wrote: > On Sun 07 Oct 2018 at 08:32:42 -0500, Richard Owlett wrote: > > [snip] > > > What should I be reading? > > https://lists.debian.org/debian-user/2017/06/msg00510.html Moving on from this helpful answer, the snipped bit is restored below: >

Re: Upgrading with a low data cap

On Mon 08 Oct 2018 at 06:35:19 (-0500), Richard Owlett wrote: > On 10/07/2018 08:25 PM, David Wright wrote: > > On Sun 07 Oct 2018 at 09:01:43 (-0500), Richard Owlett wrote: > > > On 10/07/2018 08:45 AM, Dan Purgert wrote: > > > > Richard Owlett wrote: > > > > > [...] > > > > > Is it possible to

Re: Upgrading with a low data cap

On Mon 08 Oct 2018 at 06:59:15 (+0100), Tixy wrote: > On Sun, 2018-10-07 at 20:08 -0500, David Wright wrote: > [...] > > If you're impatient and want to copy files to the stick during > > installation, note that (last time I looked) cp has no -n switch > > at this time. > > $ man cp | grep -C1

Re: Upgrading with a low data cap

On Mon 08 Oct 2018 at 08:06:56 (+), Curt wrote: > On 2018-10-07, Richard Owlett wrote: > > All my machines have use Stretch DVD1 for installation. > > I have a low monthly data cap - currently at my limit. > > One machine has an apt-get update and upgrade with the addition of some > >

Re: Upgrading with a low data cap

Richard Owlett wrote: > On 10/08/2018 06:56 AM, Dan Purgert wrote: >> [...] >> Admittedly, these options work best if you have multiple machines >> that're pretty much the same (e.g. that "lab" I did, where all the >> desktops were identical). >> > > They are not physically identical but all are

Re: Upgrading with a low data cap

On Mon, Oct 08, 2018 at 06:35:19AM -0500, Richard Owlett wrote: > > I haven't yet read the documentation for apt-cache-ng and don't know if it > would match my mental image. I was assuming that that all the packages that > I downloaded/upgraded were still in a cache which could be transferred to

Re: Upgrading with a low data cap

On 10/08/2018 06:56 AM, Dan Purgert wrote: Richard Owlett wrote: On 10/07/2018 08:25 PM, David Wright wrote: [...] Can you simultaneously connect the machine being installed to both the internet and the system running apt-cache-ng (and using http:)? I haven't yet read the documentation for

Re: Upgrading with a low data cap

Richard Owlett wrote: > On 10/07/2018 08:25 PM, David Wright wrote: >> [...] >> Can you simultaneously >> connect the machine being installed to both the internet and the >> system running apt-cache-ng (and using http:)? > > I haven't yet read the documentation for apt-cache-ng and don't know if

Re: Upgrading with a low data cap

On 2018-10-08 12:06, songbird wrote: mick crane wrote: On 2018-10-07 20:04, songbird wrote: i used to run on dialup and hated how long it took for some things to download. the package debdelta did help some at that time, but i have no idea if the service is even still there let alone

Re: Upgrading with a low data cap

On 10/07/2018 08:08 PM, David Wright wrote: On Sun 07 Oct 2018 at 08:32:42 (-0500), Richard Owlett wrote: All my machines have use Stretch DVD1 for installation. I have a low monthly data cap - currently at my limit. One machine has an apt-get update and upgrade with the addition of some

Re: Upgrading with a low data cap

On 10/07/2018 08:25 PM, David Wright wrote: On Sun 07 Oct 2018 at 09:01:43 (-0500), Richard Owlett wrote: On 10/07/2018 08:45 AM, Dan Purgert wrote: Richard Owlett wrote: [...] Is it possible to use the cached data on another machine? What should I be reading? TIA I think so, but it may be

Re: Upgrading with a low data cap

mick crane wrote: > On 2018-10-07 20:04, songbird wrote: > >> i used to run on dialup and hated how long it took >> for some things to download. the package debdelta >> did help some at that time, but i have no idea if the >> service is even still there let alone functional. > > I installed

Re: Upgrading with a low data cap

On 2018-10-07 20:04, songbird wrote: i used to run on dialup and hated how long it took for some things to download. the package debdelta did help some at that time, but i have no idea if the service is even still there let alone functional. I installed Gentoo once over dialup It took two

Re: Upgrading with a low data cap

On 2018-10-07, Richard Owlett wrote: > All my machines have use Stretch DVD1 for installation. > I have a low monthly data cap - currently at my limit. > One machine has an apt-get update and upgrade with the addition of some > packages not on DVD1. > I've not intentionally deleted any cached

Re: Upgrading with a low data cap

On Sun, 2018-10-07 at 20:08 -0500, David Wright wrote: [...] > If you're impatient and want to copy files to the stick during > installation, note that (last time I looked) cp has no -n switch > at this time. $ man cp | grep -C1 '\-n,'    -n, --no-clobber   do not overwrite an

Re: Upgrading with a low data cap

On 10/7/18 6:32 AM, Richard Owlett wrote: All my machines have use Stretch DVD1 for installation. I have a low monthly data cap - currently at my limit. One machine has an apt-get update and upgrade with the addition of some packages not on DVD1. I've not intentionally deleted any cached

Re: Upgrading with a low data cap

On Sun 07 Oct 2018 at 09:01:43 (-0500), Richard Owlett wrote: > On 10/07/2018 08:45 AM, Dan Purgert wrote: > > Richard Owlett wrote: > > > [...] > > > Is it possible to use the cached data on another machine? > > > What should I be reading? > > > TIA > > > > I think so, but it may be more manual

Re: Upgrading with a low data cap

On Sun 07 Oct 2018 at 08:32:42 (-0500), Richard Owlett wrote: > All my machines have use Stretch DVD1 for installation. > I have a low monthly data cap - currently at my limit. > One machine has an apt-get update and upgrade with the addition of > some packages not on DVD1. > I've not

Re: Upgrading with a low data cap

Richard Owlett wrote: > All my machines have use Stretch DVD1 for installation. > I have a low monthly data cap - currently at my limit. > One machine has an apt-get update and upgrade with the addition of some > packages not on DVD1. > I've not intentionally deleted any cached files. > Is it

Re: Upgrading with a low data cap

On 10/7/18, Richard Owlett wrote: > All my machines have use Stretch DVD1 for installation. > I have a low monthly data cap - currently at my limit. > One machine has an apt-get update and upgrade with the addition of some > packages not on DVD1. > I've not intentionally deleted any cached files.

Re: Upgrading with a low data cap

On Sun 07 Oct 2018 at 08:32:42 -0500, Richard Owlett wrote: [snip] > What should I be reading? https://lists.debian.org/debian-user/2017/06/msg00510.html -- Brian.

Re: Upgrading with a low data cap

On 10/07/2018 08:45 AM, Dan Purgert wrote: Richard Owlett wrote: [...] Is it possible to use the cached data on another machine? What should I be reading? TIA I think so, but it may be more manual than you'd otherwise do. NOT a problem. I've lots of time. Data cap is the constraint. My

Re: Upgrading with a low data cap

Hi. On Sun, Oct 07, 2018 at 08:32:42AM -0500, Richard Owlett wrote: > All my machines have use Stretch DVD1 for installation. > I have a low monthly data cap - currently at my limit. > One machine has an apt-get update and upgrade with the addition of some > packages not on DVD1. > I've

Re: Upgrading with a low data cap

Richard Owlett wrote: > [...] > Is it possible to use the cached data on another machine? > What should I be reading? > TIA I think so, but it may be more manual than you'd otherwise do. Perhaps you should look into apt-cache-ng (IIRC) or squid to facilitate automatic caching. Ive used the

Upgrading with a low data cap

All my machines have use Stretch DVD1 for installation. I have a low monthly data cap - currently at my limit. One machine has an apt-get update and upgrade with the addition of some packages not on DVD1. I've not intentionally deleted any cached files. Is it possible to use the cached data on

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

On Tue, 11 Sep 2018 21:24:42 -0400 Ric Moore wrote: Hello Ric, >Works a charm for me, and has for years, BUT every once in awhile As it does for many, I'm sure. >the volume levels back up to 100%. Pulse rides on top of alsa, so alsa And that's a problem. Now, if sound goes wrong there are

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

On 09/10/2018 08:27 AM, Brad Rogers wrote: On Mon, 10 Sep 2018 11:53:01 + (UTC) Curt wrote: Hello Curt, So uninstall it then in that unfortunate case--with extreme prejudice Time. Oh, and I can't be arsed to try PA in the first place. :-) Or are we dealing with the supernatural

Re: [beginning OT] Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

On Monday, September 10, 2018 09:37:28 AM Thomas Schmitt wrote: > I could offer my program cdrskin as real example. > It is a cdrecord/wodim compatibility wrapper but exceeds both when it > comes to DVD and BD media. Thanks, for: * the useful example, and * changing the Subject: line

Re: [beginning OT] Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

Hi. On Mon, Sep 10, 2018 at 03:37:28PM +0200, Thomas Schmitt wrote: > Hi, > > Reco wrote: > > > It's the usual. A compatibility wrapper can never exceed the original. > > rhkra...@gmail.com wrote: > > Hmm, I don't see why it couldn't in some sense -- I'm trying to think of how > > to

[beginning OT] Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

Hi, Reco wrote: > > It's the usual. A compatibility wrapper can never exceed the original. rhkra...@gmail.com wrote: > Hmm, I don't see why it couldn't in some sense -- I'm trying to think of how > to say what I want to say, let me try a made-up example. I could offer my program cdrskin as real

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

On Mon, 10 Sep 2018 11:53:01 + (UTC) Curt wrote: Hello Curt, >So uninstall it then in that unfortunate case--with extreme prejudice Time. Oh, and I can't be arsed to try PA in the first place. :-) >Or are we dealing with the supernatural here (software from Hell)? I'm wary because of

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

On 2018-09-10, Brad Rogers wrote: > > The machine it does affect is the one that I routinely use, which has > been in use for longer than PA has been around. I /could/ install PA, > but am reluctant to do so, since sound works here ATM and I'm concerned > that installing PA may cause issues for

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

On Monday, September 10, 2018 05:49:01 AM Reco wrote: > It's the usual. A compatibility wrapper can never exceed the original. Hmm, I don't see why it couldn't in some sense -- I'm trying to think of how to say what I want to say, let me try a made-up example. Suppose some piece of software is

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

On Mon, 10 Sep 2018 12:49:01 +0300 Reco wrote: Hello Reco, >On Mon, Sep 10, 2018 at 09:59:03AM +0100, Brad Rogers wrote: >> I've not been running apulse long, but so far, no crashes in Ff 62. >So upstream lies then. To quote apulse's README.md: Maybe, maybe not. It's only been a couple of

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

Hi. On Mon, Sep 10, 2018 at 09:59:03AM +0100, Brad Rogers wrote: > On Sun, 9 Sep 2018 11:43:39 +0300 > Reco wrote: > > Hello Reco, > > >Moreover, apulse causes Firefox to crash since Firefox version 58, as > > I've not been running apulse long, but so far, no crashes in Ff 62. So

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

On Sun, 9 Sep 2018 11:43:39 +0300 Reco wrote: Hello Reco, >Moreover, apulse causes Firefox to crash since Firefox version 58, as I've not been running apulse long, but so far, no crashes in Ff 62. >apulse is a kludge, not a solution. That's as may be (I don't have an opinion either way).

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

Rob van der Putten wrote: > Does anyone know why ALSA is no longer supported? You mean supported by Firefox? I guess they decided PA is more easy to implement as default interface ... whatever underlaying audio system you use. I still could not understand why, but this seems irreversible.

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

to...@tuxteam.de (2018-09-09): > Personally, I couldn't care less: I consider my browser's inability > to make sounds a welcome *feature*, so not having Pulse (which is my > default) just naturally takes care of that. Same for me. And apulse seems to work for me anyway. > Given the amount of

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Sep 09, 2018 at 10:24:30AM +0200, Rob van der Putten wrote: > Hi there > > > Note: A reply in bugs failed. > > On 09/09/18 10:08, Marco Lucidi wrote: > > > On Sat, 8 Sep 2018 21:41:11 +0200 Samuel Thibault > > wrote: > > > Unfortunately

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

Hi. On Sun, Sep 09, 2018 at 10:24:30AM +0200, Rob van der Putten wrote: > Hi there > > > Note: A reply in bugs failed. > > On 09/09/18 10:08, Marco Lucidi wrote: > > > On Sat, 8 Sep 2018 21:41:11 +0200 Samuel Thibault > > wrote: > > > Unfortunately AIUI upstream has stopped

Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

Hi there Note: A reply in bugs failed. On 09/09/18 10:08, Marco Lucidi wrote: > On Sat, 8 Sep 2018 21:41:11 +0200 Samuel Thibault > wrote: > > Unfortunately AIUI upstream has stopped supporting ALSA, so we are stuck > > with pulseaudio for firefox. > > Is there any particular reason for

Hibernation is not working after upgrading frmo Jessie to Stretch.

Dear all, Recently I upgraded my Debian Jessie to Stretch and I noticed that hibernation does not work anymore. When I try to hibernate to disk the process of saving the current memory state seems to be doing the job correctly. However, when I start the laptop I see that restoring the state

Re: Error while upgrading from Wheezy to Stretch

On 04/11/2018 12:31 PM, David Parker wrote: Hello, I am trying to upgrade two test boxes from Wheezy to Stretch (skipping Jessie). The upgrade worked on one of them, although I ran into errors and had to run "apt-get -f install" a few times, but that resolved the issues and it ultimately

Re: Error while upgrading from Wheezy to Stretch

On Thu, Apr 19, 2018 at 02:47:05PM -0400, Gene Heskett wrote: > > "Pinning" is an interesting subject Roberto, interesting because the info > on how to do it is generally skipped over, or only mentioned in passing, > with NO examples of how to do it in the man pages available. I have it >

Re: Error while upgrading from Wheezy to Stretch

On Thursday 19 April 2018 15:23:16 Dan Ritter wrote: > On Thu, Apr 19, 2018 at 02:47:05PM -0400, Gene Heskett wrote: > > On Thursday 19 April 2018 11:32:28 Roberto C. Sánchez wrote: > > > The only thing I would say is use apt "pinning" to prioritize the > > > backports repository lower than the

Re: Pinning (was Re: Error while upgrading from Wheezy to Stretch)

On Thu, Apr 19, 2018 at 03:46:17PM -0400, Gene Heskett wrote: > I realize that Greg, but debian's support for armhf for unusual > applications that require a realtime environment, is at its finest, an > afterthought and discarded. We linuxcnc runners are used to it. So we > build our own

Re: Pinning (was Re: Error while upgrading from Wheezy to Stretch)

On Thursday 19 April 2018 14:59:04 Greg Wooledge wrote: > On Thu, Apr 19, 2018 at 02:47:05PM -0400, Gene Heskett wrote: > > Hijacking a thread here, but it reads like I might be reading an > > expert. > > > > "Pinning" is an interesting subject Roberto, interesting because the > > info on how to

Re: Pinning (was Re: Error while upgrading from Wheezy to Stretch)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Apr 19, 2018 at 02:59:04PM -0400, Greg Wooledge wrote: > On Thu, Apr 19, 2018 at 02:47:05PM -0400, Gene Heskett wrote: > > Hijacking a thread here, but it reads like I might be reading an expert. > > > > "Pinning" is an interesting subject

Re: Error while upgrading from Wheezy to Stretch

On Thu, Apr 19, 2018 at 02:47:05PM -0400, Gene Heskett wrote: > On Thursday 19 April 2018 11:32:28 Roberto C. Sánchez wrote: > > > The only thing I would say is use apt "pinning" to prioritize the > > backports repository lower than the other repositories so you don't > > accidentally get

Re: Pinning (was Re: Error while upgrading from Wheezy to Stretch)

On Thu, Apr 19, 2018 at 02:47:05PM -0400, Gene Heskett wrote: > Hijacking a thread here, but it reads like I might be reading an expert. > > "Pinning" is an interesting subject Roberto, interesting because the info > on how to do it is generally skipped over, or only mentioned in passing, >

Re: Error while upgrading from Wheezy to Stretch

On Thursday 19 April 2018 11:32:28 Roberto C. Sánchez wrote: > On Thu, Apr 19, 2018 at 11:26:20AM -0400, Greg Wooledge wrote: > > According to http://packages.debian.org/pacemaker there is also a > > backport of the stretch version of the package in the > > jessie-backports repository. So

Re: Error while upgrading from Wheezy to Stretch

On Thu, Apr 19, 2018 at 11:45:11AM -0400, David Parker wrote: >I'm not positive what happened with it, but I wonder if the fact >that the pacemaker package was missing entirely from the new release >caused apt to just get rid of it during the upgrade. Neither of the package front-ends

Re: Error while upgrading from Wheezy to Stretch

I never thought to use the backports repo in Jessie to keep pacemaker installed. That's a great idea, I'll give it a try and see what happens. Regarding Pacemaker's data and config, as far as I could tell, it was gone. I'm not positive what happened with it, but I wonder if the fact that the

Re: Error while upgrading from Wheezy to Stretch

On Thu, Apr 19, 2018 at 11:26:20AM -0400, Greg Wooledge wrote: > > According to http://packages.debian.org/pacemaker there is also a > backport of the stretch version of the package in the jessie-backports > repository. So perhaps there is some way to convince the jessie upgrade > to use the

Re: Error while upgrading from Wheezy to Stretch

On Thu, Apr 19, 2018 at 11:18:43AM -0400, Roberto C. Sánchez wrote: > - backup your pacemaker configurations and user-generated files, let >the upgrade process remove the packages, then restore everything >after the upgrade is complete I'm still stumped by the claim that the

Re: Error while upgrading from Wheezy to Stretch

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Apr 19, 2018 at 10:57:09AM -0400, David Parker wrote: > Hi all, > > Sorry I didn't get back to this sooner, had some crazy life stuff getting > in the way. > > I should have said in my original post that there is a reason I'm trying to >

Re: Error while upgrading from Wheezy to Stretch

On Thu, Apr 19, 2018 at 10:57:09AM -0400, David Parker wrote: > >I did read the documentation and I did try Wheezy -> Jessie - > Stretch >first, but the problem was that Pacemaker was removed.  Hence, I was >hoping to skip Jessie. >If it's simply not possible to do this upgrade

Re: Error while upgrading from Wheezy to Stretch

Hi all, Sorry I didn't get back to this sooner, had some crazy life stuff getting in the way. I should have said in my original post that there is a reason I'm trying to jump from Wheezy to Stretch. These boxes are in an HA cluster with Pacemaker, Corosync, and DRBD. I have all 3 of these

Re: Error while upgrading from Wheezy to Stretch

On Thu 12 Apr 2018 at 06:42:33 (-0400), Dan Ritter wrote: > On Wed, Apr 11, 2018 at 07:57:07PM -0500, David Wright wrote: > > On Wed 11 Apr 2018 at 15:31:32 (-0400), David Parker wrote: > > > I am trying to upgrade two test boxes from Wheezy to Stretch (skipping > > > Jessie). The upgrade worked

Re: Error while upgrading from Wheezy to Stretch

David Parker wrote: ... given they are test boxes you should go straight to reinstall from netinst image or whatever you can get that will do it. :) much much faster than trying to fiddle around with upgrades. especially when many versions in between. of course, always check

Re: Error while upgrading from Wheezy to Stretch

On Wed, Apr 11, 2018 at 07:57:07PM -0500, David Wright wrote: > On Wed 11 Apr 2018 at 15:31:32 (-0400), David Parker wrote: > > I am trying to upgrade two test boxes from Wheezy to Stretch (skipping > > Jessie). The upgrade worked on one of them, although I ran into errors and > > had to run

Re: Error while upgrading from Wheezy to Stretch

On Wed 11 Apr 2018 at 15:31:32 (-0400), David Parker wrote: > I am trying to upgrade two test boxes from Wheezy to Stretch (skipping > Jessie). The upgrade worked on one of them, although I ran into errors and > had to run "apt-get -f install" a few times, but that resolved the issues > and it

Re: Error while upgrading from Wheezy to Stretch

m-modules. It's > preventing the upgrade from finishing. > > # apt-get -f install > [snip] > > Any ideas or suggestions for resolving this will be greatly > appreciated. Yes. Retore both Wheezy systems from their respective back ups Then read and follow the upgarde instructions wh

Re: Error while upgrading from Wheezy to Stretch

David Parker wrote: > Any ideas or suggestions for resolving this will be greatly appreciated. it is definitely less effort to upgrade to jessie and then to stretch - it just takes a bit more time, but less effort in debugging. can you reinstall or configure bsdmainutils? or purge man and

Error while upgrading from Wheezy to Stretch

Hello, I am trying to upgrade two test boxes from Wheezy to Stretch (skipping Jessie). The upgrade worked on one of them, although I ran into errors and had to run "apt-get -f install" a few times, but that resolved the issues and it ultimately worked. However, on the second box, I ran into an

Re: How to execute user's scripts when upgrading a certain package via apt/aptitude

On 2018-03-30 04:00, John Crawley (johnraff) wrote: > On 2018-03-29 09:15, Abdullah Ramazanoglu wrote: >> On Wed, 28 Mar 2018 20:00:34 +0200 Mikhail Morfikov said: >>> Is there some variable that holds, for instance, a list of the >>> packages that apt wants to upgrade? In such way it would be

Re: How to execute user's scripts when upgrading a certain package via apt/aptitude

On 2018-03-29 09:15, Abdullah Ramazanoglu wrote: On Wed, 28 Mar 2018 20:00:34 +0200 Mikhail Morfikov said: Is there some variable that holds, for instance, a list of the packages that apt wants to upgrade? In such way it would be easy to set this up. apt list --upgradable will print out a

Re: How to execute user's scripts when upgrading a certain package via apt/aptitude

>> >> I think the trick is to create a (nearly) empty package "my-firefox-custom" >> which depends on firefox and thus pulls it in before its own post-install >> takes over. > This sounds as if it should work, but your custom package would need > upgrading

Re: How to execute user's scripts when upgrading a certain package via apt/aptitude

On Wed, 28 Mar 2018 20:00:34 +0200 Mikhail Morfikov said: > Is there some variable that holds, for instance, a list of the > packages that apt wants to upgrade? In such way it would be easy to > set this up. On Wed, 28 Mar 2018 20:18:24 +0200 Mikhail Morfikov said: > But I will try to do

Re: How to execute user's scripts when upgrading a certain package via apt/aptitude

On 2018-03-29 03:40, to...@tuxteam.de wrote: I really thought there's some easy way to include user's scripts when you want to make some additional changes to the upgraded packages, but it looks like the apt mechanism is a little bit limited. But I will try to do something with the trigger and

Re: How to execute user's scripts when upgrading a certain package via apt/aptitude

takes over. This sounds as if it should work, but your custom package would need upgrading every time Firefox was upgraded, so the automation would be lost. @Sven, depending on how you do your upgrades, maybe a script could interrogate apt-get as to what packages it intended to upgrade, before

Re: How to execute user's scripts when upgrading a certain package via apt/aptitude

On 2018-03-28 21:25, David Wright wrote: > On Wed 28 Mar 2018 at 20:00:34 (+0200), Mikhail Morfikov wrote: >> On 2018-03-28 18:58, Andy Smith wrote: >>> On Wed, Mar 28, 2018 at 06:29:06PM +0200, Mikhail Morfikov wrote: Is there a way to pass some extra commands/script to apt/aptitude so when

Re: How to execute user's scripts when upgrading a certain package via apt/aptitude

On Wed 28 Mar 2018 at 20:00:34 (+0200), Mikhail Morfikov wrote: > On 2018-03-28 18:58, Andy Smith wrote: > > On Wed, Mar 28, 2018 at 06:29:06PM +0200, Mikhail Morfikov wrote: > >> Is there a way to pass some extra commands/script to apt/aptitude so when > >> the > >> firefox package is to be

Re: How to execute user's scripts when upgrading a certain package via apt/aptitude

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Mar 28, 2018 at 08:18:24PM +0200, Mikhail Morfikov wrote: > On 2018-03-28 20:12, Sven Joachim wrote: [...] > > It requires you to create your own package (since there is no other way > > to register triggers in dpkg) [...] > I really

Re: How to execute user's scripts when upgrading a certain package via apt/aptitude

On 2018-03-28 20:12, Sven Joachim wrote: > On 2018-03-28 19:46 +0200, Mikhail Morfikov wrote: > >> On 2018-03-28 19:29, Sven Joachim wrote: >>> On 2018-03-28 18:29 +0200, Mikhail Morfikov wrote: >>> I have some packages, for instance firefox, which need a little bit of customization

Re: How to execute user's scripts when upgrading a certain package via apt/aptitude

On 2018-03-28 19:46 +0200, Mikhail Morfikov wrote: > On 2018-03-28 19:29, Sven Joachim wrote: >> On 2018-03-28 18:29 +0200, Mikhail Morfikov wrote: >> >>> I have some packages, for instance firefox, which need a little bit of >>> customization from a user side. So basically when I install the

Re: How to execute user's scripts when upgrading a certain package via apt/aptitude

On 2018-03-28 18:58, Andy Smith wrote: > Hi Mikhail, > > On Wed, Mar 28, 2018 at 06:29:06PM +0200, Mikhail Morfikov wrote: >> Is there a way to pass some extra commands/script to apt/aptitude so when the >> firefox package is to be upgraded, it would recreate the links automatically? > > I've

Re: How to execute user's scripts when upgrading a certain package via apt/aptitude

On 2018-03-28 19:29, Sven Joachim wrote: > On 2018-03-28 18:29 +0200, Mikhail Morfikov wrote: > >> I have some packages, for instance firefox, which need a little bit of >> customization from a user side. So basically when I install the new version >> of >> firefox, I also have to do some extra

Re: How to execute user's scripts when upgrading a certain package via apt/aptitude

On 2018-03-28 18:29 +0200, Mikhail Morfikov wrote: > I have some packages, for instance firefox, which need a little bit of > customization from a user side. So basically when I install the new version of > firefox, I also have to do some extra steps and so far I've been doing it > manually

Re: How to execute user's scripts when upgrading a certain package via apt/aptitude

Hi Mikhail, On Wed, Mar 28, 2018 at 06:29:06PM +0200, Mikhail Morfikov wrote: > Is there a way to pass some extra commands/script to apt/aptitude so when the > firefox package is to be upgraded, it would recreate the links automatically? I've never tried it but looking at "man apt.conf" it seems

How to execute user's scripts when upgrading a certain package via apt/aptitude

I have some packages, for instance firefox, which need a little bit of customization from a user side. So basically when I install the new version of firefox, I also have to do some extra steps and so far I've been doing it manually because I don't know any better way. In the case of firefox, I

Re: BIND DNS problem after upgrading from Wheezy to Squeeze

Pascal Hambourg wrote: > Le 29/12/2017 à 18:27, Andrew W a écrit : >> >> On 27/12/2017 13:18, Bernhard Schmidt wrote: >>> Current BIND9 defaults to doing DNSSEC verification. DNSSEC needs large >>> packets. You might have an issue with UDP fragments being dropped at >>>

Re: BIND DNS problem after upgrading from Wheezy to Squeeze

Le 29/12/2017 à 18:27, Andrew W a écrit : On 27/12/2017 13:18, Bernhard Schmidt wrote: Current BIND9 defaults to doing DNSSEC verification. DNSSEC needs large packets. You might have an issue with UDP fragments being dropped at your firewall/NAT Gateway? Thanks for this tip. Looking into it I

Re: BIND DNS problem after upgrading from Wheezy to Squeeze

On 27/12/2017 13:18, Bernhard Schmidt wrote: Current BIND9 defaults to doing DNSSEC verification. DNSSEC needs large packets. You might have an issue with UDP fragments being dropped at your firewall/NAT Gateway? Thanks for this tip. Looking into it I discovered TCP seems to be recommened

Re: BIND DNS problem after upgrading from Wheezy to Squeeze

Andrew Wood wrote: Hi, > I have a server which acts as a DNS server for our LAN. All our internal > servers have A records on it using a .local domain and it forwards all > other requests out to the root servers using the in built list provided > with BIND. All clients on

Re: BIND DNS problem after upgrading from Wheezy to Squeeze

Andrew W wrote: > > > Does anyone have any ideas please? > I had the same experience - I think (after trying this and that) the solution was ntp (time was behind on the server), but I am not really 100%. I was thinking first it has something to do with ipv6 or firewall, but after updating

<    1   2   3   4   5   6   7   8   9   10   >