Hints for d-i jessie RC4
Hi people, here's a single round of unblock/unblock-udeb/urgent hints for the upcoming d-i upload. It's what we would normally either call RC4 or final or something like this, but I don't think it makes sense to announce it separately. Announcing Jessie is way better. ;) For those on #debian-release, the plan is to have a manual britney run in a few minutes so that we don't wait some extra hours to have these packages in testing. # fix d-i on many arm* platforms (#783019): unblock oldsys-preseed/3.16 unblock-udeb oldsys-preseed/3.16 urgent oldsys-preseed/3.16 # l10n-only: unblock console-setup/1.123 unblock-udeb console-setup/1.123 urgent console-setup/1.123 # l10n-only: unblock grub-installer/1.117 unblock-udeb grub-installer/1.117 urgent grub-installer/1.117 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/20150422115224.gb16...@mraw.org
Re: Hints for d-i jessie RC4
On 2015-04-22 12:52, Cyril Brulebois wrote: Hi people, here's a single round of unblock/unblock-udeb/urgent hints for the upcoming d-i upload. It's what we would normally either call RC4 or final or something like this, but I don't think it makes sense to announce it separately. Announcing Jessie is way better. ;) All added. For those on #debian-release, the plan is to have a manual britney run in a few minutes so that we don't wait some extra hours to have these packages in testing. That's done, and the three packages are now in testing (pending dinstall so that the mirrors being used by the buildds know that). Regards, Adam -- 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/b5f68f3b96a763a0764042b8eebcb...@mowgli.jungle.funky-badger.org
Bug#783089: debian-installer: Cannot rescue a system installed on a raid1 lvm
On Wed, Apr 22, 2015 at 07:49:02AM +0200, Jean-Yves LENHOF wrote: > Because I prefer do it this way... lvm raid is more the traditionnal > unix way of doing it (AIX and HP-UX for sure) That doesn't mean it is a good idea. Those two certainly qualify as the most unpleasant unix systems I have ever had to work with. > Why it is very inflexible ? It found it quite flexible. You can't easily add disks to the volume group in raid mode (as far as I recall the documentation last I looked at it). There are certainly restrictions on how to you expand volumes when lvm raid is in use. > Perhaps the md raid support is there from a longer time because raid1 > support (which is different from mirror support) in the kernel (and in > lvm2 tools) came later... But things changes and I saw a lot of good > things coming in LVM like thin lvm support or cache lvm support. Read > redhat docs, such things are supported by RedHat since RedHat Enterprise > 6.4 or such. Well certainly grub understands md raid, and it understands some lvm. It might not understand lvm with raid. Following the grub development mailing list for a number of years now, I can say I have never seen anyone ask about it or even mention it. I think it is also the first time I have seen it mentioned on any of the debian lists I follow. Certainly using lvm on top of md raid has worked for years for me and the debian rescue knows how to deal with is, as does knoppix and lots of other rescue systems. The lvm raid, no idea. When I looked at it a few years ago it cretainly sounded like a bad option so I avoided it. -- 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/20150422122039.gy29...@csclub.uwaterloo.ca
Re: obsolete info on https://www.debian.org/devel/debian-installer/index.en.html
Hi CC'ing debian-boot El 22/04/15 a las 14:19, Paul Wise escribió: > On Wed, Apr 22, 2015 at 7:28 PM, Paolo Cavallini wrote: > >> please replace: >> 150-280 MB >> with the current min/max size (e.g. i386 is now 305 Mb). > > That part of the website is the responsibility of the debian-installer > team. Please send an email to their list: > > https://lists.debian.org/debian-boot/ > I've gathered the sizes of each netinst iso (from http://cdimage.debian.org/cdimage/jessie_di_rc3/ ): debian-jessie-DI-rc3-amd64-netinst.iso 2015-04-18 20:01 237M debian-jessie-DI-rc3-arm64-netinst.iso 2015-04-18 21:21 152M debian-jessie-DI-rc3-armel-netinst.iso 2015-04-18 22:10 197M debian-jessie-DI-rc3-armhf-netinst.iso 2015-04-18 22:59 174M debian-jessie-DI-rc3-i386-netinst.iso 2015-04-18 18:15 305M debian-jessie-DI-rc3-kfreebsd-amd64-netinst.iso 2015-04-19 03:02 159M debian-jessie-DI-rc3-kfreebsd-i386-netinst.iso 2015-04-19 03:50 157M debian-jessie-DI-rc3-mips-netinst.iso 2015-04-19 00:38 250M debian-jessie-DI-rc3-mipsel-netinst.iso 2015-04-19 01:26 268M debian-jessie-DI-rc3-powerpc-netinst.iso 2015-04-19 04:36 279M debian-jessie-DI-rc3-ppc64el-netinst.iso 2015-04-18 23:49 180M debian-jessie-DI-rc3-s390x-netinst.iso 2015-04-19 02:15 141M (multiarch, not listed in the group of netinst: debian-jessie-DI-rc3-amd64-i386-netinst.iso 2015-04-18 20:57 545M ) Given this, I would propose change "150-280" for "140-310" (rounding a bit). What do you think? (OTOH, those numbers are MiB, not MB isn't it? If yes, I would propose the change "150-280 MB" for "140-310 MiB"). I believe the string is shown in CD/netinst/index.wml releases/jessie/debian-installer/index.wml (available after the release) devel/debian-installer/index.wml Debian-installer team, please let me/us know the decision if we need to change some of those pages or other ones. Regards -- Laura Arjona https://wiki.debian.org/LauraArjona -- 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/5537934e.7060...@larjona.net
Re: obsolete info on https://www.debian.org/devel/debian-installer/index.en.html
On Wed, 2015-04-22 at 14:25 +0200, Laura Arjona Reina wrote: > I've gathered the sizes of each netinst iso (from > http://cdimage.debian.org/cdimage/jessie_di_rc3/ ): Probably that should be done automatically or manually as part of the release process so this never gets out of date? -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Re: Bug#782712: pre-upload unblock request: systemd/215-17 for RC bug #751707
On 2015-04-17 18:22, Martin Pitt wrote: Hello Niels, Niels Thykier [2015-04-17 17:55 +0200]: Just to clarify, are we still intending to do a systemd update prior to Jessie with -17 and then now also a p-u (i.e. for 8.1) for ecryptfs? That's still my intent, yes, primarily to avoid people who have this set up in wheezy already (#751707 has at least two reporters) upgrade and find their swap partition gone and boot stuck. After some discussion on IRC, -17 has been migrated as part of the d-i "RC4" prep. Regards, Adam -- 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/23db45b6ff07d65dc43d0ec938aeb...@mowgli.jungle.funky-badger.org
Bug#783089: debian-installer: Cannot rescue a system installed on a raid1 lvm
Le 2015-04-22 14:20, Lennart Sorensen a écrit : On Wed, Apr 22, 2015 at 07:49:02AM +0200, Jean-Yves LENHOF wrote: Because I prefer do it this way... lvm raid is more the traditionnal unix way of doing it (AIX and HP-UX for sure) Taste is personnal... There are advantages and inconvenients in all of them (Linux/AIX/HP-UX/True64/Solaris/FreeBSD/whatever) FOR AIX vs linux some examples : some pro : smitty is nicely implemented (there was linuxconf in the past days of linux but not maintained anymore) mksysb is something nice to use to restore a system or to install a system with the same configuration... alternate install is something interesting when upgrading from an OS version to another one (using an alternate lvm mirror) some con : odm is something you should not touch without IBM advise, etc.. dependencies in packages are too hard and upgrading a package tend to have everything upgrading... But we are not here to speak about proprietary... but about Linux, so I will not elaborate more on that. That doesn't mean it is a good idea. Those two certainly qualify as the most unpleasant unix systems I have ever had to work with. Why it is very inflexible ? It found it quite flexible. You can't easily add disks to the volume group in raid mode (as far as I recall the documentation last I looked at it). There are certainly restrictions on how to you expand volumes when lvm raid is in use. I just add a disk on my test partition... Done a pvcreate on it, done a vgextend on it without problem. Done a lvextend on a logical partition... Resize my slashlv file system. No problem at all. Did you remake some recent tests ? What is the limitation you are speaking about ? The one I know is that you can't use lvm raid1 in a cluster yet. (It's written in the RedHat Enterprise 7 Logical Volume Documentation) Perhaps the md raid support is there from a longer time because raid1 support (which is different from mirror support) in the kernel (and in lvm2 tools) came later... But things changes and I saw a lot of good things coming in LVM like thin lvm support or cache lvm support. Read redhat docs, such things are supported by RedHat since RedHat Enterprise 6.4 or such. Well certainly grub understands md raid, and it understands some lvm. It might not understand lvm with raid. Following the grub development mailing list for a number of years now, I can say I have never seen anyone ask about it or even mention it. I think it is also the first time I have seen it mentioned on any of the debian lists I follow. You should have read my bug report about grub... There is at least one another person than me that create the bug report ;-) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782591 http://savannah.gnu.org/bugs/?func=detailitem&item_id=44534 http://lists.gnu.org/archive/html/bug-grub/2015-04/msg3.html and you should probably read more carefully the list : http://lists.gnu.org/archive/html/grub-devel/2014-08/msg00024.html Certainly using lvm on top of md raid has worked for years for me and the debian rescue knows how to deal with is, as does knoppix and lots of other rescue systems. The lvm raid, no idea. When I looked at it a few years ago it cretainly sounded like a bad option so I avoided it. Some years ago you probably test the mirror type... which I agree is not a so good solution. I speak about the raid1 type which is different raid1 is there since 2013 (there's no clear appareance of the first commit related) : https://git.fedorahosted.org/cgit/lvm2.git/tree/WHATS_NEW For mirror, the mirroring is rebuilt at each reboot For raid1, the mirroring isn't rebuilt at each reboot I will see if I can provide a patch... because I think that discussion is rubbish and code is better. I think it's just an option to add somewhere to enable the built of this kernel module in an udeb. For the debian-installer part (for this bug report here I speak about rescuing) I will make another wishlist bug report (there will be more impact because there will be some more device with rmeta in their name) Please take the time to enable this module kernel in the udeb. Regards, -- 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/6e8291e68b7bec78e8e61a0936594...@lenhof.eu.org
Bug#783081: installation-reports: Jessie daily installer installs kernel in flash without any further confirmation (QNAP TS-212)
Hello, one little addition about this installation. Emails like following get generated once a day: -- From root@nas3c3b5d Wed Apr 15 22:57:26 2015 Envelope-to: root@nas3c3b5d Delivery-date: Wed, 15 Apr 2015 22:57:26 +0200 From: mdadm monitoring To: root@nas3c3b5d Subject: DegradedArray event on /dev/md2:nas3c3b5d Date: Wed, 15 Apr 2015 22:57:26 +0200 This is an automatically generated mail message from mdadm running on nas3c3b5d A DegradedArray event had been detected on md device /dev/md2. Faithfully yours, etc. P.S. The /proc/mdstat file currently contains the following: Personalities : [raid1] md2 : active (auto-read-only) raid1 sdb2[0] 530048 blocks [2/1] [U_] md9 : active (auto-read-only) raid1 sdb1[0] 530048 blocks [2/1] [U_] bitmap: 65/65 pages [260KB], 4KB chunk md13 : active (auto-read-only) raid1 sdb4[0] 458880 blocks [2/1] [U_] bitmap: 47/57 pages [188KB], 4KB chunk unused devices: -- When I remember correctly I saw those devices as default for at least a swap device. As I wanted to leave the internal flash untouched I changed that to use/format only partitions on the usb stick. While writing this email I realized that this md* devices are probably remainings of the original firmware which did setup my hard disk that way, even when I had until now never 2 disks installed. -- root@nas3c3b5d:/home/bernhard# fdisk -l /dev/sdb Disk /dev/sdb: 465,8 GiB, 500107862016 bytes, 976773168 sectors Device Boot Start End Sectors Size Id Type /dev/sdb1 40 1060289 1060250 517,7M 83 Linux /dev/sdb2 1060296 2120579 1060284 517,7M 83 Linux /dev/sdb3 2120584 975755969 973635386 464,3G 83 Linux /dev/sdb4 975755976 976751999996024 486,3M 83 Linux -- Kind regards, Bernhard -- 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/5537d757.40...@vr-web.de
Bug#783128: Can't install Debian Jessie RC3 Freeze on detecting network
Package: installation-reports Boot method: Image version: Date: Machine: Processor:AMD A6-3420M APU with Radeon(tm) HD Graphics stepping: 0 Memory: 4gig Partitions: Résultat de lspci -knn (ou lspci -nn) :00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h Processor Root Complex [1022:1705] Subsystem: Advanced Micro Devices [AMD] Family 12h Processor Root Complex [1022:1705] 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI BeaverCreek [Radeon HD 6520G] [1002:9647] Subsystem: Toshiba America Info Systems Device [1179:fc50] Kernel driver in use: radeon 00:01.1 Audio device [0403]: Advanced Micro Devices [AMD] nee ATI BeaverCreek HDMI Audio [Radeon HD 6500D and 6400G-6600G series] [1002:1714] Subsystem: Advanced Micro Devices [AMD] nee ATI BeaverCreek HDMI Audio [Radeon HD 6500D and 6400G-6600G series] [1002:1714] Kernel driver in use: snd_hda_intel 00:04.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Family 12h Processor Root Port [1022:1709] Kernel driver in use: pcieport 00:05.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Family 12h Processor Root Port [1022:170a] Kernel driver in use: pcieport 00:11.0 SATA controller [0106]: Advanced Micro Devices [AMD] FCH SATA Controller [AHCI mode] [1022:7801] Subsystem: Toshiba America Info Systems Device [1179:fc50] Kernel driver in use: ahci 00:12.0 USB controller [0c03]: Advanced Micro Devices [AMD] FCH USB OHCI Controller [1022:7807] (rev 11) Subsystem: Toshiba America Info Systems Device [1179:fc50] Kernel driver in use: ohci-pci 00:12.2 USB controller [0c03]: Advanced Micro Devices [AMD] FCH USB EHCI Controller [1022:7808] (rev 11) Subsystem: Toshiba America Info Systems Device [1179:fc50] Kernel driver in use: ehci-pci 00:13.0 USB controller [0c03]: Advanced Micro Devices [AMD] FCH USB OHCI Controller [1022:7807] (rev 11) Subsystem: Toshiba America Info Systems Device [1179:fc50] Kernel driver in use: ohci-pci 00:13.2 USB controller [0c03]: Advanced Micro Devices [AMD] FCH USB EHCI Controller [1022:7808] (rev 11) Subsystem: Toshiba America Info Systems Device [1179:fc50] Kernel driver in use: ehci-pci 00:14.0 SMBus [0c05]: Advanced Micro Devices [AMD] FCH SMBus Controller [1022:780b] (rev 13) Subsystem: Toshiba America Info Systems Device [1179:fc50] 00:14.2 Audio device [0403]: Advanced Micro Devices [AMD] FCH Azalia Controller [1022:780d] (rev 01) Subsystem: Toshiba America Info Systems Device [1179:fc50] Kernel driver in use: snd_hda_intel 00:14.3 ISA bridge [0601]: Advanced Micro Devices [AMD] FCH LPC Bridge [1022:780e] (rev 11) Subsystem: Toshiba America Info Systems Device [1179:fc50] 00:14.4 PCI bridge [0604]: Advanced Micro Devices [AMD] FCH PCI Bridge [1022:780f] (rev 40) 00:14.5 USB controller [0c03]: Advanced Micro Devices [AMD] FCH USB OHCI Controller [1022:7809] (rev 11) Subsystem: Toshiba America Info Systems Device [1179:fc50] Kernel driver in use: ohci-pci 00:16.0 USB controller [0c03]: Advanced Micro Devices [AMD] FCH USB OHCI Controller [1022:7807] (rev 11) Subsystem: Toshiba America Info Systems Device [1179:fc50] Kernel driver in use: ohci-pci 00:16.2 USB controller [0c03]: Advanced Micro Devices [AMD] FCH USB EHCI Controller [1022:7808] (rev 11) Subsystem: Toshiba America Info Systems Device [1179:fc50] Kernel driver in use: ehci-pci 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 0 [1022:1700] (rev 43) 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 1 [1022:1701] 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 2 [1022:1702] 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 3 [1022:1703] Kernel driver in use: k10temp 00:18.4 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 4 [1022:1704] 00:18.5 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 6 [1022:1718] 00:18.6 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 5 [1022:1716] 00:18.7 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 7 [1022:1719] 01:00.0 Ethernet controller [0200]: Atheros Communications Inc. AR8152 v2.0 Fast Ethernet [1969:2062] (rev c1) Subsystem: Toshiba America Info Systems Device [1179:fc50] Kernel driver in use: atl1c 02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter [10ec:8176] (rev 01) Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:8181] Kernel driver in use: rtl8192ce Installation du système de base[E] = Initial boot: [ ] Detect network card:[
Bug#783138: installation-reports from Gremany
Package: installation-reports Boot method:
Processing of debian-installer_20150422_source.changes
debian-installer_20150422_source.changes uploaded successfully to localhost along with the files: debian-installer_20150422.dsc debian-installer_20150422.tar.gz 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/e1yl0oj-0007zm...@franck.debian.org
Re: obsolete info on https://www.debian.org/devel/debian-installer/index.en.html
Paul Wise, le Wed 22 Apr 2015 20:30:38 +0800, a écrit : > On Wed, 2015-04-22 at 14:25 +0200, Laura Arjona Reina wrote: > > > I've gathered the sizes of each netinst iso (from > > http://cdimage.debian.org/cdimage/jessie_di_rc3/ ): > > Probably that should be done automatically or manually as part of the > release process so this never gets out of date? Completely. I've made it an entity, so we don't forget to update it. Thanks! 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/20150422202609.gj4...@type.youpi.perso.aquilenet.fr
Re: kFreeBSD CD/DVD builds for Jessie
Hi Steve, Steve McIntyre wrote: > I know that the kFreeBSD ports are not being officially released > [1]. What plans (if any) have been made for any *un*official releases? > I've just removed the BSD builds from the debian-cd architecture lists > in preparation for next weekend, but I've not heard anything more... kfreebsd as a whole, I feel has been in a releaseable state for some months (massive improvement over wheezy, and no bugs that are absolutely RC). I'd still like to make a stable release out of it. But since we need to move it to a jessie-kfreebsd suite first, I think we are behind schedule with that. I'm not familiar in that area, but Christoph was speaking with ftpmaster about it. I expect it will require changes in debian-installer (for new repository URLs), and there are other d-i issues I'd quite like to patch if possible, and lots of testing I wanted to do (incl. of CD images). Given how busy I am at the moment, I couldn't do that in time for the official release. Would it be reasonable and practical - even preferable - to postpone release of kfreebsd until at least 1-2 weeks after the official release? Thanks, Regards, -- Steven Chamberlain ste...@pyro.eu.org signature.asc Description: Digital signature
debian-installer_20150422_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 22 Apr 2015 21:41:38 +0200 Source: debian-installer Binary: debian-installer Architecture: source Version: 20150422 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Cyril Brulebois Description: debian-installer - Debian installer Changes: debian-installer (20150422) unstable; urgency=medium . * Update translation-status for the release. Checksums-Sha1: a8db147d2981c22d4e38596527ec2402b57351c7 3490 debian-installer_20150422.dsc d0462a015052cce420820e7c9e6e79a095a97bc7 1379101 debian-installer_20150422.tar.gz Checksums-Sha256: e1d0723dd67f3bffa8374c4194be06236888a1e27c4959e95e55e793a37d72b0 3490 debian-installer_20150422.dsc ba4da4adf239ba797e5d4263fabe0f84e3bcf350476b2d58d8b9ff62c1b2fb44 1379101 debian-installer_20150422.tar.gz Files: c1510aad848331687b1b372b43888487 3490 devel optional debian-installer_20150422.dsc 76ccf6205bf77120e57dd2623df76fef 1379101 devel optional debian-installer_20150422.tar.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVN/ybAAoJEP+RSvDCs1UgxCwQAJxjoF1uUFqQbpxUYWQsywSf kwVaHtESPlECaDNc+xkT5V/LBN+fSsdMzQajREckAhyemQy4wmY363TdUkb2w5bq t0QAtVg59D1gJi9ZRxIAKrQRzUawFWy0c+zeKYOWWLwprRPKw37VGZA2prBfXoAw LUYmkvgEC+AbUzOBgZjYVCgmWVeW8RHRXyp8Eyt+fYGwf8jya5ltg6EtvWmErSO3 CgVcEX5k4FDlZosENeQQ6vu7RCShvUe8JDOcxxB7NKs+5RNh7JTcVvMHIOzrpUD4 AtrGW2Fg9Z2egupHgXwTzQ7DMRbmvF/TITqPhs9xpGwcdTUysWoHkZ6mA5aPhfOF lkAqNyJWEkyzFESCqN2D4kDRwatKZNMv40/dWjeEZ3sKWUtnIUwyy98QKSBHaKcb izkXrsjqUyrbnq4a9LQNXjC2XwH0khmigHOt7nEVbzZytG9vHo3qsKjonpHgvv89 Y5vc7VAoi8NvLJvABbNNSQvcRdQkt9eip8zvhRf1emFtzjEI5nCQqg9iye+6Lu16 y8YAPpBeZ6HW3sIFGFqipoCdBd1luRxw4he4+SRD/TEb3QGmJk/2NhCuC81WcKIs unp5F9x8UJF6CgRGhkfPUrTkl19CpY3sQhK1y570Dp0gd7M3b3VFWFWQYawA272u 6nzxK8rdhGf3GLRkqDsP =pAsO -END PGP SIGNATURE- Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1yl2hz-0001ww...@franck.debian.org
Processed: reassign 783041 to installation-reports, reassign 782877 to libgtk2-appindicator-perl, affects 782098
Processing commands for cont...@bugs.debian.org:
> reassign 783041 installation-reports
Bug #783041 [installation-reports (debian 8 jessie di-rc3 installer amd64 dvd)]
Advanced Options in Debian 8 Jessie DI-rc3 installer (Debian 8 Jessie DI-rc3
installer AMD64 DVD ( Re-submited)
Warning: Unknown package 'debian'
Warning: Unknown package '8'
Warning: Unknown package 'jessie'
Warning: Unknown package 'di-rc3'
Warning: Unknown package 'installer'
Warning: Unknown package 'amd64'
Warning: Unknown package 'dvd'
Bug reassigned from package 'installation-reports (debian 8 jessie di-rc3
installer amd64 dvd)' to 'installation-reports'.
Ignoring request to alter found versions of bug #783041 to the same values
previously set
Ignoring request to alter fixed versions of bug #783041 to the same values
previously set
> reassign 782877 libgtk2-appindicator-perl
Bug #782877 [src:libgtk-appindicator] libgtk-appindicator: please make the
build reproducible
Warning: Unknown package 'src:libgtk-appindicator'
Bug reassigned from package 'src:libgtk-appindicator' to
'libgtk2-appindicator-perl'.
No longer marked as found in versions libgtk-appindicator/0.15-1.
Ignoring request to alter fixed versions of bug #782877 to the same values
previously set
> affects 782098 + libgazebo5-dev
Bug #782098 [openexr,libopenexr-dev] openexr, libopenexr-dev: directory vs.
symlink conflict: /usr/share/doc/{openexr, libopenexr-dev} ->
/usr/share/doc/libopenexr6
Added indication that 782098 affects libgazebo5-dev
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
782098: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782098
782877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782877
783041: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783041
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.14297458571370.transcr...@bugs.debian.org
Please dak copy-installer 20150422 & hint it into testing
Hi, FTPmasters, please sync the installer from sid to testing: dak copy-installer 20150422 Release team, please hint it into testing: unblock debian-installer/20150422 urgent debian-installer/20150422 Happy release! Mraw, KiBi. signature.asc Description: Digital signature
Bug#763695: console-setup is slowest part of boot, not fast as setupcon manpage tells us
On Wed, 8 Oct 2014 18:27:04 +0300 Anton Zinoviev wrote: > On Wed, Oct 01, 2014 at 11:31:18PM +0200, Julian Andres Klode wrote: > > > > console-setup requires 800ms during a boot. The complete boot finishes > > in 4.1 seconds. This really should not be a shell script in the long > > term, but short term at least removing "fast" from the manual page > > would be a good idea... > > > > Here's a boot graph: > > https://people.debian.org/~jak/boot.svg > > One possible explanation is what Samuel Thibault proposed (for some > reason setupcon doesn't use cached keymap). The following is (may be) > another explanation. > > I don't know how exactly recent Debian systems boot so the following is > only a guess. Considering that keyboard-setup.service uses only 190 ms > compared to 823 ms for console-setup.service, I suppose that these 823 ms > are caused by forked printf commands (by setupcon) waiting for the > virtual consoles to become active. So during most of these 823ms the > scripts were waiting and didn't consume cpu resources. > > If my hypothesis is true, the proper fix is to improve the description > console-setup.service in order to run it only after the virtual consoles > become active. This, however, is not something I can do (with my > current knowledge). I am experiencing the same problem. I edited setupcon to add "set -x" at the beginning to help tracing where the slowness is. It doesn't look like printf is at fault. I also tried changing the amount of ACTIVE_CONSOLES in /etc/default/console-setup but it did not make much of a difference (I tried setting it to just tty1 and to the empty string). Logs, plots and systemd-blame at https://people.debian.org/~fsateler/console-setup/ Saludos -- 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/caafdzj-mpu7mexwftcixqaec-1fjgegfp7z2jxldxzutp4b...@mail.gmail.com
Re: Please dak copy-installer 20150422 & hint it into testing
On Thu, 2015-04-23 at 03:04 +0200, Cyril Brulebois wrote: > Release team, please hint it into testing: > > unblock debian-installer/20150422 > urgent debian-installer/20150422 Added. Regards, Adam -- 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/1429764040.4498.34.ca...@adam-barratt.org.uk
Re: Bug#780573: release-notes: Review from the d-i team
On 2015-04-19 21:23, Holger Wansing wrote: > Hi, > > Niels Thykier wrote: >> I tried to ask in #debian-i18n about the new languages, but so far no >> one has replied me. I am a bit overbooked, so if any you have time to >> follow on that, then I would greatly appreciate it. > > I have looked into this. Based on > http://anonscm.debian.org/cgit/d-i/debian-installer.git/log/build/translation-status > I compared the files from "Sat, 06 Apr 2013 18:00:22 +" > (which is equivalent to Wheezy release) and "Tue, 14 Apr 2015 03:11:00 +" > (this week). > If I leave out all languages that only changed the number of untranslated > strings, I get this: > > [...] > > So the new language in Jessie is: tg -> Tajik *applause* > > I have double-checked, Tajik is indeed not available in Wheezy installer, > but in Jessie. And it is available in both text and graphical installer > in Jessie. > > Based on that, I have prepared a patch against installing.dbk > (attached). > > > Holger > > Thanks, I have applied your patch as-is. ~Niels -- 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/5538972f@thykier.net
Re: Bug#780573: release-notes: Review from the d-i team
On 2015-04-20 08:26, Didier 'OdyX' Raboud wrote: > Le dimanche, 19 avril 2015, 20.17:27 Cyril Brulebois a écrit : >> Holger Wansing (2015-04-19): >>> The release-notes currently contain >>> >>> Graphical installer >>> >>> Graphical installer is now the default on supported platforms. >>> Text installer is still accessible from the very first menu, or if >>> the system has limited capabilities. >>> >>> AFAICS this is not true. >>> On the RC3 i386 netinst CD the text installer is still the default. >>> >>> Remove that paragraph? >>> >>> debian-boot: please confirm the status. >> >> Indeed, that was one of the plans for Jessie but the patches only got >> pushed a few days ago (IIRC, Didier can correct me if needed), and it >> seems a dangerous or at least non-trivial change at this point. > > That's correct. We're talking about #485586, for which I only pushed > patches on 29. March (sorry for that…). The patches are mostly > reorganisation and reordering, but I agree with KiBi: the risks at this > point are too high. > > Cheers, OdyX > Ok, I have removed the paragraph about the graphical installer. Thanks, ~Niels -- 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/5538979d.8080...@thykier.net
