On 06/28/2017 06:23 PM, KatolaZ wrote:
> On Wed, Jun 28, 2017 at 05:38:16PM -0400, zap wrote:
>
> [cut]
>
>> Oh the irony...
>>
>> To those on this list who are Christians or some other religious group...
>>
>> ;) anyways though thank you for helping me apply the fix on my system,
>> I don't
On Wed, 28 Jun 2017 15:59:05 -0400, Hendrik wrote in message
<20170628195905.ga...@topoi.pooq.com>:
> On Wed, Jun 28, 2017 at 07:58:13PM +0200, Arnt Karlsen wrote:
> >
> > ..if apt-get upgrade fails you, aptitude upgrade might work and
> > vice versa, they solve package conflicts differently.
On Wed, 2017-06-28 at 17:38 -0400, zap wrote:
>
> ;) anyways though thank you for helping me apply the fix on my
> system, I don't know what would have happened one way or another, but
> thank you. I downgraded successfully!
And thank you for reporting this issue so it could be resolved so
On Wed, Jun 28, 2017 at 05:38:16PM -0400, zap wrote:
[cut]
>
> Oh the irony...
>
> To those on this list who are Christians or some other religious group...
>
> ;) anyways though thank you for helping me apply the fix on my system,
> I don't know what would have happened one way or another,
On Wed, Jun 28, 2017 at 11:53:52PM +0200, Antony Stone wrote:
> On Wednesday 28 June 2017 at 23:38:16, zap wrote:
>
> > Regardless, I thank you for forking debian to remove systemd. I know
> > little of it, I only know it is less secure and slower to boot/more
> > resource intensive/slower
On Wednesday 28 June 2017 at 23:38:16, zap wrote:
> Regardless, I thank you for forking debian to remove systemd. I know
> little of it, I only know it is less secure and slower to boot/more
> resource intensive/slower download speed. but thanks I plan to donate to
> your cause perhaps even
On 06/28/2017 04:49 PM, KatolaZ wrote:
> On Wed, Jun 28, 2017 at 01:45:55PM -0700, Bruce Perens wrote:
>> On Wed, Jun 28, 2017 at 1:40 PM, KatolaZ wrote:
>>> On Wed, Jun 28, 2017 at 03:59:05PM -0400, Hendrik Boom wrote:
As far as I can tell at the moment, they might
On Wed, Jun 28, 2017 at 01:45:55PM -0700, Bruce Perens wrote:
> On Wed, Jun 28, 2017 at 1:40 PM, KatolaZ wrote:
> > On Wed, Jun 28, 2017 at 03:59:05PM -0400, Hendrik Boom wrote:
>
> >> As far as I can tell at the moment, they might even require systemd.
>
> For those of
On Wed, Jun 28, 2017 at 1:40 PM, KatolaZ wrote:
> On Wed, Jun 28, 2017 at 03:59:05PM -0400, Hendrik Boom wrote:
>> As far as I can tell at the moment, they might even require systemd.
For those of you requiring ritual purification, I recommend this St.
Ignutious video.
On Wed, Jun 28, 2017 at 03:59:05PM -0400, Hendrik Boom wrote:
> On Wed, Jun 28, 2017 at 07:58:13PM +0200, Arnt Karlsen wrote:
> >
> > ..if apt-get upgrade fails you, aptitude upgrade might work and
> > vice versa, they solve package conflicts differently.
> > Safely? See above. ;o)
>
> That's
-
From: "Hendrik Boom" <hend...@topoi.pooq.com>
To: <dng@lists.dyne.org>
Sent: Wednesday, June 28, 2017 3:59 PM
Subject: Re: [DNG] WARNING! DO NOT APT-GET UPDATE/UPGRADE ON ASCII
On Wed, Jun 28, 2017 at 07:58:13PM +0200, Arnt Karlsen wrote:
..if apt-get upgrade fails
On Wed, Jun 28, 2017 at 07:58:13PM +0200, Arnt Karlsen wrote:
>
> ..if apt-get upgrade fails you, aptitude upgrade might work and
> vice versa, they solve package conflicts differently.
> Safely? See above. ;o)
That's not the problem. aptitude and apt-get use the same
repositories.
The
On 28/06/17 17:06, KatolaZ wrote:
On Wed, Jun 28, 2017 at 10:50:07AM -0400, zap wrote:
[cut]
just wondered, Is aptitude upgrade safe?
No, it was not safe. If you have upgraded your Devuan Ascii (testing)
system in the last 24 hours, using whatever mean (apt-get, apt,
aptitude, synaptic,
On Wed, 28 Jun 2017 17:06:18 +0100, KatolaZ wrote in message
<20170628160618.gu14...@katolaz.homeunix.net>:
> On Wed, Jun 28, 2017 at 10:50:07AM -0400, zap wrote:
>
> [cut]
>
> >
> > just wondered, Is aptitude upgrade safe?
> >
>
> No, it was not safe. If you have upgraded your Devuan Ascii
Hello all,
I'd like to get a few comments in to the devuan developers before a
"fix" is decided upon. I'll also share the anecdote of how a separate
problem in the devuan infrastructure indirectly saved me from falling
victim to this incident:
1] IMO, the issue isn't really that devuan wasn't
On Wed, Jun 28, 2017 at 10:50:07AM -0400, zap wrote:
[cut]
>
> just wondered, Is aptitude upgrade safe?
>
No, it was not safe. If you have upgraded your Devuan Ascii (testing)
system in the last 24 hours, using whatever mean (apt-get, apt,
aptitude, synaptic, etc.) you might have erroneously
On 06/28/2017 08:11 AM, KatolaZ wrote:
> On Wed, Jun 28, 2017 at 02:06:43PM +0200, para...@dyne.org wrote:
>> On Wed, 28 Jun 2017, Svante Signell wrote:
>>
>>> On Wed, 2017-06-28 at 13:28 +0200, Edward Bartolo wrote:
Hi,
Too late for me. Apt logged the following information:
On Wed, Jun 28, 2017 at 02:06:43PM +0200, para...@dyne.org wrote:
> On Wed, 28 Jun 2017, Svante Signell wrote:
>
> > On Wed, 2017-06-28 at 13:28 +0200, Edward Bartolo wrote:
> > > Hi,
> > >
> > > Too late for me. Apt logged the following information:
> > >
> > > Start-Date: 2017-06-25 18:47:08
On Wed, 28 Jun 2017, Svante Signell wrote:
> On Wed, 2017-06-28 at 13:28 +0200, Edward Bartolo wrote:
> > Hi,
> >
> > Too late for me. Apt logged the following information:
> >
> > Start-Date: 2017-06-25 18:47:08
> > Commandline: apt-get upgrade
> > Upgrade: libpam0g:amd64 (1.1.8-3.5,
On Wed, 2017-06-28 at 13:28 +0200, Edward Bartolo wrote:
> Hi,
>
> Too late for me. Apt logged the following information:
>
> Start-Date: 2017-06-25 18:47:08
> Commandline: apt-get upgrade
> Upgrade: libpam0g:amd64 (1.1.8-3.5, 1.1.8-3.6), debconf:amd64 (1.5.60,
> 1.5.61),...
> [ a very long
The ascii repositories are now offline.
We will proceed sorting the issue and keeping you informed.
I hope everyone understands this is the first time we experience a
switch of Debian releases and that it is well part of our 'testing'
phase to adjust amprolla's behaviour to behave on these
Hi,
Too late for me. Apt logged the following information:
Start-Date: 2017-06-25 18:47:08
Commandline: apt-get upgrade
Upgrade: libpam0g:amd64 (1.1.8-3.5, 1.1.8-3.6), debconf:amd64 (1.5.60,
1.5.61),...
[ a very long list of packages ]
End-Date: 2017-06-25 18:55:08
--
If you can't explain it
22 matches
Mail list logo