Hi!
On Mon, 2014-11-03 at 11:23:37 +0100, Guillem Jover wrote:
I'm planning on starting to file bug reports for the source packages
below (BCCed).
Here's the current status. I've filed bugs now with patches, or just
uploaded for orphaned ones.
Sources list (via codesearch.d.o)
Le 18 nov. 2014 17:29, Guillem Jover guil...@debian.org a écrit :
Hi!
On Mon, 2014-11-03 at 11:23:37 +0100, Guillem Jover wrote:
I'm planning on starting to file bug reports for the source packages
below (BCCed).
Here's the current status. I've filed bugs now with patches, or just
Hi!
On Mon, 2014-11-03 at 22:20:48 +0100, Niels Thykier wrote:
On 2014-11-03 11:23, Guillem Jover wrote:
I'm planning on starting to file bug reports for the source packages
below (BCCed). I've not checked (yet) how severe the dpkg-statoverride
ones are, but if most of them do not get
On Wed, Nov 5, 2014 at 21:21:05 +0100, Guillem Jover wrote:
So, yes, given the above, I'll reinstate the compat symlinks for dpkg
1.17.22. It would be nice though, if as many of the fixes for the
remaining callers could be accepted for jessie, if possible?
The cost of keeping symlinks
Hi!
I was notified by Emmanuel Bourg that there are still packages making
use of the old compat paths for u-a, dpkg-divert and dpkg-statoverride
in /usr/sbin. Those compat symlinks got removed in dpkg 1.17.0:
,---
* Remove update-alternatives, dpkg-divert and dpkg-statoverride
On Mon, Nov 03, 2014 at 11:23:37AM +0100, Guillem Jover wrote:
Colin Watson cjwat...@debian.org
man-db
openssh (U)
Thanks, I hadn't realised these paths had changed; I'm fairly sure that
maintainer script code dates from a time when dpkg-statoverride was new
and it wasn't safe to assume
On 2014-11-03 11:23, Guillem Jover wrote:
Hi!
[...]
I'm planning on starting to file bug reports for the source packages
below (BCCed). I've not checked (yet) how severe the dpkg-statoverride
ones are, but if most of them do not get fixed, I might consider
reintroducing the compat symlink
7 matches
Mail list logo
