On Sun, Jan 29, 2023 at 09:39:41PM -0500, Antoine Beaupré wrote:
> On 2019-03-18 21:03:14, Paul Gevers wrote:
> > Hi Antoine,
> >
> > On 16-03-2019 15:46, Antoine Beaupré wrote:
> >> On 2019-03-16 15:18:27, Paul Gevers wrote:
> >>> On Mon, 05 Jan 2015 15:59:51 -0500 Antoine =?utf-8?Q?Beaupr=C3=A9?=
On 2019-03-18 21:03:14, Paul Gevers wrote:
> Hi Antoine,
>
> On 16-03-2019 15:46, Antoine Beaupré wrote:
>> On 2019-03-16 15:18:27, Paul Gevers wrote:
>>> On Mon, 05 Jan 2015 15:59:51 -0500 Antoine =?utf-8?Q?Beaupr=C3=A9?=
>>> wrote:
On 2015-01-05 15:52:23, Andrei POPESCU wrote:
> There m
Hi Antoine,
On Mon, 18 Mar 2019 21:03:14 +0100 Paul Gevers wrote:
> > The thing is am I do not believe the Debian package restarts network
> > manager automatically. I have needrestart here for stuff like that, and
> > even *that* blocks that automated restart by default...
>
> So you changed yo
Hi Antoine,
On 16-03-2019 15:46, Antoine Beaupré wrote:
> On 2019-03-16 15:18:27, Paul Gevers wrote:
>> On Mon, 05 Jan 2015 15:59:51 -0500 Antoine =?utf-8?Q?Beaupr=C3=A9?=
>> wrote:
>>> On 2015-01-05 15:52:23, Andrei POPESCU wrote:
There might however be an issue with remote upgrades over wi
On 2019-03-16 15:18:27, Paul Gevers wrote:
> Hi,
>
> On Mon, 05 Jan 2015 15:59:51 -0500 Antoine =?utf-8?Q?Beaupr=C3=A9?=
> wrote:
>> On 2015-01-05 15:52:23, Andrei POPESCU wrote:
>> > There might however be an issue with remote upgrades over wireless
>> > connections handled by Network Manager as
Hi,
On Mon, 05 Jan 2015 15:59:51 -0500 Antoine =?utf-8?Q?Beaupr=C3=A9?=
wrote:
> On 2015-01-05 15:52:23, Andrei POPESCU wrote:
> > There might however be an issue with remote upgrades over wireless
> > connections handled by Network Manager as it still reinitializes the
> > connection on servic
On Lu, 05 ian 15, 15:59:51, Antoine Beaupré wrote:
> On 2015-01-05 15:52:23, Andrei POPESCU wrote:
> >
> > If a package is dropped from Debian's repositories it isn't removed from
> > the user's system unless some other package has a Conflicts or Breaks
> > against it, which wouldn't make much se
On 2015-01-05 15:52:23, Andrei POPESCU wrote:
> On Du, 04 ian 15, 12:25:49, Antoine Beaupré wrote:
>>
>> Maybe I'm confusing the jessie upgrade with the wheezy one, but i was
>> under the impression that a major upgrade may drop some
>> license-encumbred firmare that may eventually disable the wif
On Du, 04 ian 15, 12:25:49, Antoine Beaupré wrote:
>
> Maybe I'm confusing the jessie upgrade with the wheezy one, but i was
> under the impression that a major upgrade may drop some
> license-encumbred firmare that may eventually disable the wifi card
> during the upgrade...
If a package is drop
On 2015-01-04 12:22:07, Julien Cristau wrote:
> On Tue, Dec 30, 2014 at 10:46:14 -0500, Antoine Beaupré wrote:
>
>> Package: release-notes
>> Severity: normal
>>
>> Section 4.1.5 goes through great lengths to prepare the operator with
>> a "safe" environment. However, there is no mention of networ
On Tue, Dec 30, 2014 at 10:46:14 -0500, Antoine Beaupré wrote:
> Package: release-notes
> Severity: normal
>
> Section 4.1.5 goes through great lengths to prepare the operator with
> a "safe" environment. However, there is no mention of networking per
> se - shouldn't it be recommended that opera
Package: release-notes
Severity: normal
Section 4.1.5 goes through great lengths to prepare the operator with
a "safe" environment. However, there is no mention of networking per
se - shouldn't it be recommended that operators use a wired connexion
to do the upgrade, considering firmware often goe
12 matches
Mail list logo
