Re: Help with the arm64 and ppc64el installation-guides needed
Hi Samuel, On 04/10/2015 07:24 PM, Samuel Thibault wrote: > Hello, > > Breno Leitao, le Fri 10 Apr 2015 17:44:01 -0300, a écrit : >> On 04/09/2015 01:13 PM, Karsten Merker wrote:> Hello everybody, >>> the release date for Jessie is near, but the installation-guide >>> does not seem to contain any arm64/ppc64el-specific information >>> yet. >> We have created this installation guide, but unfortunatelly it was not >> integrated yet. >> >> It is still on my github repository. Can you import it? > > Uh. I requested this very kind of information in september and > november, why wasn't this work (done in december) ever submitted > before? Sorry, I answered your email twice regarding this topic and never heard back. I answered it initially in 2014-11-29[1] and later in 2014-12-18[2]. In both cases I told about our patches to this repository. [1] https://lists.debian.org/debian-powerpc/2014/12/msg00016.html [2] https://lists.debian.org/debian-powerpc/2014/12/msg00025.html -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/552bbedd.9080...@br.ibm.com
Re: Help with the arm64 and ppc64el installation-guides needed
On Sun, Apr 12, 2015 at 09:43:07PM -0400, Lennart Sorensen wrote: > On Sun, Apr 12, 2015 at 08:45:50PM -0300, Thadeu Lima de Souza Cascardo wrote: > > When it comes to IBM latest servers, that are three options for > > platforms: OPAL (powernv in Linux), as PowerKVM guest, and PowerVM LPAR > > (both pseries platform in Linux). > > > > OPAL has petitboot built-in, PowerKVM uses SLOF and PowerVM uses IBM > > Open Firmware. The three are capable of booting from optical media, USB, > > and netboot. With the exception of KVM guests, when a supported > > graphical card is used, graphical installation should be an option as > > well. For KVM guests, there is offb, which should work with VNC. Should > > we enable graphical installation in the media? Or is just netboot images > > missing graphical support on d-i? > > So does this mean that PowerVM LPAR is the same as running on the bare > metal (which is the only way I have run debian on IBM pSeries systems, > specifically a p520 power6+ and a p710 power7). Certainly openfirmware > booting with grub2 is the only method I have ever used. IBM support > people sure do seem confused when they hear you have no HMC or VM or > anything else on your pSeries. Just Debian on the bare metal. > Well, bare metal has been mistakenly used to describe what I would call dedicated partition of single partition mode. People may call it bare metal, because there is no virtualized IO (in fact, there is the console), and CPU and memory resources are not shared with other partitions. But there is still a Hypervisor under the OS. It's still a PowerVM LPAR, and boot capabilities still apply as though you were sharing the server with other partitions. Hope that clarifies. Cascardo. > -- > Len Sorensen signature.asc Description: Digital signature
Re: Help with the arm64 and ppc64el installation-guides needed
Breno Leitao, le Mon 13 Apr 2015 10:04:29 -0300, a écrit : > Sorry, I answered your email twice regarding this topic and never heard back. > > I answered it initially in 2014-11-29[1] and later in 2014-12-18[2]. In both > cases > I told about our patches to this repository. I'm not subscribed to the debian-powerpc mailing list... Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150413133927.gj3...@type.bordeaux.inria.fr
Re: Help with the arm64 and ppc64el installation-guides needed
On Mon, Apr 13, 2015 at 10:26:51AM -0300, Thadeu Lima de Souza Cascardo wrote: > Well, bare metal has been mistakenly used to describe what I would call > dedicated partition of single partition mode. People may call it bare > metal, because there is no virtualized IO (in fact, there is the > console), and CPU and memory resources are not shared with other > partitions. But there is still a Hypervisor under the OS. It's still a > PowerVM LPAR, and boot capabilities still apply as though you were > sharing the server with other partitions. So PowerVM is built into the firmware and is always running? We certainly did not order or install PowerVM in any way. I do see in the boot messages that hvc is a virtual console. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150413140748.gk29...@csclub.uwaterloo.ca
Re: Help with the arm64 and ppc64el installation-guides needed
+++ Karsten Merker [2015-04-09 18:13 +0200]: > Hello everybody, > > the release date for Jessie is near, but the installation-guide > does not seem to contain any arm64/ppc64el-specific information > yet. It would be nice if those who are familiar with those > platforms could provide patches against the installation guide, > so that we can release with proper documentation. > > At least some basic information about the supported hardware > for the overview at > > https://jenkins.debian.net/userContent/installation-guide/installation-guide-arm64/en/ch02s01.html OK. I've done this. I don't seem to have commit rights (should I?) Sendingen/hardware/supported/arm.xml Transmitting file data .svn: E13: Commit failed (details follow): svn: E13: Can't open file '/svn/d-i/db/txn-current-lock': Permission denied so patch attached. I'll work on the 2nd part now. Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/ Index: en/hardware/supported/arm.xml === --- en/hardware/supported/arm.xml (revision 69739) +++ en/hardware/supported/arm.xml (working copy) @@ -6,49 +6,57 @@ -ARM systems are a lot more heterogenous than the i386/amd64-based PC -architecture, where all systems share a common system firmware (BIOS or/and -UEFI) which handles the board-specific basic hardware initialization in a -standardized way. +ARM systems are much more heterogenous than the i386/amd64-based PC +architecture, so whilst 64-bit ARM machines should boot in a +standardised way, like PCs, the situation is more complicated for +32-bit ARM machines. -The ARM architecture is used mainly in so-called systems-on-chip (SoCs). -These SoCs are designed by many different companies with vastly varying -hardware components even for the very basic functionality required to bring -the system up. Systems using them usually lack a common system firmware -interface and as a result, on ARM systems the Linux kernel has to take care -of many system-specific low-level issues which are handled by the -mainboard's BIOS in the PC world. + + +The ARM architecture is used mainly in so-called +systems-on-chip (SoCs). These SoCs are designed by many +different companies with vastly varying hardware components even for +the very basic functionality required to bring the system up. System +firmware interfaces have been increasingly standardised over time, but +especially on older hardware firmware/boot interfaces vary a great +deal, so on these systems the Linux kernel has to take care of many +system-specific low-level issues which are handled by the mainboard's +BIOS in the PC world. + +At the beginning of the ARM support in the Linux kernel, the hardware +variety resulted in the requirement of having a separate kernel for +each ARM system in contrast to the one-fits-all kernel +for PC systems. As this approach does not scale to a large number of +different systems, work was done to allow booting with a single ARM +kernel that can run on different ARM systems. Support for newer ARM +systems gets implemented in a way that allows the use of such a +multiplatform kernel, but for several older systems a seperate +specific kernel is still required. + -At the beginning of the ARM support in the Linux kernel, this resulted in -the requirement of having a seperate kernel for each ARM system in contrast -to the one-fits-all kernel for PC systems. As this approach does not -scale to a large number of different systems, work has started to be able to -provide a single ARM kernel that can run on different ARM systems. Support -for newer ARM systems gets implemented in a way that allows the use of such -a multiplatform kernel, but for several older systems a seperate specific -kernel is still required. - + Because of this, the standard &debian; distribution only supports -installation on a selected number of older ARM systems in addition to the -newer systems which are supported by the ARM multiplatform (armmp) kernel. +installation on a selected number of older 32-bit ARM systems in +addition to the newer (32 and 64 -bit) systems which are supported by +the ARM multiplatform kernels (called 'armmp' on 32-bit armhf, no +flavour name on 64-bit arm64). - The ARM architecture has evolved over time and modern ARM processors provide features which are not available in older models. &debian; therefore -provides two ARM ports, the &debian;/armel and the &debian;/armhf port. +provides three ARM ports: the &debian;/arm64 port for all 64-bit machines, and the &debian;/armel and the &debian;/armhf ports for 32-bit machines. &debian;/armel targets older ARM processors without support for a hardware floating point unit (FPU), while &debian;/armhf works only on newer ARM processors which implement at least the ARMv7 architecture with version 3 of the ARM vector floating point specification (VFPv3). &debian;/armhf makes use of the extended f
Re: Help with the arm64 and ppc64el installation-guides needed
Hi, Samuel Thibault wrote: > Holger Wansing, le Sat 11 Apr 2015 17:13:06 +0200, a écrit : > > +arch_porturl="ppc64el" > > +arch_listname="ppc64el" > > Please take care when updating these to be sure to understand > what they mean. http://www.debian.org/ports/ppc64el and > http://lists.debian.org/debian-ppc64el don't exist. I knew this! But there needs to be created a site under http://www.debian.org/ports/ for ppc64el, when ppc64el gets a release arch. The only page for ppc64el on the ports page ATM is on the debian wiki. That will have to be changed. Otherwise that above entity in our d-i manual will fail to work, no matter which arch name you choose. Holger -- Created with Sylpheed 3.2.0 under D E B I A N L I N U X 7 . 0 W H E E Z Y ! Registered Linux User #311290 - https://linuxcounter.net/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150413213742.378bdfd52d69d650cb930...@wansing-online.de
Re: Help with the arm64 and ppc64el installation-guides needed
On Mon, Apr 13, 2015 at 09:37:42PM +0200, Holger Wansing wrote: > Hi, > > Samuel Thibault wrote: > > Holger Wansing, le Sat 11 Apr 2015 17:13:06 +0200, a écrit : > > > +arch_porturl="ppc64el" > > > +arch_listname="ppc64el" > > > > Please take care when updating these to be sure to understand > > what they mean. http://www.debian.org/ports/ppc64el and > > http://lists.debian.org/debian-ppc64el don't exist. > > I knew this! > But there needs to be created a site under > http://www.debian.org/ports/ for ppc64el, when ppc64el gets a release arch. > The only page for ppc64el on the ports page ATM is on the debian wiki. > That will have to be changed. > Otherwise that above entity in our d-i manual will fail to work, no > matter which arch name you choose. I would think that just like armhf uses the debian-arm list, ppc64el will continue to use the debian-powerpc list. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150413195056.gl29...@csclub.uwaterloo.ca
Re: Help with the arm64 and ppc64el installation-guides needed
Hi, "Lennart Sorensen" wrote: > On Mon, Apr 13, 2015 at 09:37:42PM +0200, Holger Wansing wrote: > > Hi, > > > > Samuel Thibault wrote: > > > Holger Wansing, le Sat 11 Apr 2015 17:13:06 +0200, a écrit : > > > > +arch_porturl="ppc64el" > > > > +arch_listname="ppc64el" > > > > > > Please take care when updating these to be sure to understand > > > what they mean. http://www.debian.org/ports/ppc64el and > > > http://lists.debian.org/debian-ppc64el don't exist. > > > > I knew this! > > But there needs to be created a site under > > http://www.debian.org/ports/ for ppc64el, when ppc64el gets a release arch. > > The only page for ppc64el on the ports page ATM is on the debian wiki. > > That will have to be changed. > > Otherwise that above entity in our d-i manual will fail to work, no > > matter which arch name you choose. > > I would think that just like armhf uses the debian-arm list, ppc64el > will continue to use the debian-powerpc list. Yeah, I just saw that Samuel left the above entities at "powerpc". That does of course work :-) Holger -- Created with Sylpheed 3.2.0 under D E B I A N L I N U X 7 . 0 W H E E Z Y ! Registered Linux User #311290 - https://linuxcounter.net/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150413214642.d550d8d8f90c341da72e7...@wansing-online.de
Re: Help with the arm64 and ppc64el installation-guides needed
Wookey (2015-04-13): > OK. I've done this. I don't seem to have commit rights (should I?) > Sendingen/hardware/supported/arm.xml > Transmitting file data .svn: E13: Commit failed (details follow): > svn: E13: Can't open file '/svn/d-i/db/txn-current-lock': Permission > denied (I can't think of a reason why you shouldn't be part of the debian-installer group, so I've just added you.) Mraw, KiBi. signature.asc Description: Digital signature
Timing for D-I Jessie RC3
Hi, After checking with Steve, the following should do: - last uploads and unblocks for d-i related things happen this week; - the release happens before the end of the week (possibly on Friday 17th, cdimage builds after that, announce before the morning of Sunday 19th) → this gives us D-I Jessie RC3; - nothing is touched until the Jessie release on the 25th except in case of major blockers. It'd be great to have an updated installation-guide in testing for D-I Jessie RC3. I'm happy to see this package updated until the 25th. I'll be less available than usual during the 20th-24th week, that's part of the reason for the no-change-unless-strictly-necessary rule. (Another part is getting epsilonishly close to the release date.) Mraw, KiBi. (PS: Raphael cc'd so that he doesn't forget about the httpredir.d.o addition. Please let me/debian-boot@ know when it's done so that we make sure the next choose-mirror update has it.) signature.asc Description: Digital signature
Bug#767682: D-I: installer hangs on re-formatting ext4 partition (having grub in the partition boot record).
On 13 April 2015 at 18:18, Cyril Brulebois wrote: > Reinstall with btrfs (already reported as successful by Tianon on IRC, > cc'd to make sure): Indeed, I confirm that I tested a completely clean install of btrfs without issue on RC2 and that I also did a full install on ext4, then reinstalled right over the top with btrfs successfully (which is what was failing for me as well on RC1). ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cahnknk1pwnhn9w4muqz3c9s9qw+fesq61fq+tnaqcvicrb6...@mail.gmail.com
Bug#767682: D-I: installer hangs on re-formatting ext4 partition (having grub in the partition boot record).
Cyril Brulebois (2015-02-20): > Control: severity -1 important > > Axel Beckert (2015-02-04): > > Control: found -1 20150107 > > Control: severity -1 serious > > > > Hi, > > > > MARTON Jozsef wrote: > > > The formatting dialog hanged at 33%. > > > > > >* What outcome did you expect instead? > > > > > > To re-format /dev/sda3 creating a fresh ext4 filesystem. > > > > > > > > > After examining the situation and killing the mkfs.ext4 process on a > > > second virtual terminal, the installer gave a red screen error and > > > returned to the partitioning menu. > > > > > > Invoking mkfs.ext4 manually on the sencond VT, it gave the yes-no > > > question that follows (captured under the running Jessie install, so > > > mke2fs version might be different). This might be the point where > > > the installer hanged at. > > > > > > # mkfs.ext4 /dev/sda3 > > > mke2fs 1.42.12 (29-Aug-2014) > > > /dev/sda3 contains a ext4 file system > > > last mounted on / on Sat Nov 1 20:18:44 2014 > > > Proceed anyway? (y,n) > > > > We ran into this today with the current Jessie installer (labeled RC1 > > IIRC). Context was the reinstallation of a computer with the same > > partition layout. > > > > The question vanishes if a -F is passed to the mkfs.ext* call, so this > > should be an easy fix: > > > >-F Force mke2fs to create a filesystem, even if the > > specified device is not a partition on a block special > > device, or if other parameters do not make sense. In > > order to force mke2fs to create a filesystem even if the > > filesystem appears to be in use or is mounted (a truly > > dangerous thing to do), this option must be specified twice. > > > > > After formatting from the second VT, installer was able to continue > > > without re-formatting the partition. An other solution was to zero > > > out the forst few megabytes of sda3 using dd and /dev/zero to allow > > > formatting by the installer. > > > > I consider both variants unsuitable for unexperienced users. A hanging > > TUI without _any_ trace of reason, neither in the TUI no in the syslog > > nor in the partman log must not happen. > > > > Raising the severity to serious because I think that this is a > > scenario (reinstallation or retrying an incomplete installation) which > > can happen often enough and will confuse users massively due no > > feedback from the installer what happens. > > > > (D-I team: feel free to downgrade again to important if you disagree, > > but I really would like to see this fixed for Jessie.) > > I don't think those usecases warrant to have this as a serious bug. That > doesn't mean we shouldn't try and get this fixed (in wheezy and jessie). > > Any chance you could check and submit a patch? I couldn't reproduce this issue with the upcoming D-I Jessie RC3: Initial install: - automated partitioning on a whole disc (/ + swap) - proceed until the end Reinstall with ext4: - restart d-i - manual partitioning - switch the first partition (previous /) from unused to ext4, to be formatted, mounted as / - swap is automatically selected/used - proceed until the end Reinstall with btrfs (already reported as successful by Tianon on IRC, cc'd to make sure): - restart d-i - manual partitioning - switch the first partition (previous /) from unused to btrfs, to be formatted, mounted as / - swap is automatically selected/used - proceed until the end Reinstall with xfs: - restart d-i - manual partitioning - switch the first partition (previous /) from unused to btrfs, to be formatted, mounted as / - swap is automatically selected/used - proceed until the end Reinstall with ext4: - restart d-i - manual partitioning - switch the first partition (previous /) from unused to ext4, to be formatted, mounted as / - swap is automatically selected/used - proceed until the end So I think I'll stop trying to fix something I can't reproduce for D-I Jessie RC 3 (https://lists.debian.org/debian-boot/2015/04/msg00264.html) and move to other bug reports. Mraw, KiBi. signature.asc Description: Digital signature
Hints for d-i jessie RC3, part 3
Hi people, here's a third round of unblock/unblock-udeb hints for the upcoming d-i jessie RC3. Don't hesitate to ask questions if anything looks fishy. I've added urgents this time, to meet the timeline I've proposed (https://lists.debian.org/debian-boot/2015/04/msg00264.html). # l10n-only: unblock base-installer/1.154 unblock-udeb base-installer/1.154 urgent base-installer/1.154 # l10n-only: unblock console-setup/1.121 unblock-udeb console-setup/1.121 urgent console-setup/1.121 # usual lot of fixes with a new release. Checked on IRC, Ben is fine # with not waiting more (only one reported-but-not-a-showstopper # regression); mips build missing at the time of this writing: unblock linux/3.16.7-ckt9-2 unblock-udeb linux/3.16.7-ckt9-2 urgent linux/3.16.7-ckt9-2 # no objections because it's thpethial: unblock-udeb live-installer/49 # fix booting issues (#782279): unblock nobootloader/1.45 unblock-udeb nobootloader/1.45 urgent nobootloader/1.45 # l10n-only: unblock partitioner/0.55 unblock-udeb partitioner/0.55 urgent partitioner/0.55 # l10n-only: unblock partman-base/184 unblock-udeb partman-base/184 urgent partman-base/184 # just quicker than ivodd's age-days: urgent partman-basicfilesystems/113 # l10n-only: unblock user-setup/1.61 unblock-udeb user-setup/1.61 urgent user-setup/1.61 Thanks for your time. Mraw, KiBi. signature.asc Description: Digital signature
Bug#767682: D-I: installer hangs on re-formatting ext4 partition (having grub in the partition boot record).
Tianon Gravi (2015-04-13): > On 13 April 2015 at 18:18, Cyril Brulebois wrote: > > Reinstall with btrfs (already reported as successful by Tianon on IRC, > > cc'd to make sure): > > Indeed, I confirm that I tested a completely clean install of btrfs > without issue on RC2 and that I also did a full install on ext4, then > reinstalled right over the top with btrfs successfully (which is what > was failing for me as well on RC1). Oh, it sounds better if there's an improvement between identified versions! I'm not sure what's responsible for it out of the blue, but I'll happily focus on other things at the moment. ;) We can leave this bug report open for the time being, until someone yells that the issue is still there (and how to reproduce it), or someone finds out what did the trick. Mraw, KiBi. signature.asc Description: Digital signature
Bug#767682: D-I: installer hangs on re-formatting ext4 partition (having grub in the partition boot record).
On 13 April 2015 at 18:23, Cyril Brulebois wrote: > Oh, it sounds better if there's an improvement between identified > versions! I'm not sure what's responsible for it out of the blue, but > I'll happily focus on other things at the moment. ;) I _think_ it was that "-f" was added to the invocation of "mkfs.btrfs", from what I found while I was digging into the problem (which is the "accepted" solution upstream, however hammer-y it seems). ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cahnknk2kjpbr+7+crb5exg5ehxiregvg4uvn8mzbhrj_jay...@mail.gmail.com
Processing of apt-setup_0.97_amd64.changes
apt-setup_0.97_amd64.changes uploaded successfully to localhost along with the files: apt-setup_0.97.dsc apt-setup_0.97.tar.xz apt-setup-udeb_0.97_amd64.udeb apt-mirror-setup_0.97_all.udeb apt-cdrom-setup_0.97_all.udeb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1yhpvy-0004qu...@franck.debian.org
Bug#764982: marked as done (apt-setup-udeb: Backports via d-i, but not by default)
Your message dated Tue, 14 Apr 2015 01:33:49 +
with message-id
and subject line Bug#764982: fixed in apt-setup 1:0.97
has caused the Debian Bug report #764982,
regarding apt-setup-udeb: Backports via d-i, but not by default
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 ow...@bugs.debian.org
immediately.)
--
764982: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764982
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt-setup-udeb
Version: 1:0.82
Severity: normal
Hello,
Current apt-setup enable backports by default (since #691651),
contrary to Mike's report:
> Commenting them out by default would probably be a safe default.
See proposed patch, attached.
Regards
Mathieu Parent
>From 84467e85f52c7ec85cbde29f7177ed16cb24088c Mon Sep 17 00:00:00 2001
From: Mathieu Parent
Date: Sun, 12 Oct 2014 20:57:53 +0200
Subject: [PATCH] Don't enable backport by default
---
debian/apt-setup-udeb.templates | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/debian/apt-setup-udeb.templates b/debian/apt-setup-udeb.templates
index 3f54087..1843e65 100644
--- a/debian/apt-setup-udeb.templates
+++ b/debian/apt-setup-udeb.templates
@@ -75,7 +75,6 @@ _Description: Cannot access repository
Commented out entries for ${HOST} have been added to the
/etc/apt/sources.list file.
-# All services are enabled by default to allow preseeding
Template: apt-setup/services-select
Type: multiselect
Choices-C: security, updates, backports
@@ -84,7 +83,7 @@ Choices-C: security, updates, backports
# including host name. In short, KEEP THIS SHORT and, yes, that's tricky
# :sl1:
__Choices: security updates (from ${SEC_HOST}), release updates, backported software
-Default: security, updates, backports
+Default: security, updates
# :sl1:
_Description: Services to use:
Debian has two services that provide updates to releases: security and
--
2.1.1
--- End Message ---
--- Begin Message ---
Source: apt-setup
Source-Version: 1:0.97
We believe that the bug you reported is fixed in the latest version of
apt-setup, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 764...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Cyril Brulebois (supplier of updated apt-setup package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Tue, 14 Apr 2015 02:58:09 +0200
Source: apt-setup
Binary: apt-setup-udeb apt-mirror-setup apt-cdrom-setup
Architecture: source amd64 all
Version: 1:0.97
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team
Changed-By: Cyril Brulebois
Description:
apt-cdrom-setup - set up a CD in sources.list (udeb)
apt-mirror-setup - set up a mirror in sources.list (udeb)
apt-setup-udeb - Configure apt (udeb)
Closes: 764982
Changes:
apt-setup (1:0.97) unstable; urgency=medium
.
* Stop enabling backports by default (Closes: #764982). Rationale:
- Packages in the base suite are preferred to the ones in the
backports suite so one needs to specifically ask for the version
from backports.
- That isn't true for packages which are only available in the
backports suite.
This means one could possibly install such packages without even
noticing they're not fetched from the base suite; and that seems
a dangerous default.
Checksums-Sha1:
2bc292b2ca947b5fb2f86c30400382180104a9c5 1766 apt-setup_0.97.dsc
37646f266b59695428a150f20c727c5f2409e246 242828 apt-setup_0.97.tar.xz
256ac57ff287caa187a4afebd65f6620d3053b49 81128 apt-setup-udeb_0.97_amd64.udeb
b59f99f6f3eeb5f209dd56602db8a429d177a2f0 84000 apt-mirror-setup_0.97_all.udeb
8c02ddcbcd307b5cd86eb78be433be7b0f9edef4 119378 apt-cdrom-setup_0.97_all.udeb
Checksums-Sha256:
32552eec38a1d394c59be68c164b3f1733680ad93d2b9195dc87489f9676880a 1766
apt-setup_0.97.dsc
f469acdce0735dc0e8a6feb172a013a60f0ca021cd7ed32907ccc151290a2494 242828
apt-setup_0.97.tar.xz
51e9ea22d0e4f15383d3b6abd9460eb2eacda5f2db3d8d7a9e2101d4cbcfbcf3 81128
apt-setup-udeb_0.97_amd64.udeb
452cb888c4738b7b8c2b3b980835b3aba2060b15d78674e621adfdf2d1083a00 84000
apt-mirror-setup_0.97_all.udeb
561cc1a6576443b21743ff2c039a6b37be1c9f906229a9b25b02e7
apt-setup_0.97_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 14 Apr 2015 02:58:09 +0200 Source: apt-setup Binary: apt-setup-udeb apt-mirror-setup apt-cdrom-setup Architecture: source amd64 all Version: 1:0.97 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Cyril Brulebois Description: apt-cdrom-setup - set up a CD in sources.list (udeb) apt-mirror-setup - set up a mirror in sources.list (udeb) apt-setup-udeb - Configure apt (udeb) Closes: 764982 Changes: apt-setup (1:0.97) unstable; urgency=medium . * Stop enabling backports by default (Closes: #764982). Rationale: - Packages in the base suite are preferred to the ones in the backports suite so one needs to specifically ask for the version from backports. - That isn't true for packages which are only available in the backports suite. This means one could possibly install such packages without even noticing they're not fetched from the base suite; and that seems a dangerous default. Checksums-Sha1: 2bc292b2ca947b5fb2f86c30400382180104a9c5 1766 apt-setup_0.97.dsc 37646f266b59695428a150f20c727c5f2409e246 242828 apt-setup_0.97.tar.xz 256ac57ff287caa187a4afebd65f6620d3053b49 81128 apt-setup-udeb_0.97_amd64.udeb b59f99f6f3eeb5f209dd56602db8a429d177a2f0 84000 apt-mirror-setup_0.97_all.udeb 8c02ddcbcd307b5cd86eb78be433be7b0f9edef4 119378 apt-cdrom-setup_0.97_all.udeb Checksums-Sha256: 32552eec38a1d394c59be68c164b3f1733680ad93d2b9195dc87489f9676880a 1766 apt-setup_0.97.dsc f469acdce0735dc0e8a6feb172a013a60f0ca021cd7ed32907ccc151290a2494 242828 apt-setup_0.97.tar.xz 51e9ea22d0e4f15383d3b6abd9460eb2eacda5f2db3d8d7a9e2101d4cbcfbcf3 81128 apt-setup-udeb_0.97_amd64.udeb 452cb888c4738b7b8c2b3b980835b3aba2060b15d78674e621adfdf2d1083a00 84000 apt-mirror-setup_0.97_all.udeb 561cc1a6576443b21743ff2c039a6b37be1c9f906229a9b25b02e792c4416176 119378 apt-cdrom-setup_0.97_all.udeb Files: 2034a576c91713c9d56030f01263e58c 1766 debian-installer extra apt-setup_0.97.dsc 38b1314663b4f317c8a08fe88edfee9d 242828 debian-installer extra apt-setup_0.97.tar.xz fdb438f0312af63150a965d2d6199466 81128 debian-installer standard apt-setup-udeb_0.97_amd64.udeb 616dfc4ae1fa5d2db3b8325699b55c13 84000 debian-installer extra apt-mirror-setup_0.97_all.udeb e4ded0e436cb622e4b8f7fa646030244 119378 debian-installer extra apt-cdrom-setup_0.97_all.udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVLGnxAAoJEP+RSvDCs1Ug/eUP/0Gnq+3i0IxbJ5ouHXucoXLe xaCvEdkNejA13tG2UU6DuILLWyBkGjJQ6s9jiMs28chvGU3ObUY/sLscMat7afZE aRBgcpqKyVVbmLqQm68pV8Lwy/EDrI2gcGH/Y1Mx69o9Va9MdVwqe1Awo64ebMQH 9EoBNELtuOhEaqPuOeSsIaGnAfBXyHxqu/2kwpK1FXV+ZJfYvqmJZ6REmVlH/3K3 iSlTMnq16YR1rXT7+p2Lmo0tNPrrWZyILE6opVHorwUQSAyh4AhZwyJ5V31d8fHj kmOLLYhZ4VF+L6tEDnFTA4jkDtrEsK1LwE0Lfq+IN3As/EO4s5UdDiHYsFSfMVRt uWbBfxJznxJu78fkov4n6WTXyiEXMHANmP09Iil07Pp4oizZwx3nxOJCoXfEn5pT 2VIG6ZrOaZTzbjx6F9W4DzIJXkT9WyfHBfTHEUa0YzHO+3hyOnisN8l+hATcJgaw 0CZmK/1/Zi6n20oqBSnbOzyUiYbJzFvPymOkAl65xhds6vvjg6JVyZLf3RRXs2tW jsX+cca0wse7E3jXDXaMUuOr5IUx9bL0jfAj7IesKDBXQCsekF51xUL0IzUuhVxF febnvRapaC2MlqvDuV92640qzqri7zhT5PCsEwYzW4emAinlqDv4p8EfCH+xsnGd qL4qdCH92s9oYx+NjJZL =1NR3 -END PGP SIGNATURE- Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1yhpjz-0006dg...@franck.debian.org
Bug#781853: debian-installer: not available options install & menu from help screen
Control: tag -1 - d-i + patch pending Vaclav Ovsik (2015-04-03): > Package: debian-installer > Version: 20141002 > Severity: normal > Tags: d-i > > Dear Maintainer, > I have a PXE booting configured with Debian installer for testing/jessie > too. I noticed, that on help screen is only available label "menu". > Labels "install" and "expert" are missing. I need also the text-only > startup screen, because of DRAC SOL installations. > > I think this change is source of the problem: > https://anonscm.debian.org/cgit/d-i/debian-installer.git/commit/build/boot/x86/prompt.cfg?id=1e9968331c7938461a52d8d8ed7bd6f4431fb40b > > Reverting this change (inclusion of menu.cfg) brings install and expert back. Thanks for the pointer! I've just pushed this, the fix should be in D-I Jessie RC3: http://anonscm.debian.org/cgit/d-i/debian-installer.git/commit/?id=5ac3575 Mraw, KiBi. signature.asc Description: Digital signature
Bug#764154: debian-installer: no longer working short boot commands still listed on help pages
Holger Wansing (2014-10-05): > The help pages on the initial d-i boot screen list the short boot commands > "install", "expert", rescue", "installgui", "expertgui", rescuegui", > which are all no longer working (at least on x86). > That is on pages F3, F4, F6, F7, F8. So a fix is pending as documented in #781853. > Additionally, the help page for copyrights and warranties is no longer at F10 > (as it should be, according to the overview found on F1), it has moved to F11. I'll try and figure out why that is, but I must confess this is likely to be ignored for D-I Jessie RC3 if I don't figure it out within a few minutes. (In which case I'll open a wishlist bug report to keep track of it for a later fix.) Mraw, KiBi. signature.asc Description: Digital signature
Processed: Re: Bug#781853: debian-installer: not available options install & menu from help screen
Processing control commands: > tag -1 - d-i + patch pending Bug #781853 [debian-installer] debian-installer: not available options install & menu from help screen Bug #764154 [debian-installer] debian-installer: no longer working short boot commands still listed on help pages Bug #781992 [debian-installer] Jessie RC2 on Lenovo Thinkpad X61s, success with minor problems Removed tag(s) d-i. Removed tag(s) d-i. Removed tag(s) d-i. Bug #781853 [debian-installer] debian-installer: not available options install & menu from help screen Bug #764154 [debian-installer] debian-installer: no longer working short boot commands still listed on help pages Bug #781992 [debian-installer] Jessie RC2 on Lenovo Thinkpad X61s, success with minor problems Added tag(s) pending and patch. Added tag(s) pending and patch. Added tag(s) pending and patch. -- 764154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764154 781853: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781853 781992: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781992 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b781853.14289778097238.transcr...@bugs.debian.org
Bug#764154: debian-installer: no longer working short boot commands still listed on help pages
Package: debian-installer Version: 20140802 Cyril Brulebois (2015-04-14): > Holger Wansing (2014-10-05): > > The help pages on the initial d-i boot screen list the short boot commands > > "install", "expert", rescue", "installgui", "expertgui", rescuegui", > > which are all no longer working (at least on x86). > > That is on pages F3, F4, F6, F7, F8. > > So a fix is pending as documented in #781853. > > > Additionally, the help page for copyrights and warranties is no longer at > > F10 > > (as it should be, according to the overview found on F1), it has moved to > > F11. > > I'll try and figure out why that is, but I must confess this is likely > to be ignored for D-I Jessie RC3 if I don't figure it out within a few > minutes. (In which case I'll open a wishlist bug report to keep track > of it for a later fix.) Tests: -- for X in 20140316 20140802 20141002; do test http://ftp.fr.debian.org/debian/dists/sid/main/installer-amd64//images/netboot/mini.iso done Results: 20140316 is unaffected but the others are. Since the only changes touching build/boot between both unaffected/first affected versions are the following ones, I'm tempted to suspect something else changed (syslinux 4 → 6 happened, for example), and I won't be trying to figure out what that is since the impact is rather low. Filing a bug report accordingly as I've announced in my previous mail. In case someone figures out a patch before the end of the week, that might still end up in D-I Jessie RC3 (see https://lists.debian.org/debian-boot/2015/04/msg00264.html). Changes: | (sid-amd64-devel)kibi@wodi:~/debian-installer/installer$ git log --stat 20140316..20140802 -- build/boot/ | commit 489a4fbf607909f616989f3a6f4a2588059cc51b | Author: Ian Campbell | Date: Sat Mar 1 03:30:07 2014 + | | arm: include dtb files for netboot. | | More and more platforms require a device tree to boot. We include them in the | kernel package and the udeb, export them into the installer output as well. | | This introduces a new "medium" to the relevant architectures. This isn't a true | "medium", but since DTBs are common to the netboot/ network-console etc this | puts them at the top level. | | This is enabled for armhf and armel/kirkwood. The other armel subarchs don't | appear to produce any device tree. | | build/boot/README.device-tree | 2 ++ | 1 file changed, 2 insertions(+) | | commit bfbe903fe31da0d4398ea2cc6019e6a901f80353 | Author: Martin Michlmayr | Date: Wed Apr 2 20:29:01 2014 -0400 | | Add support for QNAP HS-210. Thanks to Kevin Woldt for the patch. | | build/boot/arm/qnap-flash-debian | 2 +- | 1 file changed, 1 insertion(+), 1 deletion(-) | | commit 0ef32ab14aba9dee627e1cc3954e8784a28fb15a | Author: Samuel Thibault | Date: Wed Mar 26 04:20:20 2014 +0100 | | Really force using 9 font width to get 720x400 video mode for crappy hardware, even if that is bogus for Unifont | | build/boot/hurd/grub-hurd-cdrom.cfg | 2 +- | build/boot/hurd/grub-hurd-pxe.cfg | 2 +- | 2 files changed, 2 insertions(+), 2 deletions(-) | | commit 1f751a4491cd6f148d6182fd189ef83a0feb80c7 | Author: Samuel Thibault | Date: Thu Mar 20 14:36:54 2014 +0100 | | Add a separate Hurd boot option for CJK support in pseudo-graphical mode | | so the default can use 720x400 resolution, instead of using 640x400 which is not | supported by some screens... | | build/boot/hurd/grub-hurd-cdrom.cfg | 5 + | build/boot/hurd/grub-hurd-pxe.cfg | 5 + | 2 files changed, 10 insertions(+) Mraw, KiBi. signature.asc Description: Digital signature
Processing of s390-netdevice_0.0.37_source.changes
s390-netdevice_0.0.37_source.changes uploaded successfully to localhost along with the files: s390-netdevice_0.0.37.dsc s390-netdevice_0.0.37.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1yhqze-0006nx...@franck.debian.org
Processing of partconf_1.47_source.changes
partconf_1.47_source.changes uploaded successfully to localhost along with the files: partconf_1.47.dsc partconf_1.47.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1yhr4v-0007ea...@franck.debian.org
partconf_1.47_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 14 Apr 2015 04:55:44 +0200 Source: partconf Binary: partconf partconf-find-partitions partconf-mkfstab Architecture: source Version: 1.47 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Cyril Brulebois Description: partconf - Configure and Mount Partitions (udeb) partconf-find-partitions - debian-installer utility for finding partitions (udeb) partconf-mkfstab - debian-installer utility for creating fstab file (udeb) Changes: partconf (1.47) unstable; urgency=medium . [ Updated translations ] * Kazakh (kk.po) by Baurzhan Muftakhidinov Checksums-Sha1: eb0ce17a22fa597b9b9523221af19643d5564004 1875 partconf_1.47.dsc 1893fab0124b110cbc4727f4183636ee8d1a 132836 partconf_1.47.tar.xz Checksums-Sha256: 6a0c3b322ab3ef066d59477b6494219e15219036ea7a9facd4b49ce2f4568ab5 1875 partconf_1.47.dsc 048ea4777ef4d2a76d4adbb54006563e7220da2641098360ad1833197a290355 132836 partconf_1.47.tar.xz Files: 47e172bb505e521f45bec95a9afd19cb 1875 debian-installer standard partconf_1.47.dsc a5d4a7b94d0ddc9cb70042da26da2e00 132836 debian-installer standard partconf_1.47.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVLIJhAAoJEP+RSvDCs1UgICgP/2YcKKzHceMQ0TgHLv/fAeMy zD2+3AYW2fSrzXb/lncFLn6eXyx5HMOGOFT3wXw7lcmW+EWQj8cJSHPzxWY2AP8f pVNHIVU5JR5+WgCSmNtQvL2cMRTCzg6+9VU1zwk9k7Su1odzF7jVGVmlyAeY1i+E qfWZicZUfEiHTT5NeKDFwC+EO5SaeSRY/cWn32jsMG8qsxiJVQH5aSnlZGu2LBDQ F99/d4O7lpM2Nqi9dF6MEKA4cPNl8yuzbAjgjuMOb9diY0bzJ876oIWESQT3A8Kq 8DR6ZebbZrfNfBNZ4TI0FIDkA995ZQZuf0Bs5oNQSpzA8FWeOGxMZ03VdOAlURFC LAdVJu75JJbVDqi5ct2yeUJI8Dunc8vGdYKxquo6FUDT4CnINvODl7D7VP5w9hGI qzCfmPEBXjcpW1oqbR6Sv1QgLVm7Bhr3OUMnamSDO8MKn4aZ6btwjrREV7nRK3PA SKmOYYrisHd75nZiThKtXca8nW2OP78/exZScS0qs6WpwrM4V2RnIQCzUVQw6Bbj FWvgMEzvit7NeT3/5HQQgwqGs6pZdmyQD7vAIDzKAyddUbEiJp6+c/4fUfCgwuVC uCDgxbLuvJFhZqLQUULiQRh2VFHBvxFuPvCPTEKzdA5BXtgF4AvZsQ2mXK81/S65 TV1V8FCRsQU3pVBZInsW =N1jl -END PGP SIGNATURE- Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1yhrhk-0004vn...@franck.debian.org
s390-netdevice_0.0.37_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 14 Apr 2015 04:51:06 +0200 Source: s390-netdevice Binary: s390-netdevice Architecture: source Version: 0.0.37 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Cyril Brulebois Description: s390-netdevice - Configure network hardware (udeb) Changes: s390-netdevice (0.0.37) unstable; urgency=medium . [ Updated translations ] * Kazakh (kk.po) by Baurzhan Muftakhidinov Checksums-Sha1: c3ad1b94179059a7f0f9795476f6871481cc8031 1786 s390-netdevice_0.0.37.dsc c9af99cf83065e4a6de1bc25d89d08bb6cac8322 108548 s390-netdevice_0.0.37.tar.xz Checksums-Sha256: 2b1f8ce9ae0a4eee7ea631fa17352bff15d9545f0e82d5e4faabb4720c863131 1786 s390-netdevice_0.0.37.dsc f151ef3897d53c183ee9f8521d24d388b1ca95f21951be1e354777f27e5a1f97 108548 s390-netdevice_0.0.37.tar.xz Files: 8733f1eef90d23c018dab487ca5300c3 1786 debian-installer standard s390-netdevice_0.0.37.dsc 9fa620eb36341a5243ab4df4576f8697 108548 debian-installer standard s390-netdevice_0.0.37.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVLIFEAAoJEP+RSvDCs1UgJ3IQAKvGB5h6N1Lr+8LqbxTITD6/ /9ssZyGp1NEpkBYD4p0LDScHici8lsumcSlfuFKryHwxIu+ANRkeRw3d0yn3G8VX op+BiHqNtuLLfqxtUxKSsJnRNcG5QZWIc48Sq3Ll9baKPSb4EuTktKlRk7WunWA1 E73IvXkt+BfEQXByeARnzL1+iTMc5Oo9Ew73AKkXGauY1iOkPOoBojRUX3YyrZkE L8xqxt72qSvK3leHHR65T2swOiJIOMR4G3RqkuFLARBQqhMXxI+8UvCA+wT/DDZC 9+OfV02CBZG+weCrcifBUHOsRdx2vPioU5rHUNMyMu19lzhGM6iwMlIGNbl8+Lhj ht3ptDdOQMma2cLVIxWMHyNqJ9Rs99H0CVW7eo1HHiq8e6C87UpiKKAUjGQyaSfw kYjGwtHIjKgBs2zBdRWKGmf2ZruJH+ZiEGTnB2GVX25+n9lsP2/+9eN/bdK2kb+8 qldMOYu2I7GFefwaSQA/3VLXBjtKMvEEYMaYvSIyyaGaZgOdYVQ0leyT1ZIzEXiW j8U45ENxO4NinmBhKqAJNBt5lm5lnga+3VMGcjjjchtuNvKpnAGi33R3nrFfZ/PK QGuXLJPZSmKHTVrCGuhELO4L8iNoz4WvKpPVFLRS5I7R1d2Tx3vAZFwD2f1nX4no PIfagwjCisBJVYbQ9qb0 =1iek -END PGP SIGNATURE- Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1yhrhp-0004wh...@franck.debian.org
Re: Hints for d-i jessie RC3, part 3
Quoting Cyril Brulebois (k...@debian.org): > Hi people, > > here's a third round of unblock/unblock-udeb hints for the upcoming d-i > jessie RC3. Don't hesitate to ask questions if anything looks fishy. > I've added urgents this time, to meet the timeline I've proposed > (https://lists.debian.org/debian-boot/2015/04/msg00264.html). I alkso have Yet Another console-setup upload (1.122) that should come for Yet Another l10n update (Croatian, this time) for two strings Of course, I'm first waiting for 1.121 to enter testing before uploading and, if an unblock can happen, that's fineand if that's not possible, the world won't fall apart. signature.asc Description: Digital signature
Re: d-i talk at mini DebConf Lyon 2015
Quoting Cyril Brulebois (k...@debian.org): > Hi people, > > I've just given a lightning talk about d-i at the mini DebConf in Lyon. > You can find the slides here: > > https://people.debian.org/~kibi/talks/2015-04-12-Lyon-mini-DebConf--lightning-talk.pdf Hey, thanks for the call for help...:-) Of course, as already said, I'll happily help anyone who would feel interested in pushing again to the wonderful world of 100%. As said, I don't intend to entirely step down: I'm still monitoring how things are going and how the various sync scripts are doing their job, of course I'm also doing the "upload fast" job, etc. What I lack time for is more the detailed tracking of each and every language, contact some "key" people (I think that several former translators just need to be waken up a bit), etc. So the person volunteering for this won't be left alone facing a giant job, but can gradually take more responsibilities in the tasK. signature.asc Description: Digital signature
