Your message dated Thu, 05 Jan 2012 13:42:52 +0100
with message-id <[email protected]>
and subject line Re: Bug#635436: obus: .pc path is used as an include dir when
building
has caused the Debian Bug report #635436,
regarding obus: .pc path is used as an include dir when building
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 [email protected]
immediately.)
--
635436: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635436
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: obus
Version: 1.1.2-2
Severity: normal
When looking at
https://buildd.debian.org/status/fetch.php?pkg=obus&arch=i386&ver=1.1.2-2&stamp=1310371113
and when building locally on Ubuntu, I found that a .pc dir was used as an
include dir:
-I .pc/0001-Fix-for-type-conv-2.3.0.patch/src
This seems to be a bug as anything in .pc should be properly applies to the
source.
-- System Information:
Debian Release: wheezy/sid
APT prefers oneiric-updates
APT policy: (500, 'oneiric-updates'), (500, 'oneiric-security'), (500,
'oneiric-proposed'), (500, 'oneiric'), (100, 'oneiric-backports')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-6-generic (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Version: 1.1.3-1
On 25/07/11 21:00, Micah Gersten wrote:
When looking at
https://buildd.debian.org/status/fetch.php?pkg=obus&arch=i386&ver=1.1.2-2&stamp=1310371113
and when building locally on Ubuntu, I found that a .pc dir was used
as an include dir: -I .pc/0001-Fix-for-type-conv-2.3.0.patch/src
This seems to be a bug as anything in .pc should be properly applies
to the source.
Thanks for this report. The described behaviour got fixed (somehow) in
1.1.3-1. I'm not sure what the fix was. I suspect something in oasis
(the build system) but didn't manage to reproduce this issue. We will
keep an eye on it.
Kind Regards,
--
Mehdi
--- End Message ---
