Bug#511153: tzsetup-udeb: time zone list in tzsetup out of date wrt glibc/tzdata time

2014-03-02 Thread Christian PERRIER
Quoting Cyril Brulebois (k...@debian.org):

  Actually, there might me other cases like this one as I haven't seen
  anyone actively trying to cope with changes in tzdata to align tzsetup
  with them (such as the recent nightmare in Argentinian timezones).
 
 what should we do about this bug report?

IIRC, there have been a few moments in various releases, where the
list of possible timezones for multi-TZ countries have been
updated. So, in short, it can be closed, IMHO.



signature.asc
Description: Digital signature


Bug#673644: Message at end of successful install talks about floppies (should be updated)

2014-03-02 Thread Christian PERRIER
Quoting Cyril Brulebois (k...@debian.org):

  _Description: Installation complete
   Installation is complete, so it is time to boot into your new system.
 - Make sure to remove the installation media (CD-ROM, floppies), so that
 - you boot into the new system rather than restarting the installation.
 + Make sure to remove the installation media (CD-ROM, DVD-ROM, USB flash
 + disk), so that you boot into the new system rather than restarting the
 + installation.

Maybe try to be more generic so that we don't have to change this
when CD-ROM, DVD or USB flash disk are considered obsolete as well?

Something like Make to to remove the installation media so that




signature.asc
Description: Digital signature


Bug#663504:

2014-03-02 Thread Chris Bainbridge
I recently installed Debian 7.0.4 and noted multiple problems: with
the check-missing-firmware phase

1. check-missing-firmware missing files list is incorrect. Installer
detects that wifi needs Broadcom firmware and says The missing
firmware files are: b43/ucode29_mimo.fw b43-open/ucode29_mimo.fw. The
list is incorrect and incomplete. The list contains only two files -
there are many more that are required. The list contains two files,
suggesting that both are needed - in fact only one copy of the file is
needed (the loader looks in two directories).
   - This bug seems to be caused by the installer interpreting the
kernel firmware loading in an overly simple way. The firmware loader
attempts to load files sequentially, and looks for them in two places.
If it does not find a file, it will immediately quit and print the two
locations that it looked for the file. The Debian installer interprets
and reports this pair of locations as an absolute list of missing
files. It is not an absolute list, it is a duplicate pair for a single
missing file.
   - Even if the file is present (eg. b43/ucode29_mimo.fw exists),
this function still reports b43-open/ucode29_mimo.fw as missing! It's
not missing, it's just an alternative location for the same file.

2. The installer should copy any firmware files on the USB drive in
one go. Because of the way the installer copies and loads one file at
a time, even if the user has done everything perfectly (all required
firmwares ready on a USB drive) the check missing files prompt will
pop up several times (3 in my case) and the user just has to keep
clicking yes. Any normal user is going to think that this is broken,
only users who are really paying attention and watching the logs will
notice that it is only loading one file every time they click
Continue.

3. check-missing-firmware does not work with a USB drive that
contains a partition table. When a USB drive with a single partition
containing the firmware is inserted, it reports that the firmware was
not found. The firmware is on partition /dev/sdc1. From the log I can
see that the function is attempting to scan drives and partitions
detected on the system, and mount them as FAT file systems. The
problem is that it does not try the USB drive partition 1 at
/dev/sdc1. It does try /dev/{sda sda sdc sdc sda1 sda1 sda sda sdc sdc
sda1 sda1 sda2 sda2 sda3 sda3} in that order. So it is trying to mount
/dev/sdc (the USB drive) but not /dev/sdc1 (the actual partition).
   - Workaround is to format the USB drive without a partition table,
e.g. mkfs.vfat -I /dev/sdc (mkfs.vfat actually expects a partition
table, -I override forces it to use the entire device)


-- 
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/CAP-bSRZDWvz4a=z3rsgtcbw+onp5ysedvtx-d2qdhgypmt-...@mail.gmail.com



Bug#418590: main-menu: Segfault during automatic install on AMD64

2014-03-02 Thread Olaf van der Spek
On Sun, Mar 2, 2014 at 3:29 AM, Cyril Brulebois k...@debian.org wrote:
 Is that still reproducible with current wheezy installation images? If
 that's the case, we'll see how to help you debug that further.

Hi KiBi,

Let's just close this bug, it has been almost 7 years since it was
opened. If it happens again it'll be reported again.


-- 
Olaf


-- 
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/caa7u3hnr4knphsvoc2paq0hqz8x_aonp40hg4lylfnnbw7j...@mail.gmail.com



Bug#418590: marked as done (main-menu: Segfault during automatic install on AMD64)

2014-03-02 Thread Debian Bug Tracking System
Your message dated Sun, 2 Mar 2014 13:17:30 +0100
with message-id 20140302121730.ga2...@mraw.org
and subject line Re: Bug#418590: main-menu: Segfault during automatic install 
on AMD64
has caused the Debian Bug report #418590,
regarding main-menu: Segfault during automatic install on AMD64
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.)


-- 
418590: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418590
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: main-menu
Severity: important

Hi,

When installing Etch using debian-40r0-amd64-netinst.iso and auto 
url=xcc.demon.nl I encounter segfaults in a loop.

See also http://xcc.demon.nl/temp/segfault.png and 
http://xcc.demon.nl/d-i/etch/preseed.cfg

Olaf

---End Message---
---BeginMessage---
Olaf van der Spek olafvds...@gmail.com (2014-03-02):
 On Sun, Mar 2, 2014 at 3:29 AM, Cyril Brulebois k...@debian.org wrote:
  Is that still reproducible with current wheezy installation images? If
  that's the case, we'll see how to help you debug that further.
 
 Hi KiBi,
 
 Let's just close this bug, it has been almost 7 years since it was
 opened. If it happens again it'll be reported again.

Works for me, thanks.
 
Mraw,
KiBi.


signature.asc
Description: Digital signature
---End Message---


Bug#740499: debian-installer: firmware-7.4.0-amd64-netinst.iso missing broadcom firmware

2014-03-02 Thread Chris Bainbridge
Package: debian-installer
Version: firmware-7.4.0-amd64-netinst.iso
Severity: normal

Dear Maintainer,

https://www.debian.org/releases/stable/amd64/ch06s04.html.en says
Alternatively, unofficial CD builds containing non-free firmware can be
found at
http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/.;

And https://wiki.debian.org/Firmware says Alternatively, there are now
versions of the netinst CD images that also include all the non-free
firmware packages directly

Both these extracts infer that all the non-free firmware is in the
firmware image, but firmware-7.4.0-amd64-netinst.iso does not contain
Broadcom firmware (at least not b43). This firmware should be added to
the CD, or the documentation should mention that unofficial builds don't
contain *all* firmware. It's a waste of the user's time to download an
installer that claims to have non-free firmware and then find the
non-free firmware they need is missing.


-- 
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/20140302123512.GA10964@localhost



Bug#740500: debian-installer: amd64 documentation is incorrect/incomplete (isohybrid issues)

2014-03-02 Thread Chris Bainbridge
Package: debian-installer
Version: stable
Severity: normal

Dear Maintainer,

https://www.debian.org/releases/stable/amd64/ch04s03.html.en

Documentation is out of date - does not mention that this the amd64
images are isohybrid BIOS/EFI boot format, with both a MBR/GPT
partition scheme.  Documentation implies there is only one partition but
there are now two (EFI system partition and ISO9660 partition).

The section on adding an extra partition will likely not be followable
due to being incorrect/incomplete - it does not mention what tools to
use - *fdisk and gdisk do not work* and it is not clear whether either
of
them could correctly modify the hybrid MBR/GPT scheme used in the image
whilst preserving its bootability on both BIOS and EFI (?)


-- 
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/20140302123733.GB10964@localhost



Bug#740503: debian-installer: check-missing-firmware does not work with a USB drive that contains a partition table

2014-03-02 Thread Chris Bainbridge
Package: debian-installer
Version: 7.0.4 wheezy iso
Severity: important

Dear Maintainer,

Installing from debian-7.4.0-amd64-netinst.iso

check-missing-firmware does not work with a USB drive that
contains a partition table. When a USB drive with a single partition
containing the firmware is inserted, it reports that the firmware was
not found. The firmware is on partition /dev/sdc1. From the log I can
see that the function is attempting to scan drives and partitions
detected on the system, and mount them as FAT file systems. The
problem is that it does not try the USB drive partition 1 at
/dev/sdc1. It does try /dev/{sda sda sdc sdc sda1 sda1 sda sda sdc sdc
sda1 sda1 sda2 sda2 sda3 sda3} in that order. So it is trying to mount
/dev/sdc (the USB drive) but not /dev/sdc1 (the actual partition).

   - Workaround is to format the USB drive without a partition table,
 e.g. mkfs.vfat -I /dev/sdc (mkfs.vfat actually expects a
 partition table, -I override forces it to use the entire device)


-- 
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/20140302124028.GE10964@localhost



Bug#740502: debian-installer: check-missing-firmware shows incorrect missing list and only copies one firmware file at a time

2014-03-02 Thread Chris Bainbridge
Package: debian-installer
Version: 7.0.4 wheezy release
Severity: normal

Dear Maintainer,

Installing from debian-7.4.0-amd64-netinst.iso

1 check-missing-firmware missing files list is incorrect. Installer
detects that wifi needs Broadcom firmware and says The missing firmware
files are: b43/ucode29_mimo.fw b43-open/ucode29_mimo.fw. The list is
incorrect and incomplete. The list contains only two files - there are
more that are required. The list contains two files, suggesting
that both are needed - in fact only one copy of the file is needed (the
loader looks in two directories).

   - This bug seems to be caused by the installer interpreting the
 kernel firmware loading in an overly simple way. The firmware
 loader attempts to load files sequentially, and looks for them in
 two places.  If it does not find a file, it will immediately quit
 and print the two locations that it looked for the file. The Debian
 installer interprets and reports this pair of locations as an
 absolute list of missing files. It is not an absolute list, it is a
 duplicate pair for a single missing file.

   - Even if the file is present (eg. b43/ucode29_mimo.fw exists), this
 function still reports b43-open/ucode29_mimo.fw as missing! It's
 not missing, it's just an alternative location for the same file.

2. The installer should copy any firmware files on the USB drive in one
go. Because of the way the installer copies and loads one file at a
time, even if the user has done everything perfectly (all required
firmwares ready on a USB drive) the check missing files prompt will
pop up several times (3 in my case) and the user just has to keep
clicking yes. Any normal user is going to think that this is broken,
only users who are really paying attention and watching the logs will
notice that it is only loading one file every time they click
Continue.


-- 
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/20140302123924.GD10964@localhost



Bug#740501: debian-installer: check-missing-firmware mounts FAT partitions case-sensitive

2014-03-02 Thread Chris Bainbridge
Package: debian-installer
Version: 7.0.4 wheezy release
Severity: normal

Dear Maintainer,

Installing from debian-7.4.0-amd64-netinst.iso

FAT-fs (sdc): utf8 is not a recommended IO charset for FAT filesystems,
filesystem will be case sensitive!

check-missing-firmware mounts partitions in a case-sensitive way -
this may cause problems for some users and seems unncessary.


-- 
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/20140302123815.GC10964@localhost



Processed: Re: Bug#714350: FTBFS when locales-all is installed

2014-03-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tag 714350 unreproducible
Bug #714350 [localechooser] FTBFS when locales-all is installed
Added tag(s) unreproducible.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
714350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714350
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.139376445827420.transcr...@bugs.debian.org



Bug#714350: marked as done (FTBFS when locales-all is installed)

2014-03-02 Thread Debian Bug Tracking System
Your message dated Sun, 2 Mar 2014 13:47:35 +0100
with message-id 20140302124725.ge22...@mraw.org
and subject line Re: Bug#714350: FTBFS when locales-all is installed
has caused the Debian Bug report #714350,
regarding FTBFS when locales-all is installed
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.)


-- 
714350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714350
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: localechooser
Severity: 2.54

localechooser FTBFS if locales-all (which provides locales) is installed.

-- 
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email:  daniel.baum...@progress-technologies.net
Internet:   http://people.progress-technologies.net/~daniel.baumann/
---End Message---
---BeginMessage---
tag 714350 unreproducible
thanks

Daniel Baumann daniel.baum...@progress-technologies.net (2014-03-02):
 reopen 714350
 found 714350 2.60
 thanks
 
 no, it does; reopening accordingly.
 
 Checking syntax of localechooser
 LC_COLLATE=C ./mklanguagelist.data languagelist debian/languagelist.data
 ./get-SUPPORTED
 make[1]: *** [debian/SUPPORTED-short] Error 1
 make[1]: Leaving directory `/home/user/localechooser-2.60'
 dh_auto_build: make -j1 returned exit code 2
 make: *** [build] Error 2
 dpkg-buildpackage: error: debian/rules build gave error exit status 2

You'll have to do better. See attached, successful build log, with:
| $ dpkg-query -s locales-all|head -2
| Package: locales-all
| Status: install ok installed

Tagging and closing accordingly.

KiBi.
 dpkg-buildpackage -rfakeroot -D -us -uc -b
dpkg-buildpackage: source package localechooser
dpkg-buildpackage: source version 2.60
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Christian Perrier bubu...@debian.org
 dpkg-source --before-build localechooser-2.60
dpkg-buildpackage: host architecture amd64
 fakeroot debian/rules clean
dh clean
   dh_testdir
   dh_auto_clean
make[1]: Entering directory 
`/home/kibi/debian-installer/packages/localechooser-2.60'
rm -f localechooser.templates debian/templates debian/templates.continents 
debian/templates.base-in debian/templates.base debian/templates.tmp 
debian/languagelist.data SUPPORTED-short debian/iso_3166.tab
rm -f -rf debian/short-tmp debian/iso-codes
make[1]: Leaving directory 
`/home/kibi/debian-installer/packages/localechooser-2.60'
   debian/rules override_dh_clean
make[1]: Entering directory 
`/home/kibi/debian-installer/packages/localechooser-2.60'
rm -rf debian/pobuild debian/iso-codes debian/short-tmp
rm -rf debian/locales debian/sort-tmp
dh_clean
make[1]: Leaving directory 
`/home/kibi/debian-installer/packages/localechooser-2.60'
 debian/rules build
dh build
   dh_testdir
   dh_auto_configure
   dh_auto_build
make[1]: Entering directory 
`/home/kibi/debian-installer/packages/localechooser-2.60'
Checking syntax of finish-install.d/05localechooser
Checking syntax of post-base-installer.d/05localechooser
Checking syntax of debian/postinst
Checking syntax of languagemap
Checking syntax of localechooser
LC_COLLATE=C ./mklanguagelist.data languagelist debian/languagelist.data
./get-SUPPORTED
isoquery -c | cut -f 1,4 | sort debian/iso_3166.tab
[ -s debian/iso_3166.tab ]
./get-iso-codes
./mkshort
Building short lists of countries...
ar
bn
bo
ca
de
el
es
eu
fr
it
nl
pa
pt
pt_BR
ru
sq
sr
sv
ta
tr
zh_CN
zh_TW
en
./mktemplates.continents debian/iso_3166.tab regionmap 
debian/templates.continents
I: skipping country code 'AN': in regionmap but not in debian/iso_3166.tab
W: unknown region for country CW: not listed in regionmap
cat debian/localechooser.templates-in debian/templates.continents 
debian/templates.base-in
./mktemplates.base debian/templates.base-in debian/templates.base
am.po  done.
ar.po .. done.
ast.po .. done.
be.po  done.
bg.po  done.
bn.po .. done.
bo.po bs.po .. done.
ca.po ... done.
cs.po  done.
cy.po .. done.
da.po  done.
de.po .. done.
dz.po ... done.
el.po 

Bug#606110: installation-report: gtk installer fail to start with PXE boot of Dell Latitude D505

2014-03-02 Thread Cyril Brulebois
Petter Reinholdtsen p...@hungry.com (2014-03-02):
 [Cyril Brulebois]
  If you still have access to this machine, does the wheezy gtk
  installer start fine? Otherwise, lacking access to such a machine,
  I'm tempted to close this bug report.
 
 I still have access to the machine at work (it is one of my collection
 of test laptops).  I'll retry the wheezy installer, but vaguely
 remeber the problem exist there too.  Anything in particular I should
 test?

Yes, try passing vga=788. Failing that, you're probably going to lack a
framebuffer, and X won't be able to start. You would then have a
scrolling log on vt1 in which you should be able to see a “(EE) no
screens found” line.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Processed: Re: Bug#714350: FTBFS when locales-all is installed

2014-03-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 reopen 714350
Bug #714350 {Done: Cyril Brulebois k...@debian.org} [localechooser] FTBFS 
when locales-all is installed
Bug reopened
Ignoring request to alter fixed versions of bug #714350 to the same values 
previously set
 tag 714350 - unreproducible
Bug #714350 [localechooser] FTBFS when locales-all is installed
Removed tag(s) unreproducible.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
714350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714350
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.139376492629858.transcr...@bugs.debian.org



Bug#714350: FTBFS when locales-all is installed

2014-03-02 Thread Daniel Baumann
reopen 714350
tag 714350 - unreproducible
thanks

On 03/02/2014 01:47 PM, Cyril Brulebois wrote:
 You'll have to do better. See attached, successful build log,
 with:

as originally already said, if you install locales-all (which provides
locales) instead of locales, localechooser fails to build from source.

removing tag and reopening accordingly.

-- 
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email:  daniel.baum...@progress-technologies.net
Internet:   http://people.progress-technologies.net/~daniel.baumann/


-- 
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/53132a3a.60...@progress-technologies.net



Bug#511153: marked as done (tzsetup-udeb: time zone list in tzsetup out of date wrt glibc/tzdata time)

2014-03-02 Thread Debian Bug Tracking System
Your message dated Sun, 2 Mar 2014 13:58:59 +0100
with message-id 20140302125859.gg22...@mraw.org
and subject line Re: Bug#511153: tzsetup-udeb: time zone list in tzsetup out of 
date wrt glibc/tzdata time
has caused the Debian Bug report #511153,
regarding tzsetup-udeb: time zone list in tzsetup out of date wrt glibc/tzdata 
time
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.)


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

Package: tzsetup-udeb
Severity: wishlist

In rev 2332 of pkg-glibc 
(http://svn.debian.org/viewsvn/pkg-glibc?rev=2332view=rev),
a number of new time zones, such as Indiana/Knox and Kentucky/Louisville 
were added.


It looks like these new time zones aren't being surfaced in tzsetup-udeb 
yet.


Please update tzsetup-udeb so it's aligned with the latest pkg-glibc 
time zone data.



-- System Information:
Debian Release: lenny/sid
APT prefers hardy-updates
APT policy: (500, 'hardy-updates'), (500, 'hardy-security'), (500, 
'hardy'), (500, 'dapper-updates'), (500, 'dapper-security'), (500, 
'dapper')


Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-19-server (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
~ 




---End Message---
---BeginMessage---
Christian PERRIER bubu...@debian.org (2014-03-02):
 Quoting Cyril Brulebois (k...@debian.org):
 
   Actually, there might me other cases like this one as I haven't seen
   anyone actively trying to cope with changes in tzdata to align tzsetup
   with them (such as the recent nightmare in Argentinian timezones).
  
  what should we do about this bug report?
 
 IIRC, there have been a few moments in various releases, where the
 list of possible timezones for multi-TZ countries have been
 updated. So, in short, it can be closed, IMHO.

Alright, doing so, thanks.

Mraw,
KiBi.


signature.asc
Description: Digital signature
---End Message---


Bug#714350: FTBFS when locales-all is installed

2014-03-02 Thread Cyril Brulebois
Control: retitle 714350 FTBFS when locales is not installed

Daniel Baumann daniel.baum...@progress-technologies.net (2014-03-02):
 On 03/02/2014 01:47 PM, Cyril Brulebois wrote:
  You'll have to do better. See attached, successful build log,
  with:
 
 as originally already said, if you install locales-all (which provides
 locales) instead of locales, localechooser fails to build from source.

What you originally said, and what you're stubbornly repeating without
any care for what was replied, is missing the point; this isn't due to
locales-all's being installed, but due to locales's not being installed,
which is a very different thing.

KiBi.


signature.asc
Description: Digital signature


Processed: Re: Bug#714350: FTBFS when locales-all is installed

2014-03-02 Thread Debian Bug Tracking System
Processing control commands:

 retitle 714350 FTBFS when locales is not installed
Bug #714350 [localechooser] FTBFS when locales-all is installed
Changed Bug title to 'FTBFS when locales is not installed' from 'FTBFS when 
locales-all is installed'

-- 
714350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714350
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.b714350.13937660904834.transcr...@bugs.debian.org



Bug#673644: Message at end of successful install talks about floppies (should be updated)

2014-03-02 Thread Cyril Brulebois
Christian PERRIER bubu...@debian.org (2014-03-02):
 Quoting Cyril Brulebois (k...@debian.org):
 
   _Description: Installation complete
Installation is complete, so it is time to boot into your new system.
  - Make sure to remove the installation media (CD-ROM, floppies), so that
  - you boot into the new system rather than restarting the installation.
  + Make sure to remove the installation media (CD-ROM, DVD-ROM, USB flash
  + disk), so that you boot into the new system rather than restarting the
  + installation.
 
 Maybe try to be more generic so that we don't have to change this
 when CD-ROM, DVD or USB flash disk are considered obsolete as well?
 
 Something like Make to to remove the installation media so that

I kinda liked the parenthesis since people might not be exactly sure
what we're talking about.

debian-cd@/Steve, any opinion on this? I don't think we're going to drop
support for CD, DVD, or USB flash disk any time soon. Not spending our
time trying to make stuff fit on CD#1 is OK, but there's still some
real needs for CD images last I heard…

Mraw,
KiBi.


signature.asc
Description: Digital signature


Processed: Remove free-form versions from found lists

2014-03-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 notfound 740499 firmware-7.4.0-amd64-netinst.iso
Bug #740499 [debian-installer] debian-installer: 
firmware-7.4.0-amd64-netinst.iso missing broadcom firmware
There is no source info for the package 'debian-installer' at version 
'firmware-7.4.0-amd64-netinst.iso' with architecture ''
Unable to make a source version for version 'firmware-7.4.0-amd64-netinst.iso'
No longer marked as found in versions firmware-7.4.0-amd64-netinst.iso.
 notfound 740500 stable
Bug #740500 [debian-installer] debian-installer: amd64 documentation is 
incorrect/incomplete (isohybrid issues)
There is no source info for the package 'debian-installer' at version 'stable' 
with architecture ''
Unable to make a source version for version 'stable'
No longer marked as found in versions stable.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
740499: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740499
740500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740500
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.139376728313050.transcr...@bugs.debian.org



Bug#575309: marked as done (user-setup: Should stop adding first user to device access groups)

2014-03-02 Thread Debian Bug Tracking System
Your message dated Sun, 2 Mar 2014 15:03:35 +0100
with message-id 20140302140335.ga6...@mraw.org
and subject line Re: Bug#575309: Time to stop adding the first created user to 
useful groups?
has caused the Debian Bug report #575309,
regarding user-setup: Should stop adding first user to device access groups
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.)


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

Package: user-setup
Version: 1.28
Tags:patch

In squeeze, the desktop uses consolekit and friends to grant access to
devices for the user in front on the screen.  This scale a lot better
when there is a lot of users in LDAP or NIS that need to get access to
the local devices on their own machine, but not the local devices on
other peoples machine.

The code in user-setup-apply to add the first user to all the groups
in passwd/user-default-groups should no longer be needed.  I believe
it should be dropped for Squeeze, or at least the default groups used
should be trimmed down to nothing.

Here is a patch to remove the code.

Index: user-setup-apply
===
--- user-setup-apply(revision 58013)
+++ user-setup-apply(working copy)
@@ -125,13 +125,6 @@
$log $chroot $ROOT chown $USER:$USER /home/$USER /dev/null 
|| true
fi

-   if [ -n $USER ]; then
-   db_get passwd/user-default-groups
-   for group in $RET; do
-   $log $chroot $ROOT adduser $USER $group /dev/null 
21 || true
-   done
-   fi
-
db_get passwd/root-login
if [ $RET = false ]  [ -n $USER ]; then
# Ensure sudo is installed, and set up the user to be able
Index: debian/user-setup-udeb.templates
===
--- debian/user-setup-udeb.templates(revision 58013)
+++ debian/user-setup-udeb.templates(working copy)
@@ -16,12 +16,6 @@
 Type: string
 Description: for internal use only

-# Allow preseeding the groups to which the first created user is added
-Template: passwd/user-default-groups
-Type: string
-Default: audio cdrom dialout floppy video plugdev netdev powerdev scanner
-Description: for internal use only
-
 Template: passwd/root-login
 Type: boolean
 Default: true

Happy hacking,
-- 
Petter Reinholdtsen


---End Message---
---BeginMessage---
Christian PERRIER bubu...@debian.org (2010-11-17):
 This issues was brought again to my attention on IRC.
 
 I'm tempted to accept such a change (though this is really late
 now). I don't really buy the argument of what could happen on a
 server without consolekit: who really cares to have the first
 created user have access to audio, or other hardware on a server?
 
 Joey raised a few objections:
 
 a. passwd/user-default-groups is a documented preseed variable,
so it probably needs to remain available for preseeders to use, and
the documentation will need to be updated.
 
 b. I'm missing the list of exactly what groups consolekit puts the
console user in, so I can't tell if we have additional groups in our

consolekit is no longer maintained, so I think keeping the current
status quo for now is OK. Maybe we'll revisit things if switching to
systemd on linux changes a few things. But then a fresh bug report with
all relevant info would be nicer than piling up stuff here.

Mraw,
KiBi.


signature.asc
Description: Digital signature
---End Message---


Bug#637453: marked as done (lower priority of root's password, use sudo in standard install)

2014-03-02 Thread Debian Bug Tracking System
Your message dated Sun, 2 Mar 2014 15:06:56 +0100
with message-id 20140302140656.ga6...@mraw.org
and subject line Re: Bug#637453: lower priority of root's password, use sudo in 
standard install
has caused the Debian Bug report #637453,
regarding lower priority of root's password, use sudo in standard install
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.)


-- 
637453: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: user-setup
Version: 1.40
Tags: wishlist, patch

Setting the root account password is not mandatory in standard installation, 
skipping it already adds the first user account to sudo.
Lowering the priority skips 2 questions in the standard installation.
The questions will still be available on the expert install and preseed.

-- 
Melhores cumprimentos/Best Regards,

Miguel Figueiredo
http://www.DebianPT.org
diff --git a/user-setup-ask b/user-setup-ask
index 3fb8a17..5815fe4 100755
--- a/user-setup-ask
+++ b/user-setup-ask
@@ -36,7 +36,7 @@ while :; do
 		# Ask how the password files should be set up.
 		db_input low passwd/shadow || true
 		# Ask if root should be allowed to login.
-		db_input medium passwd/root-login || true
+		db_input low passwd/root-login || true
 		;;
 	1)
 		db_get passwd/root-login
@@ -52,8 +52,8 @@ while :; do
 # No preseed of the root password hash
 # we will prompt the user
 db_set passwd/root-password-crypted 
-db_input critical passwd/root-password || true
-db_input critical passwd/root-password-again || true
+db_input low passwd/root-password || true
+db_input low passwd/root-password-again || true
 			fi
 		fi
 		;;
---End Message---
---BeginMessage---
Christian PERRIER bubu...@debian.org (2011-08-12):
 +1 on both remarks by Colin (not agreeing with sudo by defaultand
 the fact that the remark about Ubuntu wasn't appropriate).
 
 Still, Miguel, thanks for raising these questions again. Sometimes,
 conditions change and, at least, re-asking ourselves whether choices
 made some years ago are still valid is a good idea.
 
 Here, however, I think we shouldn't change anything (except the root
 password confirmation as mentioned by Colin).

Agreed. If anyone wants to pursue this goal, I'd suggest opening a fresh
wishlist bug report on that topic.

Mraw,
KiBi.


signature.asc
Description: Digital signature
---End Message---


Bug#406620: marked as done (user-setup: Failed to ask its questions when run during default install)

2014-03-02 Thread Debian Bug Tracking System
Your message dated Sun, 2 Mar 2014 15:29:58 +0100
with message-id 20140302142958.ga9...@mraw.org
and subject line Re: Bug#406620: Installation-report
has caused the Debian Bug report #406620,
regarding user-setup: Failed to ask its questions when run during default 
install
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.)


-- 
406620: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=406620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports

Boot method: Netinst CD 
Image version:
http://cdimage.debian.org/cdimage/etch_di_rc1/i386/iso-cd/debian-testing
-i386-netinst.iso
Date: 12-january-2007 morning (CET)

Machine: HP ML310 + smartarray 641 + 2*72 GB disk
Processor: Intel(R) Pentium(R) D CPU 3.00GHz stepping 04 - 2mb cache
Memory: 1.5 Gb
Partitions: 
FilesystemType   1K-blocks  Used Available Use% Mounted on
/dev/cciss/c0d0p3
  ext3 7692908230952   7071176   4% /
tmpfstmpfs  778012 0778012   0% /lib/init/rw
udev tmpfs   1024080 10160   1% /dev
tmpfstmpfs  778012 0778012   0% /dev/shm
/dev/cciss/c0d0p1
  ext2  120411  6415107572   6% /boot
/dev/cciss/c0d0p5
  ext3 3842376 73268   3573920   3% /home
/dev/cciss/c0d0p6
  ext3 7692876148404   7153696   3% /opt
/dev/cciss/c0d0p7
  ext3 3842376126088   3521100   4% /tmp
/dev/cciss/c0d0p8
  ext3 7692876387164   6914936   6% /usr
/dev/cciss/c0d0p9
  ext3 7692876148448   7153652   3% /usr/local
/dev/cciss/c0d0p10
  ext3 7692876312328   6989772   5% /var
/dev/cciss/c0d0p11
  ext3 7692876158656   7143444   3% /var/log


Output of lspci -nn and lspci -vnn:

sophos:~# lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation E7230 Memory Controller
Hub [8086:2778] (rev 81)
00:01.0 PCI bridge [0604]: Intel Corporation E7230 PCI Express Root Port
[8086:2779] (rev 81)
00:1c.0 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI
Express Port 1 [8086:27d0] (rev 01)
00:1c.4 PCI bridge [0604]: Intel Corporation 82801GR/GH/GHM (ICH7
Family) PCI Express Port 5 [8086:27e0] (rev 01)
00:1c.5 PCI bridge [0604]: Intel Corporation 82801GR/GH/GHM (ICH7
Family) PCI Express Port 6 [8086:27e2] (rev 01)
00:1d.0 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family)
USB UHCI #1 [8086:27c8] (rev 01)
00:1d.1 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family)
USB UHCI #2 [8086:27c9] (rev 01)
00:1d.2 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family)
USB UHCI #3 [8086:27ca] (rev 01)
00:1d.3 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family)
USB UHCI #4 [8086:27cb] (rev 01)
00:1d.7 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family)
USB2 EHCI Controller [8086:27cc] (rev 01)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge
[8086:244e] (rev e1)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801GB/GR (ICH7 Family)
LPC Interface Bridge [8086:27b8] (rev 01)
00:1f.1 IDE interface [0101]: Intel Corporation 82801G (ICH7 Family) IDE
Controller [8086:27df] (rev 01)
01:03.0 VGA compatible controller [0300]: ATI Technologies Inc ES1000
[1002:515e] (rev 02)
01:04.0 System peripheral [0880]: Compaq Computer Corporation Integrated
Lights Out Controller [0e11:b203] (rev 03)
01:04.2 System peripheral [0880]: Compaq Computer Corporation Integrated
Lights Out  Processor [0e11:b204] (rev 03)
01:04.4 USB Controller [0c03]: Hewlett-Packard Company Unknown device
[103c:3300]
05:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme
BCM5721 Gigabit Ethernet PCI Express [14e4:1659] (rev 11)
09:00.0 PCI bridge [0604]: Intel Corporation 6702PXH PCI Express-to-PCI
Bridge A [8086:032c] (rev 09)
0a:02.0 RAID bus controller [0104]: Compaq Computer Corporation Smart
Array 64xx [0e11:0046] (rev 01)




sophos:~# lspci -vnn
00:00.0 Host bridge [0600]: Intel Corporation E7230 Memory Controller
Hub [8086:2778] (rev 81)
Subsystem: Compaq Computer Corporation Unknown device
[0e11:3200]
Flags: bus master, fast devsel, latency 0
Capabilities: [e0] Vendor Specific Information

00:01.0 PCI bridge [0604]: Intel Corporation E7230 PCI Express Root Port
[8086:2779] (rev 81) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=09, subordinate=0d, sec-latency=0
I/O behind bridge: 4000-4fff
Memory behind bridge: fdf0-fdff
Prefetchable memory 

Bug#568895: marked as done (user-setup: Remove some of the default groups, they are unused now)

2014-03-02 Thread Debian Bug Tracking System
Your message dated Sun, 2 Mar 2014 15:32:56 +0100
with message-id 20140302143256.ga9...@mraw.org
and subject line Re: Bug#568895: user-setup: Remove some of the default groups, 
they are unused now
has caused the Debian Bug report #568895,
regarding user-setup: Remove some of the default groups, they are unused now
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.)


-- 
568895: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568895
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: user-setup
Version: 1.28
Severity: normal

There are too many groups for the default user, and some of theme are not
used any more : audio cdrom floppy video plugdev netdev powerdev dialout
are probably not needed.

At least plugdev is no more used, netdev and powerdev are replaced by
consolekit.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable'), (100, 'unstable'), (50, 
'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.32-trunk-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

Versions of packages user-setup depends on:
ii  adduser  3.112   add and remove users and groups
ii  debconf [debconf-2.0]1.5.28  Debian configuration management sy
ii  passwd   1:4.1.4.2-1 change and administer password and

user-setup recommends no packages.

user-setup suggests no packages.


---End Message---
---BeginMessage---
Frans Pop elen...@planet.nl (2010-02-08):
 On Monday 08 February 2010, Frans Pop wrote:
  However, user-setup should remain backwards compatible with Lenny. That
  could be implemented in different ways [1], but it does mean we cannot
  just remove the groups.
 
 Also, users only get added to groups that actually exist at the end of the 
 installation (which depends on which packages have been installed).
 So there's no real problem with leaving obsolete groups listed in the 
 default setting for backwards compatibility.

That + what I mentioned in [1] → closing this bug report.

 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575309#40

Mraw,
KiBi.


signature.asc
Description: Digital signature
---End Message---


Processed: Re: Bug#604081: root password mismatch

2014-03-02 Thread Debian Bug Tracking System
Processing control commands:

 found -1 1.48
Bug #604081 [user-setup] Does not show password mismatch when first entered 
root password is empty
Marked as found in versions user-setup/1.48.
 found -1 1.55
