On Fri, Jul 28, 2017 at 12:04:54PM -0400, Greg Wooledge wrote:
>
> The concern is that you may have used some shared library to compile a
> third-party program which is installed in /usr/local or /opt, or anywhere
> else that's outside of Debian's knowledge. Debian would not know that
> the
On 28-07-17, Greg Wooledge wrote:
> On Fri, Jul 28, 2017 at 05:39:39PM +0200, Dejan Jocic wrote:
> > So, same question as above, did and of those they messed up? Are there
> > opened bugs that autoremove from any of used tools in debian removes
> > packages it should not? And qualifications for
On Fri, Jul 28, 2017 at 05:39:39PM +0200, Dejan Jocic wrote:
> So, same question as above, did and of those they messed up? Are there
> opened bugs that autoremove from any of used tools in debian removes
> packages it should not? And qualifications for that statement are years
> of use of both
On 27-07-17, David Wright wrote:
> On Tue 25 Jul 2017 at 16:16:44 (+0200), Dejan Jocic wrote:
> > On 25-07-17, Greg Wooledge wrote:
> > > Is there any way to permanently neuter apt-get autoremove, so that even
> > > if something invokes it against my will, it will *never* remove anything?
> > >
>
On Tue 25 Jul 2017 at 20:56:31 (-0700), Patrick Bartek wrote:
> On Wed, 26 Jul 2017 00:24:00 +0100 Brian wrote:
>
> > On Tue 25 Jul 2017 at 16:14:52 -0700, Patrick Bartek wrote:
> >
> > > On Tue, 25 Jul 2017 20:06:01 +0100 Brian
> > > wrote:
> > >
>
On Tue 25 Jul 2017 at 16:16:44 (+0200), Dejan Jocic wrote:
> On 25-07-17, Greg Wooledge wrote:
> > Is there any way to permanently neuter apt-get autoremove, so that even
> > if something invokes it against my will, it will *never* remove anything?
> >
> > And more, is there a way to get apt and
On Wed 26 Jul 2017 at 08:22:19 -0400, Greg Wooledge wrote:
> On Wed, Jul 26, 2017 at 12:24:00AM +0100, Brian wrote:
> > On Tue 25 Jul 2017 at 16:14:52 -0700, Patrick Bartek wrote:
> > > In other words, Wheezy is still alive
> > > support-wise.
> >
> > A mention of the names of some of these apps
On Wed, Jul 26, 2017 at 12:24:00AM +0100, Brian wrote:
> On Tue 25 Jul 2017 at 16:14:52 -0700, Patrick Bartek wrote:
> > In other words, Wheezy is still alive
> > support-wise.
>
> A mention of the names of some of these apps would be helpful. A record
> will be in your logs.
Here's a result
On Wed, 26 Jul 2017 00:24:00 +0100 Brian wrote:
> On Tue 25 Jul 2017 at 16:14:52 -0700, Patrick Bartek wrote:
>
> > On Tue, 25 Jul 2017 20:06:01 +0100 Brian
> > wrote:
> >
> > > On Tue 25 Jul 2017 at 07:04:29 -0700, Patrick Bartek wrote:
> > >
> >
On Tuesday 25 July 2017 10:02:50 Greg Wooledge wrote:
> Is there any way to permanently neuter apt-get autoremove, so that
> even if something invokes it against my will, it will *never* remove
> anything?
>
> And more, is there a way to get apt and apt-get to *stop* prompting me
> to run it, and
On 07/24/17 23:12, VigneshDhanraj G wrote:
I am using kernel 3.2.x, i know that support from wheezy will be stopped
soon. can i upgrade to jessie with same kernel version.
Is that correct way of handling?
I prefer and recommend backing up, removing the system drive, installing
a fresh system
On Tue 25 Jul 2017 at 16:14:52 -0700, Patrick Bartek wrote:
> On Tue, 25 Jul 2017 20:06:01 +0100 Brian wrote:
>
> > On Tue 25 Jul 2017 at 07:04:29 -0700, Patrick Bartek wrote:
> >
> > > On Tue, 25 Jul 2017 11:42:12 +0530 VigneshDhanraj G
> > >
On Tue, 25 Jul 2017 20:06:01 +0100 Brian wrote:
> On Tue 25 Jul 2017 at 07:04:29 -0700, Patrick Bartek wrote:
>
> > On Tue, 25 Jul 2017 11:42:12 +0530 VigneshDhanraj G
> > wrote:
> >
> > > Hi Team,
> > >
> > > I am using kernel 3.2.x, i know
On Tue 25 Jul 2017 at 07:04:29 -0700, Patrick Bartek wrote:
> On Tue, 25 Jul 2017 11:42:12 +0530 VigneshDhanraj G
> wrote:
>
> > Hi Team,
> >
> > I am using kernel 3.2.x, i know that support from wheezy will be
> > stopped soon. can i upgrade to jessie with same
On Tue, Jul 25, 2017 at 07:40:17PM +0100, Brian wrote:
> /usr/share/doc/apt/examples/configure-index.gz has
>
> AutomaticRemove "false";
> HideAutoRemove "false";
>
> as configuration directives. I've never tried them but wouldn't mind
> "true" being tested by someone and
On Tue 25 Jul 2017 at 10:02:50 -0400, Greg Wooledge wrote:
> Is there any way to permanently neuter apt-get autoremove, so that even
> if something invokes it against my will, it will *never* remove anything?
>
> And more, is there a way to get apt and apt-get to *stop* prompting me
> to run it,
On 25-07-17, Greg Wooledge wrote:
> Is there any way to permanently neuter apt-get autoremove, so that even
> if something invokes it against my will, it will *never* remove anything?
>
> And more, is there a way to get apt and apt-get to *stop* prompting me
> to run it, and *stop* spamming me
On 25-07-17, Cindy-Sue Causey wrote:
>
>
> Ok, so this is where the OP, VigneshDhanraj, could pin their kernel if
> they know the release number... That's a-suming one can pin out of
> numerical sequence...
No, that script is for automatically marking for autoremoval no longer
needed
On Tue, 25 Jul 2017 11:42:12 +0530 VigneshDhanraj G
wrote:
> Hi Team,
>
> I am using kernel 3.2.x, i know that support from wheezy will be
> stopped soon. can i upgrade to jessie with same kernel version.
>
> Is that correct way of handling?
LTS (Long Term Support)
Is there any way to permanently neuter apt-get autoremove, so that even
if something invokes it against my will, it will *never* remove anything?
And more, is there a way to get apt and apt-get to *stop* prompting me
to run it, and *stop* spamming me with a list of packages that it would
like me
On 7/25/17, Dejan Jocic wrote:
> On 25-07-17, Cindy-Sue Causey wrote:
>> On 7/25/17, Dejan Jocic wrote:
>> > On 25-07-17, Greg Wooledge wrote:
>> >> On Tue, Jul 25, 2017 at 09:41:24AM +0200, Dejan Jocic wrote:
>> >> > When you upgrade to Jessie, it will
On 25-07-17, Cindy-Sue Causey wrote:
> On 7/25/17, Dejan Jocic wrote:
> > On 25-07-17, Greg Wooledge wrote:
> >> On Tue, Jul 25, 2017 at 09:41:24AM +0200, Dejan Jocic wrote:
> >> > When you upgrade to Jessie, it will install new kernel automatically.
> >> > However, it should
On 7/25/17, Dejan Jocic wrote:
> On 25-07-17, Greg Wooledge wrote:
>> On Tue, Jul 25, 2017 at 09:41:24AM +0200, Dejan Jocic wrote:
>> > When you upgrade to Jessie, it will install new kernel automatically.
>> > However, it should not remove your Wheezy kernel, because upgrading
On 25-07-17, Greg Wooledge wrote:
> On Tue, Jul 25, 2017 at 09:41:24AM +0200, Dejan Jocic wrote:
> > When you upgrade to Jessie, it will install new kernel automatically.
> > However, it should not remove your Wheezy kernel, because upgrading
> > kernels always leaves one old one there, in case
On Tue, Jul 25, 2017 at 09:41:24AM +0200, Dejan Jocic wrote:
> When you upgrade to Jessie, it will install new kernel automatically.
> However, it should not remove your Wheezy kernel, because upgrading
> kernels always leaves one old one there, in case that you can not boot
> into your new kernel
On 07/25/2017 09:12 AM, VigneshDhanraj G wrote:
> Hi Team,
>
> I am using kernel 3.2.x, i know that support from wheezy will be stopped
> soon. can i upgrade to jessie with same kernel version.
Hi Vignesh,
why do you want to use Wheezy's kernel on Jessie, custom kernel space
drivers maybe?
Thanks Dejan Jocic. Let me try and get back to you.
On Tue, Jul 25, 2017 at 1:11 PM, Dejan Jocic wrote:
> On 25-07-17, VigneshDhanraj G wrote:
> > Hi Team,
> >
> > I am using kernel 3.2.x, i know that support from wheezy will be stopped
> > soon. can i upgrade to jessie with
On 25-07-17, VigneshDhanraj G wrote:
> Hi Team,
>
> I am using kernel 3.2.x, i know that support from wheezy will be stopped
> soon. can i upgrade to jessie with same kernel version.
>
> Is that correct way of handling?
>
> Regards,
> VigneshDhanraj G
When you upgrade to Jessie, it will
28 matches
Mail list logo