Bug#476230: libffi5: dev packages missing
Package: libffi5 Version: 3.0.5-1 Severity: important I think the -dev package of libffi is needed. On my box pkg-config fails with the following message pkg-config --cflags-only-I pygtk-2.0 Package libffi was not found in the pkg-config search path. Perhaps you should add the directory containing `libffi.pc' to the PKG_CONFIG_PATH environment variable Package 'libffi', required by 'PyGObject', not found This makes it e.g. impossible to build matplotlib. -- System Information: Debian Release: lenny/sid APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24.4 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libffi5 depends on: ii libc6 2.7-10 GNU C Library: Shared libraries libffi5 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#476230: marked as done (libffi5: dev packages missing)
Your message dated Tue, 15 Apr 2008 11:11:43 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: Bug#476230: libffi5: dev packages missing has caused the Debian Bug report #476230, regarding libffi5: dev packages missing 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.) -- 476230: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476230 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: libffi5 Version: 3.0.5-1 Severity: important I think the -dev package of libffi is needed. On my box pkg-config fails with the following message pkg-config --cflags-only-I pygtk-2.0 Package libffi was not found in the pkg-config search path. Perhaps you should add the directory containing `libffi.pc' to the PKG_CONFIG_PATH environment variable Package 'libffi', required by 'PyGObject', not found This makes it e.g. impossible to build matplotlib. -- System Information: Debian Release: lenny/sid APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24.4 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libffi5 depends on: ii libc6 2.7-10 GNU C Library: Shared libraries libffi5 recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- included in the -dev package. Manuel Metz writes: > Package: libffi5 > Version: 3.0.5-1 > Severity: important > > I think the -dev package of libffi is needed. On my box pkg-config fails > with the following message > > pkg-config --cflags-only-I pygtk-2.0 > > Package libffi was not found in the pkg-config search path. > Perhaps you should add the directory containing `libffi.pc' > to the PKG_CONFIG_PATH environment variable > Package 'libffi', required by 'PyGObject', not found > > This makes it e.g. impossible to build matplotlib. > > -- System Information: > Debian Release: lenny/sid > APT prefers oldstable > APT policy: (500, 'oldstable'), (500, 'unstable'), (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 2.6.24.4 (SMP w/2 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > > Versions of packages libffi5 depends on: > ii libc6 2.7-10 GNU C Library: Shared libraries > > libffi5 recommends no packages. > > -- no debconf information > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] --- End Message ---
Bug#476230: closed by Matthias Klose <[EMAIL PROTECTED]> (Re: Bug#476230: libffi5: dev packages missing)
Hi Matthias, sorry for the noise, but: I'm not exactly sure _when_ this problem occured for the first time, maybe already 10 march ? I had libffi4-dev installed before and could build matplotlib, i.e. "pkg-config --cflags-only-I pygtk-2.0" worked. Then, some time ago, it stoped working and it took me some time to figure out what went wrong - so I think it is a "bug" in the sense that a necessary dependency to the libffi-dev package is missing somewhere ? Manuel Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the libffi5 package: #476230: libffi5: dev packages missing It has been closed by Matthias Klose <[EMAIL PROTECTED]>. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Matthias Klose <[EMAIL PROTECTED]> by replying to this email. Subject: Re: Bug#476230: libffi5: dev packages missing From: Matthias Klose <[EMAIL PROTECTED]> Date: Tue, 15 Apr 2008 11:11:43 +0200 To: Manuel Metz <[EMAIL PROTECTED]>, [EMAIL PROTECTED] To: Manuel Metz <[EMAIL PROTECTED]>, [EMAIL PROTECTED] included in the -dev package. Manuel Metz writes: Package: libffi5 Version: 3.0.5-1 Severity: important I think the -dev package of libffi is needed. On my box pkg-config fails with the following message pkg-config --cflags-only-I pygtk-2.0 Package libffi was not found in the pkg-config search path. Perhaps you should add the directory containing `libffi.pc' to the PKG_CONFIG_PATH environment variable Package 'libffi', required by 'PyGObject', not found This makes it e.g. impossible to build matplotlib. -- System Information: Debian Release: lenny/sid APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24.4 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libffi5 depends on: ii libc6 2.7-10 GNU C Library: Shared libraries libffi5 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] Subject: libffi5: dev packages missing From: Manuel Metz <[EMAIL PROTECTED]> Date: Tue, 15 Apr 2008 10:17:18 +0200 To: Debian Bug Tracking System <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Package: libffi5 Version: 3.0.5-1 Severity: important I think the -dev package of libffi is needed. On my box pkg-config fails with the following message pkg-config --cflags-only-I pygtk-2.0 Package libffi was not found in the pkg-config search path. Perhaps you should add the directory containing `libffi.pc' to the PKG_CONFIG_PATH environment variable Package 'libffi', required by 'PyGObject', not found This makes it e.g. impossible to build matplotlib. -- System Information: Debian Release: lenny/sid APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24.4 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libffi5 depends on: ii libc6 2.7-10 GNU C Library: Shared libraries libffi5 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#476253: libstdc++6-4.3-doc: error in doc-base file
Package: libstdc++6-4.3-doc Version: 4.3.0-3 Severity: normal Hi, /usr/share/doc-base/libstdc++6-4.3-doc contains: Index: /usr/share/doc/libstdc++6-4.3-doc/libstdc++/html_user/index.html whereas the HTML index file is here: /usr/share/doc/libstdc++6-4.3-doc/libstdc++/html/index.html -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libstdc++6-4.3-doc depends on: ii gcc-4.3-base 4.3.0-3The GNU Compiler Collection (base libstdc++6-4.3-doc recommends no packages. -- no debconf information -- Laurent Bonnaud. http://www.lis.inpg.fr/pages_perso/bonnaud/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#476230: closed by Matthias Klose
Debian Bug Tracking System wrote: Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Debian GCC Maintainers If you wish to submit further information on this problem, please send it to [EMAIL PROTECTED], as before. Please do not send mail to [EMAIL PROTECTED] unless you wish to report a problem with the Bug-tracking system. UPDATE: Cross-checking with Ubuntu I found out the following: 1) python-gobject-dev depends on libffi-dev 2) libffi4-dev provides libffi-dev So if libffi4-dev is installed, libffi-dev is not forced to be installed. Manuel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed (with 1 errors): #248172 Fixed upstream
Processing commands for [EMAIL PROTECTED]: > retitle 248172 [Fixed in 4.4] gnat: Legal program rejected, procedure of Bug#248172: gnat: Legal program rejected, procedure of protected object should be visible Changed Bug title to `[Fixed in 4.4] gnat: Legal program rejected, procedure of' from `gnat: Legal program rejected, procedure of protected object should be visible'. > protected object should be visible Unknown command or malformed arguments to command. > reassign 248172 gnat-4.3 Bug#248172: [Fixed in 4.4] gnat: Legal program rejected, procedure of Bug reassigned from package `gnat-4.1' to `gnat-4.3'. > tags 248172 fixed-upstream Bug#248172: [Fixed in 4.4] gnat: Legal program rejected, procedure of Tags were: upstream Tags added: fixed-upstream > tags 247560 fixed-upstream Bug#247560: [Fixed in 4.4] gnat: Illegal program not detected, RM 13.11(15) Tags were: upstream Tags added: fixed-upstream > tags 248683 fixed-upstream Bug#248683: [Fixed in 4.4] gnat: Illegal program not detected, RM 13.1(6) Tags were: upstream Tags added: fixed-upstream > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
FTBFSes with gdc and Sparc
severity 475857 normal severity 475863 normal severity 475864 normal severity 475865 normal severity 475866 normal severity 475867 normal severity 475869 normal thanks Hi, libphobos-XXX-dev contains the standard header files used by gdc. This package doesn't exist yet on Sparc and so gdc can't build D program (#461101). Instead of keeping a broken gdc package in Debian, wouldn't be more simple and logic to remove sparc from its supported arch list? Cheers, Gonéri signature.asc Description: Digital signature
Processed (with 1 errors): Re: Processed: Re: FTBFSes with gdc and Sparc
Processing commands for [EMAIL PROTECTED]: > unarchive 461101 Unarchived Bug 461101 > reopen 461101 Bug#461101: gdc: module stdio cannot read file 'std/stdio.d' Bug reopened, originator not changed. > reassign 461101 gcc-defaults Bug#461101: gdc: module stdio cannot read file 'std/stdio.d' Bug reassigned from package `gdc' to `gcc-defaults'. > found 461101 1.69 Bug#461101: gdc: module stdio cannot read file 'std/stdio.d' Bug marked as found in version 1.69. > retitle 461101 gdc should not be built on sparc Bug#461101: gdc: module stdio cannot read file 'std/stdio.d' Changed Bug title to `gdc should not be built on sparc' from `gdc: module stdio cannot read file 'std/stdio.d''. > severity 461101 normal Bug#461101: gdc should not be built on sparc Severity set to `normal' from `important' > merge 461101 475857 475863 475864 475865 475866 475867 475869 Bug#461101: gdc should not be built on sparc Bug#475857: a7xpg_0.11.dfsg1-4(sparc/unstable): module random cannot read file 'std/random.d' Mismatch - only Bugs in same state can be merged: Values for `package' don't match: #461101 has `gcc-defaults'; #475857 has `a7xpg' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: FTBFSes with gdc and Sparc
reopen 461101 reassign 461101 gcc-defaults found 461101 1.69 retitle 461101 gdc should not be built on sparc severity 461101 normal merge 461101 475857 475863 475864 475865 475866 475867 475869 thanks gdc is not broken on sparc, there is just no D runtime lib on sparc yet. gdc-4.1 and gdc-4.2 will still be built on sparc, but gdc won't be built anymore in gcc-defaults on it. On Tue, Apr 15, 2008 at 11:45:55PM +0200, Gonéri Le Bouder wrote: > severity 475857 normal > severity 475863 normal > severity 475864 normal > severity 475865 normal > severity 475866 normal > severity 475867 normal > severity 475869 normal > thanks > > Hi, > > libphobos-XXX-dev contains the standard header files used by gdc. This package > doesn't exist yet on Sparc and so gdc can't build D program (#461101). > > Instead of keeping a broken gdc package in Debian, wouldn't be more > simple and logic to remove sparc from its supported arch list? > > Cheers, > > Gonéri signature.asc Description: Digital signature
Re: FTBFSes with gdc and Sparc
On Wed, Apr 16, 2008 at 12:02:56AM +0200, Arthur Loiret wrote: Thank you Arthur for this fast reply. > gdc is not broken on sparc, there is just no D runtime lib on sparc yet. gdc on sparc has a different behaviour and doesn't react as expect for most of the users. Having a build dependency on it is a problem. For the moment, I think, the best is to remove sparc from the supported Arch for all these packages. I would have preferred to see gdc renamed to emphasize the difference between sparc gdc and the others. > gdc-4.1 and gdc-4.2 will still be built on sparc, but gdc won't be built > anymore in gcc-defaults on it. Sorry, I don't this the point with the sparc problem. Cheers, -- Gonéri Le Bouder signature.asc Description: Digital signature
Re: Approval to upload gcc-defaults 1.70?
On Sun, Apr 13, 2008 at 11:53:54PM +0200, Aurelien Jarno wrote: ... > FYI the glibc testsuite with gcc-4.3 on HPPA now gives the same results > than with gcc-4.2, except on one FPU test, due to a bug in the *glibc*. > > So it *seems* HPPA is ready for gcc-4.3 by default. Has anyone built a kernel with this version of gcc-4.3 and tried it? Can I "apt-get install -t sid gcc-4.3" on my hybrid system and get the right version? thanks, grant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: FTBFSes with gdc and Sparc
On Wed, Apr 16, 2008 at 12:30:28AM +0200, Gonéri Le Bouder wrote: > > gdc is not broken on sparc, there is just no D runtime lib on sparc yet. > gdc on sparc has a different behaviour and doesn't react as expect for > most of the users. Having a build dependency on it is a problem. For the > moment, I think, the best is to remove sparc from the supported Arch for > all these packages. I would have preferred to see gdc renamed to > emphasize the difference between sparc gdc and the others. > > > gdc-4.1 and gdc-4.2 will still be built on sparc, but gdc won't be built > > anymore in gcc-defaults on it. > Sorry, I don't this the point with the sparc problem. `gdc' is a "default" and almost empty package provided by gcc-defaults, which Depends on the default gdc version, gdc-4.1 for now. Then if you Build-Depends on `gdc' it will install `gdc-4.1' and its deps, with /usr/bin/gdc pointing to /usr/bin/gdc-4.1 (same for gdmd). If `gdc' from gcc-defaults is not built anymore on sparc, packages Build-Depending on it will FTBFS on sparc because they won't be able to install `gdc'. But people will still be able to install `gdc-4.1' and use /usr/bin/gdc-4.1 for D devel on sparc (for tango for example). signature.asc Description: Digital signature