Bug #604081 [user-setup] Does not show password mismatch when first entered 
root password is empty
Marked as found in versions user-setup/1.55.
 tag -1 confirmed
Bug #604081 [user-setup] Does not show password mismatch when first entered 
root password is empty
Added tag(s) confirmed.

-- 
604081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604081
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.b604081.13937715896379.transcr...@bugs.debian.org



Bug#604081: root password mismatch

2014-03-02 Thread Cyril Brulebois
Control: found -1 1.48
Control: found -1 1.55
Control: tag -1 confirmed

Christian PERRIER bubu...@debian.org (2010-11-20):
 reassign 604081 user-setup
 retitle 604081 Does not show password mismatch when first entered root 
 password is empty
 thanks
 
 Quoting Daniel Pocock (dan...@pocock.com.au):
  Package: installation-reports
  
  Installing amd64 as a domU in xen
  
  At the first prompt for root password, just hit enter
  
  At the second prompt, type a password
  
  No password-mismatch error is displayed, installer proceeds to
  setting up a user account
  
  Once rebooted, root login impossible using blank password or the
  `repeat' password
  
  Mount the root fs (e.g. from dom0 or another OS), inspect /etc/shadow:
  
  root:!:14932:0:9:7:::
 
 When the root password is empty, root account is disabled. This is
 what the first template says.
 
 Still, one can understand that entering the pwd empty, then setting
 something in the confirmation is user error and the user should have a
 chance to correct it. And we should anyway to give the false
 impression that a root password will be set.
 
 Reassigning to user-setup as this bug belongs to that package.

Still the case in wheezy and above, so recording the versions
accordingly.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Bug#711093: cdrom: Default user is not added to group sudo

2014-03-02 Thread Cyril Brulebois
Hi,

Steve McIntyre st...@einval.com (2013-06-11):
 Control: reassign -1 user-setup
 
 On Tue, Jun 04, 2013 at 06:06:24PM +0200, ashka wrote:
  Although sudo is installed, the main/default user is not added to the
  sudo group after install, which leads to errors when trying to run a
  sudo command.  The user has to use su to get root access, which is
  unexpected since sudo is installed.
 
 I'm reassigning to the user-setup package; that's where this happens
 in the installer.

well, the root password prompt contains:
|  The root user should not have an empty password. If you leave this
|  empty, the root account will be disabled and the system's initial user
|  account will be given the power to become root using the sudo
|  command.

I don't think it was intended to give sudo access to the first user if a
root password has been specified.

Should we reconsider the current behaviour?

Mraw,
KiBi.


signature.asc
Description: Digital signature


Bug#450954: Username 'admin' is reserved

2014-03-02 Thread Cyril Brulebois
Josh Kelley josh...@gmail.com (2014-02-11):
 Ubuntu no longer uses the admin group (and, as far as I can tell,
 never used the admin username).
 
 http://askubuntu.com/a/122500/5682
 https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/893842

(The latter contradicts what you put in parentheses.)

 Based on this, I suggest removing admin from the list of reserved names.

Thanks, but I'll leave that up to Colin.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Bug#544971: Assumes HOME is /home/$USER.

2014-03-02 Thread Cyril Brulebois
Control: tag -1 wontfix

Trent W. Buck trentb...@gmail.com (2009-09-04):
 Package: user-setup
 Version: 1.28
 Severity: minor
 
 user-setup-apply is used by live-initramfs to create a guest account
 at boot time.  I needed the account to have HOME outside of /home,
 because /home is an NFS mount used by non-guest accounts.
 
 Since user-setup-apply seems to end up just calling adduser, this is
 no big deal -- I can change DHOME to /tmp in adduser.conf.  But while
 RTFSing, I noticed that
 
 HOME_EXISTED=
 if [ -d $ROOT/home/$USER ]; then
 HOME_EXISTED=1
 fi
 
 Assumes that the new user's home directory will be /home/$USER.  To
 fix this, you'd need to parse and understand adduser.conf, so it may
 be reasonable to simply WONTFIX this issue.

Given the current logic (HOME_EXISTED etc.), I'm not very keen on
changing things there, so I'll go with wontfix for now. If nobody
pops up yelling and posting patches, it can be closed in a while.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Processed: Re: Bug#544971: Assumes HOME is /home/$USER.

2014-03-02 Thread Debian Bug Tracking System
Processing control commands:

 tag -1 wontfix
Bug #544971 [user-setup] Assumes HOME is /home/$USER.
Added tag(s) wontfix.

-- 
544971: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544971
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.b544971.139377249611394.transcr...@bugs.debian.org



Bug#332911: tagging 332911

2014-03-02 Thread Cyril Brulebois
Christian Perrier bubu...@debian.org (2005-10-28):
 # Automatically generated email from bts, devscripts version 2.9.8
 tags 332911 wontfix

Hello,

what should we do about this bug report?

Mraw,
KiBi.


signature.asc
Description: Digital signature


Bug#59988: marked as done (naming service (LDAP, nis+, etc) support)

2014-03-02 Thread Debian Bug Tracking System
Your message dated Sun, 2 Mar 2014 16:12:36 +0100
with message-id 20140302151236.ga14...@mraw.org
and subject line Re: Bug#59988: Dropping this BR that will never be fixed, at 
least in user-setup
has caused the Debian Bug report #59988,
regarding naming service (LDAP, nis+, etc) support
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.)


-- 
59988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=59988
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: base
Version: 2309
Severity: wishlist

Please add NIS+ support in debian.
This will lead to changes in glibc and new packages like
nis-utils, pam_keylogin, pam_unix2 .

More information can be obtained at
  http://www.suse.de/~kukuk/nisplus/index.html
  
Many thanks in advance
  Stefan 


   Linux groupUniversity Regensburg
mailto:linux.supp...@rphs1.physik.uni-regensburg.de
http://linux.uni-regensburg.de

   

-- System Information
Debian Release: potato
Kernel Version: Linux pc7979 2.2.10 #1 SMP Mon Aug 30 10:14:10 CEST 1999 i686 
unknown

---End Message---
---BeginMessage---
Christian Perrier bubu...@debian.org (2006-04-23):
 tags 59988 wontfix
 thanks
 
 I very highly doubt that we add support for external user databases in
 D-I. Neither in the near future, nor in long term.
 
 This bug is assigned to suer-setup because it's inherited from
 base-config but I really see no point in keeping it opened for no reason.
 
 Without further notice, I'll close it in the next bug cleaning round
 for user-setup

The next bug cleaning round is now. :)

Mraw,
KiBi.


signature.asc
Description: Digital signature
---End Message---


Bug#59989: marked as done (naming service (LDAP, nis+, etc) support)

2014-03-02 Thread Debian Bug Tracking System
Your message dated Sun, 2 Mar 2014 16:12:36 +0100
with message-id 20140302151236.ga14...@mraw.org
and subject line Re: Bug#59988: Dropping this BR that will never be fixed, at 
least in user-setup
has caused the Debian Bug report #59988,
regarding naming service (LDAP, nis+, etc) support
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.)


-- 
59988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=59988
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: base
Version: 2309
Severity: wishlist

Please add NIS+ support in debian.
This will lead to changes in glibc and new packages like
nis-utils, pam_keylogin, pam_unix2 .

More information can be obtained at
  http://www.suse.de/~kukuk/nisplus/index.html
  
Many thanks in advance
  Stefan 


   Linux groupUniversity Regensburg
mailto:linux.supp...@rphs1.physik.uni-regensburg.de
http://linux.uni-regensburg.de

   

-- System Information
Debian Release: potato
Kernel Version: Linux pc7979 2.2.10 #1 SMP Mon Aug 30 10:14:10 CEST 1999 i686
unknown


---End Message---
---BeginMessage---
Christian Perrier bubu...@debian.org (2006-04-23):
 tags 59988 wontfix
 thanks
 
 I very highly doubt that we add support for external user databases in
 D-I. Neither in the near future, nor in long term.
 
 This bug is assigned to suer-setup because it's inherited from
 base-config but I really see no point in keeping it opened for no reason.
 
 Without further notice, I'll close it in the next bug cleaning round
 for user-setup

The next bug cleaning round is now. :)

Mraw,
KiBi.


signature.asc
Description: Digital signature
---End Message---


Bug#656509: marked as done (user-setup-udeb: Please consider amending password advice)

2014-03-02 Thread Debian Bug Tracking System
Your message dated Sun, 2 Mar 2014 16:22:38 +0100
with message-id 20140302152238.ga14...@mraw.org
and subject line Re: Bug#656509: user-setup-udeb: Please consider amending 
password advice
has caused the Debian Bug report #656509,
regarding user-setup-udeb: Please consider amending password advice
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.)


-- 
656509: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656509
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: user-setup-udeb
Severity: wishlist


d-i says:

   A good password will contain a mixture of letters, numbers and
   punctuation and should be changed at regular intervals.

Complexity in a password is good and probably unarguable, although
length should also be considered to have some importance, Why advise
changing it at regular intervals? Why not advocate not imparting it to
anyone or not reusing it on other systems? Is there something which
causes a good password to degenerate over time?

The second part of the advice does not appear to have any technical
basis so removing it would be of little consequence.


---End Message---
---BeginMessage---
Christian PERRIER bubu...@debian.org (2012-01-20):
 Quoting Brian Potkin (claremont...@gmail.com):
  d-i says:
  
 A good password will contain a mixture of letters, numbers and
 punctuation and should be changed at regular intervals.
  
  Complexity in a password is good and probably unarguable, although
  length should also be considered to have some importance, Why advise
  changing it at regular intervals? Why not advocate not imparting it to
  anyone or not reusing it on other systems? Is there something which
  causes a good password to degenerate over time?
  
  The second part of the advice does not appear to have any technical
  basis so removing it would be of little consequence.

It takes a few seconds to find something like this in a search engine:
  https://www.schneier.com/blog/archives/2010/11/changing_passwo.html

 Are you ready to handle the round of updates for over sixty languages,
 for a very debatable and cosmetic change?
 
 I am not, sorry.

Neither am I, so I'll just close this bug report for now.

Mraw,
KiBi.


signature.asc
Description: Digital signature
---End Message---


Bug#551172: marked as done (debian-installer: Support option to decide from where the system should get it is users/authentication)

2014-03-02 Thread Debian Bug Tracking System
Your message dated Sun, 2 Mar 2014 16:25:02 +0100
with message-id 20140302152502.ga15...@mraw.org
and subject line Re: Bug#551172: debian-installer: Support option to decide 
from where the system should get it is users/authentication
has caused the Debian Bug report #551172,
regarding debian-installer: Support option to decide from where the system 
should get it is users/authentication
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.)


-- 
551172: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551172
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: debian-installer
Severity: wishlist

Hello,

I like the idea of OpenSuSE. At install time, you have to decide how users auth
on the installed system, e.g.:

* shadow (default)
* LDAP
* Windows Domäne
* Some others..

It would be realy nice if d-i also provides such a way.

-- System Information:
Debian Release: 5.0.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.28.4--std-ipv6-32 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash


---End Message---
---BeginMessage---
Christian Perrier bubu...@debian.org (2009-10-16):
 reassign 551172 user-setup
 thanks
 
 Quoting Patrick Matthäi (pmatth...@debian.org):
  Package: debian-installer
  Severity: wishlist
  
  Hello,
  
  I like the idea of OpenSuSE. At install time, you have to decide how
  users auth on the installed system, e.g.:
  
  * shadow (default)
  * LDAP
  * Windows Domäne
  * Some others..
  
  It would be realy nice if d-i also provides such a way.
 
 
 That clearly pertains to the user-setup component.
 
 Anyone feeling like implementing this? That sounds tricky as it
 involves the choice of installing libnss_foo packages, then configure
 them, etc...

Nobody popped up in the last 4+ years to work on this topic, so I'm
closing this bug report for the time being.

Mraw,
KiBi.


signature.asc
Description: Digital signature
---End Message---


Bug#673644: Message at end of successful install talks about floppies (should be updated)

2014-03-02 Thread Christian PERRIER
Quoting Cyril Brulebois (k...@debian.org):

 debian-cd@/Steve, any opinion on this? I don't think we're going to drop
 support for CD, DVD, or USB flash disk any time soon. Not spending our
 time trying to make stuff fit on CD#1 is OK, but there's still some
 real needs for CD images last I heard…

If you prefer sticking on the more detailed wording, then your wording
is fine and, yes, all you have to do is to change the template in the
package's git tree, then l10n-sync will do its magic the night after
and translators who have chosen to be notified will be notified.



signature.asc
Description: Digital signature


Bug#711093: cdrom: Default user is not added to group sudo

2014-03-02 Thread Christian PERRIER
Quoting Cyril Brulebois (k...@debian.org):

 I don't think it was intended to give sudo access to the first user if a
 root password has been specified.
 
 Should we reconsider the current behaviour?

IMHO, no.

If this bug is asking for this, then it should be marked wontfix (or closed).



signature.asc
Description: Digital signature


Bug#739976: add device support: mirabox

2014-03-02 Thread Jasmin Schnatterbeck
Hi,

On Sat, 2014-03-01 at 02:42 +, Ian Campbell wrote:
 On Mon, 2014-02-24 at 14:41 +0100, Jasmin Schnatterbeck wrote:
  Package: flash-kernel
  Version: 3.13
  Severity: important
  
  The device DB is missing support for the Mirabox.
  
  Proposal:
 
 Thanks for this.
 
 Perhaps you could also add some information to
 http://wiki.debian.org/DebianOn ?
 

The process is very similar to the one of the Dreamplug - may I can
integrate this as soon as kernel support/package is determined:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739972

  Machine: Globalscale Mirabox
  Kernel-Flavors: armmp
  DTB-Id: armada-370-mirabox.dtb
  DTB-Append: yes
 
 Is this really required on new platform like this?
 
 I would expect that a newish system would have a u-boot which supports
 FDT natively rather that via appending. Does loading the dtb at some
 address and adding that address as a third argument to the bootz or
 bootm command work?
 
 On the other hand you say the u-boot is quite old so maybe this is
 correct, I just wanted to check that you didn't just copy this bit from
 an older platform.

yes, unfortunately the bootloader is old and does not support FDT.
May there will be a DT-capable bootloader from the manufacturer in the
future, but I am not sure about that.

 
  U-Boot-Kernel-Address: 0x8000
  U-Boot-Initrd-Address: 0x0
  Boot-Device: /dev/sdb1
  Boot-Kernel-Path: uImage
  Boot-Initrd-Path: uInitrd
  Boot-DTB-Path: dtb
  Required-Packages: u-boot-tools
  Bootloader-Sets-Root: no
 
 This is now called Bootloader-Sets-Incorrect-Root.

OK; found in commit 850c8fc323bbab52a6264035d11edd372ce2596f

The bootloader sets some UBI device on internal NAND as root without
changes... but as the u-boot env variables need to be adapted anyway for
booting from the SD Card, it is preferred, that the kernel
command-line-parameter for root works as expected.

 
 OOI do you know if mainline u-boot getting any support for this device
 (whether based on the vendor's version or not)?
 

As far as I know, there are no efforts to mainline the u-boot-support.
There are some experiments regarding the barebox bootloader, but
currently with serial port support only.
http://free-electrons.com/blog/barebox-2013-07/

The old u-boot seems to be the only bootloader that works reasonable in
order to boot the device...

Jasmin


-- 
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/1393767429.8639.40.camel@genesis



Bug#543268: user-setup: Please provide preseedable passwd/user-extra-groups, to allow preseeding without overriding defaults

2014-03-02 Thread Cyril Brulebois
Control: tag -1 patch

Josh Triplett j...@joshtriplett.org (2009-08-23):
 Package: user-setup
 Severity: wishlist
 
 user-setup provides a preseedable passwd/user-default-groups, which
 overrides the default groups a user will normally get added to.  I'd
 like to have a second preseedable item passwd/user-extra-groups, empty
 by default, which I can preseed to add additional groups without
 overriding those supplied by default.

So Joey sent a patch[1] a while ago, here's the user-setup part,
refreshed against current master (for the changelog part).

 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543268#8

Tagging this bug report with patch. Of course if the patch gets pushed,
the manual wants to be updated as well (see initial patch).

Mraw,
KiBi.
From a93583034f56b6bc35192935e93911105a65efc8 Mon Sep 17 00:00:00 2001
From: Cyril Brulebois k...@debian.org
Date: Sun, 2 Mar 2014 16:30:29 +0100
Subject: [PATCH] Add preseedable passwd/user-extra-groups. Closes: #543268

---
 debian/changelog | 7 +++
 debian/user-setup-udeb.templates | 6 ++
 user-setup-apply | 8 +---
 3 files changed, 18 insertions(+), 3 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index c98349c..cf9dc22 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+user-setup (1.56) UNRELEASED; urgency=medium
+
+  [ Joey Hess ]
+  * Add preseedable passwd/user-extra-groups. Closes: #543268
+
+ -- Cyril Brulebois k...@debian.org  Sun, 02 Mar 2014 16:29:35 +0100
+
 user-setup (1.55) unstable; urgency=low
 
   * Add first created user to lpadmin group so that it can use local
diff --git a/debian/user-setup-udeb.templates b/debian/user-setup-udeb.templates
index 603325f..33b3514 100644
--- a/debian/user-setup-udeb.templates
+++ b/debian/user-setup-udeb.templates
@@ -22,6 +22,12 @@ Type: string
 Default: audio cdrom dip floppy video plugdev netdev powerdev scanner bluetooth debian-tor lpadmin
 Description: for internal use only
 
+# Allow adding user to extra groups in addition to the default
+Template: passwd/user-extra-groups
+Type: string
+Default: 
+Description: for internal use only
+
 Template: passwd/root-login
 Type: boolean
 Default: true
diff --git a/user-setup-apply b/user-setup-apply
index f24ece2..2347b9f 100755
--- a/user-setup-apply
+++ b/user-setup-apply
@@ -141,9 +141,11 @@ if [ $RET = true ]  ! is_system_user; then
 	fi
 
 	if [ -n $USER ]; then
-		db_get passwd/user-default-groups
-		for group in $RET; do
-			$log $chroot $ROOT adduser $USER $group /dev/null 21 || true
+		for type in default extra; do
+			db_get passwd/user-$type-groups
+			for group in $RET; do
+$log $chroot $ROOT adduser $USER $group /dev/null 21 || true
+			done
 		done
 	fi
 
-- 
1.9.0



signature.asc
Description: Digital signature


Processed: Re: Bug#543268: user-setup: Please provide preseedable passwd/user-extra-groups, to allow preseeding without overriding defaults

2014-03-02 Thread Debian Bug Tracking System
Processing control commands:

 tag -1 patch
Bug #543268 [user-setup] user-setup: Please provide preseedable 
passwd/user-extra-groups, to allow preseeding without overriding defaults
Added tag(s) patch.

-- 
543268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543268
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.b543268.139377446922870.transcr...@bugs.debian.org



Bug#490899: user-setup-udeb: way to (easily) *not* create a user, but do the root password setup

2014-03-02 Thread Cyril Brulebois
Control: tag -1 confirmed
Control: severity -1 important

Joerg Jaspert jo...@debian.org (2008-07-15):
 Package: user-setup-udeb
 Severity: wishlist
 
 Hi
 
 Would be nice if there is an easy way to skip creation of an user
 account but still do the rest of the task user-setup-udeb usually does.
 
 IE, when I entered the root password and then leave the username blank
 (login name), it currently displays a warning (fine), but then jumps
 back and tries to do it all again. It should please ask something like
 
 Maybe you want to go without a normal user account?
 
 and then skip the user creation. And if you only ask that in case no
 login name was entered it will only be displayed to very few users, so
 not distracting most people.
 
 Yes, one could enter some foo=bar during boot, to preseed some value and
 pass by that. But - sometimes its hard to do that (broken kvm over
 ip not letting you enter all characters is one reason), so it would be
 nice if it can be skipped during d-i run too.

I agree this is very desirable; confirming, and bumping severity.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Processed: Re: Bug#490899: user-setup-udeb: way to (easily) *not* create a user, but do the root password setup

2014-03-02 Thread Debian Bug Tracking System
Processing control commands:

 tag -1 confirmed
Bug #490899 [user-setup-udeb] user-setup-udeb: way to (easily) *not* create a 
user, but do the root password setup
Added tag(s) confirmed.
 severity -1 important
Bug #490899 [user-setup-udeb] user-setup-udeb: way to (easily) *not* create a 
user, but do the root password setup
Severity set to 'important' from 'wishlist'

-- 
490899: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490899
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.b490899.139377465024494.transcr...@bugs.debian.org



Bug#711093: cdrom: Default user is not added to group sudo

2014-03-02 Thread Cyril Brulebois
Control: tag -1 wontfix

Christian PERRIER bubu...@debian.org (2014-03-02):
 Quoting Cyril Brulebois (k...@debian.org):
  I don't think it was intended to give sudo access to the first user
  if a root password has been specified.
  
  Should we reconsider the current behaviour?
 
 IMHO, no.
 
 If this bug is asking for this, then it should be marked wontfix (or
 closed).

That's my sentiment as well, but I wanted at least a confirmation from
an old-timer (no offense!). Tagging accordingly for the time being.
Failing any objection, it can be closed in a while.

Thanks.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Processed: Re: Bug#711093: cdrom: Default user is not added to group sudo

2014-03-02 Thread Debian Bug Tracking System
Processing control commands:

 tag -1 wontfix
Bug #711093 [user-setup] cdrom: Default user is not added to group sudo
Added tag(s) wontfix.

-- 
711093: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711093
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.b711093.139377476024885.transcr...@bugs.debian.org



Bug#429549: marked as done (installation-report: option 'timestamp_timeout' in sudo config)

2014-03-02 Thread Debian Bug Tracking System
Your message dated Sun, 2 Mar 2014 16:44:36 +0100
with message-id 20140302154436.ga18...@mraw.org
and subject line Re: Bug#429549: installation-report: option 
'timestamp_timeout' in sudo config
has caused the Debian Bug report #429549,
regarding installation-report: option 'timestamp_timeout' in sudo config
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.)


-- 
429549: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=429549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports
Version: 2.29
Severity: normal


Current installer have 2 options:
1.set root password
2.don't set root password
In case 2. the configuration file sudo created with the next settings

user   ALL=(ALL) ALL

I suggest to add an option:

timestamp_timeout 0

This option will prevent getting root rights by malefactor who was
succeed in getting shell on user account (for example through
possible holes in brouser etc.)

In current case a simple script that periodically runs 'sudo command'
or more complicated script that follows for logs activity
/var/log/auth and runs on this log activity 'sudo command' can get
full control on a system where sudo configured by installer.

---End Message---
---BeginMessage---
Colin Watson cjwat...@debian.org (2007-06-18):
 On Mon, Jun 18, 2007 at 10:31:39PM +0400, Dmitry E. Oboukhov wrote:
  Current installer have 2 options:
  1.set root password
  2.don't set root password
  In case 2. the configuration file sudo created with the next settings
  
  user   ALL=(ALL) ALL
  
  I suggest to add an option:
  
  timestamp_timeout 0
  
  This option will prevent getting root rights by malefactor who was
  succeed in getting shell on user account (for example through
  possible holes in brouser etc.)
  
  In current case a simple script that periodically runs 'sudo
  command' or more complicated script that follows for logs activity
  /var/log/auth and runs on this log activity 'sudo command' can get
  full control on a system where sudo configured by installer.
 
 I don't think it's that simple. We tried that in Ubuntu three years
 ago, and the net effect was that everyone got fed up of being prompted
 for their password all the time and just ran 'sudo -s' to get a root
 shell.  We concluded that this was not a security win once we'd
 thought about it in more detail, and reverted it.

Based on Colin's feedback, I don't think we want to add this option, so
closing this bug report.

Mraw,
KiBi.


signature.asc
Description: Digital signature
---End Message---


Bug#332911: tagging 332911

2014-03-02 Thread Christian PERRIER
Quoting Cyril Brulebois (k...@debian.org):
 Christian Perrier bubu...@debian.org (2005-10-28):
  # Automatically generated email from bts, devscripts version 2.9.8
  tags 332911 wontfix
 
 Hello,
 
 what should we do about this bug report?

It's probably still valid as we continue to hardcode the groups to
which the first user is added.

However, implementing this would require checking whether, since 2005,
adduser --useful-groups option's list of groups has been updated
with useful groups added since then.



signature.asc
Description: Digital signature


Bug#408206: marked as done (warn/ask user about first accounts privs)

2014-03-02 Thread Debian Bug Tracking System
Your message dated Sun, 2 Mar 2014 16:54:12 +0100
with message-id 20140302155412.ga18...@mraw.org
and subject line Re: Bug#408206: warn/ask user about first accounts privs
has caused the Debian Bug report #408206,
regarding warn/ask user about first accounts privs
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.)


-- 
408206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=408206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
package: debian-installer
severity: wishlist

On Friday 12 January 2007 09:47, dann frazier wrote:
 I personally was surprised to see that the first user was added to
 additional groups and, had I known that, there are times I would've
 elected not to create that user at that time. (Most of my installs are
 servers, where these default groups don't make sense). I'm curious if
 I'm the only experienced admin who didn't notice and is surprised.
 I do agree that its somewhat minor - the first user is usually going
 to be a person w/ root privs, and the group privs should normally be
 pretty safe - except when bugs like #404927 pop up.

 Maybe after etch I'll propse a patch that adds an extra checkbox
 (default to yes) that asks users (in expert mode) if they want to be
 added to a set of typical desktop user groups.

Please do :)


regards,
Holger


pgpLBtGtpd8Gv.pgp
Description: PGP signature
---End Message---
---BeginMessage---
Holger Levsen deb...@layer-acht.org (2007-01-24):
 package: debian-installer
 severity: wishlist
 
 On Friday 12 January 2007 09:47, dann frazier wrote:
  I personally was surprised to see that the first user was added to
  additional groups and, had I known that, there are times I would've
  elected not to create that user at that time. (Most of my installs are
  servers, where these default groups don't make sense). I'm curious if
  I'm the only experienced admin who didn't notice and is surprised.
  I do agree that its somewhat minor - the first user is usually going
  to be a person w/ root privs, and the group privs should normally be
  pretty safe - except when bugs like #404927 pop up.

I don't think we need to work around those bugs in d-i.

  Maybe after etch I'll propse a patch that adds an extra checkbox
  (default to yes) that asks users (in expert mode) if they want to be
  added to a set of typical desktop user groups.
 
 Please do :)

We're way after etch, so closing for the time being as there's no patch
around.

Mraw,
KiBi.


signature.asc
Description: Digital signature
---End Message---


Bug#398655: installation-report: optionally create more than one user during installation

2014-03-02 Thread Cyril Brulebois
Control: tag -1 wontfix

Tshepang Lekhonkhobe tshep...@gmail.com (2006-11-15):
 On 11/15/06, Martin Wuertele mar...@wuertele.net wrote:
 Hi Frans!
 
 * Frans Pop elen...@planet.nl [2006-11-15 05:02]:
 
  On Tuesday 14 November 2006 21:26, Martin Wuertele wrote:
   It would be nice to be able to add more than one user during
   installation.
 
  Could you give a somewhat stronger rationale than just it would be nice?
  What use case do you have in mind where adding extra users after the
  reboot into the installed system is not sufficient?
 
 I occasionally set up a linux box for relatives or friends where you
 usually have between 2 and 5 users and while they're used to be able to
 define several users when eg installing XP this is not yet possible with
 d-i and when I set up the users cmd-line it looks to them a bit scary.
 It's mere for the show effect see you can define the users during
 installtion just like with XP.
 
 yours Martin
 
 I suppose those users only used GUI on XP, and in that case GNOME and
 KDE sure have facilities for that. It would still be a nice feature
 though.

Yeah, having those play with some GUI tools should be enough. Not sure
that's feasible within Xfce though, so just tagging this bug report with
wontfix for now, and not closing just yet.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Processed: Re: Bug#398655: installation-report: optionally create more than one user during installation

2014-03-02 Thread Debian Bug Tracking System
Processing control commands:

 tag -1 wontfix
Bug #398655 [user-setup] installation-report: optionally create more than one 
user during installation
Added tag(s) wontfix.

-- 
398655: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=398655
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.b398655.139377586631449.transcr...@bugs.debian.org



Bug#429549: installation-report: option 'timestamp_timeout' in sudo config

2014-03-02 Thread Ian Campbell
On Sun, 2014-03-02 at 16:44 +0100, Cyril Brulebois wrote:
 Colin Watson cjwat...@debian.org (2007-06-18):
  On Mon, Jun 18, 2007 at 10:31:39PM +0400, Dmitry E. Oboukhov wrote:
   Current installer have 2 options:
   1.set root password
   2.don't set root password
   In case 2. the configuration file sudo created with the next settings
   
   user   ALL=(ALL) ALL
   
   I suggest to add an option:
   
   timestamp_timeout 0
   
   This option will prevent getting root rights by malefactor who was
   succeed in getting shell on user account (for example through
   possible holes in brouser etc.)
   
   In current case a simple script that periodically runs 'sudo
   command' or more complicated script that follows for logs activity
   /var/log/auth and runs on this log activity 'sudo command' can get
   full control on a system where sudo configured by installer.
  
  I don't think it's that simple. We tried that in Ubuntu three years
  ago, and the net effect was that everyone got fed up of being prompted
  for their password all the time and just ran 'sudo -s' to get a root
  shell.  We concluded that this was not a security win once we'd
  thought about it in more detail, and reverted it.
 
 Based on Colin's feedback, I don't think we want to add this option, so
 closing this bug report.

Also, doesn't modern sudo tie the password cache to the current (p|t)ty,
in other words you can't run an attack loop in one session and hope to
use the password cached from another.

Ian.


-- 
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/1393775801.19684.46.ca...@hastur.hellion.org.uk



Bug#612727: marked as done (env-preseed: mirror/http/proxy= in kernel parameters via PXE doesn't work)

2014-03-02 Thread Debian Bug Tracking System
Your message dated Sun, 2 Mar 2014 17:49:10 +0100
with message-id 20140302164910.ga20...@type.youpi.perso.aquilenet.fr
and subject line Re: Bug#612727: env-preseed: mirror/http/proxy= in kernel 
parameters via PXE doesn't work
has caused the Debian Bug report #612727,
regarding env-preseed: mirror/http/proxy= in kernel parameters via PXE doesn't 
work
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.)


-- 
612727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612727
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: env-preseed
Version: 1.48
Severity: normal

Hello,

Giving mirror/http/proxy= on the PXE kernel command line (i.e. giving an
empty value) doesn't seem to be feeding debconf: the question is still
getting asked. We also tried mirror/http/proxy= with the same result.

More precisely, the pxe configuration is

APPEND ramdisk_size=14984 locale=fr_FR.UTF-8 
console-keymaps-at/keymap=fr-latin9 console-setup/layoutcode=fr 
netcfg/get_hostname=inrescuemode netcfg/get_domain=ens-lyon.fr 
mirror/country=fr mirror/http/hostname=ftp.fr.debian.org 
mirror/http/directory=debian vga=normal 
initrd=debian/squeeze/i386/debian-installer/i386/initrd.gz rescue/enable=true --

Samuel

-- System Information:
Debian Release: 6.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.37 (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/bash

-- 
Samuel Thibault samuel.thiba...@fnac.net
   La  fonction  memfrob() crypte les n premiers octets de la
   zone de mémoire  s  en  effectuant  un  OU-exclusif  entre
   chaque  octet  et le nombre 42.
(extrait de la page de man de memfrob -- Manuel du programmeur Linux)


---End Message---
---BeginMessage---
Version: 1.48

Hello,

Cyril Brulebois, le Sun 02 Mar 2014 04:28:17 +0100, a écrit :
 Samuel Thibault sthiba...@debian.org (2011-02-10):
  Giving mirror/http/proxy= on the PXE kernel command line (i.e. giving an
  empty value) doesn't seem to be feeding debconf: the question is still
  getting asked. We also tried mirror/http/proxy= with the same result.
  
  More precisely, the pxe configuration is
  
  APPEND ramdisk_size=14984 locale=fr_FR.UTF-8 
  console-keymaps-at/keymap=fr-latin9 console-setup/layoutcode=fr 
  netcfg/get_hostname=inrescuemode netcfg/get_domain=ens-lyon.fr 
  mirror/country=fr mirror/http/hostname=ftp.fr.debian.org 
  mirror/http/directory=debian vga=normal 
  initrd=debian/squeeze/i386/debian-installer/i386/initrd.gz 
  rescue/enable=true --
 
 I don't have any PXE test setup currently,

PXE can easily be tested by using e.g.

wget -r --no-parent 
http://ftp.debian.org/debian/dists/wheezy/main/installer-i386/current/images/netboot/

kvm -boot n -net 
user,tftp=ftp.fr.debian.org/debian/dists/wheezy/main/installer-i386/current/images/netboot/,bootfile=/pxelinux.0
 -net nic

It is then a matter of updating
debian-installer/i386/boot-screens/txt.cfg

 but a few tests using wheezy
 or current images seem to show the behaviour is correct when adding this
 to the syslinux prompt. Is the issue you mentioned PXE-specific?

I can't reproduce the issue either, even with squeeze, thus closing it
with the squeeze version. Just FTR, I have attached the txt.cfg I have
used to test it.

Thanks for the ping,
Samuel
default install
label install
menu label ^Install
menu default
kernel debian-installer/i386/linux
append initrd=debian-installer/i386/initrd.gz ramdisk_size=14984 
locale=fr_FR.UTF-8 keymap=fr(latin9) console-setup/layoutcode=fr 
netcfg/get_hostname=inrescuemode netcfg/get_domain=ens-lyon.fr 
mirror/country=fr mirror/http/hostname=ftp.fr.debian.org 
mirror/http/directory=/debian mirror/http/proxy= vga=normal rescue/enable=true 
--
---End Message---


Re: Bug#740073: Info received (Bug#740073: netinst hangs on scanning CD-ROM [was: Message with no Package: tag cannot be processed! (Installation report)])

2014-03-02 Thread Blues Bass

Still doesn't work.


If only we have a way to install with the older netinstall images 
(before 18/02), but they all hang just before Grub install (Bug#739682).


I can understand bugs in new releases of netinstall, mas how come images 
that worked suddenly crash?!


Is there a way we can help to solve these 2 bugs? At least can someone 
tell us what is causing them.



Thanks

Blau Araujo


Em 01-03-2014 20:21, Siarhei Akhramenia escreveu:

Hello,

Do you know that testing network installation image still doesn't work?
It's NOT POSSIBLE to install 'jessie' anyhow.
I don't believe that there is no man working on this problem... It's
just not possible. Not in our universe.

Thank you.

P.S. We, users, believe in you, Developers. And we believe in Debian.
Thank you once again.



--
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/5313627c.2080...@gmail.com



Bug#740073: (no subject)

2014-03-02 Thread Blues Bass

Still doesn't work.


If only we have a way to install with the older netinstall images 
(before 18/02), but they all hang just before Grub install (Bug#739682).


I can understand bugs in new releases of netinstall, but how come images 
that worked suddenly crash?!


Is there a way we can help to solve these 2 bugs? At least can someone 
tell us what is causing them.



Thanks

Blau Araujo


--
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/531364f3.9060...@gmail.com



Re: d-i-n-i: #695500 is apparently a grub-mkimage (or debian-installer) bug

2014-03-02 Thread Cyril Brulebois
Control: severity -1 important

Steven Chamberlain ste...@pyro.eu.org (2014-02-04):
 tags 695500 + moreinfo
 block 695500 by 711799
 user debian-...@lists.debian.org
 usertags 695500 kfreebsd

Not going to keep an RC bug tagged moreinfo for a month at serious
severity, so downgrading.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Processed: Re: d-i-n-i: #695500 is apparently a grub-mkimage (or debian-installer) bug

2014-03-02 Thread Debian Bug Tracking System
Processing control commands:

 severity -1 important
Bug #695500 [src:debian-installer,grub-common] 
debian-installer-7.0-netboot-kfreebsd-amd64: does not boot from pxe
Severity set to 'important' from 'serious'

-- 
695500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695500
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.b695500.1393792145.transcr...@bugs.debian.org



Processed: Re: Bug#700026: maybe should have a Build-Depends: syslinux

2014-03-02 Thread Debian Bug Tracking System
Processing control commands:

 retitle -1 maybe should have a Built-Using: syslinux
Bug #700026 [debian-installer] maybe should have a Build-Depends: syslinux
Changed Bug title to 'maybe should have a Built-Using: syslinux' from 'maybe 
should have a Build-Depends: syslinux'

-- 
700026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700026
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.b700026.13937931108961.transcr...@bugs.debian.org



Bug#700026: maybe should have a Build-Depends: syslinux

2014-03-02 Thread Cyril Brulebois
Control: retitle -1 maybe should have a Built-Using: syslinux

Ansgar Burchardt ans...@debian.org (2013-02-07):
 Hi,
 
 in [1] it was mentioned that d-i embeds syslinux on some
 architectures, but the current version does not include
 syslinux in its Build-Using field.

Built-Using. ;)

Adjusting subject accordingly, since it's already in Build-Depends.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Bug#720162: marked as done (debian-installer: Installed system is unbootable due to missing LVM support)

2014-03-02 Thread Debian Bug Tracking System
Your message dated Sun, 2 Mar 2014 21:47:50 +0100
with message-id 20140302204750.ga21...@mraw.org
and subject line Re: Bug#720162: debian-installer: Installed system is 
unbootable due to missing LVM support
has caused the Debian Bug report #720162,
regarding debian-installer: Installed system is unbootable due to missing LVM 
support
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.)


-- 
720162: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: debian-installer
Version: 20130613
Severity: important
Tags: d-i

Dear Maintainer,

I have installed testing from an ISO image I downloaded about 3 or 4
days ago. During installation, I decided for manual partitioning. I
set up LVM volumes in an encrypted LVM group.

After the installation has finished 'successfully', the installed
system is unbootable. After a short timeout, it reported Gave up
waiting for root device.

I have figured out that, although I prepared LVM groups/volumes in the
installer, the installed system was missing the lvm2 package. After
booting a rescue system I was able to install lvm2 on the new system
and after that it booted fine.

Thanks,
mel

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

Kernel: Linux 3.10-7.dmz.1-liquorix-amd64 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
---End Message---
---BeginMessage---
M. Schulte mfug...@gmail.com (2013-09-10):
 I'm really sorry for not writing back for so long -- had been quite
 occupied.

No worries, we're all busy. :)

 Also, the problem was that right after the installation I had documented
 in the bug report, I did a fresh reinstall of Debian stable in order to
 verify that the same partitioning scheme yields a working system (in
 order to exclude my input being the problem). Hence I couldn't send you
 the install log. It turned out that the Debian stable installation
 worked fine (i.e. LVM had been installed).

That's very nice to hear.

 Then I tried to reproduce the bug in the testing installer again using
 qemu. But LVM2 got installed in qemu! I don't know what the reason for
 this might be. Maybe it had to do with the fact that the virtualized hd
 was empty in the beginning and during partinioning I only setup
 partitions for Debian while the non-virtualized harddisk in my notebook
 contained several NTFS partitions next to which I had installed Debian.
 
 But so far I didn't do any further tests in order to reproduce the bug. :-/

No worries, I'll just close this bug report for now; feel free to reopen
this bug report or report a new one in case you experience any issues in
a later installation.

Mraw,
KiBi.


signature.asc
Description: Digital signature
---End Message---


Bug#720719: debian-installer: FTBFS with make 3.82 from experimental: recipe commences before first target

2014-03-02 Thread Cyril Brulebois
Control: tag -1 patch pending

Daniel Schepler dschep...@gmail.com (2013-08-24):
 make[1]: Entering directory `/tmp/buildd/debian-installer-20130613/build'
 Makefile:560: *** recipe commences before first target.  Stop.
 make[1]: Leaving directory `/tmp/buildd/debian-installer-20130613/build'
 make: *** [clean] Error 2
 dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2

Should be addressed by the commit I've just pushed:
| commit 568e02369157dc5fbaf9f0be482bfea6a39fd04a
| Author: Cyril Brulebois k...@debian.org
| Date:   Sun Mar 2 22:04:38 2014 +0100
| 
| build/Makefile: Move the drop_lang definition to the top (Closes: 
#720719).
| 
| That deals with incompatible changes in make 3.82 leading to the
| following error: “recipe commences before first target”.

I haven't tried a full build though.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Processed: Re: Bug#720719: debian-installer: FTBFS with make 3.82 from experimental: recipe commences before first target

2014-03-02 Thread Debian Bug Tracking System
Processing control commands:

 tag -1 patch pending
Bug #720719 [src:debian-installer] debian-installer: FTBFS with make 3.82 from 
experimental: recipe commences before first target
Added tag(s) pending and patch.

-- 
720719: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720719
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.b720719.139379446517831.transcr...@bugs.debian.org



Processed: severity of 530616 is wishlist

2014-03-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 severity 530616 wishlist
Bug #530616 [debian-installer] debian-installer: netboot tarball needs a 
symlink to enable PXE booting from multiple installers.
Severity set to 'wishlist' from 'normal'
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
530616: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530616
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.139379514421368.transcr...@bugs.debian.org



Processed: Re: Bug#642179: debian-installer: Installs on drives larger than 2.19TB fails with older bios

2014-03-02 Thread Debian Bug Tracking System
Processing control commands:

 tag -1 - d-i squeeze
Bug #642179 [debian-installer] debian-installer: Installs on drives larger than 
2.19TB fails with older bios
Removed tag(s) squeeze and d-i.

-- 
642179: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642179
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.b642179.139379543023280.transcr...@bugs.debian.org



Bug#619236: debian PS3 installation kboot.conf needed

2014-03-02 Thread Cyril Brulebois
Adding -powerpc to the loop. Initial bug report:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619236

Geoff Levand ge...@infradead.org (2013-09-04):
 We still have a need for the kboot-utils package in debian.  Recent
 daily builds of D-I work fine on PS3, but the installed system still
 cannot boot due to lack of a kboot.conf file for the PS3's native
 bootloader (petitboot).

Is anyone working on getting better PS3 support?

Mraw,
KiBi.


signature.asc
Description: Digital signature


Bug#642179: debian-installer: Installs on drives larger than 2.19TB fails with older bios

2014-03-02 Thread Cyril Brulebois
Control: tag -1 - d-i squeeze

Hi Karl,

Karl Schmidt k...@xtronics.com (2011-09-22):
 This is failing with the current squeeze installer that uses grub2.
 
 What I don't know is if this is possibly a BIOS issue - my
 understanding is that Debian takes over and uses its own driver.
 
 This is on a Tyan S7002 which uses:
 
 # lspci |grep SATA
 00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI 
 Controller
 
 for the SATA controller.
 
 I'm attempting a workaround - I'm installing the main system on a
 40GB raided pair of SSD and will have /homes on large ( 2.18TB )
 drives. I will partition the large drives with gparted and use GPT.

are you experiencing similar issues with wheezy installation images?

Mraw,
KiBi.


signature.asc
Description: Digital signature


Bug#664486: marked as done (Adding New Script Variants on Debian Installer)

2014-03-02 Thread Debian Bug Tracking System
Your message dated Sun, 2 Mar 2014 22:25:47 +0100
with message-id 20140302212547.ga25...@mraw.org
and subject line Re: Bug#664420: About offering Latin-based Uyghur in Debian 
Installer
has caused the Debian Bug report #664420,
regarding Adding New Script Variants on Debian Installer
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.)


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

On Sun, Mar 18, 2012 at 1:38 AM, Christian PERRIER bubu...@debian.orgwrote:

 Quoting Eagle Burkut (eagle.bur...@gmail.com):
  Dear Debian Developers/Maintainers,
 
  How can we have new language/script on debian installer? Is there any
  requirement? If there is, what is the requirement?
 
  Ubuntu uses Debian Installer and it has Arabic based Uyghur. We need
 Latin
  based Uyghur too.


 We need to go though the whole New Language Process as we did for ug
 with Gheyret Kenji

 Please notice however, that a new translation adds an extra size to
 the installer so we need some good rock solid rationale for adding a
 variant of an existing language.


While we have finished translating more than 95% translation string in
Ubuntu (that is 350,000 sentences!), due to lots of bugs and inabilities in
various libraries/packages/fonts, we got a localized Ubuntu with lots of
bugs/errors. In summary, the original Ubuntu has problems, bugs in every
aspect of

(1) Right-to-Left support
(2) Bi-Directional support
(3) Font selection
(4) Proper fonts

Thus, even with hundreds of translator spending couple of years of hard
work, we still ended up not so good localized Ubuntu.

If we utilize Latin based Uyghur, all of the above problems will disappear
immediately. That is why we are thinking about adding Latin based Uyghur to
Ubuntu, including the Debian Installer.

Also, variants have not been proven as working properly as of now : we
 for instance have a sr@latin variant for Serbian that is not
 activated yet because supporting it requires changes to localechooser
 that nobody did until now.

 (the main problem comes from the fact that localechooser assumes that
 the chosen language code and the chosen country can be concatenated :
 fr for language then FR as country, give fr_FR.while this
 doesn't work for sr@latin combined with a country code such as RS
 as the locale should be sr_RS@latin, not sr@latin_RS)


As Uyghur is written in modified Arabic-Persian in China, in Cyrillic in
Kazakhstan and central Asia, and in Latin elsewhere globally, we previously
had ug_CN locale in Arabic, and we have just developed ug_US locale in
Latin and submitted it to upstream glibc library, and more, we are planning
to develop ug_KZ locale in Cyrillic in near future.
---End Message---
---BeginMessage---
Christian PERRIER bubu...@debian.org (2013-08-25):
 Sorry for missing this bug report when you sent it.
 
 You request there a way to have a Debian Installer translation in
 Uyghur with Latin script.
 
 I have no strong opinion about that, but that would need going through
 the Debian Installer New Language Process described in the D-I i18n
 documentation:
 
 http://d-i.alioth.debian.org/doc/i18n/
 
 I would also suggest coordination with people currently working on the
 Arabic-script-based Uyghur translation, namely Gheyret Tohti,
 Abduqadir Abliz and the Uyghur Computer Science Association.
 
 I woyld of course welcome such translation, assuiming it has some real
 use (in short that latin-based Uyghur is widely-enough used to warrant
 such work).
 
 In the meantime, I consider closing this bug report, as adding a
 language in D-I cannot easily be handled through a bug report, indeed.

Let's do that then. Thanks for your explanations.

 The New Language Process is a multi-step process that usually includes
 the debian-i18n mailing list, which is better suited for this(but you
 obviously couldn't know...and sorry again for not noticing your bug
 report when you sent it 1.5 years ago).
 
 Thanks to Holger Levsen for digging this bug report out of the pile of
 dust accumulated over D-I bug reports.

Mraw,
KiBi.


signature.asc
Description: Digital signature
---End Message---


Bug#664420: marked as done (Adding New Script Variants on Debian Installer)

2014-03-02 Thread Debian Bug Tracking System
Your message dated Sun, 2 Mar 2014 22:25:47 +0100
with message-id 20140302212547.ga25...@mraw.org
and subject line Re: Bug#664420: About offering Latin-based Uyghur in Debian 
Installer
has caused the Debian Bug report #664420,
regarding Adding New Script Variants on Debian Installer
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.)


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

On Sat, Mar 17, 2012 at 1:05 PM, Eagle Burkut eagle.bur...@gmail.comwrote:

 Dear Debian Developers/Maintainers,

 How can we have new language/script on debian installer? Is there any
 requirement? If there is, what is the requirement?

 Ubuntu uses Debian Installer and it has Arabic based Uyghur. We need Latin
 based Uyghur too.

 Thanks.

 Ubuntu Uyghur Translation Group

 PS: For information about Uyghur language and script, please refer to the
 following Wikipedia articles:
 http://en.wikipedia.org/wiki/Uyghur_language
 http://en.wikipedia.org/wiki/Uyghur_alphabet

---End Message---
---BeginMessage---
Christian PERRIER bubu...@debian.org (2013-08-25):
 Sorry for missing this bug report when you sent it.
 
 You request there a way to have a Debian Installer translation in
 Uyghur with Latin script.
 
 I have no strong opinion about that, but that would need going through
 the Debian Installer New Language Process described in the D-I i18n
 documentation:
 
 http://d-i.alioth.debian.org/doc/i18n/
 
 I would also suggest coordination with people currently working on the
 Arabic-script-based Uyghur translation, namely Gheyret Tohti,
 Abduqadir Abliz and the Uyghur Computer Science Association.
 
 I woyld of course welcome such translation, assuiming it has some real
 use (in short that latin-based Uyghur is widely-enough used to warrant
 such work).
 
 In the meantime, I consider closing this bug report, as adding a
 language in D-I cannot easily be handled through a bug report, indeed.

Let's do that then. Thanks for your explanations.

 The New Language Process is a multi-step process that usually includes
 the debian-i18n mailing list, which is better suited for this(but you
 obviously couldn't know...and sorry again for not noticing your bug
 report when you sent it 1.5 years ago).
 
 Thanks to Holger Levsen for digging this bug report out of the pile of
 dust accumulated over D-I bug reports.

Mraw,
KiBi.


signature.asc
Description: Digital signature
---End Message---


Bug#717298: debian-installer: After installing xfce environment, don't see xfce

2014-03-02 Thread Cyril Brulebois
Control: notfound -1 Jessie

Peter Chubb peter.ch...@nicta.com.au (2013-07-19):
 Package: debian-installer
 Version: Jessie
 Severity: normal

Jessie isn't a known version of debian-installer in the archive, so
removing it from the found list for this bug report.

 I did a clean install using the netboot.tar.gz +pxe method, 
 selecting the XFCE desktop environment.  But when the machine booted, 
 it presented a Gnome desktop environment.  I expected to see XFCE.
 
 
 XFCE is present, and I was able to modify /etc/lighdm.conf to make it 
 be the default.  However, I expected it to be this way out of the box, 
 and for gnome not to be installed at all.

It would probably be nice to check what happens with the next d-i
upload (which will happen after eglibc 2.18 migrates to testing);
the default desktop change might have changed a few things…

Thanks for your report.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Processed: Re: Bug#717298: debian-installer: After installing xfce environment, don't see xfce

2014-03-02 Thread Debian Bug Tracking System
Processing control commands:

 notfound -1 Jessie
Bug #717298 [debian-installer] debian-installer: After installing xfce 
environment, don't see xfce
There is no source info for the package 'debian-installer' at version 'Jessie' 
with architecture ''
Unable to make a source version for version 'Jessie'
No longer marked as found in versions Jessie.

-- 
717298: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717298
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.b717298.139379582827162.transcr...@bugs.debian.org



Processed: Re: Bug#716977: Installer does not fill /etc/crypttab

2014-03-02 Thread Debian Bug Tracking System
Processing control commands:

 unmerge -1
Bug #716977 [debian-installer] Installer does not fill /etc/crypttab
Bug #716978 [debian-installer] Installer does not fill /etc/crypttab
Disconnected #716977 from all other report(s).
 notfound -1 stable
Bug #716977 [debian-installer] Installer does not fill /etc/crypttab
There is no source info for the package 'debian-installer' at version 'stable' 
with architecture ''
Unable to make a source version for version 'stable'
No longer marked as found in versions stable.
 notfound -1 testing
Bug #716977 [debian-installer] Installer does not fill /etc/crypttab
There is no source info for the package 'debian-installer' at version 'testing' 
with architecture ''
Unable to make a source version for version 'testing'
No longer marked as found in versions testing.

-- 
716977: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716977
716978: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716978
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.b716977.139379627030497.transcr...@bugs.debian.org



Bug#716977: Installer does not fill /etc/crypttab

2014-03-02 Thread Cyril Brulebois
Control: unmerge -1
Control: notfound -1 stable
Control: notfound -1 testing

It seems like #716977 and #716978 could be two different issues, so
unmerging them for now. Also, stable and testing are no known d-i
versions in the archive so removing them from the found list for
this bug report.

Guillaume BROGI guillaume.br...@supelec.fr (2013-07-15):
 When partitioning with a RAID0 and a lvm volume on top, the initramfs
 does not include the LVM module and, so, cannot mount /.
 
 Fix: include the LVM module inside the initramfs

Out of curiosity, did you select MODULES=dep instead of the default
MODULES=most? See the following mail for more details:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716978#19

 Additional info: This was done on a laptop with 4 ssd.
 Each ssd had a 300MB partition, with the one on sda used for /boot.
 The rest of the space on each disk is used for the raid array.
 The encrypted device is created inside /dev/md0.
 A LVM volume is created inside /dev/md0.
 There are 2 partitions inside the volume, one for /, one for the swap.
 
 The laptop is a work laptop, so I cannot try another install. I will
 however try to reproduce the issue in a virtual machine using qemu.
 If there is anything else I can do, please tell me.
 If this is the wrong mailing list, I am sorry, and could you please
 tell me which one is the right one.

No worries, you reported your issue in the correct place. Sorry it took
so long to get back to you. I'll see whether I can reproduce this in a
later bug triaging session.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Re: Bug#717791: debian-installer: virtualbox guest additions not installed correctly

2014-03-02 Thread Cyril Brulebois
(Adding original submitter to the loop.)

Ben Hutchings b...@decadent.org.uk (2013-11-16):
 On Fri, 2013-11-15 at 21:50 +0400, Алексей Шилин wrote:
  I confirm this.
  
  Looks like the reason for having wrong kernel headers installed is the 
  following dependencies chain:
* virtualbox-ose-guest-x11 depends on virtualbox-guest-x11;
* virtualbox-guest-x11 depends on virtualbox-guest-utils;
* virtualbox-guest-utils recommends virtualbox-guest-dkms;
* virtualbox-guest-dkms depends on dkms;
* dkms recommends linux-headers-686-pae | linux-headers-amd64 | 
  linux-headers-generic | linux-headers.
  
  VirtualBox doesn't enable PAE/NX by default,
 
 That seems like a bug in VirtualBox.
 
  so the installer chooses the 486 kernel for installation; however,
  when requesting virtualbox-ose-guest-x11 installation, no kernel
  headers package is explicitly requested by the installer, so APT
  chooses the default one, which is the first one in the dependencies
  list, namely linux-headers-686-pae.
  
  I guess, this can be fixed by explicitly requesting the kernel
  headers package, matching the kernel installed.
 
 Right.  Recommendation of linux-headers packages is never going to
 work for all cases.

I'm not sure how to deal with this. Probably by reassigning this bug
report to discover (and/or discover-data), so that it installs the
relevant linux-headers package when it detects virtualbox-ose-guest-x11
is needed; to achieve this, maybe a specific package (something like
linux-headers-@@whatever@@) could be specified together with that one,
so that this mechanism can be reused for non-virtualbox, yet needing
linux-headers-*, packages.

Cc-ing discover maintainers for advice.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Bug#734690: marked as done (Language-chooser: C is not a language)

2014-03-02 Thread Debian Bug Tracking System
Your message dated Sun, 2 Mar 2014 22:59:39 +0100
with message-id 20140302215939.gd3...@mraw.org
and subject line Re: Bug#734690: Language-chooser: C is not a language
has caused the Debian Bug report #734690,
regarding Language-chooser: C is not a language
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.)


-- 
734690: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734690
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: debian-installer
Severity: normal

It was just pointed out in a LCA2014 presentation that it's a bit
silly to ask the user to choose the language between C and
English. Maybe this could be moved to a lower priority or
rephrased?

Sorry I did not verify this or check. The network here is slow and
I just wanted to make sure that this isn't forgotten.

-- 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.11-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
 .''`.   martin f. krafft madduck@d.o  Related projects:
