[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#330813: marked as done ([Fixed in 4.4] cannot rename a package from an extended project)



Your message dated Tue, 02 Mar 2010 01:56:32 +0100
with message-id <87aauro81r.fsf@ludovic-brenta.org>
and subject line [Fixed in 4.4] cannot rename a package from an extended project
has caused the Debian Bug report #330813,
regarding [Fixed in 4.4] cannot rename a package from an extended project
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 responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
330813: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=330813
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: libgnatprj-3.15p
Version: 3.15p-14
Severity: normal

The GNAT project manager rejects a project file such as the following:

project P extends "Q.gpr" is
   package Compiler renames Q.Compiler;
end P;

The message from GNAT is:

"Q" is not an imported project

which is true, Q is being extended not imported.  But it seems silly
that Q's packages cannot be renamed.

adabrowse is being hit by this bug, and its project manager support
feature doesn't work.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (600, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27-2-686
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)

Versions of packages libgnatprj-3.15p depends on:
ii  libgnat-3.15p-1               3.15p-14   The GNU Ada 95 compiler runtime li

libgnatprj-3.15p recommends no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Version: 4.4.3-1

Fixed in 4.4


--- End Message ---

Reply to: