clock-setup_0.127_i386.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 22 Jan 2016 07:50:17 +0100 Source: clock-setup Binary: clock-setup Architecture: source i386 Version: 0.127 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Christian Perrier Description: clock-setup - set up clock (udeb) Changes: clock-setup (0.127) unstable; urgency=medium . [ Ben Hutchings ] * Revert "Disable e2fsck superblock time check if RTC is set to local time". This is no longer needed since e2fsprogs version 1.42.13. Checksums-Sha1: bdd61c98eed7529a8d4c4dafcd88a254ec1c431a 1630 clock-setup_0.127.dsc 4e807e5e35e10a097f069b1b9717c084c9ec61e2 75712 clock-setup_0.127.tar.xz 4a447d1cf83dc3c2ad88ce8ec4ac7d1e17b66942 63268 clock-setup_0.127_i386.udeb Checksums-Sha256: 20b66ba15e1855866a9be6583901bbcd7153d8596e6db1c1459a293bf2b3e8fb 1630 clock-setup_0.127.dsc ef41c03c488e8e582c222c9398149b243a138b4806bf44e59b1ce7d2eb3571a7 75712 clock-setup_0.127.tar.xz 72663e4b97d9a673c998b9572660611eaa236c1dfb31d648c09ebea9455bf991 63268 clock-setup_0.127_i386.udeb Files: 065eb58d43e44c831c566170c8055722 1630 debian-installer standard clock-setup_0.127.dsc 6d6e9525ad1a3cea61a292ea2b58ffe0 75712 debian-installer standard clock-setup_0.127.tar.xz fae6d0d7d5a59c8d31f2568363c8f231 63268 debian-installer standard clock-setup_0.127_i386.udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWoduFAAoJEIcvcCxNbiWoXyYQALT0zoFILkNjUST9ahbDew0q 6YKmMOh5IJnOO3wbAX+3JmFcf82VW3rxuAZeLXu6eEU1TjYkXWSLuuI6s3epys3G KL21vJvlVQeWYSyeVJfnVVYFyisxiyvk+/fNKJUwQ4cKJEdam3BvUOrB6ifgSxPp 4ncQ4GNwgSiN2+WB+JjmrNuXnMAKbbAd5O0sIGtERQkWpGdxL2b1R+i3S8nDoS/w 9OA6hMkMzJY9jYM3+UtTHiKWWlSwsxJBmRIO+mQCKlR2Lg/bj0M/SvzZ6fxTK6q0 kKo6HV3M/6V/BDMqpQWg6/hiD8NWrmhe3Y+s/adi8N9FKY5oiXeIaveTO+9h2Auz MOu0ADzdjnE1tGmh49Iu8uQpXjRR01J7FA47a7EOKr9tOQ3XoBVUnjvbXhkfeCqf 0OBNrRvYnCnfVQqSyEUdFV16qUKkdPKXjmQb1xcdmZV94JGmlBtP5c70RD4Wn0WF gFJNUkUkwoQlELKbwsn81dyfa6n6trKuMQvIUd2oImkkisvf2ynQeAxKpyZo3++B 8DkottD53CtEL2308SLzotPQLOpoV6w9bUePEALr1CU5SkCRK74SG1dBXIB/yr0V gsSLrdysAM5F/KTSL+I0k/pJ1fMxran5mPl+WhpdNch5gsYbPlWSxDx+wjtYr3Km HTI2qyQ5D0IWlCANDhNg =/RFZ -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processed: reassign 812207 to linux-image-3.16.0-4, reassign 811353 to installation-reports ...
Processing commands for cont...@bugs.debian.org: > reassign 812207 linux-image-3.16.0-4 3.16.7-ckt20 Bug #812207 [src:linux-image-3.16.0-4] linux: AUFS can hang up; Please update to v20160111 or later Warning: Unknown package 'src:linux-image-3.16.0-4' Bug reassigned from package 'src:linux-image-3.16.0-4' to 'linux-image-3.16.0-4'. Warning: Unknown package 'linux-image-3.16.0-4' Warning: Unknown package 'linux-image-3.16.0-4' No longer marked as found in versions linux-image-3.16.0-4/3.16.7-ckt20. Warning: Unknown package 'linux-image-3.16.0-4' Warning: Unknown package 'linux-image-3.16.0-4' Ignoring request to alter fixed versions of bug #812207 to the same values previously set Warning: Unknown package 'linux-image-3.16.0-4' Bug #812207 [linux-image-3.16.0-4] linux: AUFS can hang up; Please update to v20160111 or later Warning: Unknown package 'linux-image-3.16.0-4' There is no source info for the package 'linux-image-3.16.0-4' at version '3.16.7-ckt20' with architecture '' Unable to make a source version for version '3.16.7-ckt20' Marked as found in versions 3.16.7-ckt20. Warning: Unknown package 'linux-image-3.16.0-4' > reassign 811353 installation-reports Bug #811353 [cdrom/installation-reports] Proxy settings in apt will not get updated after initial values set Warning: Unknown package 'cdrom/installation-reports' Bug reassigned from package 'cdrom/installation-reports' to 'installation-reports'. Ignoring request to alter found versions of bug #811353 to the same values previously set Ignoring request to alter fixed versions of bug #811353 to the same values previously set > reassign 812192 insighttoolkit4 Bug #812192 [insightoolkit4] insightoolkit: Package depends on no longer built package libdcmtk2-dev Warning: Unknown package 'insightoolkit4' Bug reassigned from package 'insightoolkit4' to 'insighttoolkit4'. Ignoring request to alter found versions of bug #812192 to the same values previously set Ignoring request to alter fixed versions of bug #812192 to the same values previously set > reassign 811211 rakudo 2015.11-1 Bug #811211 [rakudo-star] rakudo-star: panda disfunctional Warning: Unknown package 'rakudo-star' Bug reassigned from package 'rakudo-star' to 'rakudo'. No longer marked as found in versions rakudo-star/2015.11-1. Ignoring request to alter fixed versions of bug #811211 to the same values previously set Bug #811211 [rakudo] rakudo-star: panda disfunctional Marked as found in versions rakudo/2015.11-1. > reassign 811212 rakudo 2015.11-1 Bug #811212 [rakudo-star] rakudo-star: panda manpage should list command line options Warning: Unknown package 'rakudo-star' Bug reassigned from package 'rakudo-star' to 'rakudo'. No longer marked as found in versions rakudo-star/2015.11-1. Ignoring request to alter fixed versions of bug #811212 to the same values previously set Bug #811212 [rakudo] rakudo-star: panda manpage should list command line options Marked as found in versions rakudo/2015.11-1. > reassign 799472 golang-github-golang-leveldb 0.0~git20150720.0.df57eb2-1 Bug #799472 [src:golang-github-golang-leveldb] golang-github-golang-leveldb: Non-determistically FTBFS due to unreliable tests Warning: Unknown package 'src:golang-github-golang-leveldb' Bug reassigned from package 'src:golang-github-golang-leveldb' to 'golang-github-golang-leveldb'. Warning: Unknown package 'golang-github-golang-leveldb' Warning: Unknown package 'golang-github-golang-leveldb' No longer marked as found in versions golang-github-golang-leveldb/0.0~git20150720.0.df57eb2-1. Warning: Unknown package 'golang-github-golang-leveldb' Warning: Unknown package 'golang-github-golang-leveldb' Ignoring request to alter fixed versions of bug #799472 to the same values previously set Warning: Unknown package 'golang-github-golang-leveldb' Bug #799472 [golang-github-golang-leveldb] golang-github-golang-leveldb: Non-determistically FTBFS due to unreliable tests Warning: Unknown package 'golang-github-golang-leveldb' There is no source info for the package 'golang-github-golang-leveldb' at version '0.0~git20150720.0.df57eb2-1' with architecture '' Unable to make a source version for version '0.0~git20150720.0.df57eb2-1' Marked as found in versions 0.0~git20150720.0.df57eb2-1. Warning: Unknown package 'golang-github-golang-leveldb' > thanks Stopping processing here. Please contact me if you need assistance. -- 799472: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799472 811211: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811211 811212: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811212 811353: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811353 812192: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812192 812207: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812207 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#809476: Linux 4.4-rc6 fails to boot on QNAP TS-109
On Wed, Jan 6, 2016 at 9:41 PM, Roger Shimizu wrote: > [Resend previous email to keep ARM experts in CC] > > On Thu, Dec 31, 2015 at 9:09 AM, Martin Michlmayr wrote: >> I tried to boot Debian's 4.4-rc6 kernel on my QNAP TS-109 and it failed >> to boot with: >> [ 19.380002] Unpacking initramfs... >> [ 19.380044] Initramfs unpacking failed: junk in compressed archive > > I see this error message on my Linkstation boxes for long time, but > most of time they just boot fine. > After seeing your report, now I understand the root cause why failing > sometimes. :-) > >> -U-Boot-Kernel-Address: 0x8000 >> +U-Boot-Kernel-Address: 0x00c08000 > > I tried this on local db (/etc/flash-kernel/db) of my Linkstation, but > it failed to boot. > Except above change, did you also changed the address in uboot > command? (like a few lines below) > >>> cp.b 0xff20 0x80 0x3f >>> setenv bootargs console=ttyS0,115200n8 root=/dev/ram rw >>> initrd=0x80,0x3f >>> bootm 0xff00 > >> u-boot loads it like this: >> >> ## Booting image at 0040 ... >>Load Address: 8000 >>Entry Point: 8000 > > I also don't understand where the address "0040" comes from. It's > neither in flash-kernel's db nor in uboot setting. > From my understanding, the kernel image stores in flash, which address > is 0xff00, and it will be copied to "8000" by uboot on boot > time, then kernel will uncompress the image and then boot. Am I missed > something? I asked Paul (in CC) who has been working on arm platform for years. He told me that, as my case, "ext2load" will load the uImage to 0x10 as instructed, then "bootm" will extract the "uImage" to "zImage" format to 0x8000 as mkimage configured, and kernel will boot from 0x8000 with initrd in 0x80. And these two addresses are also fixed in the kernel, which usually specified in "arch/arm/mach-/Makefile.boot". e.g. $ cat arch/arm/mach-orion5x/Makefile.boot zreladdr-y += 0x8000 params_phys-y := 0x0100 initrd_phys-y := 0x0080 The patch for this bug changed kernel start address from 0x8000 to 0xc08000. But kernel's zreladdr-y is still 0x8000, without changing. If kernel really uses this “zreladdr-y”, it may be trouble. If it only for "make uImage" to pass to mkimage when compiling, it will not be any problem. >From the result of "grep" in kernel tree, the latter one seems to be true. Cheers, Roger
Re: [PATCH initramfs-tools 0/4] Changes to busybox integration
On Fri, 2016-01-22 at 08:58 +0300, Michael Tokarev wrote: > 22.01.2016 01:14, Ben Hutchings wrote: > > This series removes the busybox hook script and definition of > > BUSYBOXDIR from initramfs-tools, leaving busybox itself responsible > > for these. > > Oh well. How many times I talked with Max on IRC, sent patches, > created a git tree for initramfs to pull from.. His answer has > always been the same: no need. So I gave up, creating an ugly > zzz-busybox which undoes the mess done in initramfs script. That's strange as the TODO file said it should be done. > Please note that once the d-i team prevented me from maintaining > busybox, this package remains unmaintained. So maybe it is a > better idea to remove usage of busybox in initramfs (which this > series actually does). It doesn't; busybox is still recommended and used by default. Ben. > Thank you Ben! > > (And yes, I'm still subscribed to busybox package, for unknown > reason). > > /mjt > -- Ben Hutchings Quantity is no substitute for quality, but it's the only one we've got. signature.asc Description: This is a digitally signed message part
Bug#809476: Linux 4.4-rc6 fails to boot on QNAP TS-109
* Roger Shimizu [2016-01-22 21:56]: > And these two addresses are also fixed in the kernel, which usually > specified in "arch/arm/mach-/Makefile.boot". > e.g. $ cat arch/arm/mach-orion5x/Makefile.boot >zreladdr-y += 0x8000 > params_phys-y := 0x0100 > initrd_phys-y := 0x0080 > > The patch for this bug changed kernel start address from 0x8000 to 0xc08000. > But kernel's zreladdr-y is still 0x8000, without changing. If kernel > really uses this “zreladdr-y”, it may be trouble. > If it only for "make uImage" to pass to mkimage when compiling, it > will not be any problem. > > >From the result of "grep" in kernel tree, the latter one seems to be true. Yes, that's my understanding too. -- Martin Michlmayr http://www.cyrius.com/
More of cdebconf and GTK+3
Hi everyone, I just realised something this afternoon about cdebconf and GTK+, which is the plugins. Obviously they'd have to be recompiled for GTK+3 as well, so I tried to do that. The build failed with the use of old stuff from GTK+2, which I replaced as they were trivial. While there, I also tweaked the Makefile.in to actually apply CPPFLAGS when compiling. It doesn't fix the OpenGL issue for d-i ; but at least that's that done. Regis
Bug#810828: flash-kernel: update kernel address for Linkstation LS-WTGL
* Roger Shimizu [2016-01-13 01:58]: > For Linkstation LS-WTGL boots fine with linux-image-4.3, but fails with > linux-image-4.4. > Here's the fix ported from QNAP TS-109 (Bug #809476), and it's been confirmed > to boot well on LS-WTGL. I don't fully grok this stuff either but I think this patch is not the right solution. The log you sent shows: bootcmd=ide reset; ext2load ide 0:1 0x0010 /$(kernel); ext2load ide 0:1 0x0080 /$(initrd); setenv bootargs $(bootargs_base) $(bootargs_root) $(bootargs_debug) $(buffalo_ver); bootm 0x0010 0x0080 So the kernel is loaded to 0x0010 and the ramdisk to 0x0080 Your patch sets the kernel load address to 0x00c08000. So u-boot will still load the kernel to 0x0010 but then (I guess) it's uncompressed at 0x00c08000. The problem is that 0x00c08000 is only 4 MB after the start of the ramdisk (0x0080), which doesn't leave a lot of space for the ramdisk. You can change initramfs-tools from MODULES=dep to MODULES=most, generate and I suspect it wouldn't boot. Can you try if something like 0x01a08000 works? BTW, I assume we need to change this for all Linkstation devices. -- Martin Michlmayr http://www.cyrius.com/
Preseeding multiple volume groups
Hi,
I am trying to build two volume groups using Cobbler but failed.
I can only see one volume group created.
I also tried
d-i partman-auto-lvm/new_vg_name string lxc exportvg
and
d-i partman-auto-lvm/new_vg_name multiselect lxc, exportvg
but failed as well.
What might be the issues?
Regards,
Kevin SZ
d-i partman-auto/choose_recipe select custompartitioning
d-i partman-auto-lvm/new_vg_name string lxc
#d-i partman-auto-lvm/new_vg_name multiselect lxc exportvg
d-i partman-auto/expert_recipe string \
custompartitioning :: \
512 1 512 ext2 \
$primary{ } \
$bootable{ }\
method{ format } format{ } \
use_filesystem{ } filesystem{ ext2 }\
label{ boot } \
mountpoint{ /boot } \
. \
155648 1 155648 ext4\
$primary{ } \
method{ lvm } \
device{ /dev/sda2 } \
vg_name{ lxc } \
. \
2048 1 2048 linux-swap \
$lvmok{ } in_vg{ lxc } \
lv_name{ swap00 } \
method{ swap } format{ }\
. \
153600 1 153600 ext4\
$lvmok{ } in_vg{ lxc } \
lv_name{ root00 } \
method{ format } format{ } \
use_filesystem{ } filesystem{ ext4 }\
label{ root } \
mountpoint{ / } \
. \
102400 1 102400 ext4\
$primary{ } \
method{ lvm } \
device{ /dev/sda3 } \
vg_name{ exportvg } \
. \
102400 1 102400 ext4\
$lvmok{ } in_vg{ exportvg } \
lv_name{ app00 }\
method{ format } format{ } \
use_filesystem{ } filesystem{ ext4 }\
label{ app }\
mountpoint{ /app } \
. \
Bug#767682: D-I: installer hangs on re-formatting ext4 partition (having grub in the partition boot record).
Hello! > Following is a workaround for this problem in preseed environment that > worked for me: > > d-i partman/early_command string sed -r -e '/^[[:space:]]*mkfs\. > /s/^([[:space:]]*)(mkfs\.[^[:space:]]+)/\1\2 -F/g' -i /lib/partman > /commit.d/50format_ext3 Which basically adds the force flag to mkfs.ext3 so it will try to create the filesystem " even if the specified device is not a partition on a block special device, or if other parameters do not make sense." (manpage mkfs.ext3). Is there a particular reason why we use "-f" in partman-btrfs [1] for mkfs but not in partman-ext3 for mkfs? It seems that running mkfs.ext3 with -F would make the formatting process more robust for most people when reading through this bug report. We're also seeing this issue on sparc64 where mkfs.ext3 is probably choking on the Sun disklabels. I'd therefore suggest to add -F to mkfs.ext3 in partman-ext3. Thanks, Adrian > [1] http://anonscm.debian.org/cgit/d-i/partman-btrfs.git/tree/commit.d/format_btrfs#n62 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
