Re: Re: Moving debootstrap to fully team maintained (drop Uploaders field)
Le Wed, Jul 19, 2023 at 12:00:20AM +0100, Luca Boccassi a écrit : > > Because the intention is not to claim the package for myself (far from > it! I already maintain too many...), but to open it up for uploads to > anybody who is part of the Salsa team (or wants to join it), removing > any barriers. Hi Luca, `dch --team` is your friend :) https://wiki.debian.org/TeamUpload There must be at least one personal email address in either Maintainer or Uploader (https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer), so if the current Uploaders agree, replacing them would be a service to the team, not a claim of ownership! Have a nice day, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Debian Med packaging team http://www.debian.org/devel/debian-med Tooting from home https://framapiaf.org/@charles_plessy - You do not have my permission to use this email to train an AI -
Re: Firmware GR result - what happens next?
Le Mon, Oct 03, 2022 at 12:33:20AM +0200, Mattia Rizzolo a écrit : > > I can live with an APT hook warning me if I have non-free but not > non-free-firmware, but I would prefer to even do without that. In addition, how about distributing the firmware in both 'non-free' and 'non-free-firmware' at the same time for a release or two ? Cheers, -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Tooting from work, https://mastodon.technology/@charles_plessy Tooting from home, https://framapiaf.org/@charles_plessy
Bug#872867: is ISO-3166 really the optimal list for our users?
Le Thu, Aug 24, 2017 at 06:22:16PM +0200, Daniel Pocock a écrit : > > mirrors in Kosovo. Hi again Daniel and everybody, please do not take it as a negative view on the work who set up these mirrors, but for most installations in Kosovo, do you know how their performance compares to the deb.debian.org content delivery network ? Some of the users in Kosovo may travel in other countries, or other continents, and for them having deb.debian.org by default can make their regular system updates simpler, as they would not have to manage /etc/apt/sources.list according to their geographical location. Have a nice day, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan
Bug#872867: is ISO-3166 really the optimal list for our users?
Le Wed, Aug 23, 2017 at 07:54:44PM +0200, Daniel Pocock a écrit : > > If that means a user in Kosovo is more likely to configure their system > correctly, then it is a good technical solution, similar to what I > described (leaving out the country codes for such regions and helping > them choose alternatives). > > We could also have a disclaimer, "Not all entries in this list are > officially recognized as countries, some are disputed territories that > have been included for the purpose of helping users in those regions get > the optimal configuration." > > More concise: "Select the entry from this list of regions and countries > that most closely matches your geographic location" Hi all, I think that configuring correctly the system is a goal that is much easier to follow compared with making sure the installer commmunicates a vision of the World in line with the user's views. It is quite a big limitation when the geographic location has to be known in order to configure a system correctly, especially that users are increasingly mobile. As far as I know, geographic location has been mostly an issue related to the choice of mirror, and fortunately the content delivery networks available from deb.debian.net should provide an excellent alternative to mirrors for most users. For the remaining users, while there may be cases where the best network source for packages is a country's mirror, it is by far not granted, so it is hard to avoid a recommendation such as "if the CDN is too slow, consult with other Debian users in your area or try mirrors that appear to be close to you". I do not see a mirror for Kosovo in <https://www.debian.org/mirror/list>, but this page uses the word "country" only twice, so it may be easier to have "Kosovo" in the list without having it seen as an endorsement by Debian. And since Kosovo does not have a TLD, there is no issue with names such as "ftp..debian.org". Country names may also be useful to pick a keyboard, but in this case there is no choice for Debian to make: we can just use the information provided by the maker. For languages, their presence or absence in the installer strongly depends on the availability of a translation team. I am quite sure that the bottleneck would not be ISO codes. Also, languages are easy to reconfigure after installation. Thus, we could remove from the list any locale that does not have visible support in Debian (installer + debconf + website + documentation + package descriptions + default desktop): that would ubloat the list and we could add a brief note that if users do not find their country, it is because Debian could not find support for it. So it seems that the solution would be to move away from asking the user to enter country codes ? Otherwise, the propose disclaimer sounds like a good alternative. Also, the elephant in the room is that any change will require some work... Have a nice day, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan
Re: Bug#758234: debian-policy: allow packages to depend on packages of lower priority
Le Sun, Jul 02, 2017 at 01:39:13PM -0700, Russ Allbery a écrit : > Control: tags -1 = pending > Control: tags 759260 = pending > Control: tags 660249 = pending > The upgrading-checklist entry for this change: > > > Priorities are now used only for controlling which packages > are part of a minimal or standard Debian installation and > should be selected based on functionality provided directly to > users (so nearly all shared libraries should have a priority > of optional). Packages may now depend on > packages with a lower priority. > > > The extra priority has been deprecated and > should be treated as equivalent to > optional. All extra > priorities should be changed to optional. > Packages with a priority of optional may > conflict with each other (but packages that both have a > priority of standard or higher still may > not conflict). > Thanks Russ and everybody who made it happen. I am a bit late, but I would like to make two comments. First, minor point, but I think that #196367 (Clarify Policy on priority inversion in dependencies) can also be closed by the changes. Second, I would like to propose one more clarification to the description of the "Important" priority. At the moment, it contains the following: "If the expectation is that an experienced Unix person who found it missing would say "What on earth is going on, where is foo?", it must be an important package. [Footnote: This is an important criterion because we are trying to produce, amongst other things, a free Unix.]" This has been written roughly 20 years ago and I think that as of today, the diversity of experiences and evolutions of "Unix" make this definition very hard to follow. Also, it makes the difference between "important" and "standard" quite blurry and matter of taste and opinions. In contrast, the definition of "required" is very straigthforward: the bare minimum needed to run dpkg. Interstingly, after a quick look at the list of "important" packages, I have the impression that they are close to the minimum needed to run apt over the network. If you agree with my analysis, I think that the Policy would be clearer with this alternative definition for "important": Packages which are necessary to run `apt` and use it to download other packages from the network, plus the bare minimum of commonly-expected and necessary tools to administrate the system. This does not include space-consuming features such as documentationa and multilingual support. (The last sentence above is there because man-db, debian-faq and locales are all priority:standard). Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan
Re: All D-I's debconf templates in a single HTML page.
Le Tue, Sep 06, 2016 at 09:18:58PM +0900, Charles Plessy a écrit : > > while working on preseeding D-I to make Cloud images, I found it a bit > difficult to figure out the details of this and that debconf template that is > listed in the preseed.txt example of the installation guide. Therefore, I > collated them in a single HTML page. Thank you everybody for your positive feedback. About the location of the page: Brian suggested a wiki, Philip and Cyril suggested the installer manual, and Cyril reminded of d-i.debian.org. Actually, before uploading on people.debian.org, I almost went for the wiki, in order to have a cheap revision tracking, but I was a bit short of time and it was easier for me to ouptut HTML than MoinMoin wiki syntax. One argument against the wiki is that this would suggest that the templates can be improved by collaborative editing. In general cases it is great, but here, the people writing the templates need a good awareness of the constraints of screen resolution, translation, and style that are very specific to D-I. I think that outputing DocBook XML should be straightforward, and I like Cyril's idea to have a curated version in the manual (I guess this means to cherry-pick the most relevant templates). Actually, I also considered integration in the manual before calling for comments, but I could not figure out how to integrate the translations, as the debconf PO files probably can not be used directly on the XML-converted text. Suggestions are welcome. For the full version, d-i.debian.org is definitely a good idea. Do I need to ask to be added to the d-i group ? Here are point-to-point answers that mostly serve as a kind of to-do list. Le Tue, Sep 06, 2016 at 07:18:59PM +0100, Brian Potkin a écrit : > > Choices, Choices-C and Default isn't always filled in. Indeed in some cases, they are empty in the Debconf templates and in that case I will ignore them instead of leaving them blank. In at least one case, the contents were not parsed, for a reason that I did not have time to troubleshoot. Le Wed, Sep 07, 2016 at 05:15:50PM +0200, Philip Hands a écrit : > > I guess that adding links to the source of the package that contains > each template would allow people to explore what difference setting a > particular thing really makes (by looking at the scripts that use the > value), which might make this more useful still. This is a good idea, I will try to do it. Le Wed, Sep 07, 2016 at 04:42:32PM +0100, Ian Campbell a écrit : > > Might be worth filtering out the non-question stuff, i.e. "text" and > "error" types which AFAIK are the contents of various dialog boxes and > not questions. I will try to produce filtered and unfiltered versions. Le Thu, Sep 08, 2016 at 12:37:15AM +0200, Cyril Brulebois a écrit : > > There are also '.templates*' files. Good point, thanks. Given the lack of speed of my reply to your suggestions, I hope that you will not be surprised if my further progresses are not lightning-fast. Of course, anybody is welcome to make changes to the script, and if there is interest, I can put it on collab-maint or any other place that would make sense. Have a nice day, Charles -- Charles Plessy Tsurumi, Kanagawa, Japan
All D-I's debconf templates in a single HTML page.
Hello everybody, while working on preseeding D-I to make Cloud images, I found it a bit difficult to figure out the details of this and that debconf template that is listed in the preseed.txt example of the installation guide. Therefore, I collated them in a single HTML page. https://people.debian.org/~plessy/DebianInstallerDebconfTemplates.html I would be very intereted to have some feedback on how useful this is, and if there would be a more relevant place or format to hold this information. To create the page I ran the following command in the debian-installer directory set up via `myrepos`: cat packages/*/debian/*.templates | debconfTemplateToHTML /dev/stdin debconfTemplateToHTML is a haskell script. It was great fun to write it, but please be kind with my beginner's clumsiness :) Also, the parsing is not perfect, for instance I did not care about unfolding correctly the long descriptions, ... https://people.debian.org/~plessy/debconfTemplateToHTML.hs Have a nice day, Charles -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan
Should apt-transport-https be Priority: Important ? (Asking to APT maintainers)
Dear APT maintainers, while discussing the package contents of Debian cloud instances, the question arose if it would make sense to install apt-https-transport on most Debian systems, by setting its priority to "Important". What do you think about this ? I pasted below a summary of the discussion that happened on the debian-cloud mailing list. If there are inacccuracies or if you know other pros or cons, I would be very glad to hear them in any case. Have a nice day, Charles > In brief: > > For a Debian system to use encrypted transport when downloading packages from > an APT mirror that has been appropriately set up, the packages > apt-transport-https and its dependancies must be installed. Would it be a > good > service for our users to install this by default by setting this package's > priority to "Important" ? > > The question can be rephrased as "are the gains high enough compared to the > costs ?" > > Here are the gains: > > - Using HTTPS partially hides information about what a user installs on his > machine. > > - Having HTTPS support by default means that users can switch directly to > HTTPS >anytime they wish: the system is ready, there is nothing to learn (which > package >to install) or to do (get the packages with either APT over HTTP or with >other tools and then install them with dpkg). Note that the use of plain > HTTP >may be mandatory in some environments. > > - We send a message to our users and the world, that we give a high > importance to >the defense of people's privacy. > > Here are limitations to these gains. > > - APT over HTTPS does not fully protect from surveillance, because by >analysing metadata such as the size of the transfers, one may deduce which >packages are being downloaded. Thus, it has been proposed that APT >over HTTPS is not good enough and that APT over TOR should be proposed > instead. > > - Most mirrors are not providing HTTPS yet, thus it is prematurate to enable >HTTPS support by default. (By the way, will the content delivery network >debs.debian.org provide HTTPS support ?) > > - Opinions may widely differ on the impact and appropriateness of driving > technical >choices (installing packages that most people will not use in the short > term) >with political views (defense of privacy). > > And here are the costs. > > - On a system freshly created with debootstrap, installing > apt-transport-https >eats roughly 10 Mo of space. > > - The following other packages are installed: ca-certificates krb5-locales > libcurl3-gnutls >libgssapi-krb5-2 libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 > libldap-2.4-2 libnghttp2-14 >librtmp1 libsasl2-2 libsasl2-modules libsasl2-modules-db libssh2-1 openssl. >This increases the system's complexity. > > Limitations to these costs: > > - Systems where disk space is crucial are or can be constructed by starting > from the >smaller subset of "Required" packages (supported in debootstrap by the > "minbase" option). > > - Systems where disk space costs (like cloud images) are not necessarly > billed at a >granularity where 10 Mo matters. For instance on the Amazon cloud, users > are billed >per Gigabyte, therefore installing apt-transport-https by default would >only cost in case it would cause images sizes to increase to the next > gigabyte. -- Charles Plessy Tsurumi, Kanagawa, Japan
Tentative summary (Re: Should apt-transport-https be Priority: Important ? (Re: own cloud task in tasksel?))
Le Tue, Mar 15, 2016 at 11:07:44AM -0400, Brian Gupta a écrit :
> On Mon, Mar 14, 2016 at 9:26 PM, Charles Plessy <ple...@debian.org> wrote:
> >
> > With the worldwide effort of using HTTPS everywhere, I wonder if
> > apt-transport-https shouldn't be installed by default anyway on systems with
> > network connectivity, that is, its priority should be Important. What do
> > people think about this ? Would it make sense to raise the question on
> > debian-devel ?
>
> If you think this makes sense, I'd raise it on debian-devel, and move
> the debate there.
>
> Going to all https is a worthy goal, especially now that Let's
> Encrypt has been launched.
Hi Brian and everybody,
while the discussion that happened did not lead to a consensus, I think that it
is time to summarise. And while the outcome is still uncertain, I think that
it is worthwile to move the debate to debian-devel, where more insights may be
gathered.
In brief:
For a Debian system to use encrypted transport when downloading packages from
an APT mirror that has been appropriately set up, the packages
apt-transport-https and its dependancies must be installed. Would it be a good
service for our users to install this by default by setting this package's
priority to "Important" ?
The question can be rephrased as "are the gains high enough compared to the
costs ?"
Here are the gains:
- Using HTTPS partially hides information about what a user installs on his
machine.
- Having HTTPS support by default means that users can switch directly to HTTPS
anytime they wish: the system is ready, there is nothing to learn (which
package
to install) or to do (get the packages with either APT over HTTP or with
other tools and then install them with dpkg). Note that the use of plain
HTTP
may be mandatory in some environments.
- We send a message to our users and the world, that we give a high importance
to
the defense of people's privacy.
Here are limitations to these gains.
- APT over HTTPS does not fully protect from surveillance, because by
analysing metadata such as the size of the transfers, one may deduce which
packages are being downloaded. Thus, it has been proposed that APT
over HTTPS is not good enough and that APT over TOR should be proposed
instead.
- Most mirrors are not providing HTTPS yet, thus it is prematurate to enable
HTTPS support by default. (By the way, will the content delivery network
debs.debian.org provide HTTPS support ?)
- Opinions may widely differ on the impact and appropriateness of driving
technical
choices (installing packages that most people will not use in the short term)
with political views (defense of privacy). [This may be rephrased, but this
is to reflect Marco's derogatory words ("privacy fetish") in the discussion]
And here are the costs.
- On a system freshly created with debootstrap, installing apt-transport-https
eats roughly 10 Mo of space.
- The following other packages are installed: ca-certificates krb5-locales
libcurl3-gnutls
libgssapi-krb5-2 libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0
libldap-2.4-2 libnghttp2-14
librtmp1 libsasl2-2 libsasl2-modules libsasl2-modules-db libssh2-1 openssl.
This increases the system's complexity.
Limitations to these costs:
- Systems where disk space is crucial are or can be constructed by starting
from the
smaller subset of "Required" packages (supported in debootstrap by the
"minbase" option).
- Systems where disk space costs (like cloud images) are not necessarly billed
at a
granularity where 10 Mo matters. For instance on the Amazon cloud, users
are billed
per Gigabyte, therefore installing apt-transport-https by default would
only cost in case it would cause images sizes to increase to the next
gigabyte.
Comments are very welcome. If I have forgotten something, if you think I
misrepresented
some points of view, or simply if you would like to continue the discussion
before
transfering it to debian-devel, please go ahead !
Have a nice day,
Charles
--
Charles Plessy
Tsurumi, Kanagawa, Japan
Re: Should apt-transport-https be Priority: Important ? (Re: own cloud task in tasksel?)
> On Mar 15, Adam Bolte <abo...@systemsaviour.com> wrote: > > > What does it buy you exactly? Debian repositories already do package > > signing, so we know things haven't been tampered with. Probably any Le Wed, Mar 16, 2016 at 11:52:49AM +0100, Marco d'Itri a écrit : > > I fully agree. Hi Marco, have you followed the part of the discussion related to privacy ? This is the main reason for wanting HTTPS support by default. Are you suggesting that the benefit is too small compared to the disadvantage of having slightly larger size for cloud images that contain all the packages of "Important" priority ? I noted your previous comment about the need to provide minimal images for containers and I fully agree, but this is not what is propoosed here: in my understanding, container images would typically be built with debootstrap's "minbase" variant, which only installs packages of priority "Required". On the other hand, if you think that the argument of size applies to both cases, can you comment on which packages should in your opinion have their priority corrected form Important to something lower ? Have a nice day, Charles -- Charles Plessy Tsurumi, Kanagawa, Japan
Should apt-transport-https be Priority: Important ? (Re: own cloud task in tasksel?)
Le Mon, Mar 14, 2016 at 10:34:14PM +0800, James Bromberger a écrit : > > No, not using any cml line params. My manifets has: > install: > - awscli > - python-boto > - python3-boto > - apt-transport-https [...] Hi again James and everybody, With the worldwide effort of using HTTPS everywhere, I wonder if apt-transport-https shouldn't be installed by default anyway on systems with network connectivity, that is, its priority should be Important. What do people think about this ? Would it make sense to raise the question on debian-devel ? Cheers, -- Charles
Re: own cloud task in tasksel?
Le Mon, Mar 14, 2016 at 10:34:14PM +0800, James Bromberger a écrit : > > No, not using any cml line params. My manifets has: > install: > - awscli > - python-boto > - python3-boto > - apt-transport-https > - lvm2 > - ncurses-term > - parted > - bootlogd > - cloud-init > - cloud-utils > - gdisk > - sysvinit > - systemd > - systemd-sysv > > > See: > https://github.com/JamesBromberger/bootstrap-vz/blob/master/manifests/official/ec2/ebs-jessie-amd64-hvm.yml Thanks James, now I understand that I was looking at the wrong place: the ebs-jessie-amd64-hvm.yml file in the andsens/bootstrap-vz repository ! Would it be possible to merge your changes in Anders' repository ? Otherwise, I worry that other people may be confused the same way I was. Have a nice day, -- Charles
Re: own cloud task in tasksel?
Le Sat, Mar 12, 2016 at 10:40:30PM +0800, James Bromberger a écrit : > On 12/03/2016 9:19 PM, Charles Plessy wrote: > > The Debian images on the Amazon cloud are of the "minbase" variant, and > > extra > > packages are added. (James, I lost track on where to find this information > > in > > the source code of bootstrap-vz, or on the Debian wiki, can you remind me > > the > > information ?) For the other cloud images, I am not familiar enough to be > > sure > > if they also use debootstrap's minbase variant or not. They will also > > install > > extra packages, some platform-specific, and some common with the other > > images. > > Configuration of packages included in images made by bootstrap-vz are in > the manifest file (eg manifests/official/ec2/...) for the image being > generated. It's a simple YAML file that you add the lines of what > additional package(s) you want in their own base image. Hi James, I do not see python-boto, awscli, etc in `manifests/official/ec2/ebs-jessie-amd64-hvm.yml`. Am I searching in the wrong place, or are you using ad-hoc command-line arguments ? Cheers, -- Charles
Re: own cloud task in tasksel?
Control: close 696154 Le Sat, Mar 12, 2016 at 04:15:08PM +, Anders Ingemann a écrit : > > Just a quick note (I'm on the go). EC2 images are *not* using the minbase > variant since we need networking and all that other nifty stuff for the > image to work. The only image that bootstrap-vz builds with minbase is > docker. Indeed, thanks for the correction and sorry for the noise. Which means that 'less' and other packages of Important priority are installed, therefore I can close #696154 :) Have a nice Sunday, -- Charles
Re: own cloud task in tasksel?
Hi all, Let me try to summarise, but first here are a few quotes for the context. Le Wed, Mar 09, 2016 at 04:53:59PM +0100, Marco d'Itri a écrit : > > I am very interested in working on reducing the footprint of a minimal > install: we risk losing mindshare on the containers market. Le Thu, Mar 10, 2016 at 09:14:01AM +0100, Martin Zobel-Helas a écrit : > > What are the minimal set of of packages then that should be installed in > every cloud image? > > debootstrap --variant=minbase? > debootstrap --variant=scratchbox? > > We should define this, and work on a policy then so we can publish that > policy enough in time for cloud providers to react for the stretch > release. Le Thu, Mar 10, 2016 at 10:03:33AM +0100, Marco d'Itri a écrit : > On Mar 10, Martin Zobel-Helas <zo...@debian.org> wrote: > > > What are the minimal set of of packages then that should be installed in > > every cloud image? > > Whatever is needed to boot it and let someone or something ssh on it. Le Fri, Mar 11, 2016 at 12:24:50AM +0800, James Bromberger a écrit : > > All of what people generally want installed in their EC2 instances can > be achieved with a suitable boot time UserData section that Cloud-init > installs. So long as the base image has enough base packages to fetch & > install additional packages at boot; which means it has enough base > packages to be configured to make a request to a Debian repo by some > means (socks, or explicitly defined proxy, or private repository, or > direct) with simple configuration, then that's easy. So, for example, in > an EC2 metadata environment, setting the UserData to: > > #!/bin/sh > apt-get update && apt-get install -y less unattended-updates > > One item of note that we have included in the AWS EC2 base images is the > apt-transport-https package, purely that, in environments where the > (customer organisational) security policy forbids the use of outgoing > HTTP from an instance, but permits (limited?) HTTPS, then permitting a > simple re-configuration of the base image sources.list file makes this > possible without being a chicken-and-egg problem. As far as I know, all cloud images and probably all container images are using debootstrap at one moment or another. And as far as I understand, deboostrap installs by default all packages of priority Important or higher, but can be called with variant "minbase", wich causes it to only install packages of priority "Required", plus apt. (The variant "scratchbox" would not be useful since it installs build-essential as well). The Debian images on the Amazon cloud are of the "minbase" variant, and extra packages are added. (James, I lost track on where to find this information in the source code of bootstrap-vz, or on the Debian wiki, can you remind me the information ?) For the other cloud images, I am not familiar enough to be sure if they also use debootstrap's minbase variant or not. They will also install extra packages, some platform-specific, and some common with the other images. Part of the discussion was about making cloud and container images slimmer. Here, I think that the obvious next step is to make concrete proposals of which package should have their priority reduced to "Important". Part of the discussion was about what packages should be guaranteed to be present on every Debian cloud image. This is a more difficult question. Given the current discussion, I wonder if a list of common packages is really needed. Are there examples of problematic discrepancies ? (By the way, if the EC2 image would use a https mirror, then debootstrap would automatically install apt-transport-https.) Lastly, since packages of priority Important are not installed by default, I wonder what would be the easiest way to install them on the first boot, without having to grep /var/lib/apt/lists/*_Packages. Are there suggestions for a one-line command that would make a good self-documented UserData for cloud-init ? Have a nice week-end, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan
Re: own cloud task in tasksel?
Le Thu, Mar 10, 2016 at 10:18:30AM +0100, Bastian Blank a écrit : > On Wed, Mar 09, 2016 at 11:51:58PM +0900, Charles Plessy wrote: > > > Maybe this problem can be solved by the use of metapackages ? With the > > exclusion of cloud-init, specialised kernels etc., can we converge on a > > metapackage that would represent the most frequent expectations of users of > > non-minimal cloud images in Debian and elsewhere ? > > Thats what a task is, a meta-package. Since debian-boot@l.d.o was CCed, I thought that "task" was employed to mean "a metapackage built from the tasksel source package", not just any metapackage in general. So let me rephrase: Is the proposal to go through tasksel ? If yes, what are the expected advantages over the use of an ad-hoc metapackage ? Cheers, -- Charles
Re: own cloud task in tasksel?
Hi all,
> On Mar 08, Martin Zobel-Helas <zo...@debian.org> wrote:
>
> > with more and more cloud provider publishing images, and the Debian
> > project wanting to be able to rebuild those images, i wonder if it makes
> > sense to have an own cloud task, that installs basic packages that are
> > needed by cloud images, eg. SSH, cloud-init, ...
Le Tue, Mar 08, 2016 at 06:35:45PM +0100, Marco d'Itri a écrit :
>
> I believe that this would be confusing, considering the wildly
> different definitions of "cloud" and different requirements of hosters.
> (E.g. my employer's cloud infrastructure would make no use of cloud-init.)
This reminds me #696154 ("Please install 'less' by default on official Debian
AMIs."). Basically, there is a tension between:
- providing cloud images that are a strict minimum on which to build new
images, and
- providing cloud images on which it is comfortable to work interactively via
the command-line interface after booting them.
Maybe this problem can be solved by the use of metapackages ? With the
exclusion of cloud-init, specialised kernels etc., can we converge on a
metapackage that would represent the most frequent expectations of users of
non-minimal cloud images in Debian and elsewhere ?
Back to the original question, I am not sure if tasks are a good solution to
that problem, since most cloud images are not built with debian-installer.
What would be the advantage over simple metapackages ?
(Side comment, in the Debian Med project, there is a "med-cloud" metapackage
that installs as many tools as possible, provided that each of them is small
enough and does not pull large components such as graphical user interfaces,
etc.)
For the reverse process of slimming down the images, it is a bit harder to
coordinate, but currently it is done ad-hoc with the cloud image building
tools. (Which is why we do not have less or killall in the Amazon images).
Ideally wouldn't it be good to make the whole Debian benefit of this work, by
adjusting priorities of packages accordingly ?
Have a nice day,
--
Charles Plessy
Debian Med packaging team,
http://www.debian.org/devel/debian-med
Tsurumi, Kanagawa, Japan
Bug#810301: technical reason for "merged /usr support" in debootstrap
Le Sun, Jan 10, 2016 at 06:43:27AM +0100, Christian PERRIER a écrit : > Quoting Geert Stappers (stapp...@stappers.nl): > > > * No pointers to the discussion in the opening of this B.R. > > There's a lengthy discussion in -devel and this issue about merged > /usr is something I see floting around for years. > > Random picks in the said discussion seem to show a quite good agreement. Hello everybody, I read aproximately three quarters of the thread, plus some of the reference documentation, and I agree that there is altogether a good agreement and that objections are adequately answered. Moreover, the patch set discussed here introduces the option "--no-merged-usr" to keep the old behaviour of debootstrap. So I think that Geert's objections are either answered or not valid. Have a nice day, Charles -- Charles Plessy Tsurumi, Kanagawa, Japan
Re: Cloud images with backports APT-enabled.
Le Mon, Nov 30, 2015 at 10:31:14PM +0900, Charles Plessy a écrit :
>
> I started a discussion on the debian-backports mailing list. Let's see how it
> goes.
>
> <https://lists.debian.org/debian-backports/2015/11/msg00067.html>
Hello everybody,
To summarise the original question:
some Debian Stable images prepared by us for some "cloud" systems contain a few
hand-picked packages from stable-backports (or from testing or unstable, in
which case the creation of a stable backport could be considered). To provide
a path for security and bug upgrades, the most straightforward way is to add
the stable-backports suite to APT's source list. This means that some users
may install backported packages without realising it. The Debian Backports
package states "Backports cannot be tested as extensively as Debian stable, and
backports are provided on an as-is basis, with risk of incompatibilities with
other components in Debian stable. Use with care!". Therefore, it is
controversial whether using and enabling Backports is appropriate for an image
that we call "Stable", and we wondered if something could be changed on APT's
side to prevent unintentional installation of backports.
First, let's recapitulate how APT installs backports.
The current behaviour of APT with the Backports suites is a logical consequence
of its design, and is actually not specific to backports. For instance,
similar phenomena can be observed with the "experimental" suite.
When the "install" command is called for a package, APT will consider the
versions available from the suites listed as APT data sources, plus the locally
installed package if any. Following some rules explained in the
apt_preferences manpage, each version receives a priority ("pin values"), and
APT will either install one of the highest-priority versions or do nothing.
Installing and upgrading a package are done with the same command ("install"),
following the same set of rules: from APT's point of view, there is no
conceptual difference. Likewise, there is nothing special about installing a
package from the backports suite without having selected it explicitely.
Thus, if a package in stable-backports has the highest priority, it will be
installed. The default priorities in backports suites are set to be lower than
the default priorities in stable suites, but if there is no package available
locally or from a stable suite, the backports can be the best valid candidate,
and therefore be installed.
About the user interface.
It is assumed that if the user typed "apt install foo", the user will be
satisfied with the installation of "foo". I think that this is a core point of
disagreement in the discussion on whether backports can be enabled by default
or not.
There is interest in the APT team to "make it (more) easy to rate a solution by
displaying more information". Depending on the user impact (including the fact
that they also use aptitude and other front-ends), this may open the way to
enable backports by default on stable systems. There is no timeline, but
obviously, contributions to APT development are most welcome.
In conclusion:
We are not going to enable backports by default in the short term, but I hope
that some readers, like me, strenghtened their understanding on how APT works.
Thanks everybody for following so far, and have a happy new year !
--
Charles
Re: Backports installed without prompt if not in base suite: bug or feature ?
Le Mon, Dec 14, 2015 at 11:16:24PM +0900, Charles Plessy a écrit :
>
> The current behaviour of the backports suite is deeply rooted in how APT
> works.
> Following the "install" command for a package, APT will look at the versions
> present in its cache and their priorities ("pin values"), and following the
> rules explained the apt_preferences manpage, will either install one of these
> versions or do nothing. In that sense, there is actually no difference
> between
> "installing" a package and "upgrading" a package. For backport packages
> without a counterpart in the base suite, the backports versions are valid
> candidtes and will be installed without warning. This is true as well for
> packages in the "experimental" suite.
>
> David wrote that he would like to implement a pattern system inspired from
> aptitude, and utilise this to configure and display package listings in a way
> that gives a chance to the user to cancel the installation of a backports
> package when this installation happens only because there is no version
> available in the base suite.
Hi David and everybody,
I would like to report the fruit of our discussion to the debian-cloud mailing
list. Please let me know if you think that the summary above is inaccurate.
You are also welcome to let me know if you thing it is accurate :)
Have a nice Sunday,
--
Charles
Re: Backports installed without prompt if not in base suite: bug or feature ?
Le Mon, Nov 30, 2015 at 09:38:43PM +0900, Charles Plessy a écrit :
>
> when a package is in the backports suite but not in the base suite, it will
> be installed by "apt install foo" without the need to select the backports
> suite. For this reason, jessie-backports has not been added to the default
> sources.list in new installations. (<https://bugs.debian.org/764982>)
>
> I was wondering if this was an unforseen limitation or a feature ?
Thanks everybody for your answers.
There were long emails which strengthened my understanding of APT, but I hope
that the summary can be concise.
The current behaviour of the backports suite is deeply rooted in how APT works.
Following the "install" command for a package, APT will look at the versions
present in its cache and their priorities ("pin values"), and following the
rules explained the apt_preferences manpage, will either install one of these
versions or do nothing. In that sense, there is actually no difference between
"installing" a package and "upgrading" a package. For backport packages
without a counterpart in the base suite, the backports versions are valid
candidtes and will be installed without warning. This is true as well for
packages in the "experimental" suite.
David wrote that he would like to implement a pattern system inspired from
aptitude, and utilise this to configure and display package listings in a way
that gives a chance to the user to cancel the installation of a backports
package when this installation happens only because there is no version
available in the base suite.
Would such a warning be enough for enabling stable-backports in default
installations ? Are there front-ends (especially graphical ones) in which it
would be necessary to have a similar warning ?
Have a nice day,
--
Charles Plessy
Tsurumi, Kanagawa, Japan
Bug#807772: task-xfce-desktop: MIME type for PDFs defaults to GIMP; should be Evince or similar
Control: reassign -1 xfce4 > Quoting Eirik Wixøe Svela (ews1...@gmail.com): > > Package: task-xfce-desktop > > Version: 3.31+deb8u1 > > Severity: normal > > > > I have noticed that on installing the XFCE version of Debian, PDF files are > > automatically opened in GIMP. Of course, this is easily modified by the > > user, > > but I believe it would improve the out-of-the-box usability of the config > > and > > also save beginners some effort if this curious design decision were > > changed to > > something a little more intuitive. I believe Evince, or something like that, > > comes with the default XFCE task. This seems like it would be an easy fix. Le Sun, Dec 13, 2015 at 08:41:46AM +0100, Christian PERRIER a écrit : > > The problem is finding in what package that should be > fixed. task-xfce-desktop has only the duty to depend on Xfce packages, > so this setting probably belongs to one of them Hello everybody, To put the XFCE package maintainers in the loop, I am reassigning this bug to xfce4. If the problem is affecting more desktop environments, it will be simple to reassign again... In my understanding, it is possible to provide a pre-defined list of desktop entries to break ties when more than one application can be associated to a given media type. http://standards.freedesktop.org/mime-apps-spec/mime-apps-spec-1.0.html Maybe that is the easiest solution ? Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan
Bug#797311: installation-reports: VAIO pro 13 mk2: insallation all good; problem with keyboard on vake-up after suspend.
Package: installation-reports Severity: normal -- Package-specific info: Boot method: USB Image version: http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/amd64/iso-cd/firmware-8.1.0-amd64-netinst.iso 2015-06-06 16:20 Date: 2015-08-24 Machine: VAIO pro 13 mk2 Partitions: df -Tl will do; the raw partition table is preferred udev devtmpfs 102400 10240 0% /dev tmpfstmpfs1615344 93281606016 1% /run /dev/sda6ext492499152 14845336 72931952 17% / tmpfstmpfs4038356 2084038148 1% /dev/shm tmpfstmpfs 51204 5116 1% /run/lock tmpfstmpfs403835604038356 0% /sys/fs/cgroup /dev/sda2vfat 26214450788 211356 20% /boot/efi tmpfstmpfs 807672 12 807660 1% /run/user/1000 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Installation went perfectly and the purpose of this bug report is to report this; therefore it can be closed anytime later at your convenience. I am particularly impressed that dual-boooting on with Windows 8 went perfecly without any effort: I shrank the Windows partion (in Windows with its native tool), then ran Debian Installer, and chose the assisted partitionning, which did everything for me. Second point that impressed me: the Debian Installer USB key was actually the only one accepting to boot on this machine. Other live USB distributions (Tails, Clef Agreg) failed. Not related to the installer, but this machine still has a major problem: after suspending the system (for instance by closing the lid), the keyboard does not wake up. If somebody knows how to solve this, feedback will be very welcome. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=8 (jessie) - installer build 20150422+deb8u1 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux bubu 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1 (2015-05-24) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Broadwell-U Host Bridge -OPI [8086:1604] (rev 09) lspci -knn: Subsystem: Device [1d19:0003] lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) lspci -knn: Subsystem: Device [1d19:0003] lspci -knn: 00:03.0 Audio device [0403]: Intel Corporation Broadwell-U Audio Controller [8086:160c] (rev 09) lspci -knn: Subsystem: Device [1d19:0003] lspci -knn: Kernel driver in use: snd_hda_intel lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Wildcat Point-LP USB xHCI Controller [8086:9cb1] (rev 03) lspci -knn: Subsystem: Device [1d19:0003] lspci -knn: Kernel driver in use: xhci_hcd lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Wildcat Point-LP MEI Controller #1 [8086:9cba] (rev 03) lspci -knn: Subsystem: Device [1d19:0003] lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation Wildcat Point-LP High Definition Audio Controller [8086:9ca0] (rev 03) lspci -knn: Subsystem: Device [1d19:0003] lspci -knn: Kernel driver in use: snd_hda_intel lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI Express Root Port #5 [8086:9c98] (rev e3) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 [8086:9c94] (rev e3) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI Express Root Port #4 [8086:9c96] (rev e3) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 [8086:9c90] (rev e3) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.5 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI Express Root Port #6 [8086:9c9a] (rev e3) lspci -knn: Kernel driver in use:
Bug#797340: choose-mirror: use httpredir.debian.org by default
Le Sat, Aug 29, 2015 at 01:05:07PM -0400, Michael Gilbert a écrit : Setting a default mirror without user intervention would nicely save 3 of those steps, and httpredir.debian.org is in many ways the ideal mirror selection anyway. Hi Michael, httpredir.debian.org is a great idea, and is already used on some official Debian for the Cloud, but unfortunately, it is still not accurate for Japan. === Your details, as seen by the redirector: IP: 122.249.122.82 AS: 4685 Continent: AS Country: JP Region: 40 City: Tokyo Had you requested a file to /debian/, you would have been sent to one of the following mirrors: http://ftp.kr.debian.org/debian/ === Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan
Re: Packages to install be default for Stretch
Le Tue, May 05, 2015 at 08:45:09PM +0200, Ansgar Burchardt a écrit : I would like to re-evaluate what we change by default for Stretch, that is the list of packages with priorities required, important and standard. In general my plan involves installing less, taking into consideration that requirements and expectations what should be available in containers, chroots, on servers and desktop systems has changed (at least IMHO). Thanks a lot Ansgar for tackling this. I have forwarded your email to the debian-cloud mailing list. Please do not hesitate to keep it in the loop when sending the summary or new questions. Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- 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/20150506014914.ga3...@falafel.plessy.net
[summary] Re: Bug#758234: transitive dependencies
a consensus on a) accepting that packages may depend on lower-priority packages if we find a satisfying way of b) keeping the relevant people informed of decisions that may change Debian's installation size. Therefore I have questions for you, and I would be especially pleased if your answers could converge into a final proposition that makes everybody comfortable. - Would a message to the relevant package maintainers be enough ? - Should the debian-boot and debian-cd mailing lists be notified as well ? - Is a message to debian-devel needed ? Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- 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/20141117132342.gd2...@falafel.plessy.net
Bug#758116: Please be verbose whether you would like to get your Blend promoted by tasksel
Le Tue, Aug 26, 2014 at 01:27:23PM +0200, Andreas Tille a écrit : Hi, yesterday I joined the videostream of the installer BoF at DebConf[1]. I also became a bit involved via IRC. Joey Hess raised the question about the criteria to add a Blend or not. I answered all in the list of the bug report #758116 which IMHO fits the criterion of actively maintained and some valuable content for users. I think it should be also a criterion that the team behind the Blend confirms that they are interested and so I'm hereby pinging all lists in question to ask you for confirmation. I have set Reply-To to the bug report and the general Blends list in case you are interested in further discussion with other Blends. Any input is welcome to make sure users will realise the fruits of your great work at the earliest point in time. Hi Andreas, Joey and everybody, I am sure that it would be great for Debian Med to have the Blends as first-class citizens in the Debian Installer. While it is not difficult to install the metapackages by hand, I expect that having it as an option in the installer will help convincing people to give it a try. Have a nice day, Charles -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- 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/20140826120926.ga5...@falafel.plessy.net
Bug#699390: Bug#707851: debian-policy: soften the wording recommending menu files
Le Wed, Jan 22, 2014 at 08:27:33PM +0100, Moritz Muehlenhoff a écrit : On Sun, May 12, 2013 at 02:04:01AM +0200, Michael Biebl wrote: Regarding the same issue, I talked to Christian, as tasksel co-maintainer, a while ago, to drop menu from the desktop task. If my memory serves me well, he basically agreed, but was worried, that my request came rather late into the wheezy release, so I've filed [1] and hope we can resolve that for jessie. Eight months later we're now in the jessie cycle. Can we drop menu from the desktop task now? Hi Moritz, given that the stated problem was the proximity to the release of Wheezy, and given that no further objection was raised, my point of view is that you do not need to wait for confimration from others. On my side, as a user, I definitely do not object. Have a nice week-end, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140125054555.gi24...@falafel.plessy.net
Bug#724869: base: Deadkeys do not work in Xorg French canadian keyboard
Le Tue, Dec 17, 2013 at 06:47:22PM +0100, Holger Levsen a écrit : reassign 724869 src:console-setup tags 724869 + confirmed # confirmed not by me but by an Canadian DD thanks Dear all, could it be a manifestation of http://bugs.debian.org/591459 (ibus, the default input manager on GNOME, breaks compose and dead keys). Have a nice day, -- Charles Plessy Illkirch-Graffenstaden, France -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131217181855.ga2...@falafel.plessy.net
Re: Is there a way to ssh into the debian installation process?
Le Sun, Dec 08, 2013 at 08:57:05PM -0800, Rick Thomas a écrit : Do I have to build my own CD? Or is there some way I can use a standard netinst CD, put a magic parameter on the boot command line and maybe something (what?) on a handy USB stick, and have it all fall into place? This seems to involve heavy use of pre-seeding. I don't have any experience with pre-seeding, but maybe this is the time to learn. Can you point me to an explanation of what I need to know? Hi Rick, with a proper preseed file, you can start the network console with a netinst CD, or even a more minimal netboot image. In theory, this needs only the three lines of preseed indicated on the Debian wiki (https://wiki.debian.org/DebianInstaller/NetworkConsole). In practice, if the installer has a question to ask before reaching that step, it will wait indefinitely for the answer. The Installer's guide has explanations on how to change the Debconf prioriy, pass start parameters and preseed a couple of early questions in order to avoid this. http://www.debian.org/releases/stable/amd64/apbs02.html.en You might need a bit of trial and error. If you think that something can be clarified in the documentation, I guess that patches will be welcome. Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131211010805.gh23...@falafel.plessy.net
Re: Is there a way to ssh into the debian installation process?
Le Sun, Dec 08, 2013 at 06:26:33PM -0800, Rick Thomas a écrit : Is there some way to tell the debian installer to enable an ssh server during the installation? I'd like to be able to ssh/slogin/scp to the installation process so I can retrieve log files and otherwise snoop the process when the keyboard/mouse are frozen. This is part of my pursuit of Bug#728936, which renders it impossible to do a normal Sid CD-based installation of my PowerPC Macs, because the USB keyboard and mouse are not recognized. Dear Rick, I think that https://wiki.debian.org/DebianInstaller/NetworkConsole is what you are looking for. Cheers, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131209035613.gb23...@falafel.plessy.net
Re: Changes for d-i, tasksel and d-cd
Le Thu, Oct 31, 2013 at 11:39:31PM +, Steve McIntyre a écrit : Finally, I've been getting some useful feedback on the front of exactly which images we should be making at this point, and I'm thinking of dropping most of the CD options, leaving us with: * netinst * *1* single CD with more content (xfce, more useful stuff) * DVD sets (and bigger) I'm thinking more about what we could/should fit into the useful stuff category, plus what we should call it (recommended, Debian developer toolbox, good stuff? *grin*). I remember Bdale asking for something like this last year at the debian-cd BoF at DC12, and there were general murmurs of support. Can we add sensible extra tasksel task(s) to cover the things that *we* consider useful? I'm thinking about: * misc devel utils * tools for wireless * all the bits you'd want to be able to configure your latest machine so it comes up on the network automatically so you can configure/install it further easily remotely * ... Hi Steve and everybody, I wonder what would be the overlap between everything non-graphical that one wants to put on a medium of intermediate size (in your proposal: a CD), and everything one wants to have on a cloud image that is not strictly minimal (the Ubuntu images come to my mind). If that would be large, then would it be interesting to maintain that list of packages (as a task ?) in a coordinated way. Have a nice week-end, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131102001700.ga7...@falafel.plessy.net
Wheezy Debian-Installer images on the Amazon cloud.
Hello everybody, I made some progresses with the preparation of Amazon Machine Images with a preseeded Debian-Installer, thanks to the option --root-device-name of euca-register (and it API equivalent), which either I never noticed before or is quite recent, and solved my problem of not being able to boot an image that is not installed partitionless. While I have not yet devised a preseed file that would fully automate the process, the method is already useful when using the network console (via password; for a reason I do not understand, my latest test with SSH keys did not work). Since Debian-Installer for Wheezy is not often updated, maintaining public images of it is not much work. I therefore went ahead and made one image per Amazon region, using the debian account that James Bromberger kindly prepared and uses to distribute Debian images. For the moment, please consider these images experimental; I might delete them if they have a strong defect. But my plan otherwise is to produce new ones each time the Stable installer is updated, and keep them as long as Stable is supported. The machine numbers and the explanation on how I created them are available on our wiki. https://wiki.debian.org/Cloud/AmazonEC2DebianInstaller I hope that you will find them useful ! For the moment, I only prepared amd64 images, but if you need i386 ones, please let me know, or create one yourself following the instructions, it is really simple. Have a nice day, Charles -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131027140535.gb17...@falafel.plessy.net
Bug#718855: [Pkg-xfce-devel] network-manager-gnome - full gnome recommends chain
Le Wed, Oct 09, 2013 at 07:41:00AM +0200, Yves-Alexis Perez a écrit : On mar., 2013-10-08 at 23:54 +0200, Michael Biebl wrote: Am 08.10.2013 15:02, schrieb Yves-Alexis Perez: I still don' think having gnome-control-center installed on Debian Xfce (or any !gnome) installations is a good idea, to be honest. I personally use network-manager-gnome nm-applet under Xfce because it doesn't actually needs GNOME bits, so imho either the gnome-bluetooth recommends should be dropped from network-manager-gnome, or the gnome-control-center one dropped from gnome-bluetooth. Both recommends are there for a reason. gnome-bluetooth relies heavily on gnome-control-center when you try to pair / manage devices and network-manager-applet relies on gnome-bluetooth for DUN and PAN connections. So no, I don't see those recommends go away. Then we should make tasksel stop installing recommends. Or maybe I should add a conflict in task-xfce-desktop (although I'm not so sure it works fine). It looks like that the problem is that when two desktop systems are installed, the one that pops up by default is not necessarly the one that the user wanted. If we can assume that the user is not bothered that GNOME packages are installed on the system despite they are not used, then the solution would be to ensure that if the task-xfce-desktop is the only desktop task installed, then the then the login managers should recogise it and propose XFCE a a default ? (dpkg triggers might help here.) Cheers, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131009061615.ga9...@falafel.plessy.net
Bug#637784: Please support installing on partitionless drives.
Message-Id: 201307171139.02755.hol...@layer-acht.org reassign 693107 partman-auto reassign 670702 partman-auto reassign 615074 lvm2 reassign 676172 partman severity 691046 wishlist retitle 644430 document the need for a bios boot partition when using GPT forcemerge 644430 691046 reassign 691046 release-notes reassign 683747 partman-lvm reassign 671879 partman-base thanks Hi, thank you for submitting installation reports, much appreciated. I read through all the (partman related) bugs mentioned here and am closing them now as - they (finally) indicated success and/or - I know from first hand experience that the functionality is working in Wheezy and/or - they only contained very little information and/or - they were (very) old. If I've closed a bug incorrectly please do reply or just file a new one - thats often better, as the bug log will be more clear. reopen 637784 reassign 637784 partman severity 637784 wishlist retitle 637784 Please support installing on partitionless drives. Dear Holger and everybody, I think that it would be great if somebody could extend debian-installer to install Debian on partitionless drives (like /dev/xvdb instead of /dev/xvdb1). This would open the possibility to use debian-installer for preparing some preseeded cloud images in a very simple way. Currently, this is done with ad-hoc tools developed from scratch. Using debian-installer would also ease the convergence between cloud images and standard installations, which is wanted (see http://wiki.debian.org/Teams/DPL/OfficialImages). (and please forgive me if partman is not the best package to hold this bug report) Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130717104733.ge16...@falafel.plessy.net
Feature dnsmasq as TFTP server in the installation guide ?
Hello everybody, today I installed debian via TFTP on a network where I was already running dnsmasq, and it had never been so simple: # cat __END__ /etc/dnsmasq.d/tftp enable-tftp tftp-root=/var/tftp __END__ # /etc/init.d/dnsmasq restart # mkdir /var/tftp ; cd /var/tftp # wget http://http.us.debian.org/debian/dists/wheezy/main/installer-amd64/current/images/netboot/gtk/netboot.tar.gz # tar xvfz netboot.tar.gz According to the Debian wiki, only the following other items need to be configured. interface=eth1 domain=yourdomain.com dhcp-range=192.168.0.3,192.168.0.253,255.255.255.0,1h dhcp-boot=pxelinux.0,pxeserver,192.168.0.2 pxe-service=x86PC, Install Linux, pxelinux https://wiki.debian.org/PXEBootInstall#Another_Way_-_use_Dnsmasq Nevertheless, it looks like pxe-service is not strictly necessary. I wonder if it would be worth mentioning dnsmasq proeminently it in the Installation Guide. It is a much easier setup than isc-dhcp-server or BOOTP (is that still needed ?) Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130715105256.ga31...@falafel.plessy.net
Bug#711299: debian-installer: man-db should be installed last
Le Thu, Jun 06, 2013 at 07:45:08AM +0100, Peter Krefting a écrit : Package: debian-installer Version: 20130430 Severity: wishlist I tried installing Debian 7.0 on a system with a fairly slow disk (an Asus eeepc 901), so I enabled btrfs and compression, which made the install process go very slowly. Doing so, I noticed that the man-db triggers are called very many times during installation (after almost every second package when installing the base system, and fairly often during the regular install). On my configuration, each invocation took a few seconds, causing a noticable delay (full install took about 14 hours). If man-db was installed last, its trigger would only need to be called once, which would be an enormous performance win. Dear Peter, this should be strongly reduced since man-db 2.6.3-6, which switched to the noawait type of triggers. Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130606131626.gb16...@falafel.plessy.net
Bug#707763: Installation Report, Macbook Pro, Bad Install.
Le Fri, May 10, 2013 at 07:01:54PM -0700, Geoffrey Boom a écrit : I had problems figuring out which install disk to choose. I used the AMD64 one. I really don't know how I'm supposed to know which of the installs I need. Perhaps you need a detailed help page on which one to install, including what AMD64 means. I understand it has something to do with... Processor? I'm aware that someone can find it on the web somewhere, but it would be nice to have a concentrated center of knowledge on how to install, because I was quite confused, despite my previous experience of installing systems. Dear Geoffrey, there is a page on how to install Debian on MacBooks on our wiki. http://wiki.debian.org/MacBook Have you tried to follow the instructions from here ? Have a nice week-end, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130511020927.gd15...@falafel.plessy.net
Bug#706262: installation-reports: 'suid man' dialog displays previous title 'Configuring popularity-contest'
Le Sat, Apr 27, 2013 at 11:45:41AM +, Thomas B. Ruecker a écrit : Answered 'no' to popcon: http://www.ruecker.fi/foss/debian/wheezy- netinstall/Screenshot%20from%202013-04-27%2010:36:39.png * What was the outcome of this action? This dialogue about suid man pops up: http://www.ruecker.fi/foss/debian /wheezy-netinstall/Screenshot%20from%202013-04-27%2010:36:52.png Not the /title/ still says [?] Configuring popularity-contest * What outcome did you expect instead? A title that reflects the actual content of the window. Dear Thomas, this reminds me of http://bugs.debian.org/679327, which was corrected in debconf 1.5.49. Do you think that something strange could have happened to your installation, such as using an outdated mirror, which could have caused an earlier version of debconf to be used. ? Have a nice Sunday, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130427230016.gb13...@falafel.plessy.net
Re: [PATCH] mention git, not svn, in http://d-i.alioth.d.o/doc/internals/ch01.html
Le Sun, Apr 07, 2013 at 12:26:21AM +0300, Regid Ichira a écrit : On Sat, Apr 06, 2013 at 01:05:00AM +0200, Cyril Brulebois wrote: Regid Ichira regi...@nt1.in (20/02/2013): /p div class=informalexamplepre class=screen -$ svn co svn+ssh://svn.debian.org/svn/d-i/trunk +$ git clone git://git.debian.org/d-i/debian-installer.git debian-installer /pre/div p that's slightly complex. Before the svn to git move, everything was in svn. Nowadays, some parts remain there (translations, manual, for example), while components have their own lives. Than perhaps your comment should be added too? Or files in the main git repository, under the relevant directories, saying that this part is still on the old svn repository, and can be found at some URL? Hi Regid and Cyril, How about pointing to the README in the subversion repository, which explains everything ? http://anonscm.debian.org/viewvc/d-i/trunk/README?revision=68298view=markup Have a nice week-end, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130406235115.gb16...@falafel.plessy.net
Bug#627064: partman-auto: Function create_primary_partitions() creates whole-disk partition even if smaller requested
Le Wed, Aug 03, 2011 at 05:56:34PM +0200, Robert Wolf a écrit : I have found one workaround. Simply I define LVM PV as second primary partition - installer does not create it, but there is something in $scheme_rest variable and therefore the first boot primary partition is created with command Dear Robert, I found your bug report while looking for a way to install on a whole disk instead of partitionning it... I just inspected the source repository of partman-auto and it looks like your workaround is close to the expected solution, where one would replace the LVM by a logical partition. commit 5d4e9ddbfeccf1899d330964681575570845e0ed Author: Colin Watson cjwat...@debian.org Date: Tue Jul 14 13:29:32 2009 + If we're creating primary partitions and find that we've reached the end of the recipe, use full rather than beginning as the place passed to NEW_PARTITION, thereby avoiding rounding problems and matching the process for creating logical partitions (closes: #516347, LP: #287571). r59347 http://anonscm.debian.org/gitweb/?p=d-i/partman-auto.git;a=commit;h=5d4e9ddbfeccf1899d330964681575570845e0ed Do you (and others) think that we can close that bug ? Or suggest a patch to our documentation ? Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130331131430.ga21...@plessy.org
How to install on /dev/xvdb instead of /dev/xvdb1 ?
Hello everybody, I am looking for a way to install Debian on a whole disk, for instance /dev/xvdb. I have not found a way to force partman to format without partitionning, so my hope was to use a hook after partman has been executed, to umount /target, run a simple mke2fs command, and remount /target. However, I could not find such a hook. My last hope was the deprecated partitionner that is used for mips, but it is only built for mips. Does someone have a suggestion ? Cheers, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130331132802.gc17...@falafel.plessy.net
Bug#703747: netcfg: preseed netcfg: confusion or regression about disable_dhcp, disable_autoconfig and use_autoconfig
Le Sat, Mar 23, 2013 at 02:00:14AM +0100, bilibop project a écrit : d-i netcfg/disable_autoconfig boolean true - doesn't work d-i netcfg/use_autoconfig boolean false - doesn't work d-i netcfg/disable_autoconfig boolean true d-i netcfg/use_autoconfig boolean false - doesn't work on boot cmdline: netcfg/disable_autoconfig=true netcfg/use_autoconfig=false - doesn't work Hello Quidame and everybody, isn't there a bug in netcfg.c ? /* always always always default back to autoconfig, unless you've specified * disable_autoconfig on the command line. */ debconf_get(client, netcfg/disable_autoconfig); if (!strcmp(client-value, true)) debconf_set(client, netcfg/use_autoconfig, false); else debconf_set(client, netcfg/use_autoconfig, true); To me, it seems that in plain English the above means: if autoconfig is not disabled then do not use autoconfig, which doees the contrary of what is intended. If this is the case, then this bug should be merged with #688273 before closing. Cheers, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130324094849.gb24...@falafel.plessy.net
Re: Listing the Debian Installer internals manual on http://www.debian.org/doc/devel-manuals ?
Le Thu, Mar 21, 2013 at 10:51:28AM +0100, Samuel Thibault a écrit : Charles Plessy, le Wed 20 Mar 2013 22:58:08 +0900, a écrit : Le Wed, Mar 20, 2013 at 10:52:11AM +0100, Samuel Thibault a écrit : Charles Plessy, le Wed 20 Mar 2013 11:33:24 +0900, a écrit : how about listing the Debian Installer internals manual on http://www.debian.org/doc/devel-manuals ? That can probably be useful, as we now and then get people asking how to work with the installer, even if that's indeed documented. If you like the idea I can propose a patch or commit directly. Please commit. Thanks for the feedback. Here is the patch that I am ready to commit in the absence of suggestions of problems. + pa href=http://d-i.alioth.debian.org/doc/internals/;HTML online/a./p + pa href=http://anonscm.debian.org/viewvc/d-i/trunk/manual/;DocBook source online/a./p The latter does not look like the source of the former :) http://anonscm.debian.org/gitweb/?p=d-i/debian-installer.git;a=tree;f=doc/devel/internals Thanks for pointing this out ! I corrected and commited the addition of the Debian Installer internals manual to the DDP Developers' Manuals page (/doc/devel-manuals.en.html#d-i-internals). Bon dimanche, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130324084352.ga24...@falafel.plessy.net
Re: d-i for wheezy on a Dreamplug, docs/recommended practice?
Le Fri, Mar 22, 2013 at 07:42:26PM +0100, Martin Lucina a écrit : Anyhow, my question / offer to help is: AFAICS at the moment there is no real documentation on how joe user can install wheezy on their Dreamplug using d-i, or if there is I haven't found it. In my case, being vaguely familiar with U-boot (and having just flashed U-boot 2013.01.01 on the plug), I followed these steps: 1. Download uImage and uInitrd from [1]. http://ftp.nl.debian.org/debian/dists/testing/main/installer-armel/current/images/. 2. Copy both to a (FAT-formatted) USB stick. 3. Boot into U-boot, stop the autoboot and run the following commands: usb start usb tree [determine, using fatls etc, which device is the usb stick] setenv bootargs console=ttyS0,115200 fatload usb 2:1 0x640 uImage fatload usb 2:1 0x800 uInitrd bootm 0x640 0x800 Who can I contact about getting these steps into the wheezy installation guide in some prominent place? Dear Martin, thanks for your input. The installation guide is packaged, so you can make your suggestion and send a patch through a bug report against the installation-guide package (which will be received on the debian-boot mailing list). As you figured out by yourself, the debian-arm mailing list is also a good place for discussing the additions that you propose. Have a nice week-end, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130323001744.ga30...@falafel.plessy.net
Re: Listing the Debian Installer internals manual on http://www.debian.org/doc/devel-manuals ?
Le Wed, Mar 20, 2013 at 10:52:11AM +0100, Samuel Thibault a écrit : Charles Plessy, le Wed 20 Mar 2013 11:33:24 +0900, a écrit : how about listing the Debian Installer internals manual on http://www.debian.org/doc/devel-manuals ? That can probably be useful, as we now and then get people asking how to work with the installer, even if that's indeed documented. If you like the idea I can propose a patch or commit directly. Please commit. Thanks for the feedback. Here is the patch that I am ready to commit in the absence of suggestions of problems. Index: devel-manuals.wml === RCS file: /cvs/webwml/webwml/english/doc/devel-manuals.wml,v retrieving revision 1.65 diff -u -r1.65 devel-manuals.wml --- devel-manuals.wml 29 Aug 2012 21:41:56 - 1.65 +++ devel-manuals.wml 20 Mar 2013 13:56:08 - @@ -257,3 +257,25 @@ /doctable /div +hr + +document Debian Installer internals d-i-internals + +div class=centerblock +p + This document is intended to make Debian Installer more accessible to new + developers and as a central location to document technical information. + +doctable + authors Frans Pop + maintainer Debian Installer team + status + ready + /status + availability + pa href=http://d-i.alioth.debian.org/doc/internals/;HTML online/a./p + pa href=http://anonscm.debian.org/viewvc/d-i/trunk/manual/;DocBook source online/a./p + /availability +/doctable +/div + Index: index.wml === RCS file: /cvs/webwml/webwml/english/doc/index.wml,v retrieving revision 1.97 diff -u -r1.97 index.wml --- index.wml 26 Jan 2013 00:54:29 - 1.97 +++ index.wml 20 Mar 2013 13:56:08 - @@ -96,6 +96,7 @@ lia href=misc-manuals#historyDebian Project History/a/li lia href=misc-manuals#markupDebiandoc-SGML Markup Manual/a/li lia href=misc-manuals#sgml-howtoDebian SGML/XML HOWTO/a/li + lia href=misc-manuals#d-i-internalsDebian Installer internals/a/li /ul /div Cheers, -- Charles Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130320095211.gc6...@type.bordeaux.inria.fr -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130320135808.ga...@falafel.plessy.net
Listing the Debian Installer internals manual on http://www.debian.org/doc/devel-manuals ?
Hello everybody, how about listing the Debian Installer internals manual on http://www.debian.org/doc/devel-manuals ? If you like the idea I can propose a patch or commit directly. Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130320023324.gc30...@falafel.plessy.net
Re: Listing the Debian Installer internals manual on http://www.debian.org/doc/devel-manuals ?
Le Tue, Mar 19, 2013 at 11:09:12PM -0400, David Prévot a écrit : Le 19/03/2013 22:33, Charles Plessy a écrit : how about listing the Debian Installer internals manual on Care to provide background, a link? http://www.debian.org/doc/devel-manuals ? Redirecting to the appropriate list, as per http://www.debian.org/doc/ddp. Ah sorry, I forgot the link. http://d-i.alioth.debian.org/doc/internals/ The doc/devel-manuals page on www.debian.org contains manuals that are not maintained by the DDP, so I did not think that there is a need to discuss something on the debian-doc mailing list. Sorry if I missed some procedures. PS: My feeling is that answers starting by Care to ? (like the ones finishing by kthxbye) are irritated, and are a predictor for further difficulties, so I will not move the idea further unless invited to do so. Cheers, -- Charles -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130320033105.gd30...@falafel.plessy.net
Bug#697890: tasksel arch any? (Re: Bug#697890: iwconfig not in /sbin)
Le Sun, Mar 10, 2013 at 05:39:56PM +0900, Charles Plessy a écrit :
Le Sun, Mar 10, 2013 at 07:59:46AM +0100, Christian PERRIER a écrit :
Here, we know about the bug and solution (I haven't looked at the code
but adding iw at the same place where wireless-tools are added when
the installation interface is wireless should be trivialevn for
someone with extremely low C skills)and we want this to be fixed.
Agreed. I reassign 697890 to netcfg, then.
Would it be as simple as adding iw through the followign patch ?
It looks like it is not necessary to check that the system being installed is
using a Linux kernel, otherwise it would already be done for the installation
of wireless-tools.
diff --git a/netcfg-static.c b/netcfg-static.c
index 4e9ca29..1987bec 100644
--- a/netcfg-static.c
+++ b/netcfg-static.c
@@ -83,7 +83,7 @@ int main(int argc, char** argv)
case WCONFIG:
if (requested_wireless_tools == 0) {
requested_wireless_tools = 1;
-di_exec_shell(apt-install wireless-tools);
+di_exec_shell(apt-install iw wireless-tools);
}
state = WCONFIG_ESSID;
break;
diff --git a/netcfg.c b/netcfg.c
index 06c1dcf..d0c46e5 100644
--- a/netcfg.c
+++ b/netcfg.c
@@ -280,7 +280,7 @@ int main(int argc, char *argv[])
case WCONFIG:
if (requested_wireless_tools == 0) {
-di_exec_shell_log(apt-install wireless-tools);
+di_exec_shell_log(apt-install iw wireless-tools);
requested_wireless_tools = 1;
}
state = WCONFIG_ESSID;
diff --git a/write_interface.c b/write_interface.c
index 1aa331a..2a42d48 100644
--- a/write_interface.c
+++ b/write_interface.c
@@ -55,7 +55,7 @@ static int nc_wi_wireless_options(const struct
netcfg_interface *interface, FILE
fprintf(fd, \twpa-ssid %s\n, interface-essid);
fprintf(fd, \twpa-psk %s\n, interface-passphrase);
} else {
- fprintf(fd, \t# wireless-* options are implemented by the
wireless-tools package\n);
+ fprintf(fd, \t# wireless-* options are implemented by the iw
and wireless-tools packages\n);
fprintf(fd, \twireless-mode %s\n,
(interface-mode == MANAGED) ? managed : ad-hoc);
fprintf(fd, \twireless-essid %s\n,
For write_interface.c, the number of characters grows from 67 to 75, not
including the tabulation. Depending on its size, it may make the message too
long for interfaces limited to 80 characters in width.
Have a nice week-end,
--
Charles Plessy
Tsurumi, Kanagawa, Japan
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130316064012.gf4...@falafel.plessy.net
Bug#697890: tasksel arch any? (Re: Bug#697890: iwconfig not in /sbin)
reassign 697890 netcfg retitle 697890 Please install iw on systems with wireless harware. thanks Le Sun, Mar 10, 2013 at 07:59:46AM +0100, Christian PERRIER a écrit : Here, we know about the bug and solution (I haven't looked at the code but adding iw at the same place where wireless-tools are added when the installation interface is wireless should be trivialevn for someone with extremely low C skills)and we want this to be fixed. Agreed. I reassign 697890 to netcfg, then. Cheers, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130310083956.gb...@falafel.plessy.net
Re: Updating http://wiki.debian.org/DebianInstaller/FAQ
Le Tue, Mar 05, 2013 at 01:33:32AM +0100, Cyril Brulebois a écrit : the FAQ page could use an update. Entries about Etch and Lenny, floppies, etc. ;-) Volunteers? It's here → http://wiki.debian.org/DebianInstaller/FAQ Hi Cyril, I gave it a try: http://wiki.debian.org/DebianInstaller/FAQ?action=info Please (anybody), let me know if corrections are necessary. Cheers, -- Charles -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130310143110.ga2...@falafel.plessy.net
Bug#697890: tasksel arch any? (Re: Bug#697890: iwconfig not in /sbin)
Le Thu, Mar 07, 2013 at 03:03:53PM -0400, Joey Hess a écrit : Oh, I didn't think this this was, but, indeed, as we already add wireless-tools through netcfg, I see not reason to not use the same concept to add iw when the (installation) interface is wireless (of course, one might argue what if the installation interface is wired and the system has wireless). Not a new argument of course... We therefore have the following choices: 1) Reassign 697890 to netcfg. 2) Go ahead and upload with architecture-dependant task(s). If we chose 1), are there good chances that the bug will be fixed ? Netcfg already has 40 bugs open, including 6 tagged help. Have a nice week-end, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130310005200.ga...@falafel.plessy.net
Bug#697868: tasksel arch any? (Re: Bug#697890: iwconfig not in /sbin)
Le Thu, Mar 07, 2013 at 03:03:53PM -0400, Joey Hess a écrit : Christian PERRIER wrote: Indeed, when committing these changes, I thought that, because that arch-dependent packages are added to Recommends and not Depend, it would not be a problem. Apparently it is. This is what slightly puzzles me, indeed. network-manager is currently listed in Depends. Note anyway that having network-manager [linux-any] in the Recommends field is also buggy. Having all packages in main satisfying their Recommends relationships has been a release goal in the past, and it may be better to ask first if this still holds. (The Policy forbids that packages in the main archive area recommend other packages outside that area, but one can argue that it is silent about recommending pakcages that do not exist). Cheers, -- Charles -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130310010612.gb...@falafel.plessy.net
Bug#697890: iwconfig not in /sbin
Le Wed, Mar 06, 2013 at 07:12:39AM +0100, Christian PERRIER a écrit : Quoting Charles Plessy (ple...@debian.org): Le Tue, Mar 05, 2013 at 09:25:31PM +0100, Cyril Brulebois a écrit : Unless I'm missing something obvious, switching to “architecture: any” for some tasks should be OK. Shall I upload with the attached patches applied ? I would prefer if this is not an NMU. There are multiple ways to solve this: - The upload is made by an uploader. - I or someone else sponsor an upload where the changelog is signed by an uploader. - The upload is marked Team upload. - The upload is made version 3.16, ignoring warnings. - I or someone else become uploader, and upload. Any is fine with me. Getting Joey's ACK would also be a good idea. Just let me know a timeline if you would like me to upload. Cheers, -- Charles -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130307002117.gb27...@falafel.plessy.net
Bug#697890: iwconfig not in /sbin
Le Tue, Mar 05, 2013 at 09:25:31PM +0100, Cyril Brulebois a écrit :
Unless I'm missing something obvious, switching to “architecture: any”
for some tasks should be OK.
Shall I upload with the attached patches applied ?
Cheers,
--
Charles
From 92aea904ba8993ad20da026dbebd1dd67469252d Mon Sep 17 00:00:00 2001
From: Charles Plessy ple...@debian.org
Date: Wed, 6 Mar 2013 07:17:54 +0900
Subject: [PATCH 1/2] Make task-desktop and task-gnome-desktop
architecture-dependant.
Both tasks recommend packages available only on linux.
---
debian/control | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/debian/control b/debian/control
index 537982a..1ac0e54 100644
--- a/debian/control
+++ b/debian/control
@@ -31,7 +31,7 @@ Description: Official tasks used for installation of Debian systems
system.
Package: task-desktop
-Architecture: all
+Architecture: any
Description: Debian desktop environment
This task package is used to install the Debian desktop.
Depends: ${misc:Depends},
@@ -65,7 +65,7 @@ Recommends:
pm-utils
Package: task-gnome-desktop
-Architecture: all
+Architecture: any
Description: GNOME desktop environment
This task package is used to install the Debian desktop, featuring
the GNOME desktop environment, and with other packages that Debian users
--
1.8.2.rc0
From 92e6319b8abf3751a99a7dfa438d9c5fb98b8e9c Mon Sep 17 00:00:00 2001
From: Charles Plessy ple...@debian.org
Date: Wed, 6 Mar 2013 07:23:56 +0900
Subject: [PATCH 2/2] Releasing version 3.14+nmu2.
---
debian/changelog | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index cfd088a..c29e2ba 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,4 +1,9 @@
-tasksel (3.16) UNRELEASED; urgency=low
+tasksel (3.14+nmu2) unstable; urgency=low
+
+ [ Charles Plessy ]
+ * Non-maintainer upload.
+ * Make task-desktop and task-gnome-desktop architecture-dependant.
+(Both tasks recommend packages available only on linux.)
[ Christian Perrier ]
* Add iw package to laptop and dektop task, in Linux
@@ -11,7 +16,7 @@ tasksel (3.16) UNRELEASED; urgency=low
[ Kenshi Muto ]
* Add mozc-utils-gui to japanese-desktop.
- -- Christian Perrier bubu...@debian.org Mon, 25 Feb 2013 07:17:51 +0100
+ -- Charles Plessy ple...@debian.org Wed, 06 Mar 2013 07:42:03 +0900
tasksel (3.14+nmu1) unstable; urgency=low
--
1.8.2.rc0
Bug#697890: iwconfig not in /sbin
Le Sun, Mar 03, 2013 at 11:03:59PM +, Ben Hutchings a écrit : On Sun, 2013-03-03 at 13:51 +0100, Christian PERRIER wrote: Quoting Charles Plessy (ple...@debian.org): unfortunately it makes the package fail to build. dpkg-gencontrol: error: the Recommends field contains an arch-specific dependency but the package is architecture all dh_gencontrol: dpkg-gencontrol -ptask-desktop -ldebian/changelog -Tdebian/task-desktop.substvars -Pdebian/task-desktop returned exit code 255 Currently all tasks are architecture-independent, so I guess that making task-desktop architecture-dependent would not be a good solution ? hmmm, and we have the same problem with the recent change to add network-manager-gnome to task-gnome-desktop. ANyone with a good suggestion, here? Hide the desktop and laptop tasks on kfreebsd-*. Hi Ben and everybody, That proposition does not remove the need to make task-desktop architecture-dependent. Would that break something ? Otherwise, despite it looks unusual, I would suggest to go ahead with architecture-dependant tasks if needed. Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130305000109.gc15...@falafel.plessy.net
Bug#697890: iwconfig not in /sbin
Le Sun, Mar 03, 2013 at 08:44:14AM +0100, Christian PERRIER a écrit : So, leaving this sitting in my TODO list. Of course, anyone is free to upload tasksel with the current pending changes. (I added [linux-any] to iw) Hi Christian, unfortunately it makes the package fail to build. dpkg-gencontrol: error: the Recommends field contains an arch-specific dependency but the package is architecture all dh_gencontrol: dpkg-gencontrol -ptask-desktop -ldebian/changelog -Tdebian/task-desktop.substvars -Pdebian/task-desktop returned exit code 255 Currently all tasks are architecture-independent, so I guess that making task-desktop architecture-dependent would not be a good solution ? Cheers -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130303083838.ga6...@falafel.plessy.net
Bug#702050: tasksel: a meta task to install all language tasks ?
Package: tasksel Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org Le Tue, Feb 26, 2013 at 04:57:48PM -0800, Russ Allbery a écrit : Charles Plessy ple...@debian.org writes: on these systems, getting all the default fonts and input methods would also be a big plus. For the moment we are years behind other systems such as Mac OS, where at any time it is possible to switch language or browse a website in a language that is not the default one of the session. Amen to this. I care a lot about having fairly complete Unicode coverage in my display fonts, and I've often had to trawl through aptitude to try to guess at which font packages I need to install just to, for example, see the front page of Wikipedia without annoying empty squares. I just installed all the task-language-desktop packages on my computer using equivs and a Depends field populated by the output of the following command, run from the tasks directory of the tasksel package. find . -maxdepth 1 -type f | xargs grep -l '^Task:'| xargs grep-dctrl --exact-match -FSection l10n --and -FEnhances desktop -sTask -n | grep -v -e gnome -e kde | sed -e 's/^/ task-/' -e 's/$/,/' The good news is that they are all co-installable. The bad news is that not all software are able to pick correctly the appropriate font. In particular, epiphany and chromium now display Chinese characters with Chinese glyphs even for texts where the indicated language is Japanese. Fortunately, iceweasel picks the right fonts. If it were posssible to tackle such issues after the Wheezy release, then I think that it would be worth to give our users the choice to install all localisation tasks. I think that I can write a patch where debian/control would be refreshed from a template, so that at each upload the meta-task would be always comprehensive. Have a nice week-end, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130302082026.ga13...@falafel.plessy.net
Bug#684629: installation-guide: Example value for preseed option network-console/authorized_keys_url.
Package: installation-guide Severity: wishlist Hello, in #592550, we have added a new preseed option to network-console, which provides support for SSH key authentification. The following patch adds an example value to the installation guide. I did not add explanations, so that translations will not be needed, but I can do if you prefer. Have a nice Sunday, -- Charles Index: preseed.xml === --- preseed.xml (révision 67925) +++ preseed.xml (copie de travail) @@ -904,6 +904,7 @@ # component for remote installation over SSH. This only makes sense if you # intend to perform the remainder of the installation manually. #d-i anna/choose_modules string network-console +#d-i network-console/authorized_keys_url string http://169.254.169.254/2012-01-12/meta-data/public-keys/0/openssh-key #d-i network-console/password password r00tme #d-i network-console/password-again password r00tme /screen/informalexample
Re: tasksel todo
Le Mon, Jun 11, 2012 at 11:23:15AM +0200, Bastian Blank a écrit : Fonts = hungarian-desktop for example _depends_ on a large amount of fonts. None of them hungarian specific. Hello everybody, talking about fonts, do you think it woud be possible to have a task that would install a default set of fonts for most languages that an average user would meet ? For instance, all languages used in Wikipedia for which a font is available in Debian ? Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120611104759.gb7...@falafel.plessy.net
Bug#672523: please include preserve /home functionality
Le Sat, May 12, 2012 at 08:08:12AM +0200, Christian PERRIER a écrit :
For example, if you need to upgrade laptops that have rather small (thus
only a swap+root partition setup) and full harddisks to the next release.
(Especially if you will also need to change the desktop environment,
to maintain the uability. Then you can get rid of the old DE by only
installing
the new one.)
The preserve /home functionallity has been used with ubuntu for
quite some time now.
The spec can be found here:
https://wiki.ubuntu.com/UbiquityPreserveHome
And this even seems to suggest there might already exist debian-installer
patches:
https://wiki.edubuntu.org/komputes/HowToDebianInstallerPreserveHome
I don't really see where this page suggests this. It gives a step by
step method, using the manual partitioning methodwhich I think
is logical for such purpose.
This is already possible with the current installer and there's
nothing to change. What exactly would you like to see changed?
Hi all,
I have the impression that this function was intrduced in the following
revision.
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/quantal/partman-target/quantal/revision/18
I attached the corresponding diff.
Have a nice day,
--
Charles
=== added directory 'commit.d'
=== added file 'commit.d/_numbers'
--- commit.d/_numbers 1970-01-01 00:00:00 +
+++ commit.d/_numbers 2008-01-22 16:06:55 +
@@ -0,0 +1,1 @@
+60 clear_partitions
=== added file 'commit.d/clear_partitions'
--- commit.d/clear_partitions 1970-01-01 00:00:00 +
+++ commit.d/clear_partitions 2008-01-22 16:06:55 +
@@ -0,0 +1,74 @@
+#! /bin/sh
+# Remove critical files to ensure we don't end up with a mixed system.
+
+. /lib/partman/lib/base.sh
+
+failed () {
+db_progress STOP
+db_input critical partman-target/clear_partitions_failed || true
+db_go || true
+exit 1
+}
+
+partitions=$(
+for dev in $DEVICES/*; do
+[ -d $dev ] || continue
+cd $dev
+open_dialog PARTITIONS
+while { read_line num id size type fs path name; [ $id ]; }; do
+ [ $fs != free ] || continue
+ [ -f $id/mountpoint ] || continue
+ [ -f $id/format ] continue
+ mp=$(cat $id/mountpoint)
+ echo $mp,$path
+done
+close_dialog
+done | sort
+)
+
+[ -n $partitions ] || exit 0
+
+tmp=/mnt/tmpmount
+mkdir -p $tmp
+for part in $partitions; do
+mp=${part%,*}
+path=${part#*,}
+mount $path $tmp$mp || failed
+done
+
+template=partman-target/clear_partitions_progress
+db_progress START 0 12 ubiquity/install/title
+db_progress INFO $template
+for x in bin boot dev etc lib lib32 lib64 proc sbin usr var sys; do
+db_progress STEP 1
+[ -e $tmp/$x ] (rm -rf $tmp/$x || failed)
+done
+for x in $tmp/initrd* $tmp/vmlinuz*; do
+[ -e $x ] (rm -rf $x || failed)
+done
+
+# /home could be a symlink.
+[ -f $tmp/home ] (rm $tmp/home || failed)
+db_progress STOP
+
+# Preserve the UID, if possible.
+db_get passwd/username || true
+username=$RET
+if [ -n $username ] [ -d $tmp/home/$username ]; then
+db_set passwd/user-uid $(stat -c %u $tmp/home/$username) || true
+db_set passwd/user-gid $(stat -c %g $tmp/home/$username) || true
+fi
+
+partitions=$(
+for part in $partitions; do
+echo $part
+done | sort -r
+)
+
+for part in $partitions; do
+mp=${part%,*}
+path=${part#*,}
+umount $path || failed
+done
+
+rmdir $tmp || failed
=== modified file 'debian/changelog'
--- debian/changelog 2007-10-23 17:53:53 +
+++ debian/changelog 2008-01-22 16:06:55 +
@@ -1,3 +1,18 @@
+partman-target (52ubuntu2) hardy; urgency=low
+
+ [ Colin Watson ]
+ * Set Vcs-Bzr for Ubuntu.
+
+ [ Evan Dandrea ]
+ * Added support for installing without reformatting existing partitions for
+the ubiquity-preserve-home specification (LP: #174619):
+- Remove critical system files from the existing filesystem before
+ installing.
+- Preserve the UID and GID of the initial user, if possible. Requires a
+ patch to user-setup.
+
+ -- Evan Dandrea ev...@ubuntu.com Tue, 22 Jan 2008 16:06:55 +
+
partman-target (52ubuntu1) hardy; urgency=low
* Resynchronise with Debian. Remaining changes:
=== modified file 'debian/control'
--- debian/control 2007-04-30 11:42:14 +
+++ debian/control 2008-01-22 16:06:55 +
@@ -5,7 +5,8 @@
XSBC-Original-Maintainer: Debian Install System Team debian-boot@lists.debian.org
Uploaders: Anton Zinoviev zinov...@debian.org
Build-Depends: debhelper (= 4.2.0), po-debconf (= 0.5.0)
-XS-Vcs-Svn: svn://svn.debian.org/d-i/trunk/packages/partman/partman-target
+XS-Original-Vcs-Svn: svn://svn.debian.org/d-i/trunk/packages/partman/partman-target
+Vcs-Bzr: http://bazaar.launchpad.net/~ubuntu-core-dev/partman-target/ubuntu
Package: partman-target
XC-Package-Type: udeb
=== modified file 'debian/partman-target.templates'
--- debian/partman-target.templates 2007-04-30 11:42:14 +
+++ debian/partman-target.templates 2008-01-22 16:06:55 +
@@ -74,3 +74,14
Re: [RFH] Release of D-I Alpha1
Le Mon, Apr 23, 2012 at 02:32:57PM -0300, Otavio Salvador a écrit : I do need help to manage the missing steps and testing. Is someone willing to help on it? Dear Otavio, I am not sure how far this can help, but I tested today's daily build of netboot (amd64) on the Amazon cloud, and it worked well unattended with the following preseed file. I am not yet able to test if the installed system is bootable; I need to package cloud-init first. By the way, I have a question. What is the difference between the netboot and the xen image ? I thought I would need the xen image on the Amazon cloud, but it worked well with the simple netboot (which is good as the xen image did not build today). Have a nice week-end, -- Charles Plessy Tsurumi, Kanagawa, Japan d-i debconf/priority select critical Contents of the preconfiguration file (for squeeze) ### Localization # Preseeding only locale sets language, country and locale. d-i debian-installer/locale string en_US # Keyboard selection. #d-i console-tools/archs select at d-i console-keymaps-at/keymap select us d-i keyboard-configuration/xkb-keymap select us # netcfg will choose an interface that has link if possible. This makes it # skip displaying a list if there is more than one interface. d-i netcfg/choose_interface select auto # Any hostname and domain names assigned from dhcp take precedence over # values set here. However, setting the values still prevents the questions # from being shown, even if values come from dhcp. d-i netcfg/get_hostname string unassigned-hostname d-i netcfg/get_domain string unassigned-domain ### Network console # Use the following settings if you wish to make use of the network-console # component for remote installation over SSH. This only makes sense if you # intend to perform the remainder of the installation manually. #d-i anna/choose_modules string network-console #d-i network-console/password password r00tme #d-i network-console/password-again password r00tme ### Mirror settings # If you select ftp, the mirror/country string does not need to be set. #d-i mirror/protocol string ftp d-i mirror/country string manual d-i mirror/http/hostname string ftp.jp.debian.org d-i mirror/http/directory string /debian d-i mirror/http/proxy string ### Account setup # Skip creation of a root account (normal user account will be able to # use sudo). d-i passwd/root-login boolean false # To create a normal user account. d-i passwd/user-fullname string Debian User d-i passwd/username string debian # Normal user's password, either in clear text d-i passwd/user-password password r00tme d-i passwd/user-password-again password r00tme # or encrypted using an MD5 hash. #d-i passwd/user-password-crypted password [MD5 hash] ### Clock and time zone setup # Controls whether or not the hardware clock is set to UTC. d-i clock-setup/utc boolean true # You may set this to any valid setting for $TZ; see the contents of # /usr/share/zoneinfo/ for valid values. d-i time/zone string UTC # Controls whether to use NTP to set the clock during the install d-i clock-setup/ntp boolean true # NTP server to use. The default is almost always fine here. #d-i clock-setup/ntp-server string ntp.example.com ### Partitioning ## Partitioning example # If the system has free space you can choose to only partition that space. # This is only honoured if partman-auto/method (below) is not set. #d-i partman-auto/init_automatically_partition select biggest_free # Alternatively, you may specify a disk to partition. If the system has only # one disk the installer will default to using that, but otherwise the device # name must be given in traditional, non-devfs format (so e.g. /dev/hda or # /dev/sda, and not e.g. /dev/discs/disc0/disc). # For example, to use the first SCSI/SATA hard disk: d-i partman-auto/disk string /dev/xvdb # In addition, you'll need to specify the method to use. # The presently available methods are: # - regular: use the usual partition types for your architecture # - lvm: use LVM to partition the disk # - crypto: use LVM within an encrypted partition d-i partman-auto/method string regular # You can choose one of the three predefined partitioning recipes: # - atomic: all files in one partition # - home: separate /home partition # - multi: separate /home, /usr, /var, and /tmp partitions d-i partman-auto/choose_recipe select atomic # This makes partman automatically partition without confirmation, provided # that you told it what to do using one of the methods above. d-i partman-partitioning/confirm_write_new_label boolean true d-i partman/choose_partition select finish d-i partman/confirm boolean true d-i partman/confirm_nooverwrite boolean true ## Controlling how partitions are mounted # The default is to mount by UUID, but you can also choose traditional to # use traditional device names, or label to try filesystem labels before # falling back to UUIDs. #d-i partman/mount_style select uuid ### Base system installation # Select
Bug#592550: String freeze for Debian Installer
Le Sat, Apr 21, 2012 at 04:13:53PM +0200, Christian PERRIER a écrit :
Even if not very important, I recommend avoiding interrogative form in
the long part.
Add a comment for translators and move to sublevel 6
Thanks for the proofreading. I attached an additional patch that can be
applied on top of the other ones.
I have the impression that I may have confused you by sending a stack of
interdependant patches in my previous email. If you are not going to apply
them with the 'git am' command, I attached a monolithic patch as a replacement.
Have a nice day,
--
Charles Plessy
Tsurumi, Kanagawa, Japan
From d1399b53ba3d7ec41fb39cb2e64834d89d973308 Mon Sep 17 00:00:00 2001
From: Charles Plessy ple...@debian.org
Date: Tue, 24 Apr 2012 09:37:12 +0900
Subject: [PATCH 5/5] Proofread by C. Perrier.
Message-ID: 20120421141353.gb3...@mykerinos.kheops.frmug.org
---
debian/network-console.templates |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/debian/network-console.templates b/debian/network-console.templates
index 26c19fa..40e056a 100644
--- a/debian/network-console.templates
+++ b/debian/network-console.templates
@@ -79,14 +79,14 @@ _Description: Start SSH
Template: network-console/authorized_keys_url
Type: string
Description: for internal use; can be preseeded
- URL to a list of authorized SSH public keys.
- .
- The file at the given URL should be of the same form as a standard SSH
- authorized_keys file.
+ This variable contains the URL that provides a list of authorized
+ SSH public keys
Template: network-console/authorized_keys_fetch_failure
Type: error
# :sl6:
+#flag:comment:2
+# Translators: do NOT translate the LOCATION variable name
_Description: Could not fetch SSH authorized keys
An error occurred while fetching SSH authorized keys from ${LOCATION}.
.
--
1.7.9.5
diff --git a/debian/changelog b/debian/changelog
index 43ac6c4..82cce35 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+network-console (1.31) UNRELEASED; urgency=low
+
+ [ Matt T. Proud ]
+ * Add support for public-key authentication (Closes:#592550, LP: #184108).
+
+ [ Charles Plessy ]
+ * Mark authorized_keys_fetch_failure for translation, sublevel 6.
+
+ -- Charles Plessy ple...@debian.org Sat, 21 Apr 2012 12:22:26 +0900
+
network-console (1.30) unstable; urgency=low
[ Updated translations ]
diff --git a/debian/network-console.postinst b/debian/network-console.postinst
index c5c0560..cbfe825 100755
--- a/debian/network-console.postinst
+++ b/debian/network-console.postinst
@@ -26,7 +26,30 @@ case $ARCHDETECT in
;;
esac
-while [ -z $PASSWORD ]; do
+db_get $TEMPLATE_ROOT/authorized_keys_url
+
+AUTHORIZED_KEYS_URL=$RET
+AUTHORIZED_KEYS_DIRECTORY=/.ssh
+AUTHORIZED_KEYS_FILE=$AUTHORIZED_KEYS_DIRECTORY/authorized_keys
+
+if [ -n $AUTHORIZED_KEYS_URL ]; then
+ if [ ! -f $AUTHORIZED_KEYS_FILE ]; then
+ [ -d $AUTHORIZED_KEYS_DIRECTORY ] || \
+ mkdir $AUTHORIZED_KEYS_DIRECTORY
+ chmod 0700 $AUTHORIZED_KEYS_DIRECTORY
+ if ! wget -q $AUTHORIZED_KEYS_URL -O $AUTHORIZED_KEYS_FILE; then
+ db_subst $TEMPLATE_ROOT/authorized_keys_fetch_failure \
+ LOCATION $AUTHORIZED_KEYS_URL
+ db_input critical $TEMPLATE_ROOT/authorized_keys_fetch_failure \
+ || true
+ db_go
+ exit 1
+ fi
+ chmod 0644 $AUTHORIZED_KEYS_FILE || true
+ fi
+fi
+
+while [ ! -f $AUTHORIZED_KEYS_FILE ] [ -z $PASSWORD ]; do
db_input critical $TEMPLATE_ROOT/password || true
COMPARE_PW=''
db_input high $TEMPLATE_ROOT/password-again COMPARE_PW=1 || true
diff --git a/debian/network-console.templates b/debian/network-console.templates
index 4439379..40e056a 100644
--- a/debian/network-console.templates
+++ b/debian/network-console.templates
@@ -75,3 +75,19 @@ _Description: Start SSH
.
Please check this carefully against the fingerprint reported by
your SSH client.
+
+Template: network-console/authorized_keys_url
+Type: string
+Description: for internal use; can be preseeded
+ This variable contains the URL that provides a list of authorized
+ SSH public keys
+
+Template: network-console/authorized_keys_fetch_failure
+Type: error
+# :sl6:
+#flag:comment:2
+# Translators: do NOT translate the LOCATION variable name
+_Description: Could not fetch SSH authorized keys
+ An error occurred while fetching SSH authorized keys from ${LOCATION}.
+ .
+ Check /var/log/syslog or see virtual console 4 for the details.
Bug#592550: String freeze for Debian Installer
Le Wed, Apr 04, 2012 at 06:51:37PM +0200, Christian PERRIER a écrit :
I propose you use sublevel 6.
Then update the patch...then propose a patch to the D-I documentation
(the part about preseeding as any preseedable value should be
documented there).
Dear Christian and everybody,
here is an updated patch to network-console, to implement SSH connection via
authorized keys downloaded at run time.
I am still studying how to test the patched udeb...
I will submit a patch to the D-I documentation separately. In the meantime,
please let me know if you spot a problem with the attached patches.
Have a nice week-end,
--
Charles Plessy
Tsurumi, Kanagawa, Japan
From a46062a72f680feebc78ff7a630ccb5765b478c1 Mon Sep 17 00:00:00 2001
From: Charles Plessy ple...@debian.org
Date: Sat, 21 Apr 2012 11:53:13 +0900
Subject: [PATCH 1/4] Add support for public-key authentication (Matt T.
Proud, LP: #184108).
URL: http://patches.ubuntu.com/n/network-console/network-console_1.29ubuntu1.patch
---
debian/network-console.postinst | 25 -
debian/network-console.templates | 16
2 files changed, 40 insertions(+), 1 deletion(-)
diff --git a/debian/network-console.postinst b/debian/network-console.postinst
index c5c0560..cbfe825 100755
--- a/debian/network-console.postinst
+++ b/debian/network-console.postinst
@@ -26,7 +26,30 @@ case $ARCHDETECT in
;;
esac
-while [ -z $PASSWORD ]; do
+db_get $TEMPLATE_ROOT/authorized_keys_url
+
+AUTHORIZED_KEYS_URL=$RET
+AUTHORIZED_KEYS_DIRECTORY=/.ssh
+AUTHORIZED_KEYS_FILE=$AUTHORIZED_KEYS_DIRECTORY/authorized_keys
+
+if [ -n $AUTHORIZED_KEYS_URL ]; then
+ if [ ! -f $AUTHORIZED_KEYS_FILE ]; then
+ [ -d $AUTHORIZED_KEYS_DIRECTORY ] || \
+ mkdir $AUTHORIZED_KEYS_DIRECTORY
+ chmod 0700 $AUTHORIZED_KEYS_DIRECTORY
+ if ! wget -q $AUTHORIZED_KEYS_URL -O $AUTHORIZED_KEYS_FILE; then
+ db_subst $TEMPLATE_ROOT/authorized_keys_fetch_failure \
+ LOCATION $AUTHORIZED_KEYS_URL
+ db_input critical $TEMPLATE_ROOT/authorized_keys_fetch_failure \
+ || true
+ db_go
+ exit 1
+ fi
+ chmod 0644 $AUTHORIZED_KEYS_FILE || true
+ fi
+fi
+
+while [ ! -f $AUTHORIZED_KEYS_FILE ] [ -z $PASSWORD ]; do
db_input critical $TEMPLATE_ROOT/password || true
COMPARE_PW=''
db_input high $TEMPLATE_ROOT/password-again COMPARE_PW=1 || true
diff --git a/debian/network-console.templates b/debian/network-console.templates
index 4439379..58daa88 100644
--- a/debian/network-console.templates
+++ b/debian/network-console.templates
@@ -75,3 +75,19 @@ _Description: Start SSH
.
Please check this carefully against the fingerprint reported by
your SSH client.
+
+Template: network-console/authorized_keys_url
+Type: string
+Description: for internal use; can be preseeded
+ What URL contains a list of authorized SSH public keys?
+ .
+ The file at the given URL should be of the same form as a standard OpenSSH
+ authorized_keys file.
+
+Template: network-console/authorized_keys_fetch_failure
+Type: error
+# should be translated when committed upstream
+Description: Could not fetch OpenSSH authorized keys
+ An error occurred while fetching OpenSSH authorized keys from ${LOCATION}.
+ .
+ Check /var/log/syslog or see virtual console 4 for the details.
--
1.7.9.5
From 2228ea565729b20691b2451af5743e331647d9e8 Mon Sep 17 00:00:00 2001
From: Charles Plessy ple...@debian.org
Date: Sat, 21 Apr 2012 12:17:31 +0900
Subject: [PATCH 2/4] Mark network-console/authorized_keys_fetch_failure for
translation.
---
debian/network-console.templates |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/debian/network-console.templates b/debian/network-console.templates
index 58daa88..db8621d 100644
--- a/debian/network-console.templates
+++ b/debian/network-console.templates
@@ -86,8 +86,8 @@ Description: for internal use; can be preseeded
Template: network-console/authorized_keys_fetch_failure
Type: error
-# should be translated when committed upstream
-Description: Could not fetch OpenSSH authorized keys
+# :sl6:
+_Description: Could not fetch OpenSSH authorized keys
An error occurred while fetching OpenSSH authorized keys from ${LOCATION}.
.
Check /var/log/syslog or see virtual console 4 for the details.
--
1.7.9.5
From 9ff20a125fc30d8b11e6fe10aa25f1f6bb9c9582 Mon Sep 17 00:00:00 2001
From: Charles Plessy ple...@debian.org
Date: Sat, 21 Apr 2012 12:22:05 +0900
Subject: [PATCH 3/4] Simplification of the authorized_keys* entries.
---
debian/network-console.templates |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/debian/network-console.templates b/debian/network-console.templates
index db8621d..26c19fa 100644
--- a/debian/network-console.templates
+++ b/debian/network-console.templates
@@ -79,15 +79,15 @@ _Description: Start SSH
Template: network-console/authorized_keys_url
Type: string
Description: for internal use; can be preseeded
- What URL contains a list of authorized SSH public keys
Bug#592550: String freeze for Debian Installer
Le Wed, Apr 04, 2012 at 07:03:14AM +0200, Christian PERRIER a écrit :
I would like to call for a string freeze in Debian Installer
packages. As you may have read elsewhere (mostly through my boring
blog posts), I'm currently fighting for bringing localization back to
completeness for several languages. And this is a very time consuming
task.
Dear Christian,
in #592550, I and others are proposing to add a functionality
to network-console, and the proposed patch would introduce the
following templates:
diff -pruN 1.29/debian/network-console.templates
1.29ubuntu1/debian/network-console.templates
--- 1.29/debian/network-console.templates 2011-06-19 02:40:08.0
+
+++ 1.29ubuntu1/debian/network-console.templates2011-10-18
17:23:42.0 +
@@ -75,3 +75,19 @@ _Description: Start SSH
.
Please check this carefully against the fingerprint reported by
your SSH client.
+
+Template: network-console/authorized_keys_url
+Type: string
+Description: for internal use; can be preseeded
+ What URL contains a list of authorized SSH public keys?
+ .
+ The file at the given URL should be of the same form as a standard OpenSSH
+ authorized_keys file.
+
+Template: network-console/authorized_keys_fetch_failure
+Type: error
+# should be translated when committed upstream
+Description: Could not fetch OpenSSH authorized keys
+ An error occurred while fetching OpenSSH authorized keys from ${LOCATION}.
+ .
+ Check /var/log/syslog or see virtual console 4 for the details.
How are considered the templates that are purposed for preseeding ? Do you
think that, from an i18n point of view, it would still be possible to get that
patch in D-I for Wheezy ? To be fair, this function is not essential; but it
is neat, as it allows to log in D-I with the same procedure as on some
high-profile machine images (like http://alestic.com/).
Reading the explanation about sublevels that you posted in 2007 (
http://lists.debian.org/debian-boot/2007/12/msg00480.html ), it looks like the
propose patch is actually missing an indication of sublevel. Would sublevel 5
be relevant ? I would like to update the patch and propose a NMU (depending on
your answer about string freeze).
Have a nice day,
--
Charles Plessy
Debian Med packaging team,
http://www.debian.org/devel/debian-med
Tsurumi, Kanagawa, Japan
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120404071116.gg12...@falafel.plessy.net
Bug#637784: installation-reports: Partition disks error: No root file system is defined.
Le Mon, Feb 13, 2012 at 10:06:06AM +0900, Charles Plessy a écrit : Le Sun, Feb 12, 2012 at 04:40:38PM +0900, Charles Plessy a écrit : Le Sat, Aug 20, 2011 at 06:26:45PM +0900, Charles Plessy a écrit : Using the shell console, I found that the partition table was the following: Disk /dev/xvda1: 1073 MB, 1073741824 bytes 255 heads, 63 sectors/track, 130 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0002dcf2 Device Boot Start End Blocks Id System /dev/xvda1p1 * 1 118 947803+ 83 Linux /dev/xvda1p2 119 130 963905 Extended /dev/xvda1p5 119 130 96358+ 82 Linux swap / Solaris However, the device files /dev/xvda1p1, p2 and p5 are not available. Do you have any idea ? I tried to modify the partition table by hand using fdisk, and after writing it I see the following error message. WARNING: Re-reading the partition table failed with error 22: Invalid argument. The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) Syncing disks. So the scenario is: - Partman partitions the disk, - the kernel is not informed of the changes, - udev does not create new links in /dev, - formatting and installation are impossible. Hello again, it looks like /dev/xvda1, where the Xen system is booted, is a special case and that in contrary to the other devices, like /dev/xvdb, etc., it can not be modified. The problem is therefore that part of the toolchain does not recognise in advance that it is impossible. Do you think that partman can or should obtain this information by itself, or that this bug should be reassigned to another package, which would be in charge of issuing an error message that partman can understand, to make sure that debian-installer does not assume that the disk has been partitionned successfully ? -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120401005553.ga7...@plessy.org
Bug#592550: Provide support for SSH-Key authentication (Supports Eucalyptus and Amazon EC2)
Dear all, Ubuntu's patched network-console can retrieve a public key from a fixed and secure location, which allows one to log in the installer without pre-defined password (such as r00tme in the example preseed file). I am not aware of problems arising from this patch, and Colin Watson was quite postitive in 2008 about applying merging it in Debian. Would that be possible ? I can help the preparation of the update if needed. In this bug report, a more extensive patch also was proposed by Kyle Moffett. It has functions that are off-topic for network-console, and that can be taken care of by the 'cloud-init' package that I hope will be uploaded to Debian soon. (See the debian-python mailing list archives in March). I propose to simply merge Ubuntu and Debian's difference, which would provide enough functionality to close this bug. Please let me know if I can help. Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120328003052.ga30...@plessy.org
Bug#637784: installation-reports: Partition disks error: No root file system is defined.
Le Sun, Feb 12, 2012 at 04:40:38PM +0900, Charles Plessy a écrit : Le Sat, Aug 20, 2011 at 06:26:45PM +0900, Charles Plessy a écrit : Using the shell console, I found that the partition table was the following: Disk /dev/xvda1: 1073 MB, 1073741824 bytes 255 heads, 63 sectors/track, 130 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0002dcf2 Device Boot Start End Blocks Id System /dev/xvda1p1 * 1 118 947803+ 83 Linux /dev/xvda1p2 119 130 963905 Extended /dev/xvda1p5 119 130 96358+ 82 Linux swap / Solaris However, the device files /dev/xvda1p1, p2 and p5 are not available. Do you have any idea ? I have tested today's build of Debian-Installer, and the bug is still there. To summarise: - On that machine, the drive's name is /dev/xvda1. - Partman handles this by making partitions called /dev/xvda1p1 /dev/xvda1p2 /dev/xvda1p5 - The installation then fails as there are no such devices. Hi again, I tried to modify the partition table by hand using fdisk, and after writing it I see the following error message. WARNING: Re-reading the partition table failed with error 22: Invalid argument. The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) Syncing disks. So the scenario is: - Partman partitions the disk, - the kernel is not informed of the changes, - udev does not create new links in /dev, - formatting and installation are impossible. Do you think that this bug should be re-assigned somewhere else ? Have a nice day, -- Charles -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120213010606.ga...@plessy.org
Bug#637784: installation-reports: Partition disks error: No root file system is defined.
Le Sat, Aug 20, 2011 at 06:26:45PM +0900, Charles Plessy a écrit : I then fails with the following error: Error informing the kernel about modifications to partition /dev/xvda1p1 -- Invalid argument. This means Linux won't know about any changes you made to /dev/xvda1p1 until you reboot -- so you shouldn't mount it or use it in any way before rebooting. Using the shell console, I found that the partition table was the following: Disk /dev/xvda1: 1073 MB, 1073741824 bytes 255 heads, 63 sectors/track, 130 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0002dcf2 Device Boot Start End Blocks Id System /dev/xvda1p1 * 1 118 947803+ 83 Linux /dev/xvda1p2 119 130 963905 Extended /dev/xvda1p5 119 130 96358+ 82 Linux swap / Solaris However, the device files /dev/xvda1p1, p2 and p5 are not available. Do you have any idea ? Dear all, I have tested today's build of Debian-Installer, and the bug is still there. To summarise: - On that machine, the drive's name is /dev/xvda1. - Partman handles this by making partitions called /dev/xvda1p1 /dev/xvda1p2 /dev/xvda1p5 - The installation then fails as there are no such devices. Have a nice Sunday, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120212074038.ga2...@plessy.org
Bug#592550: Provide support for SSH-Key authentication (Supports Eucalyptus and Amazon EC2)
Le Mon, Sep 12, 2011 at 10:56:05AM -0400, Kyle Moffett a écrit : My latest patch (attached) provides a bunch more features for installing in virtualized environments. You can also download it at this URL: http://opensource.exmeritus.com/debian-ami/network-console-1.29+euca01.patch Specifically, my patch allows you enable both password and public-key auth, by preseeding both a password and the authorized_keys URL. If you don't want to enable password authentication, you can preseed password-disabled instead. Additionally, I add a publi-ip-url key which causes the IP value in the network-console message to be obtained from the virtualized hosting system. Finally, I rewrite the post-base-installer hook to automatically copy the authorized_keys file to the newly created user on the target system. If a non-root user was created during the installation then the key is copied to that user, otherwise it is copied to root. Hi Kyle, the two first features are good additions. However, I think that the third feature, to add the SSH keys to the target system, should be at least disabled by default, or removed, for the following two reasons: 1) Public images should not contain public SSH keys that allow the owner of the private key to gain administrator priviledges, see: - http://alestic.com/2011/06/ec2-ami-security - https://forums.aws.amazon.com/thread.jspa?threadID=67299 2) The same functionality could be achieved by dowloading the public keys at the first run of fresh images, from the same special URL. I think that this is more flexible, and more images would benefit of this (for instance images that were not created through the network console). Let's have this function in a separate package. Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110914014338.gb5...@merveille.plessy.net
Bug#592550: Provide support for SSH-Key authentication (Supports Eucalyptus and Amazon EC2)
Le Tue, Aug 10, 2010 at 04:49:51PM -0400, Kyle Moffett a écrit :
When performing partially-automated virtual-server installations (using
services such as Eucalyptus or Amazon EC2, for example), it's not really
practical or secure to use password-based authentication for the
installer.
Furthermore, such virtual server environments provide an automatic
method of provisioning public SSH keys during the installation process
via an HTTP URL.
The Ubuntu guys seem to have a patch for this that never got merged:
https://bugs.launchpad.net/ubuntu/+source/network-console/+bug/184108
Dear all,
I think that it would wonderful if Ubuntu's patch were applied in Debian. Here
is a slimmed down version of it, where I removed the Ubuntu-specific parts
changing debian/control, the changelog and .gitignore files, …
http://patches.ubuntu.com/n/network-console/network-console_1.28ubuntu1.patch
--- 1.28/debian/network-console.postinst2011-01-19 04:51:17.0
+
+++ 1.28ubuntu1/debian/network-console.postinst 2011-05-04 00:19:29.0
+0100
@@ -26,7 +26,30 @@ case $ARCHDETECT in
;;
esac
-while [ -z $PASSWORD ]; do
+db_get $TEMPLATE_ROOT/authorized_keys_url
+
+AUTHORIZED_KEYS_URL=$RET
+AUTHORIZED_KEYS_DIRECTORY=/.ssh
+AUTHORIZED_KEYS_FILE=$AUTHORIZED_KEYS_DIRECTORY/authorized_keys
+
+if [ -n $AUTHORIZED_KEYS_URL ]; then
+ if [ ! -f $AUTHORIZED_KEYS_FILE ]; then
+ [ -d $AUTHORIZED_KEYS_DIRECTORY ] || \
+ mkdir $AUTHORIZED_KEYS_DIRECTORY
+ chmod 0700 $AUTHORIZED_KEYS_DIRECTORY
+ if ! wget -q $AUTHORIZED_KEYS_URL -O $AUTHORIZED_KEYS_FILE;
then
+ db_subst $TEMPLATE_ROOT/authorized_keys_fetch_failure \
+ LOCATION $AUTHORIZED_KEYS_URL
+ db_input critical
$TEMPLATE_ROOT/authorized_keys_fetch_failure \
+ || true
+ db_go
+ exit 1
+ fi
+ chmod 0644 $AUTHORIZED_KEYS_FILE || true
+ fi
+fi
+
+while [ ! -f $AUTHORIZED_KEYS_FILE ] [ -z $PASSWORD ]; do
db_input critical $TEMPLATE_ROOT/password || true
COMPARE_PW=''
db_input high $TEMPLATE_ROOT/password-again COMPARE_PW=1 || true
diff -pruN 1.28/debian/network-console.templates
1.28ubuntu1/debian/network-console.templates
--- 1.28/debian/network-console.templates 2011-01-19 04:51:17.0
+
+++ 1.28ubuntu1/debian/network-console.templates2011-05-04
00:19:29.0 +0100
@@ -75,3 +75,19 @@ _Description: Start SSH
.
Please check this carefully against the fingerprint reported by
your SSH client.
+
+Template: network-console/authorized_keys_url
+Type: string
+Description: for internal use; can be preseeded
+ What URL contains a list of authorized SSH public keys?
+ .
+ The file at the given URL should be of the same form as a standard OpenSSH
+ authorized_keys file.
+
+Template: network-console/authorized_keys_fetch_failure
+Type: error
+# should be translated when committed upstream
+Description: Could not fetch OpenSSH authorized keys
+ An error occurred while fetching OpenSSH authorized keys from ${LOCATION}.
+ .
+ Check /var/log/syslog or see virtual console 4 for the details.
Please let me know how I can help to make this happen.
Cheers,
--
Charles Plessy
Tsurumi, Kanagawa, Japan
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110910133008.ga4...@plessy.org
Bug#637784: installation-reports: Partition disks error: No root file system is defined.
Le Sat, Aug 20, 2011 at 06:26:45PM +0900, Charles Plessy a écrit : Using the shell console, I found that the partition table was the following: Disk /dev/xvda1: 1073 MB, 1073741824 bytes 255 heads, 63 sectors/track, 130 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0002dcf2 Device Boot Start End Blocks Id System /dev/xvda1p1 * 1 118 947803+ 83 Linux /dev/xvda1p2 119 130 963905 Extended /dev/xvda1p5 119 130 96358+ 82 Linux swap / Solaris However, the device files /dev/xvda1p1, p2 and p5 are not available. Do you have any idea ? Dear all, I hope that I am not too bothering with my insistance, but I am completely blocked on this issue, and I would like to ask again for your help, as I think that it would be beneficial to Debian as well if it were possible to use the Debian installer on the Amazon Elastic Computer Cloud. Please let me know how I can help the D-I team in return. Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110910133848.ga4...@plessy.org
Bug#637784: installation-reports: Partition disks error: No root file system is defined.
Le Sun, Aug 14, 2011 at 09:45:11PM +0900, Charles Plessy a écrit : I started the network installer through GRUB in the Amazon Elastic Comptuter Cloud, and connected to it through a network console launched via preseeding. I gave a couple of details on my website: http://charles.plessy.org/Debian/debiâneries/nuage/ While the detection of hard drives apparently went well (see attached partman log), the partition step fails with the following error. ┌┤ [!!] Partition disks ├─┐ │ │ │ No root file system │ │ No root file system is defined. │ │ │ │ Please correct this from the partitioning menu. │ │ │ │ Continue│ │ │ └─┘ Hi all, I have retried after commenting all partman preseeding. It allowed me to try to manually partition the drive. I have only one choice for the drive, ‘Virtual disk 1, partition #1 (xvda1) - 1.1 GB Unknown’. The guided partitionning then proposes me the following: ┌───┤ [!!] Partition disks ├───┐ │ │ │ If you continue, the changes listed below will be written to the disks. Otherwise, you will be able to make further │ │ changes manually. │ │ │ │ The partition tables of the following devices are changed: │ │Virtual disk 1, partition #1 (xvda1) │ │ │ │ The following partitions are going to be formatted: │ │partition #1 of Virtual disk 1, partition #1 (xvda1) as ext3 │ │partition #5 of Virtual disk 1, partition #1 (xvda1) as swap │ │ │ │ Write the changes to disks? │ │ │ │ Yes No │ │ │ └──┘ I then fails with the following error: Error informing the kernel about modifications to partition /dev/xvda1p1 -- Invalid argument. This means Linux won't know about any changes you made to /dev/xvda1p1 until you reboot -- so you shouldn't mount it or use it in any way before rebooting. Using the shell console, I found that the partition table was the following: Disk /dev/xvda1: 1073 MB, 1073741824 bytes 255 heads, 63 sectors/track, 130 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0002dcf2 Device Boot Start End Blocks Id System /dev/xvda1p1 * 1 118 947803+ 83 Linux /dev/xvda1p2 119 130 963905 Extended /dev/xvda1p5 119 130 96358+ 82 Linux swap / Solaris However, the device files /dev/xvda1p1, p2 and p5 are not available. Do you have any idea ? Have a nice week-end, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110820092645.ga27...@merveille.plessy.net
Bug#637784: installation-reports: Partition disks error: No root file system is defined.
Package: installation-reports Severity: normal -- Package-specific info: Boot method: network Image version: 20110106+squeeze3 Date: Sun, 14 Aug 2011 21:32:45 +0900 Machine: Amazon EC2 t1.micro instance. Partitions: Path: /dev/xvda1 Sector size: 512 Sectors: 2097152 Sectors/track: 63 Heads: 255 Cylinders: 130 Partition table: yes Type: msdos Partitions: # id length typefs pathname (0,0,0) (0,0,62)-1 0-32255 32256 primary label /dev/xvda1p-1 (0,1,0) (129,254,62)1 32256-10692863991069254144 primary ext2/dev/xvda1p1 (130,0,0) (130,138,7) -1 1069286400-1073741823 4455424 pri/log free/dev/xvda1p-1 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [ ] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[E] Comments/Problems: I started the network installer through GRUB in the Amazon Elastic Comptuter Cloud, and connected to it through a network console launched via preseeding. I gave a couple of details on my website: http://charles.plessy.org/Debian/debiâneries/nuage/ While the detection of hard drives apparently went well (see attached partman log), the partition step fails with the following error. ┌┤ [!!] Partition disks ├─┐ │ │ │ No root file system │ │ No root file system is defined. │ │ │ │ Please correct this from the partitioning menu. │ │ │ │ Continue│ │ │ └─┘ Despite being in expert mode with ‘low’ Debconf priority, the above is the only thing I get at the Partition disks step. I need to press Escape to return to the main menu, as otherwise it loops. I tried to format the virtual drive on its first partition or without partitionning, but it did not make a difference. Do you have any idea ? By the way, this is the first time I made such an advanced usage of the installer and I must say that I am very impressed. Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan partman.gz Description: GNU Zip compressed data preseed.txt.gz Description: GNU Zip compressed data hardware-summary.gz Description: GNU Zip compressed data syslog.gz Description: GNU Zip compressed data
Bug#636937: installation-guide: Please add Vcs-Browser field to debian/control.
Package: installation-guide Version: 20110122 Severity: wishlist Tags: patch Hello, Please add Vcs-Browser: http://anonscm.debian.org/viewvc/d-i/trunk/manual/ to debian/control. Just in case it helps, I attached a patch. Have a nice day, -- Charles Plessy, Tsurumi, Kanagawa, Japan. -- System Information: Debian Release: 6.0.2 APT prefers stable APT policy: (910, 'stable'), (900, 'testing'), (800, 'unstable'), (500, 'proposed-updates'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Index: debian/control === --- debian/control (révision 66750) +++ debian/control (copie de travail) @@ -4,6 +4,7 @@ Maintainer: Debian Install System Team debian-boot@lists.debian.org Standards-Version: 3.8.3 Vcs-Svn: svn://svn.debian.org/d-i/trunk/manual +Vcs-Browser: http://anonscm.debian.org/viewvc/d-i/trunk/manual/ Build-Depends: debhelper (= 6) Build-Depends-Indep: docbook, docbook-xml, docbook-xsl, xsltproc, gawk, libhtml-parser-perl, w3m, poxml, jadetex, openjade | openjade1.3, docbook-dsssl, ghostscript, texlive-lang-cyrillic, texlive-lang-czechslovak, texlive-lang-finnish, texlive-lang-french, texlive-lang-german, texlive-lang-greek, texlive-lang-italian, texlive-lang-other, texlive-lang-portuguese, texlive-lang-spanish, texlive-lang-swedish, texlive-lang-vietnamese, ko.tex-base, cm-super # This comment can also be used to generate a Build-Depends-Indep line, by
Bug#592550: support for SSH-Key authentication (Supports Eucalyptus and Amazon EC2)
Le Wed, Jul 20, 2011 at 12:55:23PM -0400, Kyle Moffett a écrit : On Jul 19, 2011, at 19:22, Charles Plessy wrote: Since the Amazon EC2 can boot on custom kernels, it looks like that with this patch (or using Petter's workaround), it would be possible to prepare an Amazon Machine Image (AMI) of Debian-Installer itself, boot it from GRUB (through Amazon's kernels using PVGRUB and preseed it via initrd, in order to install Debian on an Amazon Elastic Block. Is that what you have tried ? That is exactly what I have done. The actual construction of the AMI containing the Debian-Installer is a bit of a pain; I have a shell-script wrapper around the Amazon EC2 tools in order to do marshall it into the official EC2 format, but the patches necessary to make the SSH Console and Debian-Installer play nicely were surprisingly small. Basically, I created a new Debian-Installer image variant with a built-in preseed file containing references to the standard Amazon EC2 infrastructure for loading SSH keys and downloading additional preseed from EC2 user-data. This is really exciting. I was also wondering if the init and grub scripts that are usually installed on EC2 images could be properly packaged, so that the creation of an AMI would be a purely native Debian installation, with d-i preseeding. If you like the idea, would you be interested to co-maintain such a package, after inviting the other AMI producers (http://wiki.debian.org/Cloud/AmazonEC2Image) ? The source package could be team-maintained on Alioth within the collab-maint project, or incubated in the pkg-escience project for instance. Have a nice day, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110724035250.ga22...@merveille.plessy.net
Bug#606725: installation-guide: TFTP daemons now use /srv/tftp.
Package: installation-guide Version: 20100518 Severity: minor Dear D-I team, first of all, thank you for your hard work. I recently installed Squeeze, and it went very smoothly. I noticed a small inconsistency in the installation manual: TFTP daemons now use /srv/tftp instead of /var/lib/tftpboot. A command like the following will correct the manual and the howto. grep -r '/var/lib/tftpboot' . | grep -v svn | cut -f1 -d':' | xargs sed -i 's|/var/lib/tftpboot|/srv/tftp|' Since I did not figure out if it is necessary to run it on the whole tree, only the xml files (not the po), or only the english version, I am not submitting the corresponding patch. But let me know if there is something I can do. Have a nice week-end, -- Charles Plessy, Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101211093751.5625.56555.report...@aqwa.igloo
Bug#603444: debian-policy: clarifications in appendix b.4 of debian install guide
reassign 603444 installation-guide thanks Le Sun, Nov 14, 2010 at 12:09:21AM -0700, Gregory Nowak a écrit : Package: debian-policy Severity: normal Some explanations in appendix b.4 of the Debian installation guide are unclear to me, and might therefore be unclear to others. Dear Gregory, You sent your bug report to the wrong package. I reassigned it to the installation-guide package. Have a nice day, -- Charles Plessy, Tsurumi, Kanagawa. 1. Section b.4.3 states: Use the following settings if you wish to make use of the network-console # component for remote installation over SSH. This only makes sense if you # intend to perform the remainder of the installation manually. Where can one find more info on this? At what point can the user take manual control over the installation process when using this method? If a user doesn't have a monitor attached to the computer, how would one know when it is possible to take manual control of the installation process? Depending on the answer to the question on where one can find more info, answers to the 2 questions following that one may not be necessary. 2. Section b.4.4 reads: #d-i mirror/protocol string ftp d-i mirror/country string manual d-i mirror/http/hostname string http.us.debian.org d-i mirror/http/directory string /debian Even though the first line says mirror/protocol string ftp, some users may find it confusing that all other values begin with mirror/http/... I think it would be a good idea to state something like: If you will use an ftp mirror, fill mirror/http/hostname, and mirror/http/directory, with information for the ftp mirror you're going to use. 3. Section b.4.6 reads: If the system has free space you can choose to only partition that space. #d-i partman-auto/init_automatically_partition select biggest_free How will this space be partitioned, as one big partition, or several smaller partitions? If several smaller partitions, then how is the size and mount point of each partition determined? What file system will be used on partitions created in this way? Will this free space also have a swap partition created, or not? The phrase Alternatively, you can specify a disk to partition. leads me to understand that the discussion about recipes below doesn't apply to automatically partitioning the biggest free space, thus my confusion. -- System Information: Debian Release: 5.0.6 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.27.21 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101114072023.gg4...@merveille.plessy.net -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101114072023.gg4...@merveille.plessy.net
Re: no sound on powermac3,3 (powerbook g4 550) debian502 gnome
Le Sun, Sep 13, 2009 at 10:27:01PM -0300, Rogério Brito a écrit : It seems that on some G5 machines, snd-powerpc could cause some lock ups, but the problem was reported ages ago and it seems to have been fixed. I'm not sure if Charles Plessy (in CC) still has his dual G5 and can test it, but I seem to recall that he once had the problem and, months latter, tested it again and didn't find any problems with snd-powermac. Helo Rogério and everybody, I have indeed made a test last year on an iMac G5, and did not experience lock ups anymore, so I think that the problem is solved on that side. By the way, I have returned the now old dual G5 to the computer service at my workplace and will not be able to make tests on it anymore as I am now using the amd64 port on Intel hardware now. I still have the iMac G5 at home, and it is used by somebody else. Linux is still bootable, but unless nobody else can do tests, I would prefer not taking risks by making new installer tests. I have updated the following wiki page accordingly (by deleting my name). http://wiki.debian.org/VolunteersForPowerPC Have a nice day, and thank you very much for your dedication to this port ! -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#500464: installation-reports: No boot after reading help, and no mouse (but the rest is fine).
Subject: installation-reports: No boot after reading help, and no mouse (but the rest is fine). Package: installation-reports Severity: important Hi, after reading help, pressing enter does not manage to boot the installer, but crashes with the following message: Could not find kernel image: linux Other problem, the mouse did not work (immobile pointer). I could install using the tab key however. Everything else went fine, congratulations. I found the question about console-setup a bit difficult for non-experts. -- Package-specific info: Boot method: network Image version: http://people.debian.org/~aba/d-i/images/daily/netboot/gtk/netboot.tar.gz 20080928-11:08 Date: Date and time of the install Machine: SONY VAIO desktop Partitions: df -Tl will do; the raw partition table is preferred Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to [EMAIL PROTECTED] == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=5.0 (lenny) - installer build 20080928-11:03 X_INSTALLATION_MEDIUM=netboot-gtk == Installer hardware-summary: == umame -a: Linux aqwa 2.6.26-1-amd64 #1 SMP Wed Sep 10 15:31:12 UTC 2008 x86_64 unknown lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 0c) lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c) lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a03] (rev 0c) lspci -knn: 00:1a.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 [8086:2834] (rev 03) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1a.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 [8086:2835] (rev 03) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1a.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 [8086:283a] (rev 03) lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: Kernel modules: ehci-hcd lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD Audio Controller [8086:284b] (rev 03) lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 [8086:283f] (rev 03) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 [8086:2841] (rev 03) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 [8086:2843] (rev 03) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 [8086:2830] (rev 03) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1d.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 [8086:2831] (rev 03) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1d.2 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 [8086:2832] (rev 03) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1d.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 [8086:2836] (rev 03) lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: Kernel modules: ehci-hcd lspci -knn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev f3) lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller [8086:2815] (rev 03) lspci -knn: 00:1f.1 IDE interface [0101]: Intel
Bug#493330: installation-reports: Successful installation of Lenny on an iMac G5 revA ; Japanese keyboard missing.
Package: installation-reports Severity: normal Tags: l10n Dear Debian Installer team, I report a successful installation of Lenny on a iMac G5 revA. It went very somothly and I appreciate that there are much less questions asked in the non-expert mode. Actually, I wonder if the tasksel questions are useful in this mode, as they are very detailed for servers, but do not offer flexibility for Desktop machines (such as installing anogher desktop manager). Since many questions have been suppressed, my timezone has been guessed wrongly: I installed in French but live in Japan, and the timezone was Paris. Another issue was the choice of the keyboard. No japanese layout was proposed. I opened a bug about his some time ago and it was closed after modifying console-data: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=342756 I think that an explanation why the jp106 keymap is not proposed may be that it is not specific to macintoshes. However it works well with them and handles Apple special keys, so it is safe to add it. Have a nice week-end, and thanks for the great work you made on the installer. -- Charles Plessy, Tsurumi, Kanagawa, Japan -- Package-specific info: Boot method: CD Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/powerpc/iso-cd/debian-testing-powerpc-netinst.iso 29-Jul-2008 23:22 Date: 02 August 2008 Machine: iMac G5 revA Partitions: df -Tl will do; the raw partition table is preferred Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to [EMAIL PROTECTED] == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=5.0 (lenny) - installer build 20080729-03:30 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == umame -a: Linux sorbet 2.6.24-1-powerpc64 #1 SMP Sat May 10 20:57:22 UTC 2008 ppc64 unknown lspci -knn: :f0:0b.0 Host bridge [0600]: Apple Computer Inc. U3L AGP Bridge [106b:0058] lspci -knn: :f0:10.0 VGA compatible controller [0300]: nVidia Corporation NV34M [GeForce FX Go5200] [10de:0329] (rev a1) lspci -knn: 0001:00:01.0 PCI bridge [0604]: Apple Computer Inc. Shasta PCI Bridge [106b:0053] lspci -knn: 0001:00:02.0 PCI bridge [0604]: Apple Computer Inc. Shasta PCI Bridge [106b:0054] lspci -knn: 0001:00:03.0 PCI bridge [0604]: Apple Computer Inc. Shasta PCI Bridge [106b:0055] lspci -knn: 0001:01:01.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03) lspci -knn: Kernel driver in use: b43-pci-bridge lspci -knn: Kernel modules: ssb lspci -knn: 0001:01:07.0 Class [ff00]: Apple Computer Inc. Shasta Mac I/O [106b:004f] lspci -knn: Kernel driver in use: macio lspci -knn: 0001:01:0b.0 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43) lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 0001:01:0b.1 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43) lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 0001:01:0b.2 USB Controller [0c03]: NEC Corporation USB 2.0 [1033:00e0] (rev 04) lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: Kernel modules: ehci-hcd lspci -knn: 0001:02:0c.0 IDE interface [0101]: Broadcom K2 SATA [1166:0240] lspci -knn: Kernel driver in use: sata_svw lspci -knn: Kernel modules: sata_svw lspci -knn: 0001:02:0d.0 Class [ff00]: Apple Computer Inc. Shasta IDE [106b:0050] lspci -knn: Kernel driver in use: ide-pmac lspci -knn: 0001:02:0e.0 FireWire (IEEE 1394) [0c00]: Apple Computer Inc. Shasta Firewire [106b:0052] lspci -knn: Kernel driver in use: firewire_ohci lspci -knn: Kernel modules: firewire-ohci lspci -knn: 0001:03:0f.0 Ethernet controller [0200]: Apple Computer Inc. Shasta (Sun GEM) [106b:0051] lspci -knn: Kernel driver in use: gem lspci -knn: Kernel modules: sungem lsmod: Module Size Used by lsmod: nls_iso8859_1 10504 0 lsmod: nls_cp437 12168 0 lsmod: nls_utf87424 0 lsmod: ufs
Bug#466066: installation-reports: GRUB installation failed
Le Sat, Feb 16, 2008 at 12:54:46PM +0100, Frans Pop a écrit : Feb 16 07:06:48 apt-setup: warning: /usr/lib/apt-setup/generators/90services-select returned error code 30; discarding output Did you do anything special at that stage? If not, could you please run a new installation and, before apt-setup is started, add a line 'set -x' (below the line 'set -e') in the file /usr/lib/apt-setup/generators/90services-select Hi Frans, I did not do anything special with the installer. Here is a syslog.gz from an installation in which I added 'set -x'. The error is still there. Have a nice day, -- Charles syslog.gz Description: Binary data
Bug#440446: debian-installer: daily net gtk install frozen when applying partition changes.
Le Thu, Dec 13, 2007 at 01:06:39PM +0100, Frans Pop a écrit : Charles: if you can still reproduce this, could you run partman after adding a 'set -x' at the top of /lib/partman/definitions.sh? Hi Frans, I am affraid that I will not have opportunity to do this before January: I will use this laptop for a seminar, so I am too scared to play with partman before. After, I will be far from my tftpd server, and the laptop has no CD-ROM drive. But please do not hesitate to ping me if I do not answer before the 15th of January. Alternatively, I may have strongly over-estimated the complexity of booting the isntaller from an USB stick ? Then I could do the test after the seminar during my holidays… But I do not find anything in http://people.debian.org/~joeyh/d-i/images/daily/ (the link for ther images (netboot, usb stick, floppy, etc)). Have a nice day, -- Charles Plessy http://charles.plessy.org Wakō, Saitama, Japan
Bug#443272: Partitions detected with mac-fdisk, but not with partman.
[CC to [EMAIL PROTECTED] Does it work for someone ?] Dear installer team, I have tested the latest daily install disk, Debian GNU/Linux testing Lenny - Official Snapshot powerpc BC Binary-1 20071104-10:21, and when it arrives to Partman, it does not manage to detect my partition table. Here is the output of mac-fdisk: /dev/sda #type name length base ( size ) system /dev/sda1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/sda2 Apple_Free893149168 @ 64 (425.9G) Free space /dev/sda3 Apple_Boot eXternal booter 262144 @ 893149232 (128.0M) Unknown /dev/sda4 Apple_HFSX Apple_HFSX_Untitled_1 83361776 @ 893411376 ( 39.7G) Unknown /dev/sda5 Apple_Free 16 @ 976773152 ( 8.0k) Free space Block size=512, Number of Blocks=976773168 DeviceType=0x0, DeviceId=0x0 For the partman log, I attach it to the mail because it is a bit long. You can ignore the windows drive on sdb. It is not the one on which I will install Debian, it will be removed soon, and the problem I have with partman happened already before I connected it. I hope that you can help me to install Debian on this computer. On my side, I can test updated versions of the installer on this one, and on an iMac G5 if necessary. Have a nice day, -- Charles Plessy http://charles.plessy.org Wako, Saitama, Japan /bin/partman: *** /lib/partman/init.d/01unsupported: *** /lib/partman/init.d/30parted: *** parted_server: === Starting the server parted_server: main_loop: iteration 1 parted_server: Opening infifo /lib/partman/init.d/30parted: IN: OPEN =dev=sda /dev/sda parted_server: Read command: OPEN parted_server: command_open() parted_server: Request to open =dev=sda parted_server: Opening outfifo parted_server: OUT: OK parted_server: OUT: OK parted_server: Note =dev=sda as unchanged parted_server: Closing infifo and outfifo parted_server: main_loop: iteration 2 parted_server: Opening infifo /lib/partman/init.d/30parted: IN: OPEN =dev=sdb /dev/sdb parted_server: Read command: OPEN parted_server: command_open() parted_server: Request to open =dev=sdb parted_server: Opening outfifo parted_server: OUT: OK parted_server: OUT: OK parted_server: Note =dev=sdb as unchanged parted_server: Closing infifo and outfifo parted_server: main_loop: iteration 3 parted_server: Opening infifo /lib/partman/init.d/31md-devices: *** /lib/partman/init.d/35dump: *** /lib/partman/init.d/35dump: IN: DUMP =dev=sda parted_server: Read command: DUMP parted_server: command_dump() parted_server: Opening outfifo parted_server: OUT: OK parted_server: Closing infifo and outfifo parted_server: main_loop: iteration 4 parted_server: Opening infifo Device: yes Model: ATA ST3500630AS Path: /dev/sda Sector size: 512 Sectors: 976773168 Sectors/track: 63 Heads: 255 Cylinders: 60801 Partition table: no /lib/partman/init.d/35dump: IN: DUMP =dev=sdb parted_server: Read command: DUMP parted_server: command_dump() parted_server: Opening outfifo parted_server: OUT: OK parted_server: Closing infifo and outfifo parted_server: main_loop: iteration 5 parted_server: Opening infifo Device: yes Model: ATA FUJITSU MHV2100B Path: /dev/sdb Sector size: 512 Sectors: 195371568 Sectors/track: 63 Heads: 255 Cylinders: 12161 Partition table: yes Type: msdos Partitions: # id length typefs pathname (0,0,0) (0,0,62)-1 0-32255 32256 primary label /dev/sdb-1 (0,1,0) (6,254,62) 1 32256-57576959 57544704primary fat16 /dev/sdb1 (7,0,0) (12160,254,62) 2 57576960-100027630079 99970053120 primary ntfs/dev/sdb2 (12161,0,0) (12161,80,62) -1 100027630080-100030242815 2612736 primary label /dev/sdb-1 Dump finished. /lib/partman/init.d/50lvm: *** /lib/partman/init.d/50lvm: IN: PARTITIONS =dev=sda parted_server: Read command: PARTITIONS parted_server: command_partitions() parted_server: Opening outfifo parted_server: OUT: OK parted_server: No partitions parted_server: OUT: parted_server: Closing infifo and outfifo parted_server: main_loop: iteration 6 parted_server: Opening infifo /lib/partman/init.d/50lvm: IN: PARTITIONS =dev=sdb parted_server: Read command: PARTITIONS parted_server: command_partitions() parted_server: Opening outfifo parted_server: OUT: OK parted_server: OUT: 1 32256-57576959 57544704primary fat16 /dev/sdb1 parted_server: OUT: 2 57576960-100027630079 99970053120 primary ntfs /dev/sdb2 parted_server
Bug#443272: Partitions detected with mac-fdisk, but not with partman.
Le Mon, Nov 05, 2007 at 12:36:04PM +0100, Frans Pop a écrit : You do not say anything about what type of system this is. Please do always provide that information! Ah, sorry, I thought that the information in the first message of the bug report was sufficient. I attached the hardware-summary to this mail to be more complete. My machine is a bi-G5 powermac with a new 500 Gb hard drive that contains a fresh OS X (10.4) installation and a lot of free space to do some real work with Debian. - to check if the drive itself (and the partition table) are correctly identified by the kernel: what's the output of 'dmesg | grep sda' sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sda: [mac] sda1 sda2 sda3 sda4 sda5 sd 0:0:0:0: [sda] Attached SCSI disk - to check if libparted is the problem: could you check (using some life CD for example) if the utility 'parted' recognizes the table I tested with a Ubuntu 6.10 live, because I am not aware of a Debian live CD which boots on G5 machines. [EMAIL PROTECTED]:~# parted /dev/sda GNU Parted 1.7.1 Using /dev/sda Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) print Error: The partition's data region doesn't occupy the entire partition. Ignore/Cancel? i Disk /dev/sda: 500GB Sector size (logical/physical): 512B/512B Partition Table: mac Number Start End SizeFile system Name Flags 1 0.51kB 32.8kB 32.3kB primary 3 457GB 457GB 134MB hfs+ primary 4 457GB 500GB 42.7GB hfsx primary (parted) quit It seems that something in this partition table makes parted uncomfortable... Thanks for your prompt reply ! -- Charles umame -a: Linux gslc12 2.6.22-2-powerpc64 #1 SMP Thu Aug 30 21:51:55 CEST 2007 ppc64 unknown lspci -nn: :f0:0b.0 Host bridge [0600]: Apple Computer Inc. U3H AGP Bridge [106b:0059] lspci -nn: :f0:10.0 VGA compatible controller [0300]: ATI Technologies Inc RV350 AP [Radeon 9600] [1002:4150] lspci -nn: 0001:00:01.0 PCI bridge [0604]: Apple Computer Inc. K2 HT-PCI Bridge [106b:0045] lspci -nn: 0001:00:02.0 PCI bridge [0604]: Apple Computer Inc. K2 HT-PCI Bridge [106b:0046] lspci -nn: 0001:00:03.0 PCI bridge [0604]: Apple Computer Inc. K2 HT-PCI Bridge [106b:0047] lspci -nn: 0001:00:04.0 PCI bridge [0604]: Apple Computer Inc. K2 HT-PCI Bridge [106b:0048] lspci -nn: 0001:00:05.0 PCI bridge [0604]: Apple Computer Inc. K2 HT-PCI Bridge [106b:0049] lspci -nn: 0001:01:07.0 Unknown class [ff00]: Apple Computer Inc. K2 KeyLargo Mac/IO [106b:0041] (rev 60) lspci -nn: 0001:01:08.0 USB Controller [0c03]: Apple Computer Inc. K2 KeyLargo USB [106b:0040] lspci -nn: 0001:01:09.0 USB Controller [0c03]: Apple Computer Inc. K2 KeyLargo USB [106b:0040] lspci -nn: 0001:02:0d.0 Unknown class [ff00]: Apple Computer Inc. K2 ATA/100 [106b:0043] lspci -nn: 0001:02:0e.0 FireWire (IEEE 1394) [0c00]: Apple Computer Inc. K2 FireWire [106b:0042] lspci -nn: 0001:03:0f.0 Ethernet controller [0200]: Apple Computer Inc. K2 GMAC (Sun GEM) [106b:004c] lspci -nn: 0001:04:0c.0 IDE interface [0101]: Broadcom K2 SATA [1166:0240] lspci -nn: 0001:05:01.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03) lspci -nn: 0001:05:0b.0 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43) lspci -nn: 0001:05:0b.1 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43) lspci -nn: 0001:05:0b.2 USB Controller [0c03]: NEC Corporation USB 2.0 [1033:00e0] (rev 04) lspci -vnn: :f0:0b.0 Host bridge [0600]: Apple Computer Inc. U3H AGP Bridge [106b:0059] lspci -vnn: Flags: bus master, 66MHz, medium devsel, latency 16 lspci -vnn: Capabilities: [80] AGP version 3.0 lspci -vnn: lspci -vnn: :f0:10.0 VGA compatible controller [0300]: ATI Technologies Inc RV350 AP [Radeon 9600] [1002:4150] lspci -vnn: Subsystem: ATI Technologies Inc RV350 AP [Radeon 9600] [1002:4150] lspci -vnn: Flags: bus master, 66MHz, medium devsel, latency 16, IRQ 48 lspci -vnn: Memory at a000 (32-bit, prefetchable) [size=256M] lspci -vnn: I/O ports at 0400 [size=256] lspci -vnn: Memory at 9000 (32-bit, non-prefetchable) [size=64K] lspci -vnn: Expansion ROM at 9002 [size=128K] lspci -vnn: Capabilities: [58] AGP version 3.0 lspci -vnn: Capabilities: [50] Power Management version 2 lspci
Bug#443272: Partitions detected with mac-fdisk, but not with partman.
merge 354951 378593 388085 443272 thanks Le Mon, Nov 05, 2007 at 01:41:17PM +0100, Frans Pop a écrit : On Monday 05 November 2007, Charles Plessy wrote: Using /dev/sda Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) print Error: The partition's data region doesn't occupy the entire partition. Ignore/Cancel? i This error must be what's causing partman to not recognize the disk. Unfortunately, I just realised I am not the first to report it… You can count on me to make tests : I really need linux on this computer. -- Charles
Bug#443272: Lenny on Imac G5 no windfarm module
retitle 443272 installation-reports: Partition not detected on a ST3500630AS Seagate 500 Go drive thanks Le Mon, Oct 01, 2007 at 10:16:38AM +0200, Michel Dänzer a écrit : On Sun, 2007-09-30 at 10:33 -0700, Dylan Beaudette wrote: Most things appear to work, however the kernel/drivers/macintosh/ directory is missing form the pre-installed kernel modules. This is somewhat of a let down- without the windfarm module the computer goes into vacuum cleaner mode. Is there any way that I can get a kernel with these modules? Could it be as simple as upgrading to Sid ? Yes: http://packages.debian.org/search?suite=sidarch=anymode=filenamesearchon=contentskeywords=windfarm Excellent, it means that the same problem with the installer should probably dissapear in the future (if it has not already). -- Charles Plessy http://charles.plessy.org Wako, Saitama, Japan
Bug#443272: installation-reports: Partition not detected on a ST3500630AS Seagate 500 Go drive ; fan speed at maximum
Package: installation-reports Severity: normal Boot method: CD-ROM Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/powerpc/iso-cd/debian-testing-powerpc-netinst.iso (b6671cb1e2652dd49de8168789fc83fa, 2007-0918-09:54) Date: Thu, 20 Sep 2007 15:56:25 +0900 Machine: Power Mac G5 (PowerMac7,3) Processor: PowerPC G5 (3.0) Memory: 1 Go Partitions: pdisk l /dev/disk0 (under OS X 10.2.10 8R218) Partition map (with 512 byte blocks) on '/dev/disk0' #:type name length base ( size ) 1: Apple_partition_map Apple63 @ 1 2: Apple_Free 893149168 @ 64(425.9G) 3: Apple_Boot eXternal booter 262144 @ 893149232 (128.0M) 4: Apple_HFSX Apple_HFSX_Untitled_1 83361776 @ 893411376 ( 39.7G) 5: Apple_Free 16 @ 976773152 Device block size=512, Number of Blocks=976773168 (465.8G) DeviceType=0x0, DeviceId=0x0 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] did not detect my Mac partitions Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Dear Installer team, In order to install a dual boot on a machine with a new drive, I first re-installed and upgraded OS X, leaving free space before the system partition in order to install Linux. However, the installer did not detect the OS X (journalled, case-sensitive) partition. Etch's installer did not manage either. Is the disk too big? (500 Go) As a side problems, I had the fans running at full speed with the daily build (not with Etch). Apart from this, I have the two following comments : - The installer assumes that the keyboard will be a mac one, and does not give opportunity to declare another one. However, I am using a Lenovo keyboard with american layout. - Very often I was asked by the installer if I want to load the PCMCIA modules, and after saying no I was always asked or which options to passe to the modules. Many thanks for your work. I hope you or somebody from the debian-powerpc list (CCed) can help me to install the dual boot (even at full fan speed), as I need it at work. Have a nice day, -- Charles Plessy, Wako, Saitama, Japan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#440446: debian-installer: daily net gtk install frozen when applying partition changes.
Le Tue, Sep 04, 2007 at 03:03:40PM -0400, Joey Hess a écrit : Sep 2 09:56:29 partman: No matching physical volumes found Sep 2 09:56:29 partman: Reading all physical volumes. This may take a while... Sep 2 09:56:29 partman: No volume groups found Sep 2 09:57:25 init: Process '/sbin/debian-installer' (pid 1094) exited. Scheduling it for restart. The most common reason for d-i to exit like that would be if it ran out of memory. (A crash is also a possibility.) How much ram does the machine have, and how large is the largest partition you were creating? What filesystem? Hi, the machine has 1.5 Go of memory (1 Go + 512 Mo). In this particular example, I suppressed a 10 Go partition and replaced it by one of 8 and one of 2 (I think) to trigger the bug. But I had the same problem with other combinations. Have a nice day, -- Charles Plessy http://charles.plessy.org Wako, Saitama, Japan
Bug#440446: debian-installer: daily net gtk install frozen when applying partition changes.
Package: debian-installer Severity: normal Hi, I tried this evening to install Debian on a X60 Thinkpad with the netinstall on GTK interface (af0b43f5ee35ece1321e719f21f286f0), and it hung just after confirming the changes to the partition table (manual partitioning). I then tried an earlier build (3e97fc130ec7f68d88539f7bba2fe54f, 20070830-09:01) and it went through this step. My bad, I picked the text install instead of the gtk one for this time. I can make more serious tests if you are interested (right now, I am going to bed). In particular, I was not brave enough to copy by hand the messages on the F1 and F4 consoles, but tomorrow I can for instance send digital pictures... Have a nice day, -- Charles Plessy Wako, Saitama, Japan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#440446: debian-installer: daily net gtk install frozen when applying partition changes.
Would be nice if you can run d-i on expert mode and after it loads the modules from network you use the Save logs option and use the web option. So when it freeze, you can see if you can grab syslog using http for it. Hi, I reproduced the bug this morning. I think that it happens when partitions are modified. Once, to go faster, I only selected already existing patitions, and d-i proceeded to the next step without problem. In the attempt whose logs I send you, I think I triggered the bug by splitting one unused patition. What happens is that instead of starting to format, d-i blinks and transiently show the console. I could see the word killed (maybe in all caps ?) printed somewhere, but strangely I do not find it on the logs. After this, the http log server has to be restarted before triggering the second half of the bug, as it seems to be killed as well. When re-starting the partition manager, d-i hangs (oviously from the partman logs, it loops). Had I stayed in non-expert mode, d-i would have gone from step1 to step2 of the bug without giving me an opportunity to restart the log server. This is why in my initial report, I had the impression that it hangs after trying to apply the changes to the partition. In fact, it restarts, and then loops. Have a nice day, -- Charles Plessy http://charles.plessy.org Wako, Saitama, Japan hardware-summary.txt.gz Description: Binary data partman.txt.gz Description: Binary data syslog.txt.gz Description: Binary data
[workaround] Re: Did not manage to resize an HFS+ partition on a powermac G5.
Le Fri, Apr 27, 2007 at 09:28:01PM +0900, Charles Plessy a écrit : Dear lists, I am trying to install Debian on a powermac7,3 at work, but I did not manage to resize the main HFS+ partition. Although I have a backup, I would like to avoid reinstalling MacOS X. I saw on the web reports from 2005 in which an HFS+ partition was sucessfully resized with the debian-installer, so I wonder what I did wrong. Quick answer to myself: I started a live CD (Ubuntu 6.10, live.debian.net does not seems to support powerpc yet) and tried to move the partition with gparted. Interstingly, it does not manage to move the partition neither, but it accepts to redimention it to the right. I then copied it and deleted the original to install Etch instead. Everything now works fine (except display problems), and yaboot manages to start the cloned osX partition. Have a nice day, -- Charles Plessy http://charles.plessy.org Wako, Saitama, Japan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Did not manage to resize an HFS+ partition on a powermac G5.
Dear lists, I am trying to install Debian on a powermac7,3 at work, but I did not manage to resize the main HFS+ partition. Although I have a backup, I would like to avoid reinstalling MacOS X. I saw on the web reports from 2005 in which an HFS+ partition was sucessfully resized with the debian-installer, so I wonder what I did wrong. I am using the netinst for Etch, in which parted is version 1.7.1. when I try to resize with a command such as resize 3 100GB 50GB, I got the following error message: Error: Unable to satisfy all constraints on the partition. Here is what I know from the disk gslc12|charles|$ diskutil info / Device Node:/dev/disk0s3 Device Identifier: disk0s3 Mount Point:/ Volume Name:Macintosh HD File System:HFS+ Owners: Enabled Partition Type: Apple_HFS Bootable: Is bootable Media Type: Generic Protocol: ATA SMART Status: Verified UUID: E725DF25-8BE1-384B-A630-5BAAE5028069 Total Size: 233.6 GB Free Space: 198.2 GB Read Only: No Ejectable: No Device Location:A (upper) I disabled journaling with sudo diskutil disableJournal / Any idea ? I am a bit frustrated of not being able to use the packages I made... Have a nice day, -- Charles Plessy http://charles.plessy.org Wako, Saitama, Japan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: D-I RC2 images available for testing
Le Mon, Mar 12, 2007 at 04:05:09PM +0100, Frans Pop a écrit : For all architectures, except for m68k, installer and CD/DVD images of what is going to be D-I RC2 are now available for testing. RC2 is scheduled to be the D-I release shipped with Etch. Netboot, floppy and hd-media images are available from: http://ftp.nl.debian.org/debian/dists/etch/main/installer-arch/rc2/images/ CD/DVD images are available from: http://www.debian.org/devel/debian-installer/ Dear D-I team, I wanted to give a try to the RC2 installer, and found a gtk image for powerpc64 in the ftp.nl site. This image does not work (crash of the graphical interface during startup), but in the end, I am wondering if it was supposed to work at all, or if it is there because the iso is built automatically on each platform. I then wanted to test RC2 from www.debian.org, but could not decide between the daily and weekly builds. Also, I think that I remember that RC1 was available separately from the daily/weekly built images, but I can not find RC2... I would like to check if everything is OK on iMac G5, which image shall I use ? Have a nice day, -- Charles Plessy http://charles.plessy.org Wako, Saitama, Japan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Fan control OK on PowerMac8,1 (iMac G5)
Le Wed, Mar 14, 2007 at 05:56:48PM +0530, Praveen A a écrit : 2007/3/14, Charles Plessy [EMAIL PROTECTED]: CD/DVD images are available from: http://www.debian.org/devel/debian-installer/ I would like to check if everything is OK on iMac G5, which image shall I use ? You can use either the daily-built (no full cd/dvd images only net install) or weekly built images. AFAIK both are based on RC2. Thank you all for your answers, everything went fine for a very minimal install ; my primary goal was to make sure that the problem with the loud fans was solved (PowerMac8,1 iMac G5). I used the daily netinst of yesterday (3dd2144e53255fe6ecf4273176c25107). I am not filing a bug report since I have to hurry up this morning. Also, I added a line in the table of the wiki page which lists the problems with the GTK installer on powermacs. Have a nice day, -- Charles Plessy http://charles.plessy.org Wako, Saitama, Japan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian has failed us
Le Tue, Jan 16, 2007 at 10:35:52AM -0500, Joey Hess a écrit : Charles Plessy wrote: How about releasing a RC1.5, then, with a 2.6.18 as similar as possible as the one forecasted in testing ? There are of course all kinds of ways to hack around this, but all of them are suboptimal. For example, we could produce a hacked CD that includes unstable's kernel. And updated version of everything it depends on. And everything those dependencies depend on. But this would only work for systems installed from CD. Setting this up would take significant developer time, and that would be time that does not in the end benefit the etch release at all. Dear Joey, priorities are something very personnal, and I trust the members of the DI team to manage theirs well. I think that what the powerpc port needs is somebody with priorities focused on getting things done on powerpc. With this goal, the duplicated work you described is not necessarly a waste. At least, the criteria for deciding to do it or not become different. I do not know how difficult it would be to ease that kind of temporary digression. A sort of pbuilder checking if local patches to official packages are available, maybe ? Have a nice day, -- Charles Plessy http://charles.plessy.org Wako, Saitama, Japan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian has failed us
Le Tue, Jan 16, 2007 at 07:14:22AM +0100, Christian Perrier a écrit : Actually, it's equally frustrating for all of us that we *can't* release a new D-I despite the team plan to release RC2 a few weeks after RC1. We can't do this because the 2.6.18 kernel is not in testing. Hi all, How about releasing a RC1.5, then, with a 2.6.18 as similar as possible as the one forecasted in testing ? This would help to keep the momentum on the solving of some problems. For instance, I tested RC1 and another build for the loud fans problems on iMac G5. I did this as a service to the community: I do not suffer from this problem anymore, and I am not loyal to the powerpc arch (If my iMac breaks, I would consider any arch for replacement). In my last test, the fans were silent in the installer, but not on the newly installed system. There has been a fix since. Or maybe not. I was not pointed to something to test, and I have other projects for my Debian time. The momentum for solving this problem is being lost. What is needed to keep the ports alive is some kind of leadership, simply focused on getting things done and coordinating people who can help if asked, but who prefer doing something else otherwise. As I said in a previous mail (sent on -powerpc only), the problem is that in the current way Debian operates its ports, getting things done is often unavoidably getting somebody to do the things. This is bound to create personal conflicts from time to time. There is for the moment nobody who has : - time, - good relationship with all the key Debian infrastructures and packaging teams, - excellent knowledge of the aforementioned infrastructures and packages, - excellent knowledge of powerpc, - excellent social skills, - access to all hardware, - ... But aren't we looking for an imaginary superhero? If yes, then the question is to see if we can adapt the structure to the people instead of waiting for people to fit the structure. Would it be helpful if the ports had a bit more independance in Debian? At least the situation would be more dynamic if developpers who care for a port could do things directly by themselves, and one can not ask to the porters to be at the same time one members of the kernel, installer, release, buildd, ftp, and security teams... I hope that this message helps a bit to make the things progress. Have a nice day, -- Charles Plessy http://charles.plessy.org Wako, Saitama, Japan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#394971: This bugs affects the official powerpc port as well.
retitle 394971 [powerpc] [powerpc64] load the fan control modules. thanks Dear D-I team, This bug not only affects the unofficial powerpc64 port, but also and more importantly the official powerpc port, on iMac G5 hardware. I reported the problem for the first time in the following installation report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=340980 I confirmed that it is not fixed in RC1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=399334 It was figured out in the following report that the module windfarm_cpufreq_clamp had to be loaded before the windfarm_pm81 in order to start fan control: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=397942 I would like to stress out that once the fans start at full speed, it is not posible to stop them, as it is a low-level hardware preservation system triggered when the CPU reachs a defined temperature. Therefore, depending on the room temperature, the user will not have the opportunity to load the module by hand before the fans start. If it is not possible to integrate fan support to the installer, I would like to suggest the following addition to the installer errata: * Fan control is not supported during the installation on iMacs G5. You can safely run the installer with the fans at full speed. Please add windfarm_cpufreq_clamp and the relevant windfarm module to /etc/modules before rebooting, in order to have fan control on your newly installed Debian. Have a nice day, -- Charles Plessy http://charles.plessy.org Wako, Saitama, Japan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#342756: I think that the standard jp106 keymap can be used with japanese macintoshes.
Hi, I figured out that the japanese keyboard on recent macintosh computers is very similar to the standard jp106 keyboards of the PC world. The differences are mainly the keys to handle the input of chinese characters, but as this input is not possible with the linux console (if I understand correctly), it is not a problem. I am therfore pretty confident that one can use the jp106 keymap with the japanese macintosh keyboards, but I can not test as I just broke mine this morning. Have a nice day, -- Charles Plessy http://charles.plessy.org Wako, Saitama, Japan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
