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

Bug#323285: marked as done (/usr/lib64 should be in a separate package)



Your message dated Sat, 25 Oct 2008 02:48:47 +0200
with message-id <18690.27887.325179.388843@gargle.gargle.HOWL>
and subject line closing bugs for gcc-3.4, which won't be fixed
has caused the Debian Bug report #323285,
regarding /usr/lib64 should be in a separate package
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.)


-- 
323285: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=323285
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: libg2c0-dev
Version: 1:3.4.4-7
Severity: minor

i am not really sure why /usr/lib64 is includede in a package for a 32
bit architecture (i386 in this case). please move them to their own
package.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13-rc6
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages libg2c0-dev depends on:
ii  gcc-3.4-base                  3.4.4-7    The GNU Compiler Collection (base 
ii  libg2c0                       1:3.4.4-7  Runtime library for GNU Fortran 77

libg2c0-dev recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
tag 471831 + wontfix
tag 441104 + wontfix
tag 452115 + wontfix
tag 299188 + wontfix
tag 420533 + wontfix
tag 437537 + wontfix
tag 378107 + wontfix
tag 425053 + wontfix
tag 323285 + wontfix
tag 399100 + wontfix
thanks

closing bugs for gcc-3.4, which won't be fixed. either the binary
package is not built anymore in unstable, or we will not fix this in
3.4.



--- End Message ---

Reply to: