On Thu, Jun 07, 2018 at 02:23:15PM -0700, Julian Andres Klode wrote:
> On Thu, Jun 07, 2018 at 10:57:54PM +0200, Bill Allombert wrote:
> > On Thu, Jun 07, 2018 at 09:57:51AM -0700, Julian Andres Klode wrote:
> > > > Are you sure the upgrade failure are not caused by another patch that it
> > > > ap
On Thu, Jun 07, 2018 at 10:57:54PM +0200, Bill Allombert wrote:
> On Thu, Jun 07, 2018 at 09:57:51AM -0700, Julian Andres Klode wrote:
> > > Are you sure the upgrade failure are not caused by another patch that it
> > > applied by ubuntu ?
> >
> > Reasonably.
> >
> > > I have yet to see a single
On Thu, Jun 07, 2018 at 09:57:51AM -0700, Julian Andres Klode wrote:
> > Are you sure the upgrade failure are not caused by another patch that it
> > applied by ubuntu ?
>
> Reasonably.
>
> > I have yet to see a single upgrade failure in Debian proper.
>
> It's still broken. Let's say you have f
On Tue, Jun 05, 2018 at 11:16:43PM +0200, Bill Allombert wrote:
> On Tue, Jun 05, 2018 at 11:39:52AM -0700, Julian Andres Klode wrote:
> > Package: menu
> > Severity: normal
> > User: ubuntu-de...@lists.ubuntu.com
> > Usertags: origin-ubuntu
> >
> > menu currently uses interest triggers, causing p
On Tue, Jun 05, 2018 at 11:39:52AM -0700, Julian Andres Klode wrote:
> Package: menu
> Severity: normal
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu
>
> menu currently uses interest triggers, causing packages triggering it to not
> be
> configured until the trigger has run (so
Package: menu
Severity: normal
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu
menu currently uses interest triggers, causing packages triggering it to not be
configured until the trigger has run (so if A installs a menu file, dpkg
--configure A
first updates menu and then configures
6 matches
Mail list logo
