Re: Final steps for Jessie Beta 1
Hi Cyril, Le mardi, 12 août 2014, 01.33:37 Cyril Brulebois a écrit : two parts in this mail: information for everyone, and action for debian-cd@ at the end. I wonder (but it's certainly too late now) whether it would make sense to unblock (+byhand FTP-Master's dance) win32-loader for the next Beta release: 0.7.4.10 only contains translation updates and dh+Vcs updates. As you can see a few lines above, we can wait for netcfg but that's a bug we already had in wheezy, so we can add an errata entry for it; so if you can start a build in the morning I don't see a reason for an extra 12-hour delay. If you're only available in the afternoon or in the evening, we might get netcfg fixed for free, which I'm also OK with. :) Can we add win32-loader to the load? Cheers, OdyX -- 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/18793619.yLpRgy0Hy8@gyllingar
Re: [Pkg-xfce-devel] Reverting to GNOME for jessie's default desktop
+++ Kees de Jong [2014-08-12 02:03 +0200]: Are we really comparing RAM here as if it were the 90's? How many people here use Android? Today it needs 512 MB to function properly. In two years that could be 1 or 2 GB and that's a mobile OS. How much RAM does your browser use? Too much! I agree browsers use more ram than desktops these days, or at least the big ones (firefox, chrome) do. My Chrome/Firefox easily uses 1 GB. My GNOME 3.10 desktop (running Fedora now because I needed a modern GNOME version for Exchange support for work) is using about 800 MB to 1200 MB. Do I really care? No, because RAM is cheap and I have 8 GB. Do I need to buy more? No, because 8 GB is still more than enough. That's fine so long as your hardware is new enough to take more memory. Anyone with an ARM machine will be in the 512MB/1G/2G camp. My laptop (x200s) officially maxes out at 4G, although it turns out that 8G does actually work in practice. Memory usage does still matter as your hardware doesn't have to be particularly old to have RAM of a size that is likely to all get used, and on arm (increasingly being used for netbook/laptop/desktop usage) it's practically guaranteed. So yes, it's not the 1990s but I think we should aim to make Debian to work tolerably well on 2 or 4G systems. Alistair posted numbers suggesting 600MB for gnome3 or KDE, 360 for XFCE, 300 for LXDE, which is a difference, but not a huge one. Very significant on a 512MB machine, but not that significant on 2G. You say 800-1200 above which is twice as much. Is this the differnce between initial boot up and usage after some time, or 'various add-ons'? Knowing what 'typical' numbers are would be useful. I have various well-used XFCE desktops I could check but I'm not sure how to get a cmparable RAM-usage number of them. If you can't run GNOME because you don't have the system specs to run a modern desktop then you can select XFCE/LXDE in the installation menu. But let's be fair, those people are a minority. And a default should fit the needs of the majority. And since people easily have 4 GB of RAM or more these days with the basic 3D acceleration I only had 2G RAM till last year (when I had to buy some more because browsers take so much damn RAM). I think we should at least consider those people in the 'typical machines' bucket. (even a Raspberry Pi can run GNOME 3) A Pi is only 512MB, so 'barely'. Like most arm hardware memory levels are still low by modern x86 standards. They are like late 90s/early 2000s x86 machines in this regard. I don't want to over-emphasise the arm thing - it is still a minority sport - but it's a growing area of usage where memory is still limited. I just wanted to counter a little the 'everyone has buckets of RAM these days' view, whilst acnowledging that it is no longer the 90's and a 512Mb machine will struggle with any modern desktop+browser (which is sad IMHO - dawkins knows what software, especially browsers, do with all that memory! - hundreds of Mb for simple tables of built packages, for example, but I digress :-) Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140812085008.gl7...@stoneboat.aleph1.co.uk
Re: [Pkg-xfce-devel] Reverting to GNOME for jessie's default desktop
+++ Anthony F McInerney [2014-08-12 00:02 +0100]: XFCE: total used free sharedbuffers cached Mem:506756 362468 144288 6568 22756 179264 -/+ buffers/cache: 160448 346308 Swap: 392188 0 392188 GNOME: total used free sharedbuffers cached Mem:506756 500360 6396 1948840 37724 -/+ buffers/cache: 461796 44960 Swap: 392188 66672 325516 LXDE: total used free sharedbuffers cached Mem:506756 316504 190252 8500 18920 149812 -/+ buffers/cache: 147772 358984 Swap: 392188 0 392188 KDE: total used free sharedbuffers cached Mem:506756 499724 7032 6772 10516 109760 -/+ buffers/cache: 379448 127308 Swap: 392188 21632 370556 Thanks for this, interesting. Could you do MATE too please? Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140812085136.gm7...@stoneboat.aleph1.co.uk
Re: [Pkg-xfce-devel] Reverting to GNOME for jessie's default desktop
Le mardi 12 août 2014 à 03:03 +0100, Anthony F McInerney a écrit : I had stated previously XFCE had started showing memory usage similar to gnome. This has quite obviously changed. I was wrong, and i'm posting it as a correction to my statement. You’re comparing apples and oranges. These memory usage comparisons are only useful at feature parity - which doesn’t exist, since different environments have different paradigms and different feature sets. How much RAM does your browser use? Lots, which is why i prefer my DE not to eat it all. When the browser uses 1 GB while GNOME (including evolution and many other running applications) uses half of that, I don’t think you need to look for memory savings in the desktop. You need to buy more RAM and that’s all, because browsers won’t suddenly stop needing their gigabyte. If you can't run GNOME because you don't have the system specs to run a modern desktop then you can select XFCE/LXDE in the installation menu. But let's be fair, those people are a minority. And a default should fit the needs of the majority. Ahh good you have statistics for that. Please link them, or quote and cite sources. I just had a look at an online hardware store. Out of their 682 laptops and 332 desktops: * 1 model has 1 GiB * 48 models have 2 GiB * 470 models have 4 GiB * 495 have 6 GiB or more Which means 0,1% of the machines you can buy are not able to run a web browser anyway, 5% are more than enough for a full-fledged GNOME+web browser, and all the rest are very comfortable with anything you can run under Linux. Some people like the 'basic 3d acceleration' for other things, so not only do you want me to sacrifice my RAM to all powerful DE, but also my GPU? How kind of you ;) We happen at work to have users with very important needs of 3D resources, so one of my colleagues conducted some performance tests with and without a compositor (the compositor being GNOME 3). It turns out that with a recent adapter, 3D applications are running a small bit faster under GNOME, and that’s probably because it saves your graphics card the pain to switch from 2D to 3D contexts. -- .''`.Josselin Mouette : :' : `. `' `- -- 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/1407838921.26277.435.camel@dsp0698014
Re: Final steps for Jessie Beta 1
Didier 'OdyX' Raboud o...@debian.org (2014-08-12): Hi Cyril, Le mardi, 12 août 2014, 01.33:37 Cyril Brulebois a écrit : two parts in this mail: information for everyone, and action for debian-cd@ at the end. I wonder (but it's certainly too late now) whether it would make sense to unblock (+byhand FTP-Master's dance) win32-loader for the next Beta release: 0.7.4.10 only contains translation updates and dh+Vcs updates. If by next Beta release you mean Beta 2, sure. :) Mraw, KiBi. signature.asc Description: Digital signature
Re: Jessie: network link detection problems with Intel nics
Hi, and thanks for your report (even if the best way is filing a proper bug report in the BTS: https://www.debian.org/Bugs/). Floris Bos b...@je-eigen-domein.nl (2014-08-12): I'm having an odd problem on one of my servers in which the network link is not detected (error getting DHCP, going to console and entering ip link shows NO_CARRIER) on preseeded Jessie installations. Mainboard: http://www.supermicro.nl/products/motherboard/Xeon/C220/X10SLM_-LN4F.cfm 4x i210AT NIC on mainboard, cable connected to eth0 Problem always occurs on: - Debian Jessie when doing automated installations - Ubuntu 13.10 netinstall - Ubuntu 14.04 netinstall Problem does not occurs on: - Debian Wheezy Problem sometimes occurs on: - Interactive installations on Debian Jessie. They work most of the time, but not always. A few things that come to mind: - what if there's an extra cable plugged on to a NIC that isn't the one you PXE-booted from? There might be something going on that could be related to the boot method, like a faulty initialization somewhere because there was already some traffic on that interface. - what if you try to unload and reload the igb module? I've just checked that modprobe -r $foo and modprobe $foo work just fine from a console in the installer context. Mraw, KiBi. signature.asc Description: Digital signature
Re: [Pkg-xfce-devel] Reverting to GNOME for jessie's default desktop
On 12 August 2014 09:51, Wookey woo...@wookware.org wrote: Could you do MATE too please? MATE: (with mate-desktop-environment-extras) free ^[[C total used free shared buffers cached Mem: 506756 397480 109276 7096 58820 166076 -/+ buffers/cache: 172584 334172 Swap: 392188 0 392188 The ctrl characters came with it apparently. And as an extra, Gnome Classical: free total used free shared buffers cached Mem: 506756 498240 8516 2452 5972 71360 -/+ buffers/cache: 420908 85848 Swap: 392188 16292 375896
Bug#757920: debian-installer: vesamenu.c32 is not a COM32R image
Package: debian-installer Version: Severity: normal Tags: d-i Dear Maintainer, * What led up to the situation? I want to install Debian/testing on a new computer. * What exactly did you do (or not do) that was effective (or ineffective)? I upgraded the PXE installer for testing using di-netboot-assistant, then I tried to install with it. * What was the outcome of this action? I expected the installer to run. * What outcome did you expect instead? The installer failed with the error vesamenu.c32 is not a COM32R image (written from memory). When I compare the vesamenu.c32 files in the testing and daily installers with the same files from stable and some Ubuntu version there are some differences: * The working files have a size about 150kB and are COM executable * The problematic files have a size of 26kB and are ELF 32-bit LSB shared object This is an example of a good file: http://ftp.fr.debian.org/debian/dists/testing/main/installer-amd64/20140316/images/netboot/debian-installer/amd64/boot-screens/vesamenu.c32 This is a bad file: http://ftp.fr.debian.org/debian/dists/testing/main/installer-amd64/20140802/images/netboot/debian-installer/amd64/boot-screens/vesamenu.c32 Regards, Kim Hansen -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20140812114941.6292.82288.report...@leon.kontor.ange.dk
Bug#757920: debian-installer: vesamenu.c32 is not a COM32R image
Hi Kim, and thanks for your detailed bug report. Kim R. T. Hansen k...@rthansen.dk (2014-08-12): Package: debian-installer Version: Severity: normal Tags: d-i Dear Maintainer, * What led up to the situation? I want to install Debian/testing on a new computer. * What exactly did you do (or not do) that was effective (or ineffective)? I upgraded the PXE installer for testing using di-netboot-assistant, then I tried to install with it. * What was the outcome of this action? I expected the installer to run. * What outcome did you expect instead? The installer failed with the error vesamenu.c32 is not a COM32R image (written from memory). When I compare the vesamenu.c32 files in the testing and daily installers with the same files from stable and some Ubuntu version there are some differences: * The working files have a size about 150kB and are COM executable * The problematic files have a size of 26kB and are ELF 32-bit LSB shared object This is an example of a good file: http://ftp.fr.debian.org/debian/dists/testing/main/installer-amd64/20140316/images/netboot/debian-installer/amd64/boot-screens/vesamenu.c32 This is a bad file: http://ftp.fr.debian.org/debian/dists/testing/main/installer-amd64/20140802/images/netboot/debian-installer/amd64/boot-screens/vesamenu.c32 The fact you're using di-netboot-assistant is interesting, maybe it would have needed an update for the syslinux 6 transition? The code can be viewed online here: http://anonscm.debian.org/cgit/d-i/netboot-assistant.git/tree/di-netboot-assistant#n236 It seems there's some *.c32-specific handling, and there's even a mention of a (probably previous) transition for menu related files. I think we would have had more reports if PXE was broken in the general case so I suspect this might be a regression only in the d-i netboot assistant case. I'm adding Ron since he looked quite closely at d-i + syslinux lately, so he might have some expertise to share here. ;) Mraw, KiBi. signature.asc Description: Digital signature
Re: [Pkg-xfce-devel] Reverting to GNOME for jessie's default desktop
We happen at work to have users with very important needs of 3D resources, so one of my colleagues conducted some performance tests with and without a compositor (the compositor being GNOME 3). It turns out that with a recent adapter, 3D applications are running a small bit faster under GNOME, and that’s probably because it saves your graphics card the pain to switch from 2D to 3D contexts. Virtualbox Results (no guest drivers installed) Gnome: glxgears 1267 frames in 5.0 seconds = 253.150 FPS 1197 frames in 5.0 seconds = 239.372 FPS 1174 frames in 5.0 seconds = 234.753 FPS 1142 frames in 5.0 seconds = 228.005 FPS 1201 frames in 5.0 seconds = 239.898 FPS 1217 frames in 5.0 seconds = 243.075 FPS 1194 frames in 5.0 seconds = 238.475 FPS Gnome-Classic: glxgears 1150 frames in 5.0 seconds = 229.772 FPS 1267 frames in 5.0 seconds = 253.212 FPS 1240 frames in 5.0 seconds = 247.875 FPS 1272 frames in 5.0 seconds = 254.374 FPS 1314 frames in 5.0 seconds = 262.673 FPS 1279 frames in 5.0 seconds = 255.684 FPS XFCE: glxgears 2110 frames in 5.0 seconds = 421.982 FPS 2290 frames in 5.0 seconds = 457.800 FPS 2241 frames in 5.0 seconds = 448.046 FPS 2279 frames in 5.0 seconds = 455.636 FPS 2191 frames in 5.0 seconds = 438.094 FPS 2246 frames in 5.0 seconds = 449.114 FPS 2218 frames in 5.0 seconds = 443.590 FPS Please note xfce was installed on the same vm, that gnome / gnome-classic was on. It was therefore using much more memory, (it seems GDM + other gnome services are causing memory use, i will be testing that shortly). And here i will make a comparison. ahahahaha. That was it. Moving on. ;)
Re: [Pkg-xfce-devel] Reverting to GNOME for jessie's default desktop
Le mardi 12 août 2014 à 13:12 +0100, Anthony F McInerney a écrit : Virtualbox Results (no guest drivers installed) Glxgears is not a relevant 3D benchmark. But the funniest thing is that you did this test without any 3D acceleration, which is not representative at all of most real-world computers. Thanks for making the point that with llvmpipe, GNOME is perfectly usable on a machine without 3D. -- .''`.Josselin Mouette : :' : `. `' `- -- 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/1407846059.26277.455.camel@dsp0698014
Re: [Pkg-sysvinit-devel] Bug#757650: override: sysvinit:admin/optional sysvinit-core:admin/extra
On Mon, 11 Aug 2014, Cyril Brulebois wrote: Michael Biebl bi...@debian.org (2014-08-11): That is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754987 https://lists.debian.org/debian-user/2014/07/msg01509.html I know a workaround, but haven't figured out the underlying cause yet. FWIW I spent some time on #debian-systemd and idly noticed some mentions of a boot-time timeout; when Ben mentioned net.agent I finally connected the dots and we stopped spending more time on it. FWIW, make sure CONFIG_FW_LOADER_USER_HELPER is *NOT* set in the kernel config. I didn't check the reports above, so it is possible that this has already been checked. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- 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/20140812122812.ga22...@khazad-dum.debian.net
Re: Jessie: network link detection problems with Intel nics
On 08/12/2014 01:15 PM, Cyril Brulebois wrote: Hi, and thanks for your report (even if the best way is filing a proper bug report in the BTS: https://www.debian.org/Bugs/). Floris Bos b...@je-eigen-domein.nl (2014-08-12): I'm having an odd problem on one of my servers in which the network link is not detected (error getting DHCP, going to console and entering ip link shows NO_CARRIER) on preseeded Jessie installations. Mainboard: http://www.supermicro.nl/products/motherboard/Xeon/C220/X10SLM_-LN4F.cfm 4x i210AT NIC on mainboard, cable connected to eth0 Problem always occurs on: - Debian Jessie when doing automated installations - Ubuntu 13.10 netinstall - Ubuntu 14.04 netinstall Problem does not occurs on: - Debian Wheezy Problem sometimes occurs on: - Interactive installations on Debian Jessie. They work most of the time, but not always. A few things that come to mind: - what if there's an extra cable plugged on to a NIC that isn't the one you PXE-booted from? There might be something going on that could be related to the boot method, like a faulty initialization somewhere because there was already some traffic on that interface. Hmm, that is strange as well. With a second cable connected to one of the other ports it does work, even when PXE booting from eth0, and telling Debian to use eth0. Which doesn't work without the second cable. It doesn't see the link on eth0 straight away, only after deactivating and activating. == Aug 12 14:49:43 netcfg[1663]: INFO: Activating interface eth0 Aug 12 14:49:44 netcfg[1663]: INFO: Waiting time set to 3 Aug 12 14:49:44 kernel: [ 12.793292] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Aug 12 14:49:44 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected. Aug 12 14:49:44 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected. Aug 12 14:49:45 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected. Aug 12 14:49:45 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected. Aug 12 14:49:45 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected. Aug 12 14:49:45 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected. Aug 12 14:49:46 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected. Aug 12 14:49:46 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected. Aug 12 14:49:46 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected. Aug 12 14:49:46 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected. Aug 12 14:49:47 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected. Aug 12 14:49:47 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected. Aug 12 14:49:47 netcfg[1663]: INFO: Reached timeout for link detection on eth0 Aug 12 14:49:47 netcfg[1663]: INFO: found no link on interface eth0. Aug 12 14:49:47 netcfg[1663]: INFO: eth0 is not a wireless interface. Continuing. Aug 12 14:49:47 netcfg[1663]: INFO: Taking down interface eth0 Aug 12 14:49:47 netcfg[1663]: INFO: Taking down interface eth0 Aug 12 14:49:47 netcfg[1663]: INFO: Activating interface eth1 Aug 12 14:49:48 netcfg[1663]: INFO: Waiting time set to 3 Aug 12 14:49:48 kernel: [ 16.683201] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready Aug 12 14:49:48 netcfg[1663]: INFO: ethtool-lite: eth1 is disconnected. Aug 12 14:49:48 netcfg[1663]: INFO: ethtool-lite: eth1 is disconnected. Aug 12 14:49:49 netcfg[1663]: INFO: ethtool-lite: eth1 is disconnected. Aug 12 14:49:49 netcfg[1663]: INFO: ethtool-lite: eth1 is disconnected. Aug 12 14:49:49 netcfg[1663]: INFO: ethtool-lite: eth1 is disconnected. Aug 12 14:49:49 netcfg[1663]: INFO: ethtool-lite: eth1 is disconnected. Aug 12 14:49:50 netcfg[1663]: INFO: ethtool-lite: eth1 is disconnected. Aug 12 14:49:50 netcfg[1663]: INFO: ethtool-lite: eth1 is disconnected. Aug 12 14:49:50 netcfg[1663]: INFO: ethtool-lite: eth1 is disconnected. Aug 12 14:49:50 netcfg[1663]: INFO: ethtool-lite: eth1 is disconnected. Aug 12 14:49:51 netcfg[1663]: INFO: ethtool-lite: eth1 is disconnected. Aug 12 14:49:51 netcfg[1663]: INFO: ethtool-lite: eth1 is disconnected. Aug 12 14:49:51 netcfg[1663]: INFO: Reached timeout for link detection on eth1 Aug 12 14:49:51 netcfg[1663]: INFO: found no link on interface eth1. Aug 12 14:49:51 netcfg[1663]: INFO: eth1 is not a wireless interface. Continuing. Aug 12 14:49:51 netcfg[1663]: INFO: Taking down interface eth1 Aug 12 14:49:51 netcfg[1663]: INFO: Taking down interface eth1 Aug 12 14:49:51 netcfg[1663]: INFO: Activating interface eth2 Aug 12 14:49:52 netcfg[1663]: INFO: Waiting time set to 3 Aug 12 14:49:52 kernel: [ 20.572957] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready Aug 12 14:49:52 netcfg[1663]: INFO: ethtool-lite: eth2 is disconnected. Aug 12 14:49:52 netcfg[1663]: INFO: ethtool-lite: eth2 is disconnected. Aug 12 14:49:52 netcfg[1663]: INFO: ethtool-lite: eth2 is disconnected. Aug 12 14:49:53 netcfg[1663]: INFO: ethtool-lite: eth2 is disconnected. Aug 12 14:49:53 netcfg[1663]: INFO: ethtool-lite: eth2 is disconnected. Aug 12 14:49:53 netcfg[1663]: INFO: ethtool-lite: eth2 is
Re: Final steps for Jessie Beta 1
On Tue, Aug 12, 2014 at 01:33:37AM +0200, Cyril Brulebois wrote: Hi people, two parts in this mail: information for everyone, and action for debian-cd@ at the end. snip Bits of action: --- Steve, feel free to start a build whenever it's convenient for you (after the 1:52 dinstall + mirror pulse of course). As you can see a few lines above, we can wait for netcfg but that's a bug we already had in wheezy, so we can add an errata entry for it; so if you can start a build in the morning I don't see a reason for an extra 12-hour delay. If you're only available in the afternoon or in the evening, we might get netcfg fixed for free, which I'm also OK with. :) Bottom line: Whatever works for you! FTAOD: I started building CDs this morning, they'll be ready soon-ish. -- Steve McIntyre, Cambridge, UK.st...@einval.com The problem with defending the purity of the English language is that English is about as pure as a cribhouse whore. We don't just borrow words; on occasion, English has pursued other languages down alleyways to beat them unconscious and rifle their pockets for new vocabulary. -- James D. Nicoll -- 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/20140812132850.ga11...@einval.com
Re: [Pkg-xfce-devel] Reverting to GNOME for jessie's default desktop
I enjoy the way you keep ignoring the relevant points, memory usage and performance regressions. And the way you benchmarked gnome against gnome. How about warsaw on xfce on the same hardware or your benchmarks pretty much show nothing except that your 'slight performance increase when using gnome-shell' is pure fabrication. On 12 August 2014 13:20, Josselin Mouette j...@debian.org wrote: Le mardi 12 août 2014 à 13:12 +0100, Anthony F McInerney a écrit : Virtualbox Results (no guest drivers installed) Glxgears is not a relevant 3D benchmark. But the funniest thing is that you did this test without any 3D acceleration, which is not representative at all of most real-world computers. Thanks for making the point that with llvmpipe, GNOME is perfectly usable on a machine without 3D. -- .''`.Josselin Mouette : :' : `. `' `-
Re: [Pkg-xfce-devel] Reverting to GNOME for jessie's default desktop
On Tue, Aug 12, 2014 at 12:22:01PM +0200, Josselin Mouette wrote: I just had a look at an online hardware store. Out of their 682 laptops and 332 desktops: * 1 model has 1 GiB * 48 models have 2 GiB * 470 models have 4 GiB * 495 have 6 GiB or more Which means 0,1% of the machines you can buy are not able to run a web browser anyway, 5% are more than enough for a full-fledged GNOME+web browser, and all the rest are very comfortable with anything you can run under Linux. I must be in the 0.1% then. I have a 1GB machine. I have no trouble running Chrome or Chromium. Or even both of those at the same time. But then, I'm using XFCE instead of Gnome. -- hendrik -- 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/20140812133809.ga22...@topoi.pooq.com
Re: Reverting to GNOME for jessie's default desktop
Jordi Mallach writes (Reverting to GNOME for jessie's default desktop): It's been around 9 months since tasksel changed (for real) the default desktop for new installs. At the time of the change, it was mentioned the issue would be revisited before the freeze, around debconf time. Fascinating as this discussion is, I think it is at risk of becoming too much of a time sink. I think that it would be useful to have some authoritative guidance from those in Debian who are responsible for this decision. AFAICT that is the tasksel maintainers. So I would appreciate it if the tasksel maintainers would let us know: Do you intend to review (or are you reviewing) the decision taken in July 2012 [1] ? If so, is this discussion here on -devel useful ? If it is useful, what questions should we be focusing on ? Ian. [1] http://anonscm.debian.org/gitweb/?p=tasksel/tasksel.git;a=commit;h=2a962cc65cdba010177f27e8824ba10d9a799a08 -- 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/21482.8088.55315.575...@chiark.greenend.org.uk
Bug#757941: busybox-static: DNS resolver stopped working in busybox-static version 1.22.0-7
Package: busybox-static Version: 1:1.22.0-8 Severity: important When trying to ping an address, like debian.org, with busybox-static you get a ping: bad address 'debian.org' error. I knew that version 1.22.0-6 of busybox-static was working, so I also downloaded version 1.22.0-7 and 1.22.0-8 and tested those: # ./busybox-1.22.0-6 ping -c 1 debian.org PING debian.org (200.17.202.197): 56 data bytes 64 bytes from 200.17.202.197: seq=0 ttl=49 time=307.969 ms --- debian.org ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max = 307.969/307.969/307.969 ms # ./busybox-1.22.0-7 ping -c 1 debian.org ping: bad address 'debian.org' # ./busybox-1.22.0-8 ping -c 1 debian.org ping: bad address 'debian.org' So that means this bug was introduced with version 1.22.0-7. Note that the non-static version does work properly (tested version 1.22.0-8). It makes the package rather unusable, but I'll leave it up to the maintainer to raise the severity. Regards, Diederik -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (150, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information -- 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/20140812153024.11865.47994.report...@bagend.home.cknow.org
Bug#757941: busybox-static: DNS resolver stopped working in busybox-static version 1.22.0-7
Control: tag -1 + confirmed 12.08.2014 19:30, Diederik de Haas wrote: Package: busybox-static Version: 1:1.22.0-8 Severity: important When trying to ping an address, like debian.org, with busybox-static you get a ping: bad address 'debian.org' error. Yes, this is what we have. Current busybox-static in wheezy+ does not work. What's interesting - I compiled busybox-static on curent wheezy host, the resulting binary works fine. But the same busybox compiled on jessie does not work. Also, it is specific to amd64 arch, it does not happen on i386 (from 2 variants of x86 arches). Thanks, /mjt -- 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/53ea4bd6.4050...@msgid.tls.msk.ru
Processed: Re: Bug#757941: busybox-static: DNS resolver stopped working in busybox-static version 1.22.0-7
Processing control commands: tag -1 + confirmed Bug #757941 [busybox-static] busybox-static: DNS resolver stopped working in busybox-static version 1.22.0-7 Added tag(s) confirmed. -- 757941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757941 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.b757941.140786377229982.transcr...@bugs.debian.org
Bug#757941: busybox-static: DNS resolver stopped working in busybox-static version 1.22.0-7
12.08.2014 21:16, Michael Tokarev wrote: jessie does not work. Also, it is specific to amd64 arch, it does not happen on i386 (from 2 variants of x86 arches). No, i386 jessie does not work too. It was a very old jessie32 chroot here where I tried to build it and it worked. So it looks like the issue is specific to gcc-4.9. /mjt -- 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/53ea4ec3.9050...@msgid.tls.msk.ru
Bug#757941: busybox-static: DNS resolver stopped working in busybox-static version 1.22.0-7
On Tuesday 12 August 2014 21:16:06 Michael Tokarev wrote: Also, it is specific to amd64 arch, it does not happen on i386 (from 2 variants of x86 arches). It's not just limited to amd64, since I encountered the issue on raspbian for the Raspberry Pi, which is somewhere between armel and armhf. See https://github.com/debian-pi/raspbian-ua-netinst/issues/80 -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Bug#757941: busybox-static: DNS resolver stopped working in busybox-static version 1.22.0-7
Michael Tokarev m...@tls.msk.ru (2014-08-12): Control: tag -1 + confirmed 12.08.2014 19:30, Diederik de Haas wrote: Package: busybox-static Version: 1:1.22.0-8 Severity: important When trying to ping an address, like debian.org, with busybox-static you get a ping: bad address 'debian.org' error. Yes, this is what we have. Current busybox-static in wheezy+ does not work. What's interesting - I compiled busybox-static on curent wheezy host, the resulting binary works fine. But the same busybox compiled on jessie does not work. Also, it is specific to amd64 arch, it does not happen on i386 (from 2 variants of x86 arches). Smells like a possible compiler optimization bug? (The relevant code might be buggy and falling into undefined behaviour; meaning not a compiler bug.) Should be easy to check by building at -O0. Mraw, KiBi. signature.asc Description: Digital signature
Bug#757941: busybox-static: DNS resolver stopped working in busybox-static version 1.22.0-7
12.08.2014 21:34, Cyril Brulebois wrote: Smells like a possible compiler optimization bug? (The relevant code might be buggy and falling into undefined behaviour; meaning not a compiler bug.) Should be easy to check by building at -O0. Nope. This is getaddrinfo() function. So it is glibc, not gcc or optimization. getaddrinfo() does not work in jessie glibc when linked statically. It immediately returns Name or service not known (rc=-2) without trying to read /etc/hosts or send dns queries. At link time, there's a warning issued, -- warning: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking but even if the same library is installed it doesn't work still. This makes it.. interesting... /mjt -- 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/53ea5303.2080...@msgid.tls.msk.ru
Bug#757956: choose-mirror: no default choice in text mode once the country is selected
Package: choose-mirror Version: 2.57 Severity: normal Hi, when using choose-mirror in graphical mode, picking France leads to the default selection of ftp.fr.debian.org; however this doesn't happen in the text-based installer, where there's no default value. I know frontends are different but maybe there's something we could or should do to improve consistency here. Default choices/prompts on other screens are quite OK and pressing Enter most of the time is almost sufficient. (Seen while testing with speech synthesis; I've added the debian-accessibil...@lists.debian.org to X-D-Cc accordingly.) Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140812181521.11018.56043.report...@wodi.home.mraw.org
Artwork for jessie?
Hello desktop people, Jessie is approaching, it would be nice to know what's going to happen for this release. If there's no new artwork I suppose it's OK to stick to the current one, but stating that in advance of the freeze would be nice. :) Mraw, KiBi. signature.asc Description: Digital signature
Bug#757711: netcfg: promptly kills dhclient, deconfigures interface
On Tue, Aug 12, 2014 at 02:45:25AM +0200, Cyril Brulebois wrote: That I don't know. Maybe try and compare with netcfg + dhcp client du jour on Linux, and see whether netcfg's behaviour is different in both cases, or the dhcp client's one, or the kernel's one. In the end there's a lot of sadness around what we do, what Ubuntu does, and what the end result is. Ubuntu uses isc-dhcp-client, so the same as on kfreebsd-* and might as well have some additional patches to netcfg because of this. But at work we do use Ubuntu and found that dhclient is called with -1. If the lease expires during installation and your switch does DHCP snooping, you lose network during installation because the DHCP client does not continue to renew it. This is anecdotal experience but divergence between Linux and kfreebsd wrt DHCP might mean that certain problems need to be solved twice or certain failure modes only happen in one or another, with userspace being the reason, not even the kernel difference. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#757920: debian-installer: vesamenu.c32 is not a COM32R image
On Tue, Aug 12, 2014 at 02:00:12PM +0200, Cyril Brulebois wrote: Hi Kim, and thanks for your detailed bug report. Kim R. T. Hansen k...@rthansen.dk (2014-08-12): Package: debian-installer Version: Severity: normal Tags: d-i Dear Maintainer, * What led up to the situation? I want to install Debian/testing on a new computer. * What exactly did you do (or not do) that was effective (or ineffective)? I upgraded the PXE installer for testing using di-netboot-assistant, then I tried to install with it. * What was the outcome of this action? I expected the installer to run. * What outcome did you expect instead? The installer failed with the error vesamenu.c32 is not a COM32R image (written from memory). When I compare the vesamenu.c32 files in the testing and daily installers with the same files from stable and some Ubuntu version there are some differences: * The working files have a size about 150kB and are COM executable * The problematic files have a size of 26kB and are ELF 32-bit LSB shared object This is an example of a good file: http://ftp.fr.debian.org/debian/dists/testing/main/installer-amd64/20140316/images/netboot/debian-installer/amd64/boot-screens/vesamenu.c32 This is a bad file: http://ftp.fr.debian.org/debian/dists/testing/main/installer-amd64/20140802/images/netboot/debian-installer/amd64/boot-screens/vesamenu.c32 The fact you're using di-netboot-assistant is interesting, maybe it would have needed an update for the syslinux 6 transition? The code can be viewed online here: http://anonscm.debian.org/cgit/d-i/netboot-assistant.git/tree/di-netboot-assistant#n236 It seems there's some *.c32-specific handling, and there's even a mention of a (probably previous) transition for menu related files. I'm not that familiar with the netboot-assistant (read: I didn't even know it existed before reading this :) but from what I gather from its docs it helps automate something I was doing more manually. If the tree that it currently creates is still something like what is shown here: https://wiki.debian.org/DebianInstaller/NetbootAssistant, then yeah, this is basically the problem I mused about in #756275, in the 'slight tangent' about rearranging the tree to move pxelinux.0 and the .c32 files out of the 'release specific' part of it where it could be shared by multiple release images. The problem that Kim describes sounds like pxelinx.0 ( 5) was run, but then it tried to load .c32 files from a d-i image tree using the syslinux (= 5) version, and they indeed aren't compatible. I have successfully mixed the newer pxelinux.0 and .c32 versions (from the daily images and with the patch from #756275 applied) with the menu and kernel images from the last released wheezy d-i, and I believe that should also work with earlier images (or those from any compatible derivative distros) too, though I haven't tested those myself. Basically you need to pick the pxelinux.0 and .c32 files from just *one* release (any should do, at least until the menu files depend on some later feature, or some older feature gets dropped, but the latest version you have available is probably the safest to pick), and use those for all of the various menu/kernel release trees you want to make available. Reshuffling the remaining things in the release tree and making a new top level menu of your own as needed. Making that easier to do was what my 'slight tangent' was about. Possibly this means we should actually split the netboot.tar into two separate images now, a netboot-pxe.tar (with pxelinux.0 and the .c32) and a netboot-$release.tar with the menu and kernel/initrd files for the given release. And have those unpack into non-overlapping trees. Then people who want to do this will download just one netboot-pxe tarball, and however many -$release versions they want to support. I think we would have had more reports if PXE was broken in the general case so I suspect this might be a regression only in the d-i netboot assistant case. In the general case, the current released wheezy netboot images are ok when used as a self-contained tree. The daily images, and the new release you are preparing from those, will be broken until the patch from #756275 is applied (for a slightly different reason - that fixes the paths where the ELF .c32 files are expected to be found, which is a new constraint for syslinux = 5), so you might hear more reports of that soon :) But that can be fairly easily 'hand hacked' by users just moving some files around after installation until the patch is in. It sounds like netboot assistant will need a separate fix to that, to arrange its tree in a way that doesn't try to mix the syslinux files from different releases. Whoever finds time to work on that, might find that much easier to do if they first tease apart the -pxe and -release trees as above in the netboot images
Re: Artwork for jessie?
On mar., 2014-08-12 at 21:18 +0200, Cyril Brulebois wrote: Hello desktop people, Jessie is approaching, it would be nice to know what's going to happen for this release. If there's no new artwork I suppose it's OK to stick to the current one, but stating that in advance of the freeze would be nice. :) And in any case the extlinux themes need to be reworked since apparently the 6.x package broke support for the previous themes. Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#757711: netcfg: promptly kills dhclient, deconfigures interface
On Tue, Aug 12, 2014 at 02:45:25AM +0200, Cyril Brulebois wrote: That I don't know. Maybe try and compare with netcfg + dhcp client du jour on Linux, and see whether netcfg's behaviour is different in both cases, or the dhcp client's one, or the kernel's one. netcfg kills the running DHCP client on linux too. On 12/08/14 20:19, Philipp Kern wrote: In the end there's a lot of sadness around what we do, what Ubuntu does, and what the end result is. Ubuntu uses isc-dhcp-client, so the same as on kfreebsd-* and might as well have some additional patches to netcfg because of this. I could maybe look into porting udhcpc to kfreebsd; that is if netcfg maintainers still think it is preferred over ISC DHCP? (udhcpc saves about 2MiB in the install image, if that's reason enough). Or otherwise go the other way and try to have all architectures using isc-dhcp-client-udeb. Except - I'm not sure how heavily systemd is going to feature in d-i for jessie or jessie+1? If systemd's own DHCP client is going to take over this task someday we'd end up with different implementations again, making either of the above changes a waste of time, and personally I'd prefer to keep the fully-featured ISC DHCP in that case. (Releasing the DHCP lease and deconfiguring the interface seems to be a feature udhcpc *lacks*, hence why the problem is not seen yet on linux). But at work we do use Ubuntu and found that dhclient is called with -1. If the lease expires during installation and your switch does DHCP snooping, you lose network during installation because the DHCP client does not continue to renew it. FWIW the netcfg patch in my last message seems to have fixed this nicely for kfreebsd. And it keeps the dhclient/udhcpc running throughout the install - I think that is desirable whichever one is used, to avoid the issue described above. This is anecdotal experience but divergence between Linux and kfreebsd wrt DHCP might mean that certain problems need to be solved twice or certain failure modes only happen in one or another, with userspace being the reason, not even the kernel difference. Thanks for sharing that info. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53ea6fd0.9090...@pyro.eu.org
Bug#757711: netcfg: promptly kills dhclient, deconfigures interface
Steven Chamberlain ste...@pyro.eu.org (2014-08-12): Except - I'm not sure how heavily systemd is going to feature in d-i for jessie or jessie+1? Last I checked we were using busybox init… Mraw, KiBi. signature.asc Description: Digital signature
Re: Artwork for jessie?
On Tue, Aug 12, 2014 at 09:18:35PM +0200, Cyril Brulebois wrote: Hello desktop people, Jessie is approaching, it would be nice to know what's going to happen for this release. If there's no new artwork I suppose it's OK to stick to the current one, but stating that in advance of the freeze would be nice. :) Mraw, KiBi. Yeah. Shucks. I looked it over last week and saw one that caught my eye, (although they were all amazing; such an incredible community. So much amazing creativity). unless anyone has strong feelings, I can make an announcement and start work this week Much love, Paul -- .''`. Paul Tagliamonte paul...@debian.org | Proud Debian Developer : :' : 4096R / 8F04 9AD8 2C92 066C 7352 D28A 7B58 5B30 807C 2A87 `. `'` http://people.debian.org/~paultag `- http://people.debian.org/~paultag/conduct-statement.txt signature.asc Description: Digital signature
Re: Artwork for jessie?
The problem might be the process. Last time there where loads of proposals, but a very awkward selection mode. I guess I'm not the only one frustrated by it. So there would be loads of not yet used proposals left, if we want to go for something new: https://wiki.debian.org/DebianDesktop/Artwork/Wheezy#Proposals_for_Debian_GNU.2FLinux_7_.28.22Wheezy.22.29 I would gladly adapt what needs to be adapted for Jessie. I as well can come up with something new, but I need to know what I should deliver. The same files we used to prepare for wheezy? Cheers Franz On Tue, 2014-08-12 at 21:18 +0200, Cyril Brulebois wrote: Hello desktop people, Jessie is approaching, it would be nice to know what's going to happen for this release. If there's no new artwork I suppose it's OK to stick to the current one, but stating that in advance of the freeze would be nice. :) Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1407874335.4391.36.ca...@mim.ext
Re: Artwork for jessie?
There are new ones @ https://wiki.debian.org/DebianArt/Themes On Tue, Aug 12, 2014 at 4:12 PM, Onsemeliot onsemel...@riseup.net wrote: The problem might be the process. Last time there where loads of proposals, but a very awkward selection mode. I guess I'm not the only one frustrated by it. So there would be loads of not yet used proposals left, if we want to go for something new: https://wiki.debian.org/DebianDesktop/Artwork/Wheezy#Proposals_for_Debian_GNU.2FLinux_7_.28.22Wheezy.22.29 I would gladly adapt what needs to be adapted for Jessie. I as well can come up with something new, but I need to know what I should deliver. The same files we used to prepare for wheezy? Cheers Franz On Tue, 2014-08-12 at 21:18 +0200, Cyril Brulebois wrote: Hello desktop people, Jessie is approaching, it would be nice to know what's going to happen for this release. If there's no new artwork I suppose it's OK to stick to the current one, but stating that in advance of the freeze would be nice. :) Mraw, KiBi. -- :wq -- 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/CAO6P2QQ7sQ+meoXfTaVmaHt5f==advvbrhsagqkv2v1uzss...@mail.gmail.com
Re: Artwork for jessie?
Le mar. 12 août 2014 à 22:13, Paul Tagliamonte paul...@debian.org a écrit : There are new ones @ https://wiki.debian.org/DebianArt/Themes Hey Paul, What do you think about the one named Lines? -- 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/1407875610.186...@smtp.free.fr
Re: Artwork for jessie?
Heya, That would be my personal choice, excepting that the logo has been slightly reshaped. Gladly, the author seems to allow the use of the original logo. But again, as for previous releases, there is no try to do a « better » (understand different) integration with gtk/qt themes, as well as lightdm/slim/gdm/kdm themes. Adrien Le 12 août 2014 à 22:33, Vincent Blut vincent.deb...@free.fr a écrit : Le mar. 12 août 2014 à 22:13, Paul Tagliamonte paul...@debian.org a écrit : There are new ones @ https://wiki.debian.org/DebianArt/Themes Hey Paul, What do you think about the one named Lines? -- To UNSUBSCRIBE, email to debian-desktop-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1407875610.186...@smtp.free.fr -- 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/237b116f-9a71-459a-af72-5f2fa8f08...@gmail.com
Re: Artwork for jessie?
Le mar. 12 août 2014 à 22:41, Adrien Aubourg adrien.aubo...@gmail.com a écrit : Heya, That would be my personal choice, excepting that the logo has been slightly reshaped. Gladly, the author seems to allow the use of the original logo. Ditto, I really like it. Like you, I am quite uncomfortable with the reshape of the logo, but Juliette seems open to make modifications… But again, as for previous releases, there is no try to do a « better » (understand different) integration with gtk/qt themes, as well as lightdm/slim/gdm/kdm themes. Indeed, but that have to be clearly stated in the initial call that more invasive GTK+/Qt theming are allowed. Adrien Cheers, Vincent -- 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/1407876704.186...@smtp.free.fr
Re: Artwork for jessie?
Le mar. 12 août 2014 à 22:49, Onsemeliot onsemel...@riseup.net a écrit : On Tue, 2014-08-12 at 20:35 +0002, Vincent Blut wrote: What do you think about the one named Lines? I know you didn't ask me, but I still tell, what I think: Lines looks great, but I wouldn't distort the original logo. Yes, but as just answered to Adrien, Juliette seems willing to revert to the original logo. It might be hard to actually position the logo like proposed in most images since as far as I know the images get either cut on the right bottom corner or on each side. So it probably wouldn't work like intended on screens with different proportions... True. Franz -- 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/1407877101.186...@smtp.free.fr
Re: Artwork for jessie?
On Tue, Aug 12, 2014 at 09:00:21PM +0002, Vincent Blut wrote: Le mar. 12 août 2014 à 22:49, Onsemeliot onsemel...@riseup.net a écrit : On Tue, 2014-08-12 at 20:35 +0002, Vincent Blut wrote: What do you think about the one named Lines? I know you didn't ask me, but I still tell, what I think: Lines looks great, but I wouldn't distort the original logo. Yes, but as just answered to Adrien, Juliette seems willing to revert to the original logo. It is so close I can't even imagine why the bother to have changed it in the first place. It does look nice, although I wonder what it would look like with the swirl in the standard red (probably terrible). -- Len Sorensen -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140812210325.gy17...@csclub.uwaterloo.ca
Re: Artwork for jessie?
On Tue, 2014-08-12 at 20:35 +0002, Vincent Blut wrote: What do you think about the one named Lines? I know you didn't ask me, but I still tell, what I think: Lines looks great, but I wouldn't distort the original logo. It might be hard to actually position the logo like proposed in most images since as far as I know the images get either cut on the right bottom corner or on each side. So it probably wouldn't work like intended on screens with different proportions... Franz -- 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/1407876579.4391.45.ca...@mim.ext
Re: Artwork for jessie?
Le mar. 12 août 2014 à 23:05, Paul Tagliamonte paul...@debian.org a écrit : Sounds like Lines has consensus. Fair enough; let's go with it, but we should revert the logo back to the original aspect. Which I do realize breaks the entire concept. -T Juliette, could we have a look of your theme with the original logo, please ? Cheers, Vincent -- 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/1407877646.186...@smtp.free.fr
Re: Artwork for jessie?
I thought lines was one of the most clever, and the changing of the logo makes sense (theme reminds me of the golden ratio :) ), I'm not sure we can do that :( Sucks, was a leader in my mind. I was going to write it up more, but I really like Sharp a lot. -T On Tue, Aug 12, 2014 at 4:51 PM, Vincent Blut vincent.deb...@free.fr wrote: Le mar. 12 août 2014 à 22:41, Adrien Aubourg adrien.aubo...@gmail.com a écrit : Heya, That would be my personal choice, excepting that the logo has been slightly reshaped. Gladly, the author seems to allow the use of the original logo. Ditto, I really like it. Like you, I am quite uncomfortable with the reshape of the logo, but Juliette seems open to make modifications… But again, as for previous releases, there is no try to do a « better » (understand different) integration with gtk/qt themes, as well as lightdm/slim/gdm/kdm themes. Indeed, but that have to be clearly stated in the initial call that more invasive GTK+/Qt theming are allowed. Adrien Cheers, Vincent -- :wq -- 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/CAO6P2QRWngtN=pzl_0po25onc4dqya6pq483qgritbmhfmo...@mail.gmail.com
Re: Artwork for jessie?
I adapted Serenity for my live-spin of debian jessie with e17. https://a.fsdn.com/con/app/proj/n00bix/screenshots/build2-32bit-v2.png The menu button is actually the DVD face.
Re: Artwork for jessie?
Sounds like Lines has consensus. Fair enough; let's go with it, but we should revert the logo back to the original aspect. Which I do realize breaks the entire concept. -T On Tue, Aug 12, 2014 at 5:03 PM, Ulrich rusty@mailbox.org wrote: It is beautiful. Regarding unused proposals: If anyone really wants a collection of previous or alternative themes, this could be a solution: https://github.com/ulrich-hansen/desktop-theme-kit Ulrich Am 12.08.2014 um 22:41 schrieb Adrien Aubourg adrien.aubo...@gmail.com: Heya, That would be my personal choice, excepting that the logo has been slightly reshaped. Gladly, the author seems to allow the use of the original logo. But again, as for previous releases, there is no try to do a « better » (understand different) integration with gtk/qt themes, as well as lightdm/slim/gdm/kdm themes. Adrien Le 12 août 2014 à 22:33, Vincent Blut vincent.deb...@free.fr a écrit : Le mar. 12 août 2014 à 22:13, Paul Tagliamonte paul...@debian.org a écrit : There are new ones @ https://wiki.debian.org/DebianArt/Themes Hey Paul, What do you think about the one named Lines? -- To UNSUBSCRIBE, email to debian-desktop-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1407875610.186...@smtp.free.fr -- To UNSUBSCRIBE, email to debian-desktop-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/237b116f-9a71-459a-af72-5f2fa8f08...@gmail.com -- :wq -- 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/cao6p2qtrdoan2kwfwymsbmtcoeeyzvc77+rcm44ef1xhk8j...@mail.gmail.com
Processing of win32-loader_0.7.5_amd64.changes
Upload to ftp-master.debian.org failed Error messages: Can't use an undefined value as a symbol reference at /usr/share/perl/5.14/Net/FTP/dataconn.pm line 54. The upload will be retried in 0:30:00 Greetings, Your Debian queue daemon (running on host coccia.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1xhjgm-00065s...@coccia.debian.org
Re: Artwork for jessie?
On 12/08/14 21:13, Paul Tagliamonte wrote: There are new ones @ https://wiki.debian.org/DebianArt/Themes Wow, already. Some are pretty spectacular. Is there time for a last call via debian-devel-announce@, allowing maybe 1-2 weeks to have proposals finalised on that page, any latecomers added quickly, and suitable wheezy proposals copied over by their designers to the jessie page? And then some kind of vote, maybe happening at DebConf? Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53ea859a.3080...@pyro.eu.org
Re: Artwork for jessie?
On 12/08/14 22:05, Paul Tagliamonte wrote: Sounds like Lines has consensus. Oh. I only just received this from listserver after sending my other mail. I guess it's too late. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53ea86df.7020...@pyro.eu.org
Bug#757711: netcfg: promptly kills dhclient, deconfigures interface
tags 757711 + patch thanks I'd like to propose this patch to netcfg as a fix for this bug: https://bugs.debian.org/757711#52 On 12/08/14 20:53, Cyril Brulebois wrote: Steven Chamberlain ste...@pyro.eu.org (2014-08-12): Except - I'm not sure how heavily systemd is going to feature in d-i for jessie or jessie+1? Last I checked we were using busybox init… I guess that means there are no plans for jessie d-i to use systemd. So for now my thoughts are: * it is desirable to converge on a common DHCP client across all architectures, but for jessie (having just looked at udhcpc) it is too late to do this * for jessie+1, we'll have to wait and see whether systemd finds its way into d-i: because if it does, it may take over DHCP client functionality and non-linux ports may be best keeping isc-dhcp-client-udeb (udhcpc would go away); if it does not, it may be better for udhcpc to be ported to non-linux and converge on that instead Regards, -- Steven Chamberlain ste...@pyro.eu.org signature.asc Description: OpenPGP digital signature
Processing of win32-loader_0.7.5_amd64.changes
/win32-loader_0.7.5_amd64.changes is already present on target host: -rw--- 1 3149 1281 2876 Aug 12 21:04 win32-loader_0.7.5_amd64.changes Either you already uploaded it, or someone else came first. Job win32-loader_0.7.5_amd64.changes removed. Greetings, Your Debian queue daemon (running on host coccia.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1xhjjm-0007cm...@coccia.debian.org
Processing of win32-loader_0.7.5_amd64.changes
win32-loader_0.7.5.dsc has incorrect size; deleting it win32-loader_0.7.5.tar.bz2 doesn't exist Due to the errors above, the .changes file couldn't be processed. Please fix the problems for the upload to happen. Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1xhjm4-fe...@franck.debian.org
Re: Artwork for jessie?
I agree with Franz and Adrien... overall, there needs to be a desire or commitment to allowing a more modern style, so that the development required to implement it is no longer a 'de-selector'. A good while back, we made https://wiki.debian.org/DebianArt/Themes/7th-element For us, it was only an idea / conversation-starting-point, but I recall discussing here with the lead guys about trying to get it implemented, but the breakage was an issue (which I think Adrien is referring to). This go around, either some some parameters should be clearly stated so that the creativity can be wrapped around it... or, determine that the theme issue will be addressed from the development side, and that creative freedom can be allowed... and we all get to working on designing a UI that will truly stand out from the rest and attract a larger user base. Steve On Tue, Aug 12, 2014 at 5:07 PM, Vincent Blut vincent.deb...@free.fr wrote: Le mar. 12 août 2014 à 23:05, Paul Tagliamonte paul...@debian.org a écrit : Sounds like Lines has consensus. Fair enough; let's go with it, but we should revert the logo back to the original aspect. Which I do realize breaks the entire concept. -T Juliette, could we have a look of your theme with the original logo, please ? Cheers, Vincent -- To UNSUBSCRIBE, email to debian-desktop-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1407877646.186...@smtp.free.fr
Processed: Re: Bug#751704: partman-base 173: partman overwrites parts of u-boot
Processing control commands: tag -1 patch Bug #751704 [src:partman-base] partman-base 173: partman overwrites parts of u-boot Added tag(s) patch. -- 751704: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751704 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.b751704.140788315317430.transcr...@bugs.debian.org
Bug#751704: partman-base 173: partman overwrites parts of u-boot
Control: tag -1 patch
On Wed, Jun 18, 2014 at 09:44:12PM +0200, Karsten Merker wrote:
[On sunxi-based systems, upon writing the partition table, partman
overwrites parts of u-boot which are located between the end of
the partition table and the beginning of the first partition.]
Hello,
the following patch solves the issue for me. I have run a
successful jessie installation on a Cubietruck with this patch
applied to a locally built d-i based on kernel 3.16 from
experimental.
If there are no objections, I would like apply it to the
partman-base git repository.
Regards,
Karsten
From 35d41e3bfce60fd08c4da6dc0696a479c78bdcdd Mon Sep 17 00:00:00 2001
From: Karsten Merker mer...@debian.org
Date: Tue, 12 Aug 2014 23:10:13 +0200
Subject: [PATCH] Take care of the firmware area on sunxi-based systems
By default partman calls ped_disk_clobber when writing the
partition table, but on sunxi-based systems this would overwrite
the firmware area, resulting in an unbootable system (see
bug #751704). Handle this as a special case in command_commit().
---
parted_server.c | 34 ++
1 file changed, 34 insertions(+)
diff --git a/parted_server.c b/parted_server.c
index 55cf151..bc4523a 100644
--- a/parted_server.c
+++ b/parted_server.c
@@ -1330,6 +1330,25 @@ command_dump()
oprintf(OK\n);
}
+/* Check whether we are running on a sunxi-based system. */
+int
+is_sunxi_system()
+{
+int cpuinfo_handle;
+int result=0;
+char buf[4096];
+int length;
+
+if ((cpuinfo_handle = open(/proc/cpuinfo, O_RDONLY)) != -1 ) {
+length = read(cpuinfo_handle, buf, sizeof(buf)-1);
+buf[length]='\0';
+if (strstr(buf,Allwinner)!=NULL)
+result=1;
+close(cpuinfo_handle);
+}
+return result;
+}
+
void
command_commit()
{
@@ -1337,6 +1356,21 @@ command_commit()
if (dev == NULL)
critical_error(The device %s is not opened., device_name);
log(command_commit());
+
+/*
+ * The boot device on sunxi-based systems needs special handling.
+ * By default partman calls ped_disk_clobber when writing the
+ * partition table, but on sunxi-based systems this would overwrite
+ * the firmware area, resulting in an unbootable system (see
+ * bug #751704).
+ */
+if (is_sunxi_system() !strcmp(disk-dev-path, /dev/mmcblk0)) {
+disk-needs_clobber=0;
+log(Sunxi platform detected. Disabling ped_disk_clobber \
+for the boot device %s to protect the firmware \
+area., disk-dev-path);
+}
+
open_out();
if (disk != NULL named_is_changed(device_name))
ped_disk_commit(disk);
--
2.1.0.rc1
--
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.
--
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/20140812223858.ga9...@excalibur.cnev.de
Bug#745262: console-setup: Caps lock doesn't take effect on øæå (Danish characters)
Anton Zinoviev, le Wed 06 Aug 2014 20:39:02 +0300, a écrit : On Sun, Apr 20, 2014 at 10:35:23PM +0200, Samuel Thibault wrote: Andreas, le Sun 20 Apr 2014 03:30:13 +0200, a écrit : On the Linux console the caps lock key doesn't take effect on the Danish characters æøå. With caps lock on they are simply rendered æøå (lower case), and not ÆØÅ as one would expect. Oops, indeed, it seems the version in Jessie does not properly defines the ctrll layer for upper cases like it used to in Wheezy. See ckbcomp dk: keycode 39 = +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute It uses only +U+00e6 +U+00c6, while it should use +U+00c6 +U+00e6 for ctrll layers. I am unable to reproduce this. What locale do you use? I've tested with LC_ALL=C, LC_ALL=da_DK.utf8 and LC_ALL=da_DK. Well, whatever the locale, LC_ALL=C for instance, I get only +U+00e6 +U+00c6, and never +U+00c6 +U+00e6. I've tried both console-setup 1.102 and 1.111. Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140812224726.gc8...@type.youpi.perso.aquilenet.fr
Bug#751704: partman-base 173: partman overwrites parts of u-boot
On Wed, Aug 13, 2014 at 12:38:58AM +0200, Karsten Merker wrote: If there are no objections, I would like apply it to the partman-base git repository. Please adhere to local coding style, including indentation, spacing, and use or otherwise of tabs; it really makes things easier to follow later. PedDisk.needs_clobber is marked as office use only in parted; I interpret that as meaning that it really shouldn't be fiddled with outside parted, even though it's technically exposed. Could you please look at fixing parted to avoid clobbering the firmware area instead? I think that would be more correct. Thanks, -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140812224551.gl5...@riva.ucam.org
Bug#757552: marked as done (Guided and manual LVM fails)
Your message dated Wed, 13 Aug 2014 00:27:39 +0100 with message-id 20140812232739.ga14...@riva.ucam.org and subject line Re: Bug#757552: Guided and manual LVM fails has caused the Debian Bug report #757552, regarding Guided and manual LVM fails 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.) -- 757552: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757552 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: debian-installer Version: 20140802 When using both 20140802 and latest nightly amd64 hd-media installer, when I get to the Partition hard drives stage and choose Guided - used entire disk and setup LVM, choose any of the recipes (single, separate /home, etc.), the install then fails and I get an error message stating This probably happened because there are too many (primary) partitions in the partition table.. Upon continuing, I can see the following partitions have been created: - ~250MB /boot partition - LVM partition/volume using the rest of the disk space - LVM volume group ([hostname]-vg) - root LVM volume, ~300MB If I then manually go to Configure the Logical Volume Manager, remove the existing root volume, create appropriately sized volumes and go back to the partition list, the list is now as follows: - ~250MB /boot partition - LVM partition/volume using the rest of the disk space ie. The volume group and volumes are missing. Choosing Manual partitioning also has the same effect. syslog doesn't show any errors: Aug 9 07:41:11 partman-lvm: Writing physical volume data to disk /dev/cciss/c0d0p5 Aug 9 07:41:11 partman-lvm: Physical volume /dev/cciss/c0d0p5 successfully created Aug 9 07:41:11 partman-lvm: Volume group hp1 successfully created Aug 9 07:41:12 partman-lvm: Logical volume root created Guided and Manual LVM works correctly in the stable 7.6 installer. ---End Message--- ---BeginMessage--- On Sun, Aug 10, 2014 at 12:42:38AM +1000, m...@mazzanet.net.au wrote: Thanks, that does indeed match the behaviour I experienced, I'll follow that bug. This bug can be closed. Thanks. This should all be fixed now too, per that bug. -- Colin Watson [cjwat...@debian.org]---End Message---
Processed: tagging 756065
Processing commands for cont...@bugs.debian.org: tags 756065 + pending Bug #756065 [installation-guide] installation-guide: (D.3.7) For jessie ssh root login with password is by default impossible Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 756065: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756065 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.140788614632651.transcr...@bugs.debian.org
Re: Bad link on Debian Installer-dev page
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, Thanks for your interest in the Debian web site. Le 04/08/2014 19:21, Will Brokenbourgh a écrit : On the Debian Installer-dev page: https://www.debian.org/devel/debian-installer/ there is a link to 'known issues': https://wiki.debian.org/DebianInstaller/Today however this link is bad. The context of the link is: Notes * Before you download the daily built images, we suggest you check for known issues. CCing debian-boot in charge of this section (as documented in the bottom of the page). Cyril (currently handling d-i) proposed to comment out this advice until a proper information is available (there is work in progress in that regard). That’s done, so the bad URL will disappear in a few hours. Regards David -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJT6sCIAAoJEAWMHPlE9r08UvUIAIIW1HHvs3w48Em4HbmvyB6u VznMpBu1JD6mbwRcnKsCwgU08SarE4opwfaF50s4clJgRbpvjZlQYgsZ0kTjfbbR haFgc46zSCR1mW6XPpN6cqIXe8YF+f34U0zcYf9MMIRpuurmjq1/skx+TLyse+aT rsfOpz1bIHAPL6efWlwjTqFeDRt4CvJNOyQHNhpoPpIw3oPehdBj/E53LAK4KeD+ PeFWSa4TM0AEuuhAfWr1j4868n8aC+Sqgr+Z80wzvPzl+TF2UuWW7YJp8YtxuXY2 ycKIT5Rv80c9pA1qsnlGRxmS6pg3p404VtwLzk/gs2aecgS/vilqwQyWJLK0LGQ= =K4Od -END PGP SIGNATURE- -- 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/53eac089.7020...@debian.org
Bug#757985: kfreebsd: hang with ENOSPC after a few components are loaded
Package: debian-installer Version: 20140802 Severity: important User: debian-...@lists.debian.org Usertags: kfreebsd Hi, with a wheezy/amd64/kvm-based setup (hda is ~5GB, RAM is 1GB), the following images don't work at all, with the following message on vt1: | /: write failed, filesystem is full (Looking at syslog when I can, it seems anna is the tool running into a full partition, which isn't surprising.) - debian-jessie-DI-a1-kfreebsd-amd64-netinst.iso debian-jessie-DI-b1-kfreebsd-amd64-netinst.iso → with Default install (graphical mode), after locale settings, when udeb components are loaded. - debian-jessie-DI-a1-kfreebsd-i386-netinst.iso debian-jessie-DI-b1-kfreebsd-i386-netinst.iso → with Default install, after locale settings, when udeb components are loaded. I'm very concerned to see that Jessie Alpha 1 images were already totally broken for kfreebsd-i386 (ditto for kfreebsd-amd64 in graphical mode), and that it doesn't seem to have been detected/worked on/fixed. Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140813015546.21404.15511.report...@wodi.home.mraw.org
Bug#757988: kfreebsd: troubles with dhcp (configuration going away)
Package: debian-installer Version: 20140802 Severity: important User: debian-...@lists.debian.org Usertags: kfreebsd Hi, I know this is tracked as #757711 but I'm trying to get a comprehensive list of issues affecting kfreebsd-*, along with possible solutions for those using images. So, using debian-jessie-DI-b1-kfreebsd-amd64-netinst.iso with DHCP, an error is shown right after the mirror selection, since network configuration obtained through DHCP is lost at this point. It would be nice to make sure what triggered this issue before blindly applying a patch against netcfg IMHO. Switching to vt2 (alt-f2), and typing this allowed me to resume my (kvm-based) installation test: ifconfig re0 10.0.2.15 255.255.255.0 route add default 10.0.2.2 (I hope my notes are correct on this, readers should get the idea anyway.) Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140813015634.23685.74184.report...@wodi.home.mraw.org
Bug#757986: kfreebsd: multiple inappropriate ioctl for device prompts
Package: debian-installer Version: 20140802 Severity: important User: debian-...@lists.debian.org Usertags: kfreebsd Hi, it seems the following warning still hasn't been decided upon (harmless, should go away; or important, should stay), and it pops up multiple times: | Could not get identity of device /dev/ada0 - Inappropriate ioctl for | device | | Warning! | | Ignore | Cancel | | Back Please investigate and take a decision. Thanks for your time. Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140813015557.22518.72789.report...@wodi.home.mraw.org
Bug#757987: kfreebsd: cannot create swap space
Package: debian-installer Version: 20140802 Severity: important User: debian-...@lists.debian.org Usertags: kfreebsd Hi, using debian-jessie-DI-b1-kfreebsd-amd64-netinst.iso with a single (kvm) disc, I can't get past the automatic partioning step due to a failure to create a swap partition on /dev/ada0; this might be a consequence of the recent migration to parted 3.2, or something else. Please investigate and get in touch with the parted maintainers, which will likely be interested in both /var/log/syslog and /var/log/partman. In the meanwhile, it's possible to go back to the partioning menu, so as to delete this partition, and try again without it. Thanks for your time. Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140813015606.23091.83900.report...@wodi.home.mraw.org
