Guillem Jover writes ("Re: Important information regarding upcoming dpkg 1.16.2
upload"):
> On Mon, 2012-03-19 at 08:12:08 +0100, Raphael Hertzog wrote:
> > It has always been possible to sort-of "duplicate" a system by doing
> > "dpkg --get-selections
On Mon, 2012-03-19 at 08:12:08 +0100, Raphael Hertzog wrote:
> > In addition selections for packages unknown to dpkg will not be
> > accepted anymore.
>
> I'm not sure I understand this correctly but I'm afraid that this is a
> serious regression.
>
> It has always been possible to sort-of "dupli
Hi,
On Sun, 18 Mar 2012, Guillem Jover wrote:
> With multiarch, non-installed selections w/o an architecture, do not
> make sense, in addition there's no guarantee they match any entry
> from the available file and the db could end up with a selection that
> could not be addressed from the command
On Sun, Mar 18, 2012 at 10:16:06AM -0500, John D. Hendrickson and Sara Darnell
wrote:
> Hi, I like dselect, dpkg, and aptitude. I have a request. aptitude should
> import and export
>
> /var/lib/dpkg/status
>
> At least when asked. Right now aptitude takes awkwardly and but doesn't gi
TL;DR: aptitude does keep dpkg/status and apt/extended_states
up-to-date with the *current* state of a package, just like other
software. Please do not grok pkgstates to determine if something is
installed, etc.
On 18 March 2012 23:16, John D. Hendrickson and Sara Darnell
wrote:
> Hi, I like ds
Hi, I like dselect, dpkg, and aptitude. I have a request. aptitude should
import and export
/var/lib/dpkg/status
At least when asked. Right now aptitude takes awkwardly and but doesn't give
back.
It's not just private selections. Private methods and worse pivate status make other
Hi,
On Sat, 2012-03-10 at 09:35:39 +0100, Guillem Jover wrote:
> I'll be uploading dpkg 1.16.2 targeting unstable, by the end of
> this weekend or beginning of next week the latest (after some final
> polishing).
Unfortunately I found some issues with the selection handling and with
dselect and t
Hi,
On Wed, 14 Mar 2012, Sven Joachim wrote:
> Here is a patch adding two missing newlines on output:
Thanks.
> Note that libc-bin:amd64 is actually purged, however it remains in the
> status file (note that the "Multi-Arch: foreign" field is missing):
Ok, fixed that as well by ignoring "not-in
On 2012-03-14 11:33 +0100, Raphael Hertzog wrote:
> On Wed, 14 Mar 2012, Raphael Hertzog wrote:
>> If it outputs nothing on your system, then you're fine. Otherwise
>> it should give you some instructions to follow to bring it back to a
>> coherent state.
>
> There was a bug in the script. An upda
On Wed, 14 Mar 2012, David Greaves wrote:
> I got the following results:
>
> root@ash:~# dpkg --version
> Debian `dpkg' package management program version 1.16.1.2 (amd64).
The script is meant for people who are using a version of dpkg with
multiarch support. You're using the current sid version
Hi
I got the following results:
root@ash:~# dpkg --version
Debian `dpkg' package management program version 1.16.1.2 (amd64).
root@ash:~# perl ~david/tmp/dpkg-chk.pl | tail
PROBLEM: gcc-4.4-base:amd64 has missing info files
SOLUTION: apt-get --reinstall install gcc-4.4-base:amd64
PROBLEM: libpwl
On Wed, 14 Mar 2012, Raphael Hertzog wrote:
> If it outputs nothing on your system, then you're fine. Otherwise
> it should give you some instructions to follow to bring it back to a
> coherent state.
There was a bug in the script. An updated version is attached.
Note that it will list your forei
Hello,
For people who have been playing with multiarch and are scared by
Guillem's (uncoordinated) announce, I have written a small script
to detect whether you have been affected by one of the theoretical
problems that Guillem diagnosed (you only need libdpkg-perl and perl).
If it outputs nothin
13 matches
Mail list logo
