date:20141124

Your message dated Tue, 25 Nov 2014 01:37:18 +0100
with message-id <20141125003718.gb3...@mraw.org>
and subject line Re: Bug#770812: tasksel: task-sysvinit to allow easy 
installation of non-systemd systems
has caused the Debian Bug report #770812,
regarding tasksel: task-sysvinit to allow easy installation of non-systemd 
systems
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
770812: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tasksel
Version: 3.29
Severity: wishlist

Hello,
It has been argued that late changes to the debian installer should be
avoided, and the maintainers have clearly expressed that they do not want
to add another debconf question:
https://lists.debian.org/debian-boot/2014/11/msg00408.html

My proposal is not to forcibly have users answer this question and decide
on an init system upon install. But there seems to be a larger userbase
that does want to keep sysvinit (in fact, I have switched all my systems
to systemd; but I do have an interest to have the noise eventually stop).

Can maybe the "tasks" system help here?
Can we have a task-sysvinit which depends on sysvinit-core, and which
conflicts systemd-sysv, and does installing such a task achieve the
desired results at installation time?

IMHO, adding a task package is a minimally invasive change to the install
process, and given the many requests for a sysvinit install option, this
may well be acceptable to the release managers. It's just not entirely
clear to me whether this works (i.e. when tasks are considered during
the installation phase, and whether this allows overriding the package
providing "init"), and the procedure necessary to get such a change
accepted into tasksel, the installation media, and jessie.

(And yes, I'm aware of the preseeding option to pass
  preseed/late_command="in-target apt-get install -y sysvinit-core"
to the installer. Essentially, I'm thinking of minimally invasive ways
to make this easier to access by end users - this is a pretty long
boot option to type, without the option of doing copy&paste when installing
a physical system...)

In the end, "Switch boot process to sysvinit" is a "task" that will end up
on the TODO list of many sysadmins (e.g. where because of some compatibility
or policy issue, they want to have all their servers on sysvinit)

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages tasksel depends on:
ii  apt 1.0.9.3
ii  debconf [debconf-2.0]   1.5.53
ii  liblocale-gettext-perl  1.05-8+b1
ii  perl-base   5.20.1-3
ii  tasksel-data3.29

tasksel recommends no packages.

tasksel suggests no packages.

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Erich Schubert  (2014-11-24):
> reopen 770812
> thanks

Please stop BTS ping-pong.

> Hello,
> Read the QUESTION.
> Not only the word "systemd".
> 
> You are still not listening to my actual question, only raising your
> sysvinit-shields.
> 
> 
> I'm asking if a TASK can solve this maybe more nicely than the other
> proposed approaches.
> 
> Bug #668001 does not mention this possibility as far as I can tell:
> The word "task" is NEVER discussed there.
> And the "late_command" solution is not userfriendly at all.
> 
> Therefore, this is a different wishlist item, against a different
> package, too...
> There is a reason why I filed this bug against *tasksel*, and not debootstrap!
> 
> I WILL accept a closing for this (non-RC, wishlist) bug IF you can
> point out a thread e.g. on debian-boot where the option of a
> task-sysvinit package to make the users happy is discussed.
> The tech-ctte discussion you cited also does NOT discuss this option...
> Because adding a task to the tasksel list IS something else than
> adding a whole new bootstrap option...
> 
> The only mentioning of tasksel in the tech-ctte thread is this:
> "1. The TC encourages a team (probably debian-boot) to provide a
> package (similar to tasksel), let's call it initsel,"
> Making a "similar" mechanism clearly is much more invasive than trying
> to use the existing tasksel mechanism, isn't it?
> 
> 
> But apparently you didn't read my question, only "systemd" and
> "sysvinit install".
> I begin to understand what the systemd op

Re: Bug#770259: eglibc: FTBFS: These critical programs are missing or too old: make

2014-11-24 Thread Scott Kitterman

On Tuesday, November 25, 2014 01:42:17 Cyril Brulebois wrote:
> Adam D. Barratt  (2014-11-24):
> > On Thu, 2014-11-20 at 14:30 +0100, Aurelien Jarno wrote:
> > > control: reassign -1 ftp.debian.org
> > > control: retitle -1 RM: debian-installer [sparc] -- out of date, doesn't
> > > build> 
> > > On Wed, Nov 19, 2014 at 06:37:40PM -0800, Daniel Schepler wrote:
> > [...]
> > 
> > > > Given that src:eglibc is pretty much obsoleted by src:glibc now, I'd
> > > > guess the easiest way to fix this would be to just request the
> > > > removal of src:eglibc from sid.
> > > 
> > > It has already been removed as it can be seen in bug #753420. It's still
> > > in the Sources files with Extra-Source-Only: yes, you should ignore
> > > these packages when doing archive rebuilds.
> > > 
> > > It's still there because debian-installer from sparc is still using it.
> > > I am therefore reassigning the bug to ftp.debian.org to ask for
> > > debian-installer removal on sparc.
> > 
> > ftp-master mentioned on IRC that they'd like an explicit KiBi-{,n}ack on
> > this; CCing.

Yes.  Thanks for the CC.

> Looking at the eglibc vs. glibc thing, it seems to be it wouldn't cause
> any troubles if debian-installer were to build again on sparc later,
> since it would then pull the new glibc package as Extra-Source-Only:
> yes? So there's no need to try and make sure it no longer builds there
> (n-f-u or similar)?
> 
> In which case: yes, it looks to me old binaries can be removed.
> 
> [ Cc-ing debian-boot@ just in case. ]

I'll wait until tomorrow (Tuesday) to do the removal to give people at least a 
little time to scream.

Scott K

signature.asc
Description: This is a digitally signed message part.

Re: Bug#770259: eglibc: FTBFS: These critical programs are missing or too old: make

Adam D. Barratt  (2014-11-24):
> On Thu, 2014-11-20 at 14:30 +0100, Aurelien Jarno wrote:
> > control: reassign -1 ftp.debian.org
> > control: retitle -1 RM: debian-installer [sparc] -- out of date, doesn't 
> > build
> > 
> > On Wed, Nov 19, 2014 at 06:37:40PM -0800, Daniel Schepler wrote:
> [...] 
> > > Given that src:eglibc is pretty much obsoleted by src:glibc now, I'd 
> > > guess the
> > > easiest way to fix this would be to just request the removal of 
> > > src:eglibc from
> > > sid.
> > 
> > It has already been removed as it can be seen in bug #753420. It's still
> > in the Sources files with Extra-Source-Only: yes, you should ignore
> > these packages when doing archive rebuilds.
> > 
> > It's still there because debian-installer from sparc is still using it.
> > I am therefore reassigning the bug to ftp.debian.org to ask for
> > debian-installer removal on sparc.
> 
> ftp-master mentioned on IRC that they'd like an explicit KiBi-{,n}ack on
> this; CCing.

Looking at the eglibc vs. glibc thing, it seems to be it wouldn't cause
any troubles if debian-installer were to build again on sparc later,
since it would then pull the new glibc package as Extra-Source-Only:
yes? So there's no need to try and make sure it no longer builds there
(n-f-u or similar)?

In which case: yes, it looks to me old binaries can be removed.

[ Cc-ing debian-boot@ just in case. ]

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#769996: debian-installer: Possible help text for win32diskimager users

2014-11-24 Thread Paul Wise

On Tue, Nov 25, 2014 at 4:26 AM, Holger Wansing wrote:

