Hi,
I saw this old bug report yesterday whilst looking for the convention
for bug subjects used in dpkg.
* Changwoo Ryu [2004-07-04 06:57 +0900]:
In my ko_KR.UTF-8 locale and with the new Korean translation added
(#254590),
dpkg-query --list prints each fields in wrong columns (see attached
Hi,
thanks for applying and extending the patch that fast!
* Guillem Jover [2012-06-05 11:12 +0200]:
(a configure script would ease testing patches)
I'm not sure what you mean with this?
I did not write what I meant ;)
What I meant is that it is not obvious without looking into the
From: Carsten Hey cars...@debian.org
Date: Mon, 4 Jun 2012 09:27:01 +0200
Subject: [PATCH] s-s-d: Do not follow symlinks when creating pidfiles
---
utils/start-stop-daemon.c |8 +++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/utils/start-stop-daemon.c b/utils/start-stop
* Carsten Hey [2012-06-04 09:36 +0200]:
start-stop-daemon should not follow symlinks:
# ls -l /etc/shadow /var/run/foo.pid
-rw-r- 1 root shadow 662 Apr 10 12:20 /etc/shadow
lrwxrwxrwx 1 nobody nogroup 11 Jun 4 06:00 /var/run/foo.pid - /etc/shadow
# start-stop-daemon --start
Package: dpkg
Version: 1.16.3
Severity: wishlist
dpkg-query --list should add arch suffix to all foreign arch packages.
# dpkg --print-architecture
amd64
# dpkg -l sc | grep ' sc' | tr -s ' '
ii sc 7.16-3 Text-based spreadsheet with VI-like keybindings
# apt-get remove sc
...
* Guillem Jover [2012-05-16 22:46 +0200]:
As long as the user enabled a foreign architecture, and the
dependencies are fulfilled, I don't see why the fact that it's
foreign or not is really important.
There are cases where knowing that a package is installed from arch foo
is interesting,
* Russ Allbery [2012-02-16 14:55 -0800]:
Carsten Hey cars...@debian.org writes:
There are still files that differ that do not need to be fixed, for
example documentation that contains it's build date.
Every file that differs has to be fixed in the current multi-arch plan.
Documentation
* David Kalnischkies [2012-02-17 17:20 +0100]:
Why would it be intuitive to add a specific value for the arch attribute with
apt-get install foo # arch |= native
but remove all values of the attribute with
apt-get remove foo# arch = ~all-architectures
?
We had a similar discussion
* David Kalnischkies [2012-02-16 03:59 +0100]:
On Thu, Feb 16, 2012 at 00:39, Russ Allbery r...@debian.org wrote:
it needs to find and remove foo:*
foo:all (or foo:any) instead of foo:* would save the need to quote it.
Actually, why would that be the behavior? Why would dpkg --purge foo
* Russ Allbery [2012-02-16 10:43 -0800]:
* Users who want to co-install separate architectures will immediately
encounter a dpkg error saying that the files aren't consistent. This
means they won't be able to co-install the packages, but dpkg will
prevent any actual harm from happening.
* Aron Xu [2012-02-09 01:22 +0800]:
Some packages come with data files that endianness matters, and many
of them are large enough to split into a separate arch:all package if
endianness were not something to care about. ...
Debian Policy, begin of section 5.6.8:
| Depending on context and the
11 matches
Mail list logo