: :'  :  proud Debian developer   http://debiansystem.info
`. `'`   http://people.debian.org/~madduckhttp://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
---End Message---
---BeginMessage---
martin f krafft madd...@debian.org (2014-01-09):
 Package: debian-installer
 Severity: normal
 
 It was just pointed out in a LCA2014 presentation that it's a bit
 silly to ask the user to choose the language between C and
 English. Maybe this could be moved to a lower priority or
 rephrased?
 
 Sorry I did not verify this or check. The network here is slow and
 I just wanted to make sure that this isn't forgotten.

It's a little sad not to know what the bug report was really about. If
that's the same as #384067, then the same answers (Christian's and mine)
apply:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384067#19

Closing this bug report as well.

Mraw,
KiBi.


signature.asc
Description: Digital signature
---End Message---


Bug#734690: Language-chooser: C is not a language

2014-03-02 Thread Cyril Brulebois
martin f krafft madd...@debian.org (2014-03-02):
 also sprach Cyril Brulebois k...@debian.org [2014-03-02 22:59 +0100]:
  It's a little sad not to know what the bug report was really about.
 
 It was really about C not being a language.
 
  If that's the same as #384067, then the same answers (Christian's
  and mine) apply:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384067#19
 
 If the user is presented with
 
   C — no localization
 
 then that'd fine. However, that was not the case, it just said C,
 and I think that's asking a bit too much. Consider replacing that
 with None or so…

Err, please clarify what “that was not the case, it just said C”
means. I'm attaching a screenshot of the current state. (And Christian
mentioned that was the case, so it's not clear to me what you're trying
to say.)

Mraw,
KiBi.
attachment: c.png

signature.asc
Description: Digital signature


Bug#740271: d-i fails to purge LVM despite preseeding

2014-03-02 Thread Cyril Brulebois
martin f krafft madd...@debian.org (2014-02-27):
 Package: debian-installer
 Version: 20130613+deb7u1+b2
 Severity: normal
 
 Despite
 
   d-i partman-auto/purge_lvm_from_device boolean true
   d-i partman-lvm/device_remove_lvm boolean true
   d-i partman-lvm/confirm boolean true
   d-i partman-lvm/confirm_nooverwrite boolean true
 
 d-i fails to install a machine when libvirt passes it a storage
 volume that has previously been used as PV by another host.
 
 What happens (in my case) is that partman creates a new GPT, but
 often that will be exactly the same as the one used by the previous
 host using the volume. Therefore, /dev/vda3 will be a valid LVM PV,
 meaning that LVM will find the previous VG.
 
 Now, depending on whether the hostname is (a) the same, or (b)
 different, d-i will fail to install claiming
 
   (a) a VG with the same name is already present;
   (b) the PV is already in use by another VG.

Logs would be helpful.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Bug#696418: missing Built-Using on bf-utf (for bf-utf-source)

2014-03-02 Thread Cyril Brulebois
Control: tag -1 patch pending

Ansgar Burchardt ans...@debian.org (2012-12-20):
 Package: src:debian-installer
 Version: 20121114
 Severity: serious
 
 debian-installer uses bf-utf-source, but misses a Built-Using field for this
 package.
 
 Since dpkg (= 1.16.2), dpkg-query has an easier way to extract the required
 information for installed packages:
 
dpkg-query -f '${source:Package} (= ${source:Version}), ' -W bf-utf-source
 
 should give the missing value.

I'm tempted to push the attached patch (with the not-existing part
stripped of course, that was just for demo/test purposes) to solve
both issues.

Mraw,
KiBi.
From a8b8566c4f71e894879e33996e5a29f64c6c44fd Mon Sep 17 00:00:00 2001
From: Cyril Brulebois k...@debian.org
Date: Mon, 3 Mar 2014 00:00:46 +0100
Subject: [PATCH] Extend write-built-using to also generate the
 ${extra:Built-Using} substvar.

This makes it possible to track packages mentioned in the EXTRA_PACKAGES
variable (currently set to bf-utf-source syslinux). Thanks to Ansgar
Burchardt for the reports (Closes: #696418, #700026).

Note: Unknown packages are ignored, so architecture-specific packages
shouldn't be a problem.
---
 build/util/write-built-using | 7 +++
 debian/changelog | 4 
 debian/control   | 2 +-
 3 files changed, 12 insertions(+), 1 deletion(-)

diff --git a/build/util/write-built-using b/build/util/write-built-using
index 97beb13..c9c9c73 100755
--- a/build/util/write-built-using
+++ b/build/util/write-built-using
@@ -6,3 +6,10 @@ cat build/tmp/*/built-using.txt \
 | tr \n , \
 | sed 's/,/, /g;s/, $//g'  debian/debian-installer.substvars
 echo  debian/debian-installer.substvars
+
+EXTRA_PACKAGES=bf-utf-source syslinux not-existing
+echo -n extra:Built-Using=  debian/debian-installer.substvars
+for package in $EXTRA_PACKAGES; do
+  dpkg-query -f '${source:Package} (= ${source:Version}), ' -W $package 2/dev/null
+done  debian/debian-installer.substvars
+echo  debian/debian-installer.substvars
diff --git a/debian/changelog b/debian/changelog
index 83c3382..1a0e3b7 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -20,6 +20,10 @@ debian-installer (20140210) UNRELEASED; urgency=medium
   * build/Makefile: Move the drop_lang definition to the top of the file to
 deal with incompatible changes in make 3.82 leading to the following
 error: “recipe commences before first target” (Closes: #720719).
+  * Extend write-built-using to also generate the ${extra:Built-Using}
+substvar, making it possible to track packages mentioned in the
+EXTRA_PACKAGES variable (currently set to bf-utf-source syslinux).
+Thanks to Ansgar Burchardt for the reports (Closes: #696418, #700026).
 
   [ Robert Millan ]
   * Enable kfreebsd-10 builds.
diff --git a/debian/control b/debian/control
index 61f8311..3d21dee 100644
--- a/debian/control
+++ b/debian/control
@@ -164,7 +164,7 @@ Build-Depends:
 
 Package: debian-installer
 Architecture: any
-Built-Using: ${initrd:Built-Using}
+Built-Using: ${initrd:Built-Using}, ${extra:Built-Using}
 Depends: ${misc:Depends}
 Description: Debian installer
  This package currently only contains some documentation for the Debian
-- 
1.9.0



signature.asc
Description: Digital signature


Processed: Re: Bug#696418: missing Built-Using on bf-utf (for bf-utf-source)

2014-03-02 Thread Debian Bug Tracking System
Processing control commands:

 tag -1 patch pending
Bug #700026 [debian-installer] maybe should have a Built-Using: syslinux
Added tag(s) pending and patch.

-- 
700026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700026
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.b700026.139380143629582.transcr...@bugs.debian.org



Processed: Re: Bug#696418: missing Built-Using on bf-utf (for bf-utf-source)

2014-03-02 Thread Debian Bug Tracking System
Processing control commands:

 tag -1 patch pending
Bug #696418 [src:debian-installer] missing Built-Using on bf-utf (for 
bf-utf-source)
Added tag(s) pending and patch.

-- 
696418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696418
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.b696418.139380143629573.transcr...@bugs.debian.org



Bug#704162: Wrong sum for GTK installer initrd.gz inside netboot.tar.gz

2014-03-02 Thread Cyril Brulebois
Control: tag -1 patch

Benjamin Cama benjamin.c...@telecom-bretagne.eu (2013-03-28):
 I don't really know where to file that; please reassign if I'm wrong.

No worries; it finally landed in the debian-installer territory, where
it belongs.

 I noticed, after unpacking it and checking for the sums, hoping that
 they will be the same as if I downloaded all the files individually,
 that they all validate except one: the initrd.gz for this installer. (I
 checked the sum of the .tar.gz itself, and it's OK).
 
 The sums are, e.g., here:
 http://debian.univ-nantes.fr/debian/dists/wheezy/main/installer-amd64/current/images/SHA256SUMS
 
 When getting directly the initrd.gz from
 http://debian.univ-nantes.fr/debian/dists/wheezy/main/installer-amd64/current/images/netboot/gtk/debian-installer/amd64/initrd.gz
 I correctly get
 f8971317915ed2ce8358b24ca88ea95c75ebe97a1e0a95f60c7977da368b3352
 But when extracting it from the archive, I get
 c2103b9533baa88814e770b493e5ba93f3043f3d73ce6e018addcd7c84b22cd4
 
 By looking closer, the uncompressed initrd from both files is the same.
 Only the date (from the gzip header) differs by a couple of seconds. And
 this only happens for the GTK installer, not the text one, once again…
 
 Furthermore, I also realized that Ubuntu is affected, too (!); the sum
 for the GTK installer of Precise Pangolin has the same problem.
 
 There must be a small packaging bug somewhere…

The timestamp issue was indeed a nice clue. gzip has -n to avoid storing
such information, improving build reproducibility:
|-n --no-name
|   When compressing, do not save the original file  name  and  time
|   stamp by default. (The original name is always saved if the name
|   had to be truncated.) When decompressing,  do  not  restore  the
|   original  file name if present (remove only the gzip suffix from
|   the compressed file name) and do not restore the  original  time
|   stamp if present (copy it from the compressed file). This option
|   is the default when decompressing.

I shall note pigz needs has -n and -T:
|-n --no-name
|   Do not store or restore file name in/from header.
|-T --no-time
|   Do not store or restore mod time in/from header.

But why do we need that, you ask? Let's mention the md5sum of each
generated initrd.gz during a full build:
| MD5SUM: c47a2e5b24eb72737e566c0fee4bc2fe  ./tmp/cdrom_gtk/initrd.gz
| MD5SUM: 3767e38d0790c2a89f5ccacc7f4845af  ./tmp/cdrom_isolinux/initrd.gz
| MD5SUM: 99646ced5c6045386c4ebbac9334bee7  ./tmp/cdrom_gtk/initrd.gz
| MD5SUM: 73902a6e23b5c281172182a19633cf4d  ./tmp/cdrom_gtk/initrd.gz
| MD5SUM: bb6a60f95815569a5cc41fe9466e9d97  ./tmp/netboot/initrd.gz
| MD5SUM: 4707ee1a9a643e4513723029129e07dd  ./tmp/netboot-gtk/initrd.gz [1]
| MD5SUM: 6614937379a7f83a95f8741a63f00394  ./tmp/netboot-gtk/initrd.gz [2]
| MD5SUM: 586b60ef353423481f828ee03927a682  ./tmp/hd-media_gtk/initrd.gz
| MD5SUM: 0e3bfa9304fbcf9a1081e6746866bb7f  ./tmp/hd-media/initrd.gz
| MD5SUM: 5a5f192055293b6042463650dfa1a0b4  ./tmp/hd-media_gtk/initrd.gz

Let's look at the file extracted from netboot.tar.gz:
| 4707ee1a9a643e4513723029129e07dd  ./foo/debian-installer/amd64/initrd.gz

Let's look at the MD5SUMS file:
| 6614937379a7f83a95f8741a63f00394  
./netboot/gtk/debian-installer/amd64/initrd.gz

So netboot.tar.gz contains the initrd.gz that was generated on a first
pass, while the MD5SUMS (generated at the end of the build process,
through “make release”) contains the checksum of the one generated on a
second pass. Adding -n/-T to gzip/pigz makes both initrd.gz identical
so this issue goes away.

Tagging with patch as the solution has been identified; I haven't
committed a proper patch yet though.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Processed: Re: Bug#704162: Wrong sum for GTK installer initrd.gz inside netboot.tar.gz

2014-03-02 Thread Debian Bug Tracking System
Processing control commands:

 tag -1 patch
Bug #704162 [debian-installer] Wrong sum for GTK installer initrd.gz inside 
netboot.tar.gz
Added tag(s) patch.

-- 
704162: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704162
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.b704162.139380722325188.transcr...@bugs.debian.org



Bug#616512: marked as done (debian-installer: Need menuitem for switch off installing Recommends by default)

2014-03-02 Thread Debian Bug Tracking System
Your message dated Mon, 3 Mar 2014 02:00:38 +0100
with message-id 20140303010038.ga17...@mraw.org
and subject line Re: Bug#616512: debian-installer: Need menuitem for switch off 
installing Recommends by default
has caused the Debian Bug report #616512,
regarding debian-installer: Need menuitem for switch off installing Recommends 
by default
to be marked as done.

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

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


-- 
616512: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616512
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: debian-installer
Severity: wishlist
Tags: d-i


Sometime need install ssh-only server without other packages not from base.
When i choose only ssh from tasksel in debian-installer, it install Recommends 
for ssh packages.
I don't need this packages by default and i need switch off Recommeds before 
tasksel.


-- System Information:
Debian Release: 6.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


---End Message---
---BeginMessage---
Control: tag -1 - confirmed

stanislav@gmail.com stanislav@gmail.com (2011-03-05):
 Package: debian-installer
 Severity: wishlist
 Tags: d-i
 
 Sometime need install ssh-only server without other packages not from base.
 When i choose only ssh from tasksel in debian-installer, it install 
 Recommends for ssh packages.
 I don't need this packages by default and i need switch off Recommeds before 
 tasksel.

From debian-installer-utils, debian/di-utils/bin/apt-install has:
| if db_get base-installer/install-recommends  [ $RET = false ]; then
| if [ $WITH_RECOMMENDS ]; then
| apt_opts=$apt_opts -o APT::Install-Recommends=true
| fi
| else
| if [ $NO_RECOMMENDS ]; then
| apt_opts=$apt_opts -o APT::Install-Recommends=false
| fi
| fi

From base-installer, debian/base-installer.templates has:
| Template: base-installer/install-recommends
| Type: boolean
| Default: true
| Description: for internal use; can be preseeded
|  Will configure APT in the target system not to install recommened
|  packages by default. For experienced users only.

It appears to have been implemented before squeeze was released;
closing this bug report accordingly.

Mraw,
KiBi.


signature.asc
Description: Digital signature
---End Message---


Bug#596335: marked as done (debian-installer: build ready-to-use hd-media images)

2014-03-02 Thread Debian Bug Tracking System
Your message dated Mon, 3 Mar 2014 02:05:17 +0100
with message-id 20140303010517.ga18...@mraw.org
and subject line Re: Bug#596335: debian-installer: build ready-to-use hd-media 
images
has caused the Debian Bug report #596335,
regarding debian-installer: build ready-to-use hd-media images
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.)


-- 
596335: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596335
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: debian-installer
Severity: wishlist

Hello,

As opposed to the optical disk images, the images that are provided for
installing Debian from an hd-media are not directly usable, but need to be
manually completed by adding an optical disk image into their filesystem.

This requires a more complicated procedure, and make the installation of Debian
from an USB key more complicated than from an optical disk, whereas there is no
theoretical reason for such a difference. Compare these two typical use cases:
(preparing an installation CD)
[optional: read the installation manual]
[find the URL of the CD image]
wget http://url/of/the/cd.iso
wodim dev=/dev/cdrom cd.iso
(preparing an installation USB drive)
[mandatory: read the installation manual]
[find the URL of the hd-media image]
wget http://url/of/the/hd-media.img.gz
[optional: try to write it directly, boot on that, fail]
gunzip hd-media.img.gz
dd if=hd-media.img of=/dev/stick
[optional: try to boot on that, fail]
[optional: give up and switch to the CD way]
[find the URL a small CD image]
wget http://url/of/the/cd.iso
mount /dev/stick /mnt
cp cd.iso /mnt
umount /mnt

The installation manual explains that in a non-straightforward way, describing
two methods, and giving only hints to find where to download the two needed
images. In addition, this procedure depends on *nix tools, and is thus
inapplicable for many user that start installing Debian from a foreign system,
which is a common case. Because of this complication, I see many beginners
failing at preparing installation USB sticks, if not failing to install Debian
at all because they do not have an optical drive.

It would be useful to build and provide ready-to-use hd-media images, that
would be as easy to use as the optical disk ones. I see four ways to implement
that:
1. work around: after building the incomplete hd-media image as it is
   currently done, post-process it to add an optical disk image on its 
filesystem;
2. hi-tech, space-saving: using the recent hybrid boot feature of SYSLINUX,
   that allow to build single images that are bootable either as El Torito
   optical media or as MBR on-optical media, if applicable to the Debian
   installer: cf. bug #593484;
3. clean: find a way to build autonomous hd-media image, that use data on their
   file system instead of relying on an optical disk image;
4. minimalistic: build hd-media image that use the netboot process, thus
   containing only a bootloader, a kernel and an initrd: cd. bug #505773.

Regards,

-- 
Tanguy Ortolo

-- System Information:
Debian Release: squeeze/sid
  APT prefers stable
  APT policy: (990, 'stable'), (60, 'testing'), (50, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-bpo.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


signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Tanguy Ortolo tanguy+deb...@ortolo.eu (2010-09-10):
 As opposed to the optical disk images, the images that are provided for
 installing Debian from an hd-media are not directly usable, but need to be
 manually completed by adding an optical disk image into their filesystem.

The manual has:
   4.3.1. Preparing a USB stick using a hybrid CD or DVD image

and those images are ready to use, so closing this bug report.

Mraw,
KiBi.


signature.asc
Description: Digital signature
---End Message---


Bug#613714: marked as done (debian-installer: make debian-installer builds available through Debian infrastructure)

2014-03-02 Thread Debian Bug Tracking System
Your message dated Mon, 3 Mar 2014 02:10:22 +0100
with message-id 20140303011022.ga18...@mraw.org
and subject line Re: Bug#613714: debian-installer: make debian-installer builds 
available through Debian infrastructure
has caused the Debian Bug report #613714,
regarding debian-installer: make debian-installer builds available through 
Debian infrastructure
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.)


-- 
613714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: debian-installer
Version: 20101020
Severity: wishlist

Hello,

  It would be useful if debian-installer images are built through Debian buildd 
infrastructure instead having to setup build daemons on random sites. It might 
be a nice goal for next release.

Best regards,
  -- Hector Oron

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- no debconf information


---End Message---
---BeginMessage---
Hi,

Otavio Salvador ota...@ossystems.com.br (2011-02-16):
 On Wed, Feb 16, 2011 at 21:54, Hector Oron hector.o...@gmail.com wrote:
 ...
  True, maybe a parallel development daily builder is useful, but the
  reason I am asking for such feature is to ease the release process and
  those builds might be useful for other projects such debian-live.
 ...
 
 I believe we ought to make more regular uploads but not sure if
 automated in any specific frequency will give any benefit for us. Live
 and others can use dailies but fetch them from a different URL.

so we have daily builds on regular buildds, and we're having around an
upload per month, which looks reasonably enough for now. I think this
addresses what that bug report was about, so I'm closing it.

Feel free to reopen with more information if you feel that's incorrect.

Mraw,
KiBi.


signature.asc
Description: Digital signature
---End Message---


Bug#645765: marked as done (please consider allowing to load installer components from a different mirror)

2014-03-02 Thread Debian Bug Tracking System
Your message dated Mon, 3 Mar 2014 02:20:41 +0100
with message-id 20140303012041.ga19...@mraw.org
and subject line Re: Bug#645765: please consider allowing to load installer 
components from a different mirror
has caused the Debian Bug report #645765,
regarding please consider allowing to load installer components from a 
different mirror
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.)


-- 
645765: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: debian-installer
Severity: wishlist
Tags: d-i

Hi,

when entities deploy Debian via network install, point releases can
pose challenges. For example, a site I consult for has a mirror which
is rsynced daily, but the installation server is not updated
automatically with the latest initrd and kernel files.

After the last point release[1], installation was broken since the
kernel from 6.0.2 wasn't willing to load the kernel modules loaded
from the 6.0.3 mirror. Disk not found, game over.

To get around this, I think that it would be desireable to be able to
load installer components from a different source than the repository
that the actual system that is being installed. That way, one would be
able to dump the contents of a (probably older) netinstall CD to a web
server, and point the installer to that web server while still
doing the actual install from ftp.de.d.o.

This could be accomplished, for example, with the following algorithm:

  (1) Run through the normal mirror selection process. Take answer as
  d-i mirror/installer/hostname
  (2) Check whether d-i mirror/installer/hostname is a full mirror or a
  installation image only
  (2a) if full mirror, set d-i mirror/http/hostname to d-i
   mirror/installer/hostname's value
  (3) Expert: Ask Use the same mirror to for the installation?
  (3a) if no, ask for d-i mirror/http/hostname
  (4) load installer components from d-i mirror/installer/hostname
  (5) install actual system from d-i mirror/http/hostname

both mirror/installer/hostname and mirror/http/hostname should be
preseedable. Same algorithm for other parameters such as
mirror/*/directory et al.

That way, one could make sure to always have an installer repository
consistent with the kernel/initrd pair offered by the PXE server, and
keep the triple kernel/initrd/repository stable and verified, while
still installing the current point release from the actual mirror.

Please consider adding this functionality to the installer; it would
have saved us (and probably other installations) a lot of grief.
Currently, we have a safety latch active which stops all archive
updates once
/debian/dists/*/main/debian-installer/*/Packages.gz
changes from the file we're familiar with. This is kind of an ugly
workaround, and a nicer solution would be to have the installer load
its components from a dedicated URL that could be forced into sync.

Greetings
Marc



[1] I don't have the slightest idea why this issue has only surfaced
after 6.0.3


---End Message---
---BeginMessage---
Philipp Kern pk...@debian.org (2011-10-18):
 On 2011-10-18, Marc Haber mh+debian-packa...@zugschlus.de wrote:
  when entities deploy Debian via network install, point releases can
  pose challenges. For example, a site I consult for has a mirror which
  is rsynced daily, but the installation server is not updated
  automatically with the latest initrd and kernel files.
 
 There are debian-installer-6.0-netboot-* packages for this in squeeze
 now, FWIW.  It helps in quite a bunch of cases, just maybe not in yours.
 (The install server needs to run on squeeze.)  ;-)
 
  [1] I don't have the slightest idea why this issue has only surfaced
  after 6.0.3
 
 It certainly happens for new kernel ABIs.  But yeah, point releases
 regularly break d-i netboot images because of the way they work.
 Basically whenever we respin the kernel udebs and then d-i to
 incorporate new security updates / other misc bugfixes.  I wonder what
 was different here if it didn't happen with .1 or .2 (which both had
 non-ABI breaking d-i kernel updates).  Do you have some sort of
 failure message?

I don't think this happens anymore in wheezy, so I'm closing this bug
report. We have another one with a similar goal in mind, with an
attached patch, to review (#736373).

Mraw,
KiBi.


signature.asc
Description: Digital signature
---End Message---


Re: Bug#712696: debian-installer: Add Cinnamon and Mate as alternative DEs.

2014-03-02 Thread Cyril Brulebois
Control: reassign -1 src:tasksel

Steven Chamberlain ste...@pyro.eu.org (2014-02-02):
 Andreas Cadhalpun wrote:
  Re: Processed: closed by spam, thus reopening
 
 The bug wasn't closed by spam, but by Ben Hutchings who said:
  We do not have packages of these, and probably never will.  This is not
  a bug in the installer.
 
 although now I think we actually do, so maybe we want to revisit this.
 
 If packaging of those is anywhere near complete, the next thing we'd
 need are tasksel tasks for these desktops...

I'm not sure we want to support every desktop environment out there… but
I guess tasks might not hurt, so punting that to tasksel. And adding
debian-cd@ to the loop, to get some feelings about whether new images
would sound like a vaguely sane idea (I'm really not sure).

Mraw,
KiBi.


signature.asc
Description: Digital signature


Processed: Re: Bug#712696: debian-installer: Add Cinnamon and Mate as alternative DEs.

2014-03-02 Thread Debian Bug Tracking System
Processing control commands:

 reassign -1 src:tasksel
Bug #712696 [src:tasksel] debian-installer: Add Cinnamon and Mate as 
alternative DEs.
Ignoring request to reassign bug #712696 to the same package

-- 
712696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712696
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.u712696.13938101278056.transcr...@bugs.debian.org



Processed: Re: Bug#712696: debian-installer: Add Cinnamon and Mate as alternative DEs.

2014-03-02 Thread Debian Bug Tracking System
Processing control commands:

 reassign -1 src:tasksel
Bug #712696 [debian-installer] debian-installer: Add Cinnamon and Mate as 
alternative DEs.
Bug reassigned from package 'debian-installer' to 'src:tasksel'.
Ignoring request to alter found versions of bug #712696 to the same values 
previously set
Ignoring request to alter fixed versions of bug #712696 to the same values 
previously set

-- 
712696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712696
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.b712696.13938101278046.transcr...@bugs.debian.org



Bug#722720: marked as done (Please add installer images for Raspberry Pi)

2014-03-02 Thread Debian Bug Tracking System
Your message dated Mon, 3 Mar 2014 02:32:46 +0100
with message-id 20140303013246.ga21...@mraw.org
and subject line Re: Bug#722720: Please add installer images for Raspberry Pi
has caused the Debian Bug report #722720,
regarding Please add installer images for Raspberry Pi
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.)


-- 
722720: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: debian-installer
Severity: wishlist

Hello,

Please add installer images for Raspberry Pi in architecture armel.

There are several images available in
/dists/wheezy/main/installer-armel/current/images.
For example: there are images for qnap nas storage in images/kirkwood.
But there is no image for Raspberry Pi.

Thank you for the great work.

Best regards
Bernhard



signature.asc
Description: OpenPGP digital signature
---End Message---
---BeginMessage---
Ben Hutchings b...@decadent.org.uk (2013-09-14):
 On Fri, 2013-09-13 at 18:55 +0200, Bernhard wrote:
  Package: debian-installer
  Severity: wishlist
  
  Hello,
  
  Please add installer images for Raspberry Pi in architecture armel.
  
  There are several images available in
  /dists/wheezy/main/installer-armel/current/images.
  For example: there are images for qnap nas storage in images/kirkwood.
  But there is no image for Raspberry Pi.
 
 The Raspberry Pi uses an SoC in which the main processor is a multicore
 GPU (VideoCore IV) and the ARM core is a peripheral.  The GPU must be
 booted first, and it is also booted from the SD card.  Since there is no
 free software (or documentation) for the GPU, we cannot currently build
 an official Debian installer image for the RPi that you could write
 directly to an SD card.  Perhaps it would be possible to build an image
 that could be concatenated with the GPU boot code, though.
 
 In addition to this, it requires a number of kernel drivers which are
 not included in mainline Linux.  Comparing Linux 3.11 with the RPi
 branch: […]

Maybe things improved lately, but it looks to me we're not ready to try
and support RPi, so I'm closing this bug report for the time being. If
stuff got better on the kernel side, great; but that's not a sufficient
condition if I'm reading you properly.

Mraw,
KiBi.


signature.asc
Description: Digital signature
---End Message---


Bug#724891: [debian-installer] debian-installer: Build firmware for the DNS-320/DNS-325

2014-03-02 Thread Cyril Brulebois
Control: retitle -1 debian-installer: Build firmware for the DNS-320/DNS-325

bastien ROUCARIES roucaries.bast...@gmail.com (2013-09-29):
 Package: debian-installer
 Severity: wishlist
 
 Please support the DNS-320 and dns-325
 
 I can support it I own a DNS-320
 
 See http://jamie.lentin.co.uk/devices/dlink-dns325/
 
 DNS-320 run a custom debian system

Let's pretend I know nothing about arm*. We have orion5x on armel, which
seems to include support for dns323. Isn't that what you need? Not close
enough? Not at all?

Mraw,
KiBi.


signature.asc
Description: Digital signature


Processed: Re: Bug#724891: [debian-installer] debian-installer: Build firmware for the DNS-320/DNS-325

2014-03-02 Thread Debian Bug Tracking System
Processing control commands:

 retitle -1 debian-installer: Build firmware for the DNS-320/DNS-325
Bug #724891 [debian-installer] [debian-installer] debian-installer: Build 
firmware for the DNS-320/DNS-325
Changed Bug title to 'debian-installer: Build firmware for the DNS-320/DNS-325' 
from '[debian-installer] debian-installer: Build firmware for the 
DNS-320/DNS-325'

-- 
724891: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724891
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.b724891.139381067610855.transcr...@bugs.debian.org



Bug#247078: marked as done (Please support ISDN connectivity)

2014-03-02 Thread Debian Bug Tracking System
Your message dated Mon, 3 Mar 2014 02:43:20 +0100
with message-id 20140303014320.ga23...@mraw.org
and subject line Re: Bug#247078: ISDN?
has caused the Debian Bug report #247078,
regarding Please support ISDN connectivity
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.)


-- 
247078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=247078
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports

Debian-installer-version: 2004-03-19,
gluck.debian.org/cdimage/testing/sarge_d-i/i386/beta3/sarge-i386-netins
t.iso
uname -a: Linux [...] 2.4.25-1-386 #1 Tue Feb 24 08:11:13 EST 2004 i686
[...]
Date: 2004-04-30
Method: Booted from the netinst-CD (SCSI-drive), no network uplink
available.

Machine: Asus A7V
Processor: AMD Duron
Memory: 384 MB SDRAM
Root Device: hda6
Root Size/partition table: ~7GB, mounted as /
Output of lspci: (Run on a different Debian-installation):
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133]
  (rev 02)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686[Apollo Super South]
  (rev 22)
00:04.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus
  Master IDE (rev 10)
00:04.2 USB Controller: VIA Technologies, Inc. USB (rev 10)
00:04.3 USB Controller: VIA Technologies, Inc. USB(rev 10)
00:04.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
  (rev 30)
00:09.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1
  (rev 08)
00:09.1 Input device controller: Creative Labs SB Live! MIDI/Game
  Port (rev 08)
00:0a.0 SCSI storage controller: Adaptec AIC-7861 (rev 03)
00:0c.0 Network controller: AVM Audiovisuelles MKTG  Computer System
  GmbH Fritz!PCI v2.0 ISDN (rev 01)
00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL-8139/8139C/8139C+ (rev 10)
00:11.0 Unknown mass storage controller: Promise Technology, Inc. 20265
  (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation NV4 [RIVA TNT]
  (rev 04)


Base System Installation Checklist:

Initial boot worked:[O]
Configure network HW:   [O]
Config network: [E]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Create file systems:[O]
Mount partitions:   [O]
Install base system:[O]
Install boot loader:[O]
Reboot: [O]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Comments/Problems:

Config network:
---
There was no DHCP-server on the network, so the installation process
prompted me to configure the network manually.
While this worked (I suppose, I didn't try the connection later though),
when configuring the Gateway, it told me that the field could also be
blank in rare situations. Not having a Gateway, I tried this, but than
the installer told me (on red background) that the string set as gateway
was not a valid IP address.
I'd suppose to either make it possible to enter _no_ GW, or to adapt the
description of this situation.

The Partitioner:

To me, it was a bit confusing and too unclear, how to change the
partitions, have them formatted, where I'd made changes already (and
which partitions were still untouched), ...
Above all, eventually the d-i asked whether to really change the
partitions accordingly. Not being sure about which ones I'd changed, NOT
having a list of what will be done was quite -- exciting, to say the
least ;).
I'd suppose to present a list of changes that will be performed!

GRUB:
-
At some point during partitioning my HDD, I got to the list of the
overall installation procedure. Later-on, I chose Install GRUB from
this list, which was the last step before rebooting the machine. While
it worked fine, it did not ask me to include any of the other OS's (e.g.
other Linux-installations on other partitions) available.
Would be nice ...

Uplink-connectivity:

... though this is nothing d-i-related, actually, I don't know who's
responsible for which packages are included in the ISO's:
At least the netinst-ISO does not include any ISDN-packages (at least I
didn't find them). Having to download them manually over another
installation/machine is quite uncomfortable. ISDN is a well-established
protocol here in Europe. Including ipppd and isdnutils-base (which
suffice for basic configurations) would only add another 352 kB and was
worth it definitely, IMHO.

Thanks for all your good work!

Cheers,
Max

-- 
The first time any man's freedom is trodden on, we're all damaged.
   

Bug#704768: marked as done (please suport neo2, dvorak, french bépo, ..., keyboard layouts)

2014-03-02 Thread Debian Bug Tracking System
Your message dated Mon, 3 Mar 2014 02:48:21 +0100
with message-id 20140303014821.ga23...@mraw.org
and subject line Re: Bug#691666: installation-reports: please propose french 
bépo keyboard layout during installation
has caused the Debian Bug report #691666,
regarding please suport neo2, dvorak, french bépo, ..., keyboard layouts
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.)


-- 
691666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: debian-installer
Version: wheezy RC-1-Release
Severity: wishlist

Hi,

I have a keyboard with the german Neo2 layout.
Currently it appears that there is no option to select it in the debian-
installer.
I can only enable it after the installation with dpkg --reconfigure keyboard-
configuration.
Would be great to have it in the installer!

Thank you for maintaining the debian-installer!
Best regards,
Simon



-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
---End Message---
---BeginMessage---
Samuel Thibault sthiba...@debian.org (2012-10-28):
 Fred, le Sun 28 Oct 2012 15:01:54 +0100, a écrit :
  I didn't saw this bug report.
 
 Did you read the discussion there?
 
  Meanwhile, the simplicity shouldn't go against usability, no ?
 
 See the discussion there. It is still considered that doubling the
 amount of choices in an already very long list hurts more than having
 to type with the layout that is used in the vast rest of one's own
 country.

[ etc. ]

Closing this bug report as I'm not sure we're going to revisit that any
time soon. (Quite the contrary in fact.)

Mraw,
KiBi.


signature.asc
Description: Digital signature
---End Message---


Bug#691666: marked as done (please suport neo2, dvorak, french bépo, ..., keyboard layouts)

2014-03-02 Thread Debian Bug Tracking System
Your message dated Mon, 3 Mar 2014 02:48:21 +0100
with message-id 20140303014821.ga23...@mraw.org
and subject line Re: Bug#691666: installation-reports: please propose french 
bépo keyboard layout during installation
has caused the Debian Bug report #691666,
regarding please suport neo2, dvorak, french bépo, ..., keyboard layouts
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.)


-- 
691666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports

Boot method: hdmedia's kernel+initrd, and netinst multi-arch CD (on the
usbkey) Image version:
http://cdimage.debian.org/cdimage/wheezy_di_beta3/multi-arch/iso-cd/debian-wheezy-DI-b3-amd64-i386-netinst.iso
Date: 28/10/2012

Machine: IBM Thinkpad X201
Processor: I5
Memory: 4GB
Partitions:

# fdisk -l /dev/sda

Disque /dev/sda: 500.1 Go, 500107862016 octets
255 têtes, 63 secteurs/piste, 60801 cylindres
Unités = cylindres de 16065 * 512 = 8225280 octets
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Identifiant de disque : 0x

Périphérique Amorce  DébutFin  Blocs Id  Système
/dev/sda1   *   1 498 4000153+  83  Linux
Partition 1 does not start on physical sector boundary.
/dev/sda2 499 996 4000185   82  Linux swap /
Solaris Partition 2 does not start on physical sector boundary.
/dev/sda3 9971120  996030   83  Linux
Partition 3 does not start on physical sector boundary.
/dev/sda41121   60801   479387632+   5  Etendue
/dev/sda51121   60801   479387601   83  Linux
Partition 5 does not start on physical sector boundary.

Résultat de lspci -knn (ou lspci -nn) :

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:  [E]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Clock/timezone setup:   [O]
User/password setup:[E]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

I've tried to install wheezy on a free partition on my current Squeeze
system, but with the standard boot method, the debian installer was
stuck trying to detect where is the install-CD ISO, when parsing my
hard disk sda4 partition (before to look at the USB key /dev/sdb where
the ISO lies) : bug already known, see #684293. I had to use expert
install to workaround this, the beta3 version has same problem as the
beta2 I tried before.

I have then a problem choosing keyboard layout, as I use a
« dvorak-like » layout designed for french language, called « bépo » :
this layout is very different from qwerty, azerty or either [english]
dvorak, and so it's very difficult to use blindly an azerty or qwerty
layout on a Bépo keyboard ! This causes problems entering root's
password, simple user login and password, and also after the
installation, to reconfigure the system to be able to use the correct
layout [in fact, I installed default Gnome 3(?) desktop, and I wasn't
used with this system, I was unable to find how to modify the layout
nor how to open a terminal to do it with command line...].

For information, I also requested to add this layout for the Squeeze
installer (see #550962), and Christian didn't find it pertinent, I hope
this time will be the good one :-)

The Bépo layout, community built as a free software, is fully
integrated in Xorg since 2007 (has also drivers for Windows and Mac OSX
systems), quite a lot of [french] developpers/users has at least heard
about it, and is recognized by some ergonomic keyboard builders
(Typematrix: http://www.typematrix.com, CECIAA:
http://www.ceciaa.com/clavier-ergoneos-fort-contraste-disposition-bepo-c2391-7.php).
Its user base, while difficult to estimate, seems to grow ; its
community regularly do some demonstrations/presentations/stands in
exhibitions (RMLL for example) to let it be known. More information
about this layout is available at http://www.bepo.fr.
---End Message---
---BeginMessage---
Samuel Thibault sthiba...@debian.org (2012-10-28):
 Fred, le Sun 28 Oct 2012 15:01:54 +0100, a écrit :
  I didn't saw this bug report.
 
 Did you read the discussion there?
 
  Meanwhile, the simplicity shouldn't go against usability, no ?
 
 See the discussion there. It is still considered that doubling the
 amount of choices 

Bug#642179: debian-installer: Installs on drives larger than 2.19TB fails with older bios

2014-03-02 Thread Karl Schmidt

On 03/02/2014 03:23 PM, Cyril Brulebois wrote:

Control: tag -1 - d-i squeeze

This is from quite a while ago - There have been changes to grub2 and many other tools in the mean 
time.  There are two issues - one is bios limitations on some MBs and the other is the need to use 
GPT for the partition table on large TB drives.


I have some notes on this here:

http://wiki.xtronics.com/index.php/EFI_UEFI_GUID_GPT_and_large_TB_partitions

One can sometimes work around the BIOS issues by changing to coreboot on 
supported MBs.

I have not tested this with wheezy as my preferred set up now uses a raid of SSHDs for the / (system 
files) and only /home is on the large drives.


Your question should be if the install images support GPT - and that I don't 
know.  Hope I've helped.




Hi Karl,

Karl Schmidt k...@xtronics.com (2011-09-22):

This is failing with the current squeeze installer that uses grub2.

What I don't know is if this is possibly a BIOS issue - my
understanding is that Debian takes over and uses its own driver.

This is on a Tyan S7002 which uses:

# lspci |grep SATA
00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI 
Controller

for the SATA controller.

I'm attempting a workaround - I'm installing the main system on a
40GB raided pair of SSD and will have /homes on large ( 2.18TB )
drives. I will partition the large drives with gparted and use GPT.


are you experiencing similar issues with wheezy installation images?

Mraw,
KiBi.




--

Karl Schmidt  EMail k...@xtronics.com
Transtronics, Inc.  WEB http://xtronics.com
3209 West 9th Street Ph (785) 841-3089
Lawrence, KS 66049  FAX (785) 841-0434

History may not repeat itself, but it does rhyme a lot. -Mark Twain




--
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/5313db2a.7060...@xtronics.com



Bug#696124: marked as done (please stop ejecting the installation medium)

2014-03-02 Thread Debian Bug Tracking System
Your message dated Mon, 3 Mar 2014 02:53:08 +0100
with message-id 20140303015308.ga24...@mraw.org
and subject line Re: Bug#696124: (no subject)
has caused the Debian Bug report #696124,
regarding please stop ejecting the installation medium
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.)


-- 
696124: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696124
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Subject: installation-reports: The installer, when finished, ejects the optical 
disk.  This is unhelpful and annoying, especially if you are installing from an 
.iso image into a virtual machine, and wish to install packages from the disk 
after the install (and APT sources.list defaults to an install from a local 
disk vs. network servers).  Ejecting the optical disk is a bad solution to the 
problem of inexperienced users inadvertantly re-entering the installer after 
the install is complete; a more helpful solution wuld be something similiar to 
Microsoft Windows, which, if it detects a hard disk is bootable, prompts the 
user to strike a key if they wish to boot from the CD-ROM (and if no key is 
pressed within 5 seconds, automatically defaults to booting the hard disk).
Package: installation-reports
Severity: wishlist



-- Package-specific info:

Boot method: CD
Image version: debian-6.0.6-i386-DVD-1.iso
Date: Date and time of the install

Machine: VMware VM
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:   [ ]
Detect network card:[ ]
Configure network:  [ ]
Detect CD:  [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

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 sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=6.0 (squeeze) - installer build 20110106+squeeze4+b2
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux dsql1 2.6.32-5-486 #1 Sun Sep 23 09:17:35 UTC 2012 i686 
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 
82443BX/ZX/DX Host bridge [8086:7190] (rev 01)
lspci -knn: Subsystem: VMware Device [15ad:1976]
lspci -knn: Kernel driver in use: agpgart-intel
lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation 440BX/ZX/DX - 
82443BX/ZX/DX AGP bridge [8086:7191] (rev 01)
lspci -knn: 00:07.0 ISA bridge [0601]: Intel Corporation 82371AB/EB/MB PIIX4 
ISA [8086:7110] (rev 08)
lspci -knn: Subsystem: VMware Device [15ad:1976]
lspci -knn: 00:07.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 
IDE [8086:7111] (rev 01)
lspci -knn: Subsystem: VMware Device [15ad:1976]
lspci -knn: Kernel driver in use: ata_piix
lspci -knn: 00:07.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI 
[8086:7113] (rev 08)
lspci -knn: Subsystem: VMware Device [15ad:1976]
lspci -knn: 00:07.7 System peripheral [0880]: VMware Virtual Machine 
Communication Interface [15ad:0740] (rev 10)
lspci -knn: Subsystem: VMware Virtual Machine Communication Interface 
[15ad:0740]
lspci -knn: 00:0f.0 VGA compatible controller [0300]: VMware SVGA II Adapter 
[15ad:0405]
lspci -knn: Subsystem: VMware SVGA II Adapter [15ad:0405]
lspci -knn: 00:10.0 SCSI storage controller [0100]: LSI Logic / Symbios Logic 
53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI [1000:0030] (rev 01)
lspci -knn: Subsystem: VMware Device [15ad:1976]
lspci -knn: Kernel driver in use: mptspi
lspci -knn: 00:11.0 PCI bridge [0604]: VMware PCI bridge [15ad:0790] (rev 02)
lspci -knn: 00:15.0 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] 
(rev 01)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:15.1 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] 
(rev 01)
lspci 

Bug#718548: debian-installer: add bcache support to partitions setup and bcache-tools to installer

2014-03-02 Thread Cyril Brulebois
Control: tag -1 moreinfo

Josep Lladonosa jllad...@gmail.com (2013-08-02):
 Last kernel versions have added bcache to the system. It allows to use an SSD
 drive as a cache for a -for example- a disk drive partition.
 
 A common installation is /dev/sda as the main disk drive and /dev/sdb as a
 cache drive for it. After a configuration like this, one gets the /dev/bcache0
 device to mkfs the filesystem  on it, in a similar way to LVM or RAID. Even
 more, bcache can be combined with these.
 
 It would be nice if the installer gave these options to configure, for 
 example,
 at the moment, in an expert mode install. It would require bcache-tools at 
 boot
 and bcache as a module in the kernel.

bcache.ko is shipped in current debian kernels, alright. I don't see any
bcache-tools package though.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Processed: Re: Bug#718548: debian-installer: add bcache support to partitions setup and bcache-tools to installer

2014-03-02 Thread Debian Bug Tracking System
Processing control commands:

 tag -1 moreinfo
Bug #718548 [debian-installer] debian-installer: add bcache support to 
partitions setup and bcache-tools to installer
Added tag(s) moreinfo.

-- 
718548: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718548
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.b718548.139381204217032.transcr...@bugs.debian.org



Bug#655438: installation-reports: nilfs2 support

2014-03-02 Thread Cyril Brulebois
FWIW I have no idea whether adding nilfs2 support to d-i would make
sense somewhat, just trying to answer so that you get an overall idea
of the needed bits.

Walter Landry wlan...@caltech.edu (2012-01-10):
 It would be nice to support nilfs2 as a option during installation.
 It seems that there are only two things that need to be done: Add
 nilfs2 to the list of kernel modules, and get partman to support
 nilfs2. I presume the first thing is easy, but I do not know how
 hard the second is.

Yes for the first part, nilfs2.ko is already available in the linux
image packages, and would only need to be included in some udeb for
use within d-i; should be trivial.

You may want to look at what happens in the various partman-*
packages; you probably would need to have an extra udeb built from
the nilfs-tools package (for mkfs.nilfs2 and possibly other bits),
and a new partman-nilfs udeb shipping the various bits for partman
integration, and depending on both the kernel and the nilfs-tools
udeb.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Bug#724891: [debian-installer] debian-installer: Build firmware for the DNS-320/DNS-325

2014-03-02 Thread Ben Hutchings
On Mon, 2014-03-03 at 02:37 +0100, Cyril Brulebois wrote:
 Control: retitle -1 debian-installer: Build firmware for the DNS-320/DNS-325
 
 bastien ROUCARIES roucaries.bast...@gmail.com (2013-09-29):
  Package: debian-installer
  Severity: wishlist
  
  Please support the DNS-320 and dns-325
  
  I can support it I own a DNS-320
  
  See http://jamie.lentin.co.uk/devices/dlink-dns325/
  
  DNS-320 run a custom debian system
 
 Let's pretend I know nothing about arm*. We have orion5x on armel, which
 seems to include support for dns323. Isn't that what you need? Not close
 enough? Not at all?

I found these pages:

http://jamie.lentin.co.uk/devices/dlink-dns325/
http://jamie.lentin.co.uk/devices/dlink-dns325/keeping-original-firmware/

They say that these models use a Kirkwood SoC (so the kirkwood kernel
and installer flavours should be used) and that they are supported by
the standard kernel package in wheezy-backports but not wheezy.

Given that the instructions include writing a custom kernel install
hook, I would assume that flash-kernel doesn't support these models and
therefore this bug should be reassigned to flash-kernel.  But there may
be other changes needed elsewhere.

Ben.

-- 
Ben Hutchings
When you say `I wrote a program that crashed Windows', people just stare ...
and say `Hey, I got those with the system, *for free*'. - Linus Torvalds


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


Bug#724891: [debian-installer] debian-installer: Build firmware for the DNS-320/DNS-325

2014-03-02 Thread Ben Hutchings
On Mon, 2014-03-03 at 02:25 +, Ben Hutchings wrote:
 On Mon, 2014-03-03 at 02:37 +0100, Cyril Brulebois wrote:
  Control: retitle -1 debian-installer: Build firmware for the DNS-320/DNS-325
  
  bastien ROUCARIES roucaries.bast...@gmail.com (2013-09-29):
   Package: debian-installer
   Severity: wishlist
   
   Please support the DNS-320 and dns-325
   
   I can support it I own a DNS-320
   
   See http://jamie.lentin.co.uk/devices/dlink-dns325/
   
   DNS-320 run a custom debian system
  
  Let's pretend I know nothing about arm*. We have orion5x on armel, which
  seems to include support for dns323. Isn't that what you need? Not close
  enough? Not at all?
 
 I found these pages:
 
 http://jamie.lentin.co.uk/devices/dlink-dns325/

Oh, that's exactly what Bastien linked to.  Well anyway, I hope I
extracted the most useful information below.

Ben.

 http://jamie.lentin.co.uk/devices/dlink-dns325/keeping-original-firmware/
 
 They say that these models use a Kirkwood SoC (so the kirkwood kernel
 and installer flavours should be used) and that they are supported by
 the standard kernel package in wheezy-backports but not wheezy.
 
 Given that the instructions include writing a custom kernel install
 hook, I would assume that flash-kernel doesn't support these models and
 therefore this bug should be reassigned to flash-kernel.  But there may
 be other changes needed elsewhere.

-- 
Ben Hutchings
When you say `I wrote a program that crashed Windows', people just stare ...
and say `Hey, I got those with the system, *for free*'. - Linus Torvalds


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


Processed: Re: Bug#724891: [debian-installer] debian-installer: Build firmware for the DNS-320/DNS-325

2014-03-02 Thread Debian Bug Tracking System
Processing control commands:

 reassign -1 flash-kernel
Bug #724891 [debian-installer] debian-installer: Build firmware for the 
DNS-320/DNS-325
Bug reassigned from package 'debian-installer' to 'flash-kernel'.
Ignoring request to alter found versions of bug #724891 to the same values 
previously set
Ignoring request to alter fixed versions of bug #724891 to the same values 
previously set

-- 
724891: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724891
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.b724891.139381494330105.transcr...@bugs.debian.org



  1   2   >