> [   Maybe this could better be added to the Debian website under   ]
> [   http://www-staging.debian.org/CD/faq/index#write-usb   ]
> [   instead of adding it to the installer manual ? ]
> [   debian-www in CC.  ]

I think it would be best to add it to both places so that users are
more likely to find it.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


-- 
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/CAKTje6H1GumMM8fzh5jBOz0DPn4ZinKrictLCSWyvn1eiq=w...@mail.gmail.com

Bug#770231: Amd64-efi installer becomes unresponsive on x86 bios

2014-11-24 Thread Samuel Comeau

Hello Ian,

Well, it appears I have made a mistake about the type of processor that's
in here : Intel(R) Pentium(R) 4 CPU 2.80GHz. I don't have the text of the
menu screen for you yet, I would have to retry installing linux, which I
haven't had the time to do yet. I can at least tell you, however, that the
menu I got to was very similar to this one
http://debian-handbook.info/browse/stable/images/inst-boot.png , apart from
the fact that my installer boot menu didn't have 64 bit anywhere in it.

The hang occurs when I try to select any option.

On Sat, Nov 22, 2014 at 5:31 AM, Ian Campbell  wrote:

> On Fri, 2014-11-21 at 15:40 -0500, Samuel Comeau wrote:
> > On November 21, 2014 03:30:13 PM Steve McIntyre wrote:
> > > [ Re-adding the CC to the bug report ]
> > >
> > > On Thu, Nov 20, 2014 at 10:49:42PM -0500, Samuel Comeau wrote:
> > > >Hello Steve,
> > > >
> > > >The intent of the report was that the installer fails "silently",
> instead
> > > >of crashing with human readable output. I seem to recall seeing an
> > > >installer fail with references to incompatible architecture, but that
> may
> > > >be faulty memory.
> > > Right, OK. I'm not sure about that myself... :-) That answers my
> > > question, too. How about we re-assign this to the kernel package and
> > > ask about such a message?
> >
> > I thought that since there's the installer running, we could put an
> > architecture check right there, so when you reach the menu, the installer
> > would already be aware what it's running on. So when the amd64 kernel
> tries to
> > start, it would correctly assume it's trying to run on compatible
> hardware,
> > unless the installer prevents it. I'm not sure how that would tie in
> with the
> > other installation methods, however, so it may be best to do as you say
> and
> > let kernel deal with that.
> >
> > > >I understand from your comment that this behaviour is known, but my
> > > >pre-bug- report-search didn't turn up any relevant results about
> "amd64 +
> > > >installer + (hangs OR stalls OR unresponsive) + x86". The results I
> get
> > > >are all about boot time, not installation time, unless I misunderstood
> > > >something very fundamental. In my understanding, when I reach the
> > > >installer menu, the boot procedure is complete.
> > >
> > > Correct - at that point you're in Linux with d-i running.
> >
> > That implies that there is some form of kernel running? Obviously not an
> amd64
> > kernel, if it shows up fine even on x86. Therefore, I assume the arch
> specific
> > kernel gets booted once the user selects an operation to perform.
>
> What is the text of the last menu which you get to before the hang? Is
> there anything written on the screen at the point of the hang? If it is
> too much text to transcribe then a digital photo of the screen would be
> ok too.
>
> Which model of Xeon are you running on? If you don't know then by
> pressing cancel/back at the d-i menu you can get to a menu with an
> option to drop to a shell and from there run "cat /proc/cpuinfo". I'm
> most interested in the "model name" field. If you aren't getting to a
> d-i menu at all then there is probably an indication of the processor
> model in the BIOS screens somewhere.
>
> If you are booting to a proper Debian installer menu (i.e. past the
> initial bootloader menu) then with an amd64 netinst you must be running
> something which is at least somewhat amd64 capable and not an i?86 only
> thing, there is nothing other than an amd64 kernel on such an image
> AFAIK.
>
> Which suggests to me that the hang is happening elsewhere later on,
> perhaps when loading the driver modules, but is not related directly to
> the processor architecture.
>
> Ian.
>
>
>

Bug#769996: debian-installer: Possible help text for win32diskimager users

2014-11-24 Thread Holger Wansing

[   Maybe this could better be added to the Debian website under   ]
[   http://www-staging.debian.org/CD/faq/index#write-usb   ]
[   instead of adding it to the installer manual ? ]
[   debian-www in CC.  ]



Hi,

Geert Stappers  wrote:
> On Tue, Nov 18, 2014 at 06:04:20AM +0100, nodiscc wrote:
> > 
> > Hello, here is a short text that can be used in the documentation:
> > 
> >  * download win32diskimager from 
> > http://sourceforge.net/projects/win32diskimager/, unpack the archive and 
> > run Win32DiskImager.exe
> >  * in the "Image file" area, select the .iso debian installer iage you 
> > downloaded from debian.org
> >  * in the "Device" area, select the drive letter for the USB drive you want 
> > to use as an installation media
> >* you may have to format the USB drive first to affect a drive letter to 
> > it
> >  * Click "Write". **All data present on the USB drive will be erased!**
> > 
> > Thanks!
>  
> 
> Proposal:
> 
> --- manual/en/install-methods/boot-usb-files.xml  (revision 69458)
> +++ manual/en/install-methods/boot-usb-files.xml  (working copy)
> @@ -178,4 +178,32 @@
>  
>
>  
> +  
> +  Creating USB-stick Debian-installer under Windows
> +
> +
> +Download win32diskimager from 
> http://sourceforge.net/projects/win32diskimager/,
> +unpack the archive and run Win32DiskImager.exe
> +
> +
> +
> +In the "Image file" area,
> +select the .iso installer image you downloaded.
> +
> +
> +
> +In the "Device" area,
> +select the drive letter for the USB drive
> +you want to use as an installation media.
> +
> +
> +
> +You may have to format the USB drive first
> +to affect a drive letter to it.
> +Click "Write". **All data present on the USB drive will be erased!**
> +
> +
> +
> +  
> +
>   
> 
> 
> Attached the same patch.
> 
> Reason for not tagging with 'patch' is because I have build the manual.
> 
> 
> 
> Groeten
> Geert Stappers
> -- 
> Leven en laten leven


-- 

Created with Sylpheed 3.2.0 under the new
D E B I A N   L I N U X   7 . 0   W H E E Z Y !

Registered Linux User #311290 - https://linuxcounter.net/



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20141124212606.24ceb04a0205029c0c052...@wansing-online.de

Bug#770812: Patch to add a sysvinit task to tasksel (untested)

Control: tag -1 +patch

Attached is a patch that adds a sysvinit task to tasksel.
It's fairly light (11 lines total in two files: control and task
description) but it means translations need to be updated.
Plus I haven't tested it, as I don't intend to use sysvinit myself anyway.

IMHO, it should be considered for Debian 8.1 (Next Jessie refresh) or
maybe even the first Jessie release, given the amount of user interest
on this functionality.
Main stopper is the freeze, as this should be tested (fortunately it
is really light) and translated.
Nevertheless, the freeze managers may consider a freeze exception for
this: we've all seen the amount of discussion on how to avoid
installing with systemd.
If this patch can make a non-systemd installation easy, it is worth
consideration, isn't it?

Regards,
Erich
From 4499a0a4ffe884e9da65f05b85ec0d5ee2ca8ef3 Mon Sep 17 00:00:00 2001
From: Erich Schubert 
Date: Mon, 24 Nov 2014 20:54:54 +0100
Subject: [PATCH] add sysvinit task

---
 debian/control | 6 ++
 tasks/sysvinit | 5 +
 2 files changed, 11 insertions(+)
 create mode 100644 tasks/sysvinit

diff --git a/debian/control b/debian/control
index bca654f..0794d21 100644
--- a/debian/control
+++ b/debian/control
@@ -2473,3 +2473,9 @@ Description: Cyrillic KDE desktop
 Depends: ${misc:Depends}, 
 Recommends:
 
+Package: task-sysvinit
+Architecture: all
+Description: SysV system init instead of systemd
+ This task installes sysvinit-core instead of systemd-sysv
+Depends: ${misc:Depends}, sysvinit-core
+Conflicts: systemd-sysv
diff --git a/tasks/sysvinit b/tasks/sysvinit
new file mode 100644
index 000..db9a268
--- /dev/null
+++ b/tasks/sysvinit
@@ -0,0 +1,5 @@
+Task: sysvinit
+Relevance: 5
+Section: server
+Key:
+  task-sysvinit
-- 
2.1.3

Processed: Patch to add a sysvinit task to tasksel (untested)

Processing control commands:

> tag -1 +patch
Bug #770812 [tasksel] tasksel: task-sysvinit to allow easy installation of 
non-systemd systems
Added tag(s) patch.

-- 
770812: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.b770812.141685939827014.transcr...@bugs.debian.org

Processed: Re: Bug#770854: drop elilo from jessie (and d-i)

Processing commands for cont...@bugs.debian.org:

> forcemerge 770854 768427
Bug #770854 [debian-installer] drop elilo from jessie (and d-i)
Bug #768427 [debian-installer] debian-installer: build-depends: elilo [ia64], 
with elilo gone away
Merged 768427 770854
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
768427: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768427
770854: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770854
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.c.141685437222365.transcr...@bugs.debian.org

Bug#770854: drop elilo from jessie (and d-i)

Holger Levsen  (2014-11-24):
> package: debian-installer
> x-debbugs-cc: debian-rele...@lists.debian.org
> 
> Hi,
> 
> according to #755509 "RM: elilo -- RoQA; Orphaned since a year, replaced by 
> better options" d-i only used elilo for ia64, which is not supported anymore, 
> so it seems elilo could also be removed from jessie?
> 
>  elilo |3.12-4 |  oldstable | source, amd64, i386, ia64
>  elilo |3.14-2 | stable | source, amd64, i386, ia64
>  elilo |3.14-3 |testing | source, amd64, i386
> 
> elilo is not in sid anymore.
> 
> According to #debian-release elilo is on the "keep these packages in testing 
> for d-i's purposes" list and needs to be removed there by the debian 
> installer 
> team, thus this bug.

#768427 was opened a tiny while ago.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#770854: drop elilo from jessie (and d-i)

2014-11-24 Thread Holger Levsen

package: debian-installer
x-debbugs-cc: debian-rele...@lists.debian.org

Hi,

according to #755509 "RM: elilo -- RoQA; Orphaned since a year, replaced by 
better options" d-i only used elilo for ia64, which is not supported anymore, 
so it seems elilo could also be removed from jessie?

 elilo |3.12-4 |  oldstable | source, amd64, i386, ia64
 elilo |3.14-2 | stable | source, amd64, i386, ia64
 elilo |3.14-3 |testing | source, amd64, i386

elilo is not in sid anymore.

According to #debian-release elilo is on the "keep these packages in testing 
for d-i's purposes" list and needs to be removed there by the debian installer 
team, thus this bug.


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.

Processed: forcemerge

Processing commands for cont...@bugs.debian.org:

> forcemerge 720538 721013
Bug #720538 [installation-reports] installation-reports ; elilo could not be 
installed
Bug #721013 [installation-reports] installation-reports : elilo is missing in 
/target/usr/sbin
Added indication that 721013 affects 696093,by
Merged 720538 721013
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
720538: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720538
721013: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721013
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.c.14168521928333.transcr...@bugs.debian.org

Bug#770812: tasksel: task-sysvinit to allow easy installation of non-systemd systems

reopen 770812
thanks

Hello,
Read the QUESTION.
Not only the word "systemd".

You are still not listening to my actual question, only raising your
sysvinit-shields.

I'm asking if a TASK can solve this maybe more nicely than the other
proposed approaches.

Bug #668001 does not mention this possibility as far as I can tell:
The word "task" is NEVER discussed there.
And the "late_command" solution is not userfriendly at all.

Therefore, this is a different wishlist item, against a different
package, too...
There is a reason why I filed this bug against *tasksel*, and not debootstrap!

I WILL accept a closing for this (non-RC, wishlist) bug IF you can
point out a thread e.g. on debian-boot where the option of a
task-sysvinit package to make the users happy is discussed.
The tech-ctte discussion you cited also does NOT discuss this option...
Because adding a task to the tasksel list IS something else than
adding a whole new bootstrap option...

The only mentioning of tasksel in the tech-ctte thread is this:
"1. The TC encourages a team (probably debian-boot) to provide a
package (similar to tasksel), let's call it initsel,"
Making a "similar" mechanism clearly is much more invasive than trying
to use the existing tasksel mechanism, isn't it?

But apparently you didn't read my question, only "systemd" and
"sysvinit install".
I begin to understand what the systemd opponents complain about...
You don't actually discuss the technical aspect (can a task package
solve this), but instead you try to silence me by 1.) closing the bug
without discussion, now 2) closing it with a totally different
argument and the "Tech-CTTE and GR have decided" hammer and "don't
bring up the bug count"?!?

We had a GR about making it *mandatory* to support sysvinit.
The GR does allow to use the traditional Debian way of developing
features and improving portability.
Reporting a specific wishlist bug for an *optional* functionality IS
THE PROPER PROCEDURE, isn't it?

Don't come with absurd "we're in freeze, so don't open wishlist bugs"
arguments...
That's not what a freeze is, and the wishlist bug does not
> - Debian is frozen, we're trying to get the RC count down
Seriously. A wishlist bug is not RC, is it?

Back to the topic, would you PLEASE bother to discuss the option of
adding a task to tasksel for sysvinit installation?
Is it possible (at all), and how much testing is needed, can get this
tested in time for jessie?

Regards,
Erich

--
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/CAGKbab_B26rak-2ufcuR5+EQLqT2159f=-n7+xb3b+ois5g...@mail.gmail.com

Processed: Re: Bug#770812: tasksel: task-sysvinit to allow easy installation of non-systemd systems

Processing commands for cont...@bugs.debian.org:

> reopen 770812
Bug #770812 {Done: Holger Levsen } [tasksel] tasksel: 
task-sysvinit to allow easy installation of non-systemd systems
Bug reopened
Ignoring request to alter fixed versions of bug #770812 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
770812: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.c.141685088531267.transcr...@bugs.debian.org

Bug#755686: installation-reports: another case of not detected firmware

2014-11-24 Thread Tarin Gamberini



- Messaggio originale -
> Da: Cyril Brulebois 
> [cut]
> That's the expected behaviour until the Beta 3 (maybe called RC1) release.
> 
> Mraw,
> KiBi.

> 

Ok.

Thanks,
Tarin


-- 
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/2008448759.375150.1416847902290.javamail.ya...@jws11153.mail.ir2.yahoo.com

Bug#770812: marked as done (tasksel: task-sysvinit to allow easy installation of non-systemd systems)

Your message dated Mon, 24 Nov 2014 17:31:04 +0100
with message-id <201411241731.06027.hol...@layer-acht.org>
and subject line Re: Bug#770812: tasksel: task-sysvinit to allow easy 
installation of non-systemd systems
has caused the Debian Bug report #770812,
regarding tasksel: task-sysvinit to allow easy installation of non-systemd 
systems
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
770812: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tasksel
Version: 3.29
Severity: wishlist

Hello,
It has been argued that late changes to the debian installer should be
avoided, and the maintainers have clearly expressed that they do not want
to add another debconf question:
https://lists.debian.org/debian-boot/2014/11/msg00408.html

My proposal is not to forcibly have users answer this question and decide
on an init system upon install. But there seems to be a larger userbase
that does want to keep sysvinit (in fact, I have switched all my systems
to systemd; but I do have an interest to have the noise eventually stop).

Can maybe the "tasks" system help here?
Can we have a task-sysvinit which depends on sysvinit-core, and which
conflicts systemd-sysv, and does installing such a task achieve the
desired results at installation time?

IMHO, adding a task package is a minimally invasive change to the install
process, and given the many requests for a sysvinit install option, this
may well be acceptable to the release managers. It's just not entirely
clear to me whether this works (i.e. when tasks are considered during
the installation phase, and whether this allows overriding the package
providing "init"), and the procedure necessary to get such a change
accepted into tasksel, the installation media, and jessie.

(And yes, I'm aware of the preseeding option to pass
  preseed/late_command="in-target apt-get install -y sysvinit-core"
to the installer. Essentially, I'm thinking of minimally invasive ways
to make this easier to access by end users - this is a pretty long
boot option to type, without the option of doing copy&paste when installing
a physical system...)

In the end, "Switch boot process to sysvinit" is a "task" that will end up
on the TODO list of many sysadmins (e.g. where because of some compatibility
or policy issue, they want to have all their servers on sysvinit)

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages tasksel depends on:
ii  apt 1.0.9.3
ii  debconf [debconf-2.0]   1.5.53
ii  liblocale-gettext-perl  1.05-8+b1
ii  perl-base   5.20.1-3
ii  tasksel-data3.29

tasksel recommends no packages.

tasksel suggests no packages.

-- debconf information excluded
--- End Message ---
--- Begin Message ---
On Montag, 24. November 2014, Holger Levsen wrote:
> you might have a point

thought about it some more and come to the conclusion, "no, you actually don't 
have a point", thus closing.

justification:

- this is clearly a wishlist bug of the very-nice-to-have level:
-- "apt-get install -y sysvinit-core" is really easy, nobody really needs a 
task for this urgently. If you need sys5 and cannot deal with that, I don't 
think you are real.
-- so is preseeding this
- d-i is frozen even longer than Debian
- Debian is frozen, we're trying to get the RC count down
- we had a tech-ctte decission on the appropriate init system for jessie and 
you know the result
- we had a GR about... more than just that and you know the result. (and it 
said processes are going fine, and the d-i maintainer said "no", the release-
team says "we're frozen please stop this discussion and fix RC bugs" and 
everybody in Debian agreed that this GR was unneeded because things are going 
fine...)
- and closing and not keeping it open "til whenever" because of 
http://blog.liw.fi/posts/wishlist-bugs/
- if you really still think it's useful after the release and the dust has 
settled, you are much welcome to come back afther the jessie release, but 
please, be nice and have a patch ready.

And please don't override the maintainers decission again.


signature.asc
Description: This is a digitally signed message part.
--- End Message ---

Linux kernel ABI bump in experimental: from 3.17-1 to 3.17.0-trunk

2014-11-24 Thread Linux kernel watcher

Linux kernel ABI bump in experimental: from 3.17-1 to 3.17.0-trunk


Full summary: http://d-i.debian.org/kernel-summary.html#experimental


--
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/e1xswwi-00014n...@dillon.debian.org

Bug#755686: Errata corrige on network and graphic card detection

2014-11-24 Thread Tarin Gamberini

> Base System Installation Checklist:

> [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
> Initial boot:   [O]

> Detect network card:[E]
>
Detect network card: [O]

The network card is correctly detected.



>
> [cut]
>
> Even if GDM3 works fine my "AMD Radeon R9 290X Graphics Card" 

> isn't correctlydetect.
>
I was wrong.

My graphic card is correctly detected:

lspci -knn: 02:00.0 VGA compatible controller [0300]: Advanced Micro 
Devices,
Inc. [AMD/ATI] Hawaii XT [Radeon R9 290X] [1002:67b0]

So I'm sending this installation report because the website of the Debian-

Installer asks to do so, even if ther weren't any problems, except for the 
"*ERROR*Unknown table version 3, 1" messages.


-- 
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/961613178.372538.1416847089884.javamail.ya...@jws11120.mail.ir2.yahoo.com

Bug#755686: installation-reports: another case of not detected firmware

taringamberini  (2014-11-24):
> Package: installation-reports
> Followup-For: Bug #755686
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> 
>   The first installation.
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
>   Manually installed missing firmware as reported by kern.log.
> 
>* What was the outcome of this action?
> 
>   The firmware was succesfully loaded, even if some:
> 
>   *ERROR* Unknown table version 3, 1
> 
>   are still present.
> 
>* What outcome did you expect instead?
> 
>   The firmware loads without any *ERROR*.
> 
>In attachment there are:
> 
>   * 20141124_1234_kern.log first boot 2 firmware missing
>   * manually installed 1 firmware
>   * 20141124_1348_kern.log second boot 1 firmware missing
>   * manually installed 1 firmware
>   * 20141124_1428_kern.log third boot 0 firmware missing but "*ERROR*
> Unknown table version 3, 1" are still present
> 
> 
> 
> -- Package-specific info:
> 
> Boot method: CD installation
> Image version: http://cdimage.debian.org/cdimage/jessie_di_beta_2/amd64/iso-cd
> /debian-jessie-DI-b2-amd64-CD-1.iso

Hi,

That's the expected behaviour until the Beta 3 (maybe called RC1) release.

Mraw,
KiBi.


-- 
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/20141124163705.ga29...@mraw.org

Bug#770812: tasksel: task-sysvinit to allow easy installation of non-systemd systems

2014-11-24 Thread Holger Levsen

Hi Erich,

On Montag, 24. November 2014, Erich Schubert wrote:
> Please DISCUSS, don't just turn down.

again and again and again and again?

and then again and again and again and again?

and then, over and over again and again?

and then...

how long do you think is appropriate?

> You owe this to me, and others, that want to make our users happy.

I don't think anybody owns anybody anything. 

> This is a frequently requested feature, and you don't even want to
> discuss whether the suggested approach is possible...

Uhm. This very bug, which message
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668001#60
was pointed out _several times_ now in the short time since #60 has been 
written, has more interesting messages, eg #20, #28, #33

> Your behavior is nothing short of rude.
> Did you even read the mail?

uhm. did you even look in the bts for previous discussions?
accusing Cyril of not discussing is quite absurd looking at
http://blends.debian.net/liststats/authorstat_debian-boot.png

you might have a point and certainly want to help, but the way you are 
approaching this, is hardly helpful.

Holger, worried the next person will say "ciao, I owe you nothing..."

signature.asc
Description: This is a digitally signed message part.

Re: Old-timer installer, task-sysvinit?

2014-11-24 Thread Lennart Sorensen

On Mon, Nov 24, 2014 at 06:36:37AM +0100, Cyril Brulebois wrote:
> Pretty sure it's either dbus(-{daemon,launch}) or systemd-udev.

Yes I think you are right, I must have misread the line in ps somehow.

> Please stop posting random rants on debian-boot@.

Fair enough.

-- 
Len Sorensen


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141124150758.gy24...@csclub.uwaterloo.ca

Bug#770812: tasksel: task-sysvinit to allow easy installation of non-systemd systems

Please DISCUSS, don't just turn down.

You owe this to me, and others, that want to make our users happy.

This is a frequently requested feature, and you don't even want to
discuss whether the suggested approach is possible...

Your behavior is nothing short of rude.
Did you even read the mail?

On Mon, Nov 24, 2014 at 2:06 PM, Cyril Brulebois  wrote:
> Erich Schubert  (2014-11-24):
>> Package: tasksel
>> Version: 3.29
>> Severity: wishlist
>>
>> Hello,
>> It has been argued that late changes to the debian installer should be
>> avoided, and the maintainers have clearly expressed that they do not want
>> to add another debconf question:
>> https://lists.debian.org/debian-boot/2014/11/msg00408.html
>>
>> My proposal is not to forcibly have users answer this question and decide
>> on an init system upon install. But there seems to be a larger userbase
>> that does want to keep sysvinit (in fact, I have switched all my systems
>> to systemd; but I do have an interest to have the noise eventually stop).
>>
>> Can maybe the "tasks" system help here?
>> Can we have a task-sysvinit which depends on sysvinit-core, and which
>> conflicts systemd-sysv, and does installing such a task achieve the
>> desired results at installation time?
>>
>> IMHO, adding a task package is a minimally invasive change to the install
>> process, and given the many requests for a sysvinit install option, this
>> may well be acceptable to the release managers. It's just not entirely
>> clear to me whether this works (i.e. when tasks are considered during
>> the installation phase, and whether this allows overriding the package
>> providing "init"), and the procedure necessary to get such a change
>> accepted into tasksel, the installation media, and jessie.
>>
>> (And yes, I'm aware of the preseeding option to pass
>>   preseed/late_command="in-target apt-get install -y sysvinit-core"
>> to the installer. Essentially, I'm thinking of minimally invasive ways
>> to make this easier to access by end users - this is a pretty long
>> boot option to type, without the option of doing copy&paste when installing
>> a physical system...)
>>
>> In the end, "Switch boot process to sysvinit" is a "task" that will end up
>> on the TODO list of many sysadmins (e.g. where because of some compatibility
>> or policy issue, they want to have all their servers on sysvinit)
>
> Again, no.
>
> Mraw,
> KiBi.


-- 
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/CAGKbab-vK8J2Mf1bGLgm18FsZTqYNOnQH93POX6YhyuH=kt...@mail.gmail.com

Processed: Re: Bug#770078: ifupdown: interfaces(5) falsely claims that interfaces.d is included by default on new installs

Processing control commands:

> reassign -1 debian-installer
Bug #770078 [ifupdown] ifupdown: interfaces(5) falsely claims that interfaces.d 
is included by default on new installs
Bug reassigned from package 'ifupdown' to 'debian-installer'.
No longer marked as found in versions ifupdown/0.7.49.
Ignoring request to alter fixed versions of bug #770078 to the same values 
previously set

-- 
770078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770078
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.b770078.14168362449818.transcr...@bugs.debian.org

Bug#770812: marked as done (tasksel: task-sysvinit to allow easy installation of non-systemd systems)

Your message dated Mon, 24 Nov 2014 14:06:05 +0100
with message-id <20141124130605.gc19...@mraw.org>
and subject line Re: Bug#770812: tasksel: task-sysvinit to allow easy 
installation of non-systemd systems
has caused the Debian Bug report #770812,
regarding tasksel: task-sysvinit to allow easy installation of non-systemd 
systems
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
770812: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tasksel
Version: 3.29
Severity: wishlist

Hello,
It has been argued that late changes to the debian installer should be
avoided, and the maintainers have clearly expressed that they do not want
to add another debconf question:
https://lists.debian.org/debian-boot/2014/11/msg00408.html

My proposal is not to forcibly have users answer this question and decide
on an init system upon install. But there seems to be a larger userbase
that does want to keep sysvinit (in fact, I have switched all my systems
to systemd; but I do have an interest to have the noise eventually stop).

Can maybe the "tasks" system help here?
Can we have a task-sysvinit which depends on sysvinit-core, and which
conflicts systemd-sysv, and does installing such a task achieve the
desired results at installation time?

IMHO, adding a task package is a minimally invasive change to the install
process, and given the many requests for a sysvinit install option, this
may well be acceptable to the release managers. It's just not entirely
clear to me whether this works (i.e. when tasks are considered during
the installation phase, and whether this allows overriding the package
providing "init"), and the procedure necessary to get such a change
accepted into tasksel, the installation media, and jessie.

(And yes, I'm aware of the preseeding option to pass
  preseed/late_command="in-target apt-get install -y sysvinit-core"
to the installer. Essentially, I'm thinking of minimally invasive ways
to make this easier to access by end users - this is a pretty long
boot option to type, without the option of doing copy&paste when installing
a physical system...)

In the end, "Switch boot process to sysvinit" is a "task" that will end up
on the TODO list of many sysadmins (e.g. where because of some compatibility
or policy issue, they want to have all their servers on sysvinit)

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages tasksel depends on:
ii  apt 1.0.9.3
ii  debconf [debconf-2.0]   1.5.53
ii  liblocale-gettext-perl  1.05-8+b1
ii  perl-base   5.20.1-3
ii  tasksel-data3.29

tasksel recommends no packages.

tasksel suggests no packages.

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Erich Schubert  (2014-11-24):
> Package: tasksel
> Version: 3.29
> Severity: wishlist
> 
> Hello,
> It has been argued that late changes to the debian installer should be
> avoided, and the maintainers have clearly expressed that they do not want
> to add another debconf question:
> https://lists.debian.org/debian-boot/2014/11/msg00408.html
> 
> My proposal is not to forcibly have users answer this question and decide
> on an init system upon install. But there seems to be a larger userbase
> that does want to keep sysvinit (in fact, I have switched all my systems
> to systemd; but I do have an interest to have the noise eventually stop).
> 
> Can maybe the "tasks" system help here?
> Can we have a task-sysvinit which depends on sysvinit-core, and which
> conflicts systemd-sysv, and does installing such a task achieve the
> desired results at installation time?
> 
> IMHO, adding a task package is a minimally invasive change to the install
> process, and given the many requests for a sysvinit install option, this
> may well be acceptable to the release managers. It's just not entirely
> clear to me whether this works (i.e. when tasks are considered during
> the installation phase, and whether this allows overriding the package
> providing "init"), and the procedure necessary to get such a change
> accepted into tasksel, the installation media, and jessie.
> 
> (And yes, I'm aware of the preseeding option to pass
>   preseed/late_command="in-target apt-get install -y sysvinit-core"
> to the inst

Processed: Reopen because: closed without discussion / explanation.

Processing commands for cont...@bugs.debian.org:

> reopen 770812
Bug #770812 {Done: Cyril Brulebois } [tasksel] tasksel: 
task-sysvinit to allow easy installation of non-systemd systems
Bug reopened
Ignoring request to alter fixed versions of bug #770812 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
770812: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.c.141683510332214.transcr...@bugs.debian.org

Bug#770829: installation-report: Font too small on UltraHD screen

2014-11-24 Thread Eugen Dedu


Package: installation-reports
Version: 2.57
Severity: normal

Dear Maintainer,

I am installing debian on a laptop with 3840x2160 resolution.

The first screen, allowing to choose Install, Graphical install etc. is 
fine.


Afterwards, the following screens, in both text (newt) and graphical 
install, font is too small, almost unreadable on the screen.


I put a video at http://eugen.dedu.free.fr/2014-11-24-130034.webm.  It 
is not of so good quality, since I have not had a camera with me, and 
used the webcam, but allows to see the problem.


I attach three files about the system.

This is a somehow important problem, since nothing can be done to
workaround it.  The installer is also the first program a new user sees
when installing linux.


-- Package-specific info:

Boot method: USB
Image version: 
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd, 
21/11/2014

Date: 

Machine: Lenovo Y50


Xorg.0.log.gz
Description: GNU Zip compressed data


hardware-summary.gz
Description: GNU Zip compressed data


syslog.gz
Description: GNU Zip compressed data

Bug#770812: tasksel: task-sysvinit to allow easy installation of non-systemd systems

Package: tasksel
Version: 3.29
Severity: wishlist

Hello,
It has been argued that late changes to the debian installer should be
avoided, and the maintainers have clearly expressed that they do not want
to add another debconf question:
https://lists.debian.org/debian-boot/2014/11/msg00408.html

My proposal is not to forcibly have users answer this question and decide
on an init system upon install. But there seems to be a larger userbase
that does want to keep sysvinit (in fact, I have switched all my systems
to systemd; but I do have an interest to have the noise eventually stop).

Can maybe the "tasks" system help here?
Can we have a task-sysvinit which depends on sysvinit-core, and which
conflicts systemd-sysv, and does installing such a task achieve the
desired results at installation time?

IMHO, adding a task package is a minimally invasive change to the install
process, and given the many requests for a sysvinit install option, this
may well be acceptable to the release managers. It's just not entirely
clear to me whether this works (i.e. when tasks are considered during
the installation phase, and whether this allows overriding the package
providing "init"), and the procedure necessary to get such a change
accepted into tasksel, the installation media, and jessie.

(And yes, I'm aware of the preseeding option to pass
  preseed/late_command="in-target apt-get install -y sysvinit-core"
to the installer. Essentially, I'm thinking of minimally invasive ways
to make this easier to access by end users - this is a pretty long
boot option to type, without the option of doing copy&paste when installing
a physical system...)

In the end, "Switch boot process to sysvinit" is a "task" that will end up
on the TODO list of many sysadmins (e.g. where because of some compatibility
or policy issue, they want to have all their servers on sysvinit)

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages tasksel depends on:
ii  apt 1.0.9.3
ii  debconf [debconf-2.0]   1.5.53
ii  liblocale-gettext-perl  1.05-8+b1
ii  perl-base   5.20.1-3
ii  tasksel-data3.29

tasksel recommends no packages.

tasksel suggests no packages.

-- debconf information excluded


-- 
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/20141124104223.14454.30806.reportbug@localhost

partman-efi_56_i386.changes ACCEPTED into unstable



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 24 Nov 2014 09:02:59 +0100
Source: partman-efi
Binary: partman-efi
Architecture: source i386
Version: 56
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Christian Perrier 
Description:
 partman-efi - Add to partman support for EFI System Partitions (udeb)
Closes: 770033
Changes:
 partman-efi (56) unstable; urgency=medium
 .
   [ Steve McIntyre ]
   * Force umask for /boot/efi in mount options. Closes: #770033. Thanks to
 Marc Deslauriers for the patch.
 .
   [ Updated translations ]
   * German (de.po) by Holger Wansing
   * Italian (it.po) by Milo Casagrande
   * Polish (pl.po) by Michał Kułach
   * Thai (th.po) by Theppitak Karoonboonyanan
Checksums-Sha1:
 e20ca79dbb82cc2b06035ca93549f9a63271e309 1685 partman-efi_56.dsc
 11f994b1269583af04229d262fc4dc90ee07c791 60136 partman-efi_56.tar.xz
 e813eb5825d8ad4c249f96332d3419ce592858cd 36324 partman-efi_56_i386.udeb
Checksums-Sha256:
 68a5092d1ec2ac2b8e859e57f4838f009a5054a3f5fb44b823908834831e62c8 1685 
partman-efi_56.dsc
 a688a52afdf4248e72b539fe0d3c26ab02668365e33c237c90badaab0c90bc02 60136 
partman-efi_56.tar.xz
 35bb7b57ce01eee3ce937300a323f1dd5cc842d0f5a6acd507e6ec2f26ae1adf 36324 
partman-efi_56_i386.udeb
Files:
 29bd4f97bf09e47ea650be27466610d2 1685 debian-installer standard 
partman-efi_56.dsc
 847bb08565f5467a1c67eee23387580e 60136 debian-installer standard 
partman-efi_56.tar.xz
 b0b07c13a0820c2787e72d4253ebc68e 36324 debian-installer standard 
partman-efi_56_i386.udeb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJUcuaKAAoJEIcvcCxNbiWoVRgQAIcjsoXTDjjeFsbEmmP5x841
EV6JaSjqgI1bkfJxNFxbyn5S5EAVQWgS+SZC11MhqZJ25IdUbMVXNqqGmmutDcN/
I4GcXWKxTnOO+NKWpwEWNJw38/nIbSeeSLgPoKkRXk0r3KnqchOJtIJV+Uz8OhVe
LmxRppLvoc65YDbBUvDyCP3nC1mqs0KIQUus+vP3s420XGyXo3pGNjYV2/YwnLK2
J8JbHKgZApSLCqBui3Lklb3EEUnygA+lXQLwwPxPYzDrl7OlKe82JcuWqt7QwZXv
XmcHrMlfz3JXoxvt7ItXgAg7ZYydOoX6e8xu3rwf1dh1k3sJU/7VPGk86SsGtwB8
9usC/fQ3ZGCHViPkYUrJhtaAxN5fUSB+Fs7SLPZu13dhYST1tW6Lzqv3nCdqCrVZ
wDTnOqUQyX1MzpuFcmCbe13Ou1T7GSRIW0q7lq0lln2HWJbrvkiMA46GlmzhaaJz
EozXbTqEwIDzJHMT6kannA+Fh3hJITQYbjf8LUAuetGIPG+55DtGjomG0c0kZpdv
/zeyqDCWeCd/qd+JLYh5t+4M46QajLL6NAeZb6vHwiZsGw8rPeCKT7e43kKaptET
hgap4GX44AvbKxz+hZNPFepmEoQGvVvOvc989h8OsFp+4HdkRVEcbuxbzS+a0hY0
bKXbvLhTK5I/8C4UczPH
=EhiE
-END PGP SIGNATURE-


Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/e1xspoo-0004gu...@franck.debian.org

debootstrap_1.0.66_i386.changes ACCEPTED into unstable



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 24 Nov 2014 09:15:50 +0100
Source: debootstrap
Binary: debootstrap debootstrap-udeb
Architecture: source all
Version: 1.0.66
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team 
Changed-By: Christian Perrier 
Description:
 debootstrap - Bootstrap a basic Debian system
 debootstrap-udeb - Bootstrap the Debian system (udeb)
Closes: 770214
Changes:
 debootstrap (1.0.66) unstable; urgency=low
 .
   [ Cyril Brulebois ]
   * Specify gzip compression in debian/source/options to allow for better
 portability on other platforms (Closes: #770214). Thanks, Joey Hess!
   * Specify gzip compression for debootstrap, and xz for debootstrap-udeb,
 to mitigate the need for xz on non-Debian platforms (see: #770217).
Checksums-Sha1:
 8c0faf8e8fc1c849005458dd8362457d8390f1ca 1792 debootstrap_1.0.66.dsc
 fbfc56b7a455e6da43d217ea8cbdb18021b6647c 61338 debootstrap_1.0.66.tar.gz
 f023cc57133aae3f190511e763000d6681e18625 62612 debootstrap_1.0.66_all.deb
 3e7e9d56215807aee788d144085a3611075fae52 18272 debootstrap-udeb_1.0.66_all.udeb
Checksums-Sha256:
 aeaebb850dd2d31f644239430b6008a9152b950c1226bdd91686d05827eab8ef 1792 
debootstrap_1.0.66.dsc
 33246d6926aee18eef841169d0c9c45f8a7747e95ffcf7d08a0eb833f735f095 61338 
debootstrap_1.0.66.tar.gz
 d3bab5314adc6337e1ebfbcedf5d3e324e3f90aa3e09f10a1abcd9779e4d5bbc 62612 
debootstrap_1.0.66_all.deb
 7832da2417e9964a964777e6679697c05bfb389f7e4f8f1f726dbbdcc27ec2ee 18272 
debootstrap-udeb_1.0.66_all.udeb
Files:
 49fac75a8bc619346ec1829175fdc9f8 1792 admin extra debootstrap_1.0.66.dsc
 1caeb6221810566b423de17650414cc2 61338 admin extra debootstrap_1.0.66.tar.gz
 fd92b892554cce0a0757000e6d701769 62612 admin extra debootstrap_1.0.66_all.deb
 bf6370ea0aa80308dfb03a4a35e33ad1 18272 debian-installer extra 
debootstrap-udeb_1.0.66_all.udeb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJUcuoXAAoJEIcvcCxNbiWolAMQAKI9Ogk0+dV6u5cDhM3WMLvv
qZmxl8yw/XHG5NksG6UOyXIDQwERxatY6R1jRXPogy8Whw5RB3xrldbxKPGoWO9e
OKe8hzDb5p4SHXLfBGPR8cdrZUZ8Y927xObVMqDLj83TnE8IiWGuhWFA4+HVIgpo
jmuLtzq7FEKYlVUeXvMCGECFBzBjLN99sjbsAEb82vLiThY/3tmxFZwyZt85J26A
xnEHoGiVuoeoyp7icUVu+ypJprFS4083KzeKzZnzPP+kNXHojGs6M01B/pkE4U0+
06uPF502xFdFVHImvJ/2BXYtNPD/Jk3JJgrxsMMsy2zzOQOQK5IuCSQdEzpRfzSp
cEgrn/0Gi5tngSBvwMecxpeie6QX3Z2ZytA2P+MJ2MUpXgfT/Jyu4SWawqz2Jdpa
AResz5B397OlrDCPtVbfKYQNmcg0GafatMbMgGUjUnFv5EnL6GpY7grUUxelIeq9
NpyBtCabCdOmtoyvjjCr9wcPPx3NJCbBxJ6KV7zgotVFi+Xf2qqjuR7PX60Jl1Aw
83t8IL866iwL7mjQk7ozHO4cvNIMAAMlqVdUyQUaJi3g36gWqs+SpMpuHwxOYFUH
O7wAdmLleyj9YfWnI5j/f7mMmdAuEbijgK8odBHIyM0FlO3nCUQqbGLETepZxEmW
m6KGCyuwgitZNy82BcC4
=4Juy
-END PGP SIGNATURE-


Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/e1xspnh-0003mn...@franck.debian.org

Bug#770214: marked as done (source tarball should not be compressed with xz)

Your message dated Mon, 24 Nov 2014 09:19:17 +
with message-id 
and subject line Bug#770214: fixed in debootstrap 1.0.66
has caused the Debian Bug report #770214,
regarding source tarball should not be compressed with xz
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
770214: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770214
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap
Version: 1.0.64
Severity: normal

xz is not a common format, and this makes it unncessarily difficult to
install debootstrap from source on unfamiliar linux systems. The space
savings are miniscule. Please switch to a tar.gz.

-- 
see shy jo


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.66

We believe that the bug you reported is fixed in the latest version of
debootstrap, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 770...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian Perrier  (supplier of updated debootstrap package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 24 Nov 2014 09:15:50 +0100
Source: debootstrap
Binary: debootstrap debootstrap-udeb
Architecture: source all
Version: 1.0.66
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team 
Changed-By: Christian Perrier 
Description:
 debootstrap - Bootstrap a basic Debian system
 debootstrap-udeb - Bootstrap the Debian system (udeb)
Closes: 770214
Changes:
 debootstrap (1.0.66) unstable; urgency=low
 .
   [ Cyril Brulebois ]
   * Specify gzip compression in debian/source/options to allow for better
 portability on other platforms (Closes: #770214). Thanks, Joey Hess!
   * Specify gzip compression for debootstrap, and xz for debootstrap-udeb,
 to mitigate the need for xz on non-Debian platforms (see: #770217).
Checksums-Sha1:
 8c0faf8e8fc1c849005458dd8362457d8390f1ca 1792 debootstrap_1.0.66.dsc
 fbfc56b7a455e6da43d217ea8cbdb18021b6647c 61338 debootstrap_1.0.66.tar.gz
 f023cc57133aae3f190511e763000d6681e18625 62612 debootstrap_1.0.66_all.deb
 3e7e9d56215807aee788d144085a3611075fae52 18272 debootstrap-udeb_1.0.66_all.udeb
Checksums-Sha256:
 aeaebb850dd2d31f644239430b6008a9152b950c1226bdd91686d05827eab8ef 1792 
debootstrap_1.0.66.dsc
 33246d6926aee18eef841169d0c9c45f8a7747e95ffcf7d08a0eb833f735f095 61338 
debootstrap_1.0.66.tar.gz
 d3bab5314adc6337e1ebfbcedf5d3e324e3f90aa3e09f10a1abcd9779e4d5bbc 62612 
debootstrap_1.0.66_all.deb
 7832da2417e9964a964777e6679697c05bfb389f7e4f8f1f726dbbdcc27ec2ee 18272 
debootstrap-udeb_1.0.66_all.udeb
Files:
 49fac75a8bc619346ec1829175fdc9f8 1792 admin extra debootstrap_1.0.66.dsc
 1caeb6221810566b423de17650414cc2 61338 admin extra debootstrap_1.0.66.tar.gz
 fd92b892554cce0a0757000e6d701769 62612 admin extra debootstrap_1.0.66_all.deb
 bf6370ea0aa80308dfb03a4a35e33ad1 18272 debian-installer extra 
debootstrap-udeb_1.0.66_all.udeb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJUcuoXAAoJEIcvcCxNbiWolAMQAKI9Ogk0+dV6u5cDhM3WMLvv
qZmxl8yw/XHG5NksG6UOyXIDQwERxatY6R1jRXPogy8Whw5RB3xrldbxKPGoWO9e
OKe8hzDb5p4SHXLfBGPR8cdrZUZ8Y927xObVMqDLj83TnE8IiWGuhWFA4+HVIgpo
jmuLtzq7FEKYlVUeXvMCGECFBzBjLN99sjbsAEb82vLiThY/3tmxFZwyZt85J26A
xnEHoGiVuoeoyp7icUVu+ypJprFS4083KzeKzZnzPP+kNXHojGs6M01B/pkE4U0+
06uPF502xFdFVHImvJ/2BXYtNPD/Jk3JJgrxsMMsy2zzOQOQK5IuCSQdEzpRfzSp
cEgrn/0Gi5tngSBvwMecxpeie6QX3Z2ZytA2P+MJ2MUpXgfT/Jyu4SWawqz2Jdpa
AResz5B397OlrDCPtVbfKYQNmcg0GafatMbMgGUjUnFv5EnL6GpY7grUUxelIeq9
NpyBtCabCdOmtoyvjjCr9wcPPx3NJCbBxJ6KV7zgotVFi+Xf2qqjuR7PX60Jl1Aw
83t8IL866iwL7mjQk7ozHO4cvNIMAAMlqVdUyQUaJi3g36gWqs+SpMpuHwxOYFUH
O7wAdmLleyj9YfWnI5j/f7mMmdAuEbijgK8odBHIyM0FlO3nCUQqbGLETepZxEmW
m6KGCyuwgitZNy82BcC4
=4Juy
-END PGP SIGNATURE End Message ---

Bug#770033: marked as done (partman-efi: Should force umask in mount options)

Your message dated Mon, 24 Nov 2014 09:20:00 +
with message-id 
and subject line Bug#770033: fixed in partman-efi 56
has caused the Debian Bug report #770033,
regarding partman-efi: Should force umask in mount options
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
770033: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770033
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: partman-efi
Version: 25
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu vivid ubuntu-patch



*** /tmp/tmpryAK4b/bug_body

In Ubuntu, the attached patch was applied to achieve the following:


  * fstab.d/efi: force umask in mount options to ensure directory never
ends up with incorrect permissions. (LP: #1390183)


Thanks for considering the patch.


-- System Information:
Debian Release: jessie/sid
  APT prefers utopic-updates
  APT policy: (500, 'utopic-updates'), (500, 'utopic-security'), (500, 
'utopic-proposed'), (500, 'utopic'), (100, 'utopic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-25-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru partman-efi-25ubuntu6/debian/changelog partman-efi-25ubuntu7/debian/changelog
diff -Nru partman-efi-25ubuntu6/fstab.d/efi partman-efi-25ubuntu7/fstab.d/efi
--- partman-efi-25ubuntu6/fstab.d/efi	2010-09-03 08:40:28.0 -0400
+++ partman-efi-25ubuntu7/fstab.d/efi	2014-11-18 08:38:31.0 -0500
@@ -23,7 +23,7 @@
 		[ -f "$id/method" ] || continue
 		method=$(cat $id/method)
 		[ "$method" = efi ] || continue
-		echo "$path" /boot/efi vfat defaults 0 1
+		echo "$path" /boot/efi vfat umask=0077 0 1
 		seen_efi=1
 	done
 	close_dialog
--- End Message ---
--- Begin Message ---
Source: partman-efi
Source-Version: 56

We believe that the bug you reported is fixed in the latest version of
partman-efi, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 770...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian Perrier  (supplier of updated partman-efi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 24 Nov 2014 09:02:59 +0100
Source: partman-efi
Binary: partman-efi
Architecture: source i386
Version: 56
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Christian Perrier 
Description:
 partman-efi - Add to partman support for EFI System Partitions (udeb)
Closes: 770033
Changes:
 partman-efi (56) unstable; urgency=medium
 .
   [ Steve McIntyre ]
   * Force umask for /boot/efi in mount options. Closes: #770033. Thanks to
 Marc Deslauriers for the patch.
 .
   [ Updated translations ]
   * German (de.po) by Holger Wansing
   * Italian (it.po) by Milo Casagrande
   * Polish (pl.po) by Michał Kułach
   * Thai (th.po) by Theppitak Karoonboonyanan
Checksums-Sha1:
 e20ca79dbb82cc2b06035ca93549f9a63271e309 1685 partman-efi_56.dsc
 11f994b1269583af04229d262fc4dc90ee07c791 60136 partman-efi_56.tar.xz
 e813eb5825d8ad4c249f96332d3419ce592858cd 36324 partman-efi_56_i386.udeb
Checksums-Sha256:
 68a5092d1ec2ac2b8e859e57f4838f009a5054a3f5fb44b823908834831e62c8 1685 
partman-efi_56.dsc
 a688a52afdf4248e72b539fe0d3c26ab02668365e33c237c90badaab0c90bc02 60136 
partman-efi_56.tar.xz
 35bb7b57ce01eee3ce937300a323f1dd5cc842d0f5a6acd507e6ec2f26ae1adf 36324 
partman-efi_56_i386.udeb
Files:
 29bd4f97bf09e47ea650be27466610d2 1685 debian-installer standard 
partman-efi_56.dsc
 847bb08565f5467a1c67eee23387580e 60136 debian-installer standard 
partman-efi_56.tar.xz
 b0b07c13a0820c2787e72d4253ebc68e 36324 debian-installer standard 
partman-efi_56_i386.udeb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJUcuaKAAoJEIcvcCxNbiWoVRgQAIcjsoXTDjjeFsbEmmP5x841
EV6JaSjqgI1bkfJxNFxbyn5S5EAVQWgS+SZC11MhqZJ25IdUbMVXNqqGmmutDcN/
I4GcXWKxTnOO+NKWpwEWNJw38/nIbSeeSLgPoKkRXk0r3KnqchOJtIJV+Uz8OhVe
LmxRppLvoc65YDbBUvDyCP3nC1mqs0KIQUus+vP3s420XGyXo3pGNjYV2/YwnLK2
J8JbHKgZApSLCqBui3Lklb3EEUnygA+lXQLwwPxPYzDrl7OlKe82JcuWqt7QwZXv
XmcHrMlfz3JXoxvt7ItXgAg7ZYydOoX6e8xu

Re: Processing of debootstrap_1.0.66_i386.changes

Christian PERRIER  (2014-11-24):
> Well, sorry for this Cyril. My interpretation is that this *was*
> making sense for Jessie, indeed. The bug is in Jessie and I think that
> having an "easier-to-use" debootstrap in Jessie is good for the future
> and worth a freeze exception. Such bugs easily fall in the category of
> "those bugs we only really care when the release is close", and so
> low invasive that arguing for a freeze exception is kinda easy.
> 
> I should have talked about that first in -boot before shooting,
> though. Sorry for the trouble.

[ I think I sent my mail too fast anyway, I meant to add: ]

This is my fault, I meant to send a mail about master vs. jessie/stretch
branches, specifically after this push to master, but got swamped with
work in the meanwhile and only thought about it again when I saw the
"Processing" mails.

Not much harm done anyway, probably a nice-yet-not-ideal-reminder that I
should communicate more. I'll try and get that fixed this week.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Re: Processing of debootstrap_1.0.66_i386.changes

2014-11-24 Thread Christian PERRIER

Quoting Cyril Brulebois (k...@debian.org):
> Debian FTP Masters  (2014-11-24):
> > debootstrap_1.0.66_i386.changes uploaded successfully to localhost
> > along with the files:
> >   debootstrap_1.0.66.dsc
> >   debootstrap_1.0.66.tar.gz
> >   debootstrap_1.0.66_all.deb
> >   debootstrap-udeb_1.0.66_all.udeb
> 
> While it might have been a good idea on my side not to push those
> patches to master, but to a different branch instead, it would be
> nice not to upload stuff that doesn't make sense for jessie. That
> means more noise when reviewing. :(


Well, sorry for this Cyril. My interpretation is that this *was*
making sense for Jessie, indeed. The bug is in Jessie and I think that
having an "easier-to-use" debootstrap in Jessie is good for the future
and worth a freeze exception. Such bugs easily fall in the category of
"those bugs we only really care when the release is close", and so
low invasive that arguing for a freeze exception is kinda easy.

I should have talked about that first in -boot before shooting,
though. Sorry for the trouble.




-- 




signature.asc
Description: Digital signature

Re: Processing of debootstrap_1.0.66_i386.changes

Debian FTP Masters  (2014-11-24):
> debootstrap_1.0.66_i386.changes uploaded successfully to localhost
> along with the files:
>   debootstrap_1.0.66.dsc
>   debootstrap_1.0.66.tar.gz
>   debootstrap_1.0.66_all.deb
>   debootstrap-udeb_1.0.66_all.udeb

While it might have been a good idea on my side not to push those
patches to master, but to a different branch instead, it would be
nice not to upload stuff that doesn't make sense for jessie. That
means more noise when reviewing. :(

Please note other bug reports were still being handled…

Mraw,
KiBi.


signature.asc
Description: Digital signature

Processing of debootstrap_1.0.66_i386.changes

debootstrap_1.0.66_i386.changes uploaded successfully to localhost
along with the files:
  debootstrap_1.0.66.dsc
  debootstrap_1.0.66.tar.gz
  debootstrap_1.0.66_all.deb
  debootstrap-udeb_1.0.66_all.udeb

Greetings,

Your Debian queue daemon (running on host franck.debian.org)


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/e1xsoss-00047x...@franck.debian.org

Processing of debootstrap_1.0.66_i386.changes

debootstrap_1.0.66_i386.changes uploaded successfully to ftp-master.debian.org
along with the files:
  debootstrap_1.0.66.dsc
  debootstrap_1.0.66.tar.gz
  debootstrap_1.0.66_all.deb
  debootstrap-udeb_1.0.66_all.udeb

Greetings,

Your Debian queue daemon (running on host coccia.debian.org)


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/e1xsoss-0003zm...@coccia.debian.org

Processing of partman-efi_56_i386.changes

partman-efi_56_i386.changes uploaded successfully to localhost
along with the files:
  partman-efi_56.dsc
  partman-efi_56.tar.xz
  partman-efi_56_i386.udeb

Greetings,

Your Debian queue daemon (running on host franck.debian.org)


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/e1xsoem-0002do...@franck.debian.org

Processing of partman-efi_56_i386.changes