Re: [Pkg-openssl-devel] Bug#827951: libssl udeb inclusion in Jessie
Le jeudi 23 juin 2016 à 23:13 +0200, jcris...@debian.org a écrit : > On Thu, Jun 23, 2016 at 12:55:54 +0200, Yann Soubeyrand wrote: > > > Le jeudi 23 juin 2016 à 11:20 +0200, k...@roeckx.be a écrit : > > > On Thu, Jun 23, 2016 at 10:58:54AM +0200, Yann Soubeyrand wrote: > > > > Package: openssl > > > > Severity: normal > > > > Version: 1.0.1t-1+deb8u2 > > > > X-Debbugs-CC: debian-rele...@lists.debian.org > > > > X-Debbugs-CC: debian-boot@lists.debian.org > > > > > > > > Hi, > > > > > > > > Marga Manterola provided a patch to build a libssl udeb as well as the > > > > libcrypto udeb that was included in Sid (#802591). Could this patch be a > > > > candidate for Jessie inclusion? If so, you can find a patch attached to > > > > this mail. > > > > > > Is there a reason why you would like it in jessie? Will the > > > installer start to make use of it? > > > > > > Kurt > > > > At the company I work for, we customize the installer to fit our needs > > and we make use of wget udeb's https support. It would make our task > > simpler not to have to maintain a modified version of openssl and wget > > packages. > > > That doesn't sound suitable for a stable update, sorry. > > Cheers, > Julien OK, I understand. Cheers Yann
Bug#828052: Sparc and "Invalid Release file, no entry for main/binary-sparc/Packages"
Package: debootstrap Version: 1.0.67 Severity: important I have a Debian 8.5 host on amd64/x86_64 with Testing enabled. I am attempting to setup a Sparc guest with Unstable enabled using the following command: qemu-debootstrap --arch=sparc --keyring /usr/share/keyrings/debian-ports-archive-keyring.gpg \ --variant=buildd --exclude=debfoster unstable debian-sparc http://ftp.ports.debian.org/debian-ports The command results in: I: Running command: debootstrap --arch sparc --foreign --keyring /usr/share/keyrings/debian-ports-archive-keyring.gpg --variant=buildd --exclude=debfoster unstable debian-sparc http://ftp.ports.debian.org/debian-ports I: Retrieving Release I: Retrieving Release.gpg I: Checking Release signature I: Valid Release signature (key id 69DDB0560EA86E87E83599B3B4C86482705A2CE1) E: Invalid Release file, no entry for main/binary-sparc/Packages According to the Debian Ports page at https://www.debian.org/ports/, Sparc is an official and supported.
Next d-i alpha release: late June
Hi, I've just checked with Ben, it seems we could be getting a 4.6 kernel suitable for testing (no regressions reported from previous version + mips* FTBFS fix) shortly. We could think about urgenting it into testing and releasing a new d-i early in the week, which seems OK on the -cd side too. Glibc maintainers (esp. Aurélien): you should then have a clear path for the new glibc in unstable. I'm not sure how much time it'll need to be ready, that's why I'd slightly prefer if we could go for a d-i release first (as outlined above). In case major blockers pop up, we would probably let you go ahead with the new glibc upload and postpone d-i until glibc reaches testing. Having checked with -release already, I'm freezing udebs right away. (Please cc me on replies.) KiBi. signature.asc Description: Digital signature
Processed: reassign
Processing commands for cont...@bugs.debian.org: > reassign 827733 openrc Bug #827733 [busybox] BusyBox Init + OpenRC Bug reassigned from package 'busybox' to 'openrc'. No longer marked as found in versions 1.22.0-19. Ignoring request to alter fixed versions of bug #827733 to the same values previously set > -- Stopping processing here. Please contact me if you need assistance. -- 827733: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827733 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: jessie won't install/boot on a Dell Poweredge R815
Please note that bootint with rootdelay=20 does not solve the problem. It only masks it. 1. If I attempt a fresh USB install of jessie, when md0 is correctly built before the install, the process of doing the fresh install breaks md0. When it gets to grub install, components of md0 are missing (even though all six components were present before the install). And grub-install fails. At this point it is impossible to complete the install and produce a bootable system. 2. If I do a fresh minimal USB install of wheezy, rebuilding md0 in the process, and then do a dist-upgrade to jessie, I can manually add rootdelay=20 in grub and boot into jessie with all six components of md0 present. But if I do so, then after boot, if I do dpkg-reconfigure pc-grub, doing that gives errors, drops components of md0, precludes me from adding them back, fails to install grub, and leaves the machine in an unbootable state. I fear that there is a problem writing to disk. Even if I boot with rootdelay=20, unless the kind of writes that dpkg-reconfigure pc-grub does are different, doing ordinary writes to disk may also corrupt the disk. Please let me know what new information you would like me to gather. Jeff (http://engineering.purdue.edu/~qobi)
Re: jessie won't install/boot on a Dell Poweredge R815
On Fri, Jun 24, 2016 at 06:22:37PM -0400, Jeffrey Mark Siskind wrote: >Please note that bootint with rootdelay=20 does not solve the problem. It only >masks it. > > 1. If I attempt a fresh USB install of jessie, when md0 is correctly built >before the install, the process of doing the fresh install breaks >md0. When it gets to grub install, components of md0 are missing (even >though all six components were present before the install). And >grub-install fails. At this point it is impossible to complete the install >and produce a bootable system. > > 2. If I do a fresh minimal USB install of wheezy, rebuilding md0 in the >process, and then do a dist-upgrade to jessie, I can manually add >rootdelay=20 in grub and boot into jessie with all six components of md0 >present. But if I do so, then after boot, if I do dpkg-reconfigure pc-grub, >doing that gives errors, drops components of md0, precludes me from adding >them back, fails to install grub, and leaves the machine in an unbootable >state. > >I fear that there is a problem writing to disk. Even if I boot with >rootdelay=20, unless the kind of writes that dpkg-reconfigure pc-grub does are >different, doing ordinary writes to disk may also corrupt the disk. > >Please let me know what new information you would like me to gather. Ummm. Checking back up-thread, I can see that you're using md0 across more than 4 disks and you're trying to boot off it with grub-pc. You're hitting BIOS limitations here - the BIOS is only capable of accessing 4 disks. I'm *guessing* that maybe the newer grub in jessie is just being pickier about checking BIOS access to those disks. Try just using 4 of the disks for md0, and I'd expect it to work. -- Steve McIntyre, Cambridge, UK.st...@einval.com "Arguing that you don't care about the right to privacy because you have nothing to hide is no different than saying you don't care about free speech because you have nothing to say." -- Edward Snowden
