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

Bug#777749: marked as done (lilo-installer: x32 port)

Your message dated Fri, 03 Apr 2020 04:48:27 +0000
with message-id <E1jKEFn-0007s5-5g@fasolo.debian.org>
and subject line Bug#955507: Removed package(s) from unstable
has caused the Debian Bug report #777749,
regarding lilo-installer: x32 port
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.)


-- 
777749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777749
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: lilo-installer
Version: 1.47
Severity: wishlist
Tags: d-i patch
User: debian-x32@lists.debian.org
Usertags: port-x32 di-x32

Hi!
Please apply the attached patch.  It adds support for the x32 architecture.
The patch can be applied directly to the d-i/lilo-installer git repository.

If you want to test, as the patch-set for x32 in d-i involves around twenty
packages, you'll want ready packages from the repository at debian-x32.org.
Complete d-i isos are available at http://debian-x32.org/#debian-installer 
while debs/udebs/modified sources at http://ftp.debian-x32.org/debian/


-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (600, 'unstable'), (500, 'unreleased'), (50, 'experimental')
Architecture: x32 (x86_64)

Kernel: Linux 3.19.0-x32 (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

>From 8d71debe874d8878600a57b1ee7033b0b9c4a2fd Mon Sep 17 00:00:00 2001
From: Adam Borowski <kilobyte@angband.pl>
Date: Thu, 12 Feb 2015 07:17:08 +0100
Subject: [PATCH] Add support for x32.

---
 debian/control       | 2 +-
 debian/isinstallable | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/debian/control b/debian/control
index 24993e8..547981a 100644
--- a/debian/control
+++ b/debian/control
@@ -8,7 +8,7 @@ Vcs-Browser: http://anonscm.debian.org/gitweb/?p=d-i/lilo-installer.git
 Vcs-Git: git://anonscm.debian.org/d-i/lilo-installer.git
 
 Package: lilo-installer
-Architecture: i386 amd64
+Architecture: i386 amd64 x32
 Provides: bootable-system
 Depends: ${misc:Depends}, kernel-installer, di-utils (>= 1.15), di-utils-mapdevfs, fdisk-udeb, os-prober
 XB-Installer-Menu-Item: 7500
diff --git a/debian/isinstallable b/debian/isinstallable
index 80a7939..530e491 100755
--- a/debian/isinstallable
+++ b/debian/isinstallable
@@ -7,7 +7,7 @@ log() {
 
 ARCH="$(archdetect)"
 case $ARCH in
-    i386/mac|amd64/mac|i386/efi|amd64/efi)
+    i386/mac|amd64/mac|x32/mac|i386/efi|amd64/efi|x32/efi)
 	# LILO stands a better chance of working in BIOS compatibility mode,
 	# where /sys/firmware/efi doesn't exist.
 	# Note: depends on partman-efi to load the efivars module!
-- 
2.1.4

--- End Message ---
--- Begin Message --- 
Version: 1.62+rm

Dear submitter,

as the package lilo-installer has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/955507

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---
Reply to: