Your message dated Mon, 19 Nov 2007 09:32:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#186809: fixed in dpkg 1.14.8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Mon, 19 Nov 2007 09:32:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#222652: fixed in dpkg 1.14.8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Mon, 19 Nov 2007 09:32:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#186809: fixed in dpkg 1.14.8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Mon, 19 Nov 2007 09:32:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#186809: fixed in dpkg 1.14.8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Mon, 19 Nov 2007 09:32:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#383916: fixed in dpkg 1.14.8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Mon, 19 Nov 2007 09:32:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#41907: fixed in dpkg 1.14.8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Mon, 19 Nov 2007 09:32:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#178203: fixed in dpkg 1.14.8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Mon, 19 Nov 2007 09:32:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#222652: fixed in dpkg 1.14.8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Mon, 19 Nov 2007 09:32:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#186809: fixed in dpkg 1.14.8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Mon, 19 Nov 2007 09:32:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#446119: fixed in dpkg 1.14.8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Mon, 19 Nov 2007 09:32:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#41907: fixed in dpkg 1.14.8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Mon, 19 Nov 2007 09:32:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#178203: fixed in dpkg 1.14.8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Mon, 19 Nov 2007 09:32:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#222652: fixed in dpkg 1.14.8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Mon, 19 Nov 2007 09:32:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#178203: fixed in dpkg 1.14.8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Mon, 19 Nov 2007 09:32:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#109954: fixed in dpkg 1.14.8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Mon, 19 Nov 2007 09:32:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#382673: fixed in dpkg 1.14.8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Mon, 19 Nov 2007 09:32:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#222652: fixed in dpkg 1.14.8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Mon, 19 Nov 2007 09:32:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#447476: fixed in dpkg 1.14.8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Mon, 19 Nov 2007 09:32:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#178203: fixed in dpkg 1.14.8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Mon, 19 Nov 2007 09:32:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#445852: fixed in dpkg 1.14.8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Mon, 19 Nov 2007 09:32:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#109954: fixed in dpkg 1.14.8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Mon, 19 Nov 2007 09:32:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#445858: fixed in dpkg 1.14.8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
An online order is a better way to buy meds as through this method they come on
cheaper rate and delivery.
carita hodson
http://thanreason.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Tumble all night long
callahan Fallah
http://www.thanreason.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing commands for [EMAIL PROTECTED]:
reassign 451954 dpkg
Bug#451954: gettext: Package will not configure
Bug reassigned from package `gettext' to `dpkg'.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator,
On 2007-11-19 08:21:24 +0100, Sven Joachim wrote:
This is a bug in update-alternatives, not in the emacs22 packages, see
the discussion I had with jidanni in #433567. Run
update-alternatives --auto emacs to fix the symlinks.
Discussion in #433567 is confusing. The bug report says:
Package: dpkg-dev
Version: 1.14.8
Severity: normal
Exiting subroutine via last at /usr/share/perl5/Dpkg/Path.pm line 52.
Exiting subroutine via last at /usr/share/perl5/Dpkg/Path.pm line 52.
Exiting subroutine via last at /usr/share/perl5/Dpkg/Path.pm line 52.
Seen while running dpkg-shlibdeps
Package: dpkg-dev
Version: 1.14.8
Severity: serious
dpkg-gencontrol -plibaa-bin -ldebian/changelog -isp
-Tdebian/libaa-bin.substvars -Pdebian/libaa-bin
dpkg-gencontrol: warning: unknown substitution variable ${shlibs:Depends}
dpkg-gencontrol: warning: unknown substitution variable
Processing commands for [EMAIL PROTECTED]:
severity 451872 normal
Bug#451872: emacs22-gtk: replacing emacs-snapshot by emacs22 leads to broken
alternatives
Bug#76295: [U-A] update-alternative doesn't check consistency if only one
alternative
Bug#246906: /usr/sbin/update-alternatives:
To reproduce this bug, run dpkg-shlibdeps on a package that does not
yet have a debian/tmp/DEBIAN directory.
For example, this displays the perl warning. It also generates an empty
substvars file despite the binaries linking to libc6 and stuff.
[EMAIL PROTECTED]:~package/aalibdpkg-shlibdeps
severity 451872 normal
thanks
On 2007-11-19 18:41 +0100, Vincent Lefevre wrote:
Discussion in #433567 is confusing. The bug report says:
Installing emacs and removing emacs-snapshot caused this alternative
to become auto mode,
This is normal behavior: If you remove your preferred
Package: dpkg-dev
Version: 1.14.8
Severity: serious
Justification: Potentially breaks all unofficial architectures
The new dpkg-gensymbols is surely a great thing that will help the
release a lot, but it has been pushed into unstable with a *known*
problem: it potentially breaks all unofficial
Processing commands for [EMAIL PROTECTED]:
severity 452022 wishlist
Bug#452022: dpkg-dev: please ignore symbols differences on non-official
architectures
Severity set to `wishlist' from `serious'
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking
On Mon, 19 Nov 2007, Joey Hess wrote:
Exiting subroutine via last at /usr/share/perl5/Dpkg/Path.pm line 52.
On Mon, 19 Nov 2007, Joey Hess wrote:
dpkg-gencontrol -plibaa-bin -ldebian/changelog -isp
-Tdebian/libaa-bin.substvars -Pdebian/libaa-bin
dpkg-gencontrol: warning: unknown
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.10.11
package dpkg dpkg-dev dselect
Ignoring bugs not assigned to: dselect dpkg-dev dpkg
tags 452012 + pending
Bug#452012: Path.pm exits subroutine via last
There were no tags set.
Tags
severity 452022 wishlist
thanks
On Mon, 19 Nov 2007, Aurelien Jarno wrote:
Package: dpkg-dev
Version: 1.14.8
Severity: serious
Huh ?! I know it's important for you, but that doesn't make it RC.
problem: it potentially breaks all unofficial architectures, as the
symbols for those
Raphael Hertzog a écrit :
severity 452022 wishlist
thanks
On Mon, 19 Nov 2007, Aurelien Jarno wrote:
Package: dpkg-dev
Version: 1.14.8
Severity: serious
Huh ?! I know it's important for you, but that doesn't make it RC.
Even if it is not important for you that doesn't give you the
Hi,
On Mon, 2007-11-19 at 08:02:20 -0500, Avalith wrote:
Package: gettext
Version: 0.16.1-2
Severity: grave
Justification: renders package unusable
gettext will not configure because it claims to need access to
/usr/share/info/dir when /usr/share/info is a file, so the directory
cannot
Your message dated Tue, 20 Nov 2007 05:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452012: fixed in dpkg 1.14.9
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Tue, 20 Nov 2007 05:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452013: fixed in dpkg 1.14.9
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
40 matches
Mail list logo
