Processed: Re: Bug#567431: Installation Report
Processing commands for cont...@bugs.debian.org: > reassign 567431 kernel-wedge 2.62 Bug #567431 [installation-reports] Installation Report Bug reassigned from package 'installation-reports' to 'kernel-wedge'. Bug #567431 [kernel-wedge] Installation Report Bug Marked as found in versions kernel-wedge/2.62. > tags 567431 pending Bug #567431 [kernel-wedge] Installation Report Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567431: Installation Report
reassign 567431 kernel-wedge 2.62 tags 567431 pending thanks On Friday 29 January 2010, boice...@msu.edu wrote: > Comments/Problems: > Using the text installer, USB Keyboard did not work even with BIOS > legacy emulation enabled once I passed the "Install" menu choice and > was on the language screen. Had to pull out an old PS/2 keyboard to > finish. The USB keyboard works fine on the fully installed system. This is a known issue for some USB keyboards that has already been fixed for when we change over to the 2.6.32 kernel in the installer. Cheers, FJP -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: 32-bit install kernel sleeps off during installation
Frans Pop schrieb: > - install build dependencies > - build a netboot image using: > make reallyclean; fakeroot make build_netboot At this point I fail. The build process wants to install packages like acpi-modules-2.6.26-2-686-di but they seem not to be in the scope of my Lenny based sources.list :-( Regards Rainer -- Dipl.-Inf. (FH) Rainer Koenig Project Manager Linux Business Clients Dept. TSP CLI R&D SW OSE Fujitsu Technology Solutions Bürgermeister-Ullrich-Str. 100 86199 Augsburg Germany Telephone: +49-821-804-3321 Telefax: +49-821-804-2131 Mail: mailto:rainer.koe...@ts.fujitsu.com Internet ts.fujtsu.com Company Details ts.fujitsu.com/imprint.html -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#567182: gcc: Please add libgcc1-udeb for Debian Installer
On Wednesday 27 January 2010, Frans Pop wrote:
> Please consider the attached patch which adds a udeb for libgcc1
> containing only libgcc_s.so.1.
In case we do decide on inclusion in gcc, here is an updated patch for 4.4
and the additional patch for 4.5.
Changes:
- added libgcc[246] udebs for m68k/hppa
- the udeb should not be cross-built, so I removed the bits in the
control.m4 file that IIUC are to enable that
I've successfully tested the patches for standard builds:
- gcc-4.4 for amd64 and hppa;
- gcc-4.5 for amd64.
diff -u gcc-4.4-4.4.3/debian/control.m4 gcc-4.4-4.4.3/debian/control.m4
--- gcc-4.4-4.4.3/debian/control.m4
+++ gcc-4.4-4.4.3/debian/control.m4
@@ -188,6 +188,14 @@
environment.
')`'dnl
+Package: libgcc1-udeb
+XC-Package-Type: udeb
+Architecture: any
+Section: debian-installer
+Priority: extra
+Depends: ${shlibs:Depends}, ${misc:Depends}
+Description: GCC support library
+
Package: libgcc2`'LS
Architecture: ifdef(`TARGET',`all',`m68k')
Section: ifdef(`TARGET',`devel',`libs')
@@ -217,6 +225,14 @@
This package contains files for TARGET architecture, for use in cross-compile
environment.
')`'dnl
+
+Package: libgcc2-udeb
+XC-Package-Type: udeb
+Architecture: m68k
+Section: debian-installer
+Priority: extra
+Depends: ${shlibs:Depends}, ${misc:Depends}
+Description: GCC support library
')`'dnl libgcc
ifenabled(`lib4gcc',`
@@ -247,6 +263,14 @@
This package contains files for TARGET architecture, for use in cross-compile
environment.
')`'dnl
+
+Package: libgcc4-udeb
+XC-Package-Type: udeb
+Architecture: hppa
+Section: debian-installer
+Priority: extra
+Depends: ${shlibs:Depends}, ${misc:Depends}
+Description: GCC support library
')`'dnl lib4gcc
ifenabled(`lib64gcc',`
diff -u gcc-4.4-4.4.3/debian/control gcc-4.4-4.4.3/debian/control
--- gcc-4.4-4.4.3/debian/control
+++ gcc-4.4-4.4.3/debian/control
@@ -36,6 +36,14 @@
Description: GCC support library (debug symbols)
Debug symbols for the GCC support library.
+Package: libgcc1-udeb
+XC-Package-Type: udeb
+Architecture: any
+Section: debian-installer
+Priority: extra
+Depends: ${shlibs:Depends}, ${misc:Depends}
+Description: GCC support library
+
Package: libgcc2
Architecture: m68k
Section: libs
@@ -54,6 +62,14 @@
Description: GCC support library (debug symbols)
Debug symbols for the GCC support library.
+Package: libgcc2-udeb
+XC-Package-Type: udeb
+Architecture: m68k
+Section: debian-installer
+Priority: extra
+Depends: ${shlibs:Depends}, ${misc:Depends}
+Description: GCC support library
+
Package: libgcc4
Architecture: hppa
Section: libs
@@ -72,6 +88,14 @@
Description: GCC support library (debug symbols)
Debug symbols for the GCC support library.
+Package: libgcc4-udeb
+XC-Package-Type: udeb
+Architecture: hppa
+Section: debian-installer
+Priority: extra
+Depends: ${shlibs:Depends}, ${misc:Depends}
+Description: GCC support library
+
Package: lib64gcc1
Architecture: i386 powerpc sparc s390 mips mipsel
Section: libs
diff -u gcc-4.4-4.4.3/debian/rules.d/binary-libgcc.mk gcc-4.4-4.4.3/debian/rules.d/binary-libgcc.mk
--- gcc-4.4-4.4.3/debian/rules.d/binary-libgcc.mk
+++ gcc-4.4-4.4.3/debian/rules.d/binary-libgcc.mk
@@ -14,8 +14,10 @@
p_lgcc = libgcc$(GCC_SONAME)
p_lgccdbg = libgcc$(GCC_SONAME)-dbg
+p_lgccudeb = libgcc$(GCC_SONAME)-udeb
d_lgcc = debian/$(p_lgcc)
d_lgccdbg = debian/$(p_lgccdbg)
+d_lgccudeb = debian/$(p_lgccudeb)
p_l32gcc = lib32gcc$(GCC_SONAME)
p_l32gccdbg = lib32gcc$(GCC_SONAME)-dbg
@@ -42,7 +44,10 @@
dh_installdirs -p$(p_lgcc) \
$(docdir)/$(p_lgcc) \
$(libdir)
-
+ dh_installdirs -p$(p_lgccudeb) \
+ $(libdir)
+
+ cp $(d)/$(PF)/lib/libgcc_s.so.$(GCC_SONAME) $(d_lgccudeb)/$(libdir)/.
ifeq ($(with_shared_libgcc),yes)
mv $(d)/$(PF)/lib/libgcc_s.so.$(GCC_SONAME) $(d_lgcc)/$(libdir)/.
endif
@@ -57,8 +62,9 @@
debian/dh_rmemptydirs -p$(p_lgcc)
debian/dh_rmemptydirs -p$(p_lgccdbg)
dh_strip -v -p$(p_lgcc) --dbg-package=$(p_lgccdbg)
- dh_compress -p$(p_lgcc) -p$(p_lgccdbg)
- dh_fixperms -p$(p_lgcc) -p$(p_lgccdbg)
+ dh_strip -v -p$(p_lgccudeb)
+ dh_compress -p$(p_lgcc) -p$(p_lgccdbg) -p$(p_lgccudeb)
+ dh_fixperms -p$(p_lgcc) -p$(p_lgccdbg) -p$(p_lgccudeb)
ifeq ($(with_shared_libgcc),yes)
dh_makeshlibs -p$(p_lgcc) -V '$(p_lgcc) (>= $(DEB_LIBGCC_SOVERSION))' \
-- -v$(DEB_LIBGCC_VERSION)
@@ -68,17 +74,17 @@
endif
cat debian/$(p_lgcc)/DEBIAN/shlibs >> debian/shlibs.local
endif
- dh_shlibdeps -p$(p_lgcc)
- dh_gencontrol -p$(p_lgcc) -p$(p_lgccdbg) \
+ dh_shlibdeps -p$(p_lgcc) -p$(p_lgccudeb)
+ dh_gencontrol -p$(p_lgcc) -p$(p_lgccdbg) -p$(p_lgccudeb) \
-- -v$(DEB_LIBGCC_VERSION) $(common_substvars)
mkdir -p $(d_lgcc)/usr/share/lintian/overrides
echo '$(p_lgcc): package-name-doesnt-match-sonames' \
> $(d_lgcc)/usr/share/lintian/overrides/$(p_lgcc)
- dh_installdeb -p$(p_lgcc) -p$(p_lgccdbg)
- dh_md5sums -p$(p_lgcc) -p$(p_lgccdbg)
- dh_builddeb -p$(p_lgcc) -p$(p_lgccdbg)
+ dh_installdeb -p$(p_lgcc) -p$(p_lgccdbg) -p$(p_lgccudeb)
+ dh_md5sums -p$(p
Re: Bug#433568: VLANs during install are important
On Friday 29 January 2010, Josef Wolf wrote: > Since the interface name can be used to decide whether to activate vlan > support, no new debconf questions (like netcfg/enable_vlan or something) > are needed, IMHO. Doesn't that already answer your question about the user interface? :-) One request: please make vlan support optional so that netcfg still works when the bits needed for it are not available. It's probably not relevant for all architectures. For installs where netcfg is run after anna (CD-based installs), the loading of additional udebs should probably be done by the relevant part of hw-detect (ethdetect) and not by netcfg itself. And for e.g. netboot images the vlan udeb would need to be included in the initrd for relevant architectures. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Seg faults on PowerPC Re: [RFT]: Debian Installer - Pre-Alpha1 images ready for testing
severity 564150 grave merge 562575 564150 thanks On Freitag, 29. Januar 2010, Rick Thomas wrote: > The PowerPC installer suffers from bug # 564150 cheers, Holger signature.asc Description: This is a digitally signed message part.
Processed: Re: Seg faults on PowerPC Re: [RFT]: Debian Installer - Pre-Alpha1 images ready for testing
Processing commands for cont...@bugs.debian.org: > severity 564150 grave Bug #564150 [installation-reports] Segmentation fault on iBook Severity set to 'grave' from 'normal' > merge 562575 564150 Bug#562575: installation-reports: Buisnesscard PowerPC installer loops with Segmentation faults Bug#564150: Segmentation fault on iBook Merged 562575 564150. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#433568: VLANs during install are important
j...@raven.inka.de wrote: >The rest would be mostly straight forward: load stp, garp and 8021q modules, Why do you believe that STP and GARP are needed for a network edge node? -- ciao, Marco -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#567182: gcc: Please add libgcc1-udeb for Debian Installer
Hello, On Thu, Jan 28, 2010 at 11:30 AM, Frans Pop wrote: > I'm still not convinced that the (IMO minor) disadvantages of having a udeb > in gcc are sufficient to treat gcc different from all other packages that > provide udebs. With britney support it won't change anything for GCC maintainers since it will migrate automatically when it is ready (normal rules for testing) so I see no point in making it harder using an extra source. -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#433568: VLANs during install are important
On Fri, Jan 29, 2010 at 10:49:50AM +, Marco d'Itri wrote: > j...@raven.inka.de wrote: > > >The rest would be mostly straight forward: load stp, garp and 8021q modules, > Why do you believe that STP and GARP are needed for a network edge node? In most cases, VLAN means _lots_ of interfaces, so chances are that it is not really an edge node. But this was not the reason why I included stp and garp. AFAIR, 8021q doesn't load without garp, which in turn doesn't load without stp (or the other way around). But I will double-check to make sure that only needed modules will be really loaded. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: [RFT]: Debian Installer - Pre-Alpha1 images ready for testing
On Thu, 2010-01-28 at 13:53 -0200, Otavio Salvador wrote:
> Hello,
>
> The images using last uploaded debian-installer are available for
> testing[1]; If all looks fine I'd like to call it "a release".
>
> 1. http://cdimage.debian.org/cdimage/squeeze_di_test1/
>
> I'd like to ask people to run tests using those so we can decide about
> releasing it or fixing any major issue.
The amd64+i386+powerpc netinst iso seems to be missing the
install.{386,amd}/xen directory. These are included in the daily builds
since VARIANTS=xen is set in the right places in cronjob.daily from
svn://svn.debian.org/debian-cd/setup.
Do I need to send a patch to somewhere else to have official release
builds include this variant?
Ian.
--
Ian Campbell
Current Noise: Roadsaw - Roadsaw
The price of success in philosophy is triviality.
-- C. Glymour.
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#433568: VLANs during install are important
On Fri, Jan 29, 2010 at 01:25:42PM +0100, Josef Wolf wrote: > On Fri, Jan 29, 2010 at 10:49:50AM +, Marco d'Itri wrote: > > >The rest would be mostly straight forward: load stp, garp and 8021q > > >modules, > > Why do you believe that STP and GARP are needed for a network edge node? > In most cases, VLAN means _lots_ of interfaces, so chances are that it is not > really an edge node. But this was not the reason why I included stp and garp. During the installation it is an edge node. > AFAIR, 8021q doesn't load without garp, which in turn doesn't load without > stp (or the other way around). But I will double-check to make sure that only > needed modules will be really loaded. Module dependencies are detected. Bastian -- There are certain things men must do to remain men. -- Kirk, "The Ultimate Computer", stardate 4929.4 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#433568: VLANs during install are important
On Sun, Jan 17, 2010 at 09:35:47PM +0100, Josef Wolf wrote: > 2. Install vlan package into installer environment. Only the vconfig >binary (9kb) is really needed. But it needs libc6. Is this an issue? Not needed: | config VCONFIG | bool "vconfig" | default n | help | Creates, removes, and configures VLAN interfaces Bastian -- Women are more easily and more deeply terrified ... generating more sheer horror than the male of the species. -- Spock, "Wolf in the Fold", stardate 3615.4 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#433568: VLANs during install are important
On Fri, Jan 29, 2010 at 09:44:21AM +0100, Frans Pop wrote: Thanks for your response, Frans! > On Friday 29 January 2010, Josef Wolf wrote: > > Since the interface name can be used to decide whether to activate vlan > > support, no new debconf questions (like netcfg/enable_vlan or something) > > are needed, IMHO. > > Doesn't that already answer your question about the user interface? :-) I just wanted to double check that this method would be in-line with the design of d-i and the opinions of the core-developer. As you can see, it was good to ask :-) > One request: please make vlan support optional so that netcfg still works > when the bits needed for it are not available. It's probably not relevant > for all architectures. Hmm, I intended to make it the other way around: netcfg would anna-install the vlan stuff only when it sees that the chosen interface matches one of the patterns for vlan interfaces. > For installs where netcfg is run after anna (CD-based installs), the > loading of additional udebs should probably be done by the relevant part > of hw-detect (ethdetect) and not by netcfg itself. But at that time the interface chosen interface is not known. So deducing from chosen interface name (as outlined above) is not possible and this method would only work with preseeding or if additional questions are asked. > And for e.g. netboot > images the vlan udeb would need to be included in the initrd for relevant > architectures. Oh, I've completely forgotten about netboot. To be honest, I have no clue what this means exactly. Can you point me to some information about that? BTW: Actually there are two udebs: - one udeb created from vlan.deb (only the XC-Package-Type line needs to be added to debian/control) - the kernel modules would be created via kernel-wedge Is it OK to do it this way or does d-i have its own framework to create the udebs? -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: [RFT]: Debian Installer - Pre-Alpha1 images ready for testing
On Fri, 2010-01-29 at 13:02 +, Ian Campbell wrote:
> On Thu, 2010-01-28 at 13:53 -0200, Otavio Salvador wrote:
> > Hello,
> >
> > The images using last uploaded debian-installer are available for
> > testing[1]; If all looks fine I'd like to call it "a release".
> >
> > 1. http://cdimage.debian.org/cdimage/squeeze_di_test1/
> >
> > I'd like to ask people to run tests using those so we can decide about
> > releasing it or fixing any major issue.
>
> The amd64+i386+powerpc netinst iso seems to be missing the
> install.{386,amd}/xen directory. These are included in the daily builds
> since VARIANTS=xen is set in the right places in cronjob.daily from
> svn://svn.debian.org/debian-cd/setup.
>
> Do I need to send a patch to somewhere else to have official release
> builds include this variant?
Oh, nevermind, these are full DVD images not netinsts.
Ian.
--
Ian Campbell
Current Noise: Mötley Crüe - Kickstart My Heart
You can always tell luck from ability by its duration.
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#433568: VLANs during install are important
On Friday 29 January 2010, Bastian Blank wrote: > On Sun, Jan 17, 2010 at 09:35:47PM +0100, Josef Wolf wrote: > > 2. Install vlan package into installer environment. Only the vconfig > >binary (9kb) is really needed. But it needs libc6. Is this an > > issue? > > Not needed: > | config VCONFIG > | bool "vconfig" > | default n > | help > | Creates, removes, and configures VLAN interfaces Just to be clear: that's a busybox option that's currently disabled. You can simply build a custom version of busybox with it enabled (see debian/config/udeb) for your development and testing before requesting it to be enabled. It can then be enabled when we have a full (tested) set of patches. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#433568: VLANs during install are important
On Friday 29 January 2010, Josef Wolf wrote: > But at that time the interface chosen interface is not known. So > deducing from chosen interface name (as outlined above) is not possible > and this method would only work with preseeding or if additional > questions are asked. No. The sequence should be: - if the interfaces are there, hw-setup should install additional needed stuff - if additional needed stuff is not available, netcfg should not offer the interfaces for selection > > And for e.g. netboot > > images the vlan udeb would need to be included in the initrd for > > relevant architectures. > > Oh, I've completely forgotten about netboot. To be honest, I have no > clue what this means exactly. Can you point me to some information about > that? Just build the target and use the mini.iso for your development and testing. It's by far the easiest way to develop new functionality anyway. See further the document I pointed t earlier, especially the comments about localudebs and pkg-lists/local. > BTW: > Actually there are two udebs: > - one udeb created from vlan.deb (only the XC-Package-Type line needs > to be added to debian/control) Not needed according to Bastian. > - the kernel modules would be created via kernel-wedge Correct. Only question is whether they should be in a separate udeb, or included in one of the existing network-drivers udebs. That depends on: - size - whether it is generally needed/useful or only for selected arches. I think a separate udeb is the best option to start with. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Daily Debian Installer builds
FYI I've taken over the daily builds of Debian Installer for s390 as lophos has been down for well over a month now. If the service on lophos is ever reinstated, or if someone wants to set up (and manage) the builds on a regular buildd I'll be happy to stop them again. The link on the D-I page [1] (after next website build) and the build overview page have been updated. Cheers, FJP [1] http://www.debian.org/devel/debian-installer/index.html signature.asc Description: This is a digitally signed message part.
Re: [RFT]: Debian Installer - Pre-Alpha1 images ready for testing
Hi, Otavio Salvador wrote: > I'd like to ask people to run tests using those so we can decide about > releasing it or fixing any major issue. An i18n issue regarding the changed localechooser dialogs: performed an expert install. Choose german as language. The next page looks like this: -- Wählen Sie Ihren Standort The selected location will be used to set your time zone and also for example to help select the system locale. ... Diese Liste enthält nur eine kleine Auswahl von Standorten, basierend auf ... Country, territory or area: -- - So, the first line is localized (german translation, correct) - The second chapter is NOT LOCALIZED (is in english !) - The third chapter is localized (german translation, correct) - The last line is NOT LOCALIZED (is in english !) I checked this for french and dutch, the problem exists there, too. Holger -- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Created with Sylpheed 2.5.0 under DEBIAN GNU/LINUX 5.0.0 - L e n n y Registered LinuxUser #311290 - http://counter.li.org/ = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: [RFT]: Debian Installer - Pre-Alpha1 images ready for testing
On Friday 29 January 2010, Holger Wansing wrote: > - So, the first line is localized (german translation, correct) > - The second chapter is NOT LOCALIZED (is in english !) > - The third chapter is localized (german translation, correct) > - The last line is NOT LOCALIZED (is in english !) You're right. I'd noticed it as well, but ignored it as just a result of incomplete translations :-/ I've uploaded a fixed version. Cheers, FJP -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processing of localechooser_2.24_amd64.changes
localechooser_2.24_amd64.changes uploaded successfully to localhost along with the files: localechooser_2.24.dsc localechooser_2.24.tar.gz localechooser_2.24_amd64.udeb Greetings, Your Debian queue daemon (running on host ries.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processing of choose-mirror_2.32_amd64.changes
choose-mirror_2.32_amd64.changes uploaded successfully to localhost along with the files: choose-mirror_2.32.dsc choose-mirror_2.32.tar.gz choose-mirror_2.32_all.udeb choose-mirror-bin_2.32_amd64.udeb Greetings, Your Debian queue daemon (running on host ries.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
choose-mirror_2.32_amd64.changes ACCEPTED
Accepted: choose-mirror-bin_2.32_amd64.udeb to main/c/choose-mirror/choose-mirror-bin_2.32_amd64.udeb choose-mirror_2.32.dsc to main/c/choose-mirror/choose-mirror_2.32.dsc choose-mirror_2.32.tar.gz to main/c/choose-mirror/choose-mirror_2.32.tar.gz choose-mirror_2.32_all.udeb to main/c/choose-mirror/choose-mirror_2.32_all.udeb Override entries for your package: choose-mirror-bin_2.32_amd64.udeb - extra debian-installer choose-mirror_2.32.dsc - source debian-installer choose-mirror_2.32_all.udeb - extra debian-installer Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 502245 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#502245: marked as done (choose-mirror: incorrect translation generated for se)
Your message dated Fri, 29 Jan 2010 23:34:38 + with message-id and subject line Bug#502245: fixed in choose-mirror 2.32 has caused the Debian Bug report #502245, regarding choose-mirror: incorrect translation generated for se 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.) -- 502245: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502245 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: choose-mirror Version: 2.27 Severity: serious During some testing I noticed that when Northern Sami is selected as language, the countrylist during mirror selection consists of country codes instead of country names. The template.dat file contains: Name: mirror/http/countries Type: select [...] Default-se.UTF-8: US Choices-se.UTF-8: enter information manually, AR, AT, AU, BE, BG, BR, BY, CA, CH, CL, CN, CZ, DE, DK, EE, ES, FI, FR, GB, GR, HK, HR, HU, ID, IE, IL, IN, IS, IT, JP, KR, LT, LV, MT, MX, NC, NI, NL, NO, NZ, PF, PL, PT, RO, RU, SE, SG, SI, SK, SV, TH, TR, TW, UA, US, UZ, VE, ZA Indices-se.UTF-8: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59 Apparently for some reason we generate the template file incorrectly for se. signature.asc Description: This is a digitally signed message part. --- End Message --- --- Begin Message --- Source: choose-mirror Source-Version: 2.32 We believe that the bug you reported is fixed in the latest version of choose-mirror, which is due to be installed in the Debian FTP archive: choose-mirror-bin_2.32_amd64.udeb to main/c/choose-mirror/choose-mirror-bin_2.32_amd64.udeb choose-mirror_2.32.dsc to main/c/choose-mirror/choose-mirror_2.32.dsc choose-mirror_2.32.tar.gz to main/c/choose-mirror/choose-mirror_2.32.tar.gz choose-mirror_2.32_all.udeb to main/c/choose-mirror/choose-mirror_2.32_all.udeb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 502...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Frans Pop (supplier of updated choose-mirror package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 29 Jan 2010 23:45:47 +0100 Source: choose-mirror Binary: choose-mirror choose-mirror-bin Architecture: source all amd64 Version: 2.32 Distribution: unstable Urgency: low Maintainer: Debian Install System Team Changed-By: Frans Pop Description: choose-mirror - Choose mirror to install from (menu item) (udeb) choose-mirror-bin - Choose mirror to install from (program) (udeb) Closes: 502245 Changes: choose-mirror (2.32) unstable; urgency=low . * Improve generation of country selection templates to avoid display of untranslated country codes. Closes: #502245. * Use Norwegian Bokmaal country names if no iso-codes translation is available for Northern Sami. . [ Updated translations ] * Belarusian (be.po) by Pavel Piatruk * German (de.po) by Holger Wansing * Greek, Modern (1453-) (el.po) * Spanish (es.po) by Javier Fernández-Sanguino Peña * Finnish (fi.po) by Esko Arajärvi * Hungarian (hu.po) by SZERVÁC Attila * Polish (pl.po) by Bartosz Fenski * Portuguese (pt.po) by Miguel Figueiredo * Slovenian (sl.po) by Vanja Cvelbar * Turkish (tr.po) by Mert Dirik * Simplified Chinese (zh_CN.po) by 苏运强 Checksums-Sha1: bbcc786c511777397fe09dda92af29bd873dd226 1020 choose-mirror_2.32.dsc 3ec5184e92385c44cab31f3403f9078a8fb2fc4b 185256 choose-mirror_2.32.tar.gz 7c9670dfa1a79093f198216a49f2ba353f6f2ef2 930 choose-mirror_2.32_all.udeb f5ce5840f7f5e464ad35250e8a4582b1812c94b6 146888 choose-mirror-bin_2.32_amd64.udeb Checksums-Sha256: 858d101e851ad80d9f2a157b8030e6424e1a9ac18a4815dad28d91b9b34ca7fc 1020 choose-mirror_2.32.dsc dcd9e9bdf0031acb6fdf37b32d5011c7eea2bc71dc1d63b23014a899b21551e4 185256 choose-mirror_2.32.tar.gz 39777bf578866a1c111592756f31cf7c4e49966e104d28fce9a57485570dd781 930 choose-mirror_2.32_all.udeb 14798ebe220b5184751237a083841fd039d51149844ead485f61eb34b908c89f 146888 choose-mirror-bin_2.32_amd64.udeb Files: 2de78d670d6cda9f412e0f3d8210948a 1020 debian-installer extra choos
Re: Bug#433568: VLANs during install are important
On Fri, Jan 29, 2010 at 02:54:58PM +0100, Frans Pop wrote: > On Friday 29 January 2010, Josef Wolf wrote: > > But at that time the interface chosen interface is not known. So > > deducing from chosen interface name (as outlined above) is not possible > > and this method would only work with preseeding or if additional > > questions are asked. > > No. The sequence should be: > - if the interfaces are there, hw-setup should install additional needed > stuff > - if additional needed stuff is not available, netcfg should not offer > the interfaces for selection Umm, I don't think this would work with vlan. See, a vlan is not a piece of hardware that you can auto detect. All that you get is your normal network interface (e.g. eth0) which you have anyway. Although this interface is detected, there is no way to tell whether you want to run vlans on that interface or whether you want to use it as an ordinary iface. AFAICS, all you can get from hw-setup is your plain-vanilla interface (e.g. eth0). The vlan interfaces won't spring into existence until you load the required kernel modules and create them with commands like vconfig set_name_type DEV_PLUS_VID_NO_PAD vconfig eth0 5 This will create eth0.5 (may get a different name, depends on the naming scheme, which has also to be configured by vconfig, as shown above) See the chicken+egg problem here? You have to load the modules and execute vconfig to create the interface. So you can not rely on hw-setup to load the udebs since there's no way for hw-setup to know that the vlan udebs need to be loaded in the first place. This is why my original proposal was to decide from the value of netcfg/chosen_interface whether to load/configure all the vlan stuff. If chosen_interface matches one of the vlan naming schemes, then load and configure the vlan stuff appropriately. AFAICS, hw-setup is too early to parse chosen_interface and decide whether it matches one of the vlan naming schemes. > > > And for e.g. netboot > > > images the vlan udeb would need to be included in the initrd for > > > relevant architectures. > > > > Oh, I've completely forgotten about netboot. To be honest, I have no > > clue what this means exactly. Can you point me to some information about > > that? > > Just build the target and use the mini.iso for your development and > testing. It's by far the easiest way to develop new functionality anyway. Building the installer is not exactly an everyday-task for me, so please be patient with me. It may take some time until I get my head around it. BTW: I could use a little bit hand-holding on this topic ;-) > See further the document I pointed t earlier, especially the comments about > localudebs and pkg-lists/local. Somehow I managed to miss that, and google seems not to have it in its index (yet?). Can you give me some more pointer? > > BTW: > > Actually there are two udebs: > > - one udeb created from vlan.deb (only the XC-Package-Type line needs > > to be added to debian/control) > > Not needed according to Bastian. Would be just a change in a config option, right? So that's not really a big deal and could be done independently of the changes we are discussing in this thread, right? So, _PLEASE_ consider to activate this option independently from the results on this thread. Then, people would be able to configure vlans manually even if the efforts in this thread would fail for whatever reason... > > - the kernel modules would be created via kernel-wedge > > Correct. Only question is whether they should be in a separate udeb, or > included in one of the existing network-drivers udebs. That depends on: > - size > - whether it is generally needed/useful or only for selected arches. > > I think a separate udeb is the best option to start with. The required modules are (size might vary with kernel version...): 8021q.ko 32328 bytes garp.ko 13460 bytes stp.ko4456 bytes Thats a total of about 50 kbytes. BTW: I have double-checked now. 8021q won't load without garp. And garp won't load without stp. So I think the question that appeared earlier in this thread can be answered now: all three modules are needed. We would have to talk to the kernel developers to change that. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
localechooser_2.24_amd64.changes ACCEPTED
Accepted: localechooser_2.24.dsc to main/l/localechooser/localechooser_2.24.dsc localechooser_2.24.tar.gz to main/l/localechooser/localechooser_2.24.tar.gz localechooser_2.24_amd64.udeb to main/l/localechooser/localechooser_2.24_amd64.udeb Override entries for your package: localechooser_2.24.dsc - source debian-installer localechooser_2.24_amd64.udeb - optional debian-installer Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#433568: VLANs during install are important
On Saturday 30 January 2010, Josef Wolf wrote: > This is why my original proposal was to decide from the value of > netcfg/chosen_interface whether to load/configure all the vlan stuff. So you would *always* show vlan interfaces, even for regular users on normal systems? I don't think I like that idea very much. Note that during most installs the dialog to select an interface is not even displayed currently (if there's only one) and we certainly wouldn't want to change that. > Somehow I managed to miss that, and google seems not to have it in its > index (yet?). Can you give me some more pointer? It's also linked in the wiki, but: http://d-i.alioth.debian.org/doc/internals/ > Would be just a change in a config option, right? So that's not really a > big deal and could be done independently of the changes we are > discussing in this thread, right? It would also mean a size increase of the initrd for all architectures... We usually don't do make such changes lightly. > So, _PLEASE_ consider to activate this > option independently from the results on this thread. Then, people would > be able to configure vlans manually even if the efforts in this thread > would fail for whatever reason... Please check that it works first and try to implement proper support. If that does not work out we can always discuss alternatives. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#433568: VLANs during install are important
On Sat, Jan 30, 2010 at 01:07:04AM +0100, Frans Pop wrote: > On Saturday 30 January 2010, Josef Wolf wrote: > > This is why my original proposal was to decide from the value of > > netcfg/chosen_interface whether to load/configure all the vlan stuff. > > So you would *always* show vlan interfaces, even for regular users on > normal systems? I don't think I like that idea very much. > Note that during most installs the dialog to select an interface is not > even displayed currently (if there's only one) and we certainly wouldn't > want to change that. As I read the original proposal, it was actually only a preseeded option -- if you preseeded netcfg/choose_interface to have a VLANesque name (eth0.X), then vconfig would be invoked, otherwise no such luck. Personally, I think that if you're going to go to the trouble of implementing it, a (low) priority question would be worth the hassle, but personally I don't see why anyone would ever want to install over a *tagged* VLAN, myself. But then, I don't work in a fortress of intransigence, and I get to manage my own network ports. - Matt -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567590: debian-installer: GPT with RAID fails to install
Package: debian-installer Severity: normal I have a system containing two 2TB SATA drives which I have configured into a RAID1 and am using through LVM. When using the Debian 5.03 amd64 installer, I was unable to use the partitioner provided in the menus to install. When the partitioner started, I created new partition tables on the otherwise empty drives. Because the drives are so large (2TB each), the installer wisely suggested that I use GPT rather than the traditional MBR partition table. I created a new GPT on each drive with a single partition (named "RAID1-0" and "RAID1-1" respectively). I then chose to configure software RAID; this is the point at which things broke down. I received an error message indicating that there were no Linux RAID/Autodetect partitions available and that I should format one of my drives to create one. It is my suspicion that the check to ensure that RAID partitions exist is assuming an MBR-style partition table. I ran an mdadm --create command from the secondary terminal and restarted the partitioner. When it rescanned the disks and discovered my RAID1 already in place, I was able to set up LVM without difficulty. -- System Information: Debian Release: 5.0.2 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (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/bash -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567590: Reproducable
I managed to reproduce the problem on my laptop with a KVM instance and two 8G QEMU drive images. I used the i386 Debian 5.03 net installer CD and started an expert install. I put a GPT on each of the two drives and created a single partition on each. I instructed the installer to use each as a physical device for software RAID. Here's the interesting bit. I sped through the menus and discovered that the RAID system was quite happy to create a RAID1 for me. I went back, deleted the RAID, and started over. The second time, I was able to reproduce the bug. The only difference between these two runs was that I remembered to flag both drives as bootable the second time. It seems that a bootable GPT partition is the problem; the RAID menu system doesn't seem to see it. (Again, mdadm works just fine.) Cheers, Zach -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
