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

Bug#268709: marked as done (Architecture names should have a "${kernel}-" prefix)

Your message dated Fri, 4 Apr 2008 01:23:56 +0200
with message-id <200804040123.56765.peter_e@gmx.net>
and subject line Re: Bug#268709: Architecture names should have a "${kernel}-" prefix
has caused the Debian Bug report #268709,
regarding Architecture names should have a "${kernel}-" prefix
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

268709: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=268709
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: general
Severity: normal

Currently none of the Linux-based dpkg architecture names are using the
corresponding "linux-" prefix.  This is unconsistent with non-Linux dpkg
architectures like "hurd-i386" or "kfreebsd-i386".  In fact, it is the source
of an endless number of bugs since maintainers tend to assume "i386" means
i386, but ignore that "i386" actualy means Linux with i386.

Unfortunately, fixing the problem for existing arches is unviable in the
short term.  We can, however, prevent new arches from duplicating it.
Therefore, I intend to inform the maintainers of new ports and the maintainers
of dpkg to ensure they're aware of the problem.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: kfreebsd-i386 (i386)
Kernel: GNU/kFreeBSD 5.2.1-6
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (ignored: LC_ALL set to C)

Attachment: signature.asc
Description: Digital signature

--- End Message ---
--- Begin Message ---
dpkg supports this now, pretty much as described in this bug discussion.

--- End Message ---

Reply to: