Control: close -1 4.0.0+repack-5
On Sun, Jan 06, 2019 at 09:29:30AM +0200, Adrian Bunk wrote:
> On Sat, Jan 05, 2019 at 11:10:52PM +0100, Mattia Rizzolo wrote:
> > On Sat, Jan 05, 2019 at 09:53:13PM +0100, Gilles Filippini wrote:
> >...
> > > > Incidentally, I think that would also cover the just
On Sat, 5 Jan 2019 22:11:44 +0100 pini wrote:
> On Sat, 5 Jan 2019 21:53:13 +0100 Gilles Filippini wrote:
> Oh, looking at cruft-report [1] I see that syrthes-tools still dépends on
> libmedc1v5, preventing the removal :
> * source package med-fichier version 4.0.0+repack-6 no longer builds
>
On Sat, Jan 05, 2019 at 11:10:52PM +0100, Mattia Rizzolo wrote:
> On Sat, Jan 05, 2019 at 09:53:13PM +0100, Gilles Filippini wrote:
>...
> > > Incidentally, I think that would also cover the just openend #918372,
> > > as with a Conflicts the libgmsh3 package from testing woudln't be
> > > installa
On Sat, Jan 05, 2019 at 09:53:13PM +0100, Gilles Filippini wrote:
> > > In this special case, you probably need to add
> > > Breaks+Replaces: libmed1v5 (>= 4)
> > > respectively
> > > Breaks+Replaces: libmedc1v5 (>= 4)
> > > since the versions before 4 should not have any file conflicts.
> >
>
On Sat, 5 Jan 2019 21:53:13 +0100 Gilles Filippini wrote:
> On Sat, 5 Jan 2019 17:23:11 +0100 Mattia Rizzolo wrote:
> > Control: reopen -1
> >
> > On Wed, Jan 02, 2019 at 12:45:08AM +0100, Andreas Beckmann wrote:
> > > On Sun, 30 Dec 2018 09:21:03 -0600 Kurt Kremitzki
> > > wrote:
> > > > I wa
On Sat, 5 Jan 2019 17:23:11 +0100 Mattia Rizzolo wrote:
> Control: reopen -1
>
> On Wed, Jan 02, 2019 at 12:45:08AM +0100, Andreas Beckmann wrote:
> > On Sun, 30 Dec 2018 09:21:03 -0600 Kurt Kremitzki wrote:
> > > I was just about to open a bug on this same issue. It's actually present
> > > in
Control: reopen -1
On Wed, Jan 02, 2019 at 12:45:08AM +0100, Andreas Beckmann wrote:
> On Sun, 30 Dec 2018 09:21:03 -0600 Kurt Kremitzki wrote:
> > I was just about to open a bug on this same issue. It's actually present
> > in both libmed11 and libmedc11. Instead of Conflicts, they both need
> >
On Sun, 30 Dec 2018 09:21:03 -0600 Kurt Kremitzki wrote:
> I was just about to open a bug on this same issue. It's actually present
> in both libmed11 and libmedc11. Instead of Conflicts, they both need
> Breaks + Replaces, see Policy 7.6 [1] or #906110 [2] for a similar
In this special case, you
Hi Rock & Gilles,
On Sun, 30 Dec 2018 11:01:07 + Rock Storm wrote:
> Package: libmedc11
> Severity: grave
>
> Dear Maintainer,
>
> While trying to update freecad I run into the following broken apt
> state:
>
> Preparing to unpack .../libmedc11_4.0.0+repack-3_amd64.deb ...
> Unpacking libm
Package: libmedc11
Severity: grave
Dear Maintainer,
While trying to update freecad I run into the following broken apt
state:
Preparing to unpack .../libmedc11_4.0.0+repack-3_amd64.deb ...
Unpacking libmedc11:amd64 (4.0.0+repack-3) ...
dpkg: error processing archive
/var/cache/apt/archives/libm
10 matches
Mail list logo
