Mapping stretch to stable.
Mapping stable to proposed-updates.
binary:acpi-modules-4.9.0-9-686-di is NEW.
binary:acpi-modules-4.9.0-9-686-pae-di is NEW.
binary:acpi-modules-4.9.0-9-amd64-di is NEW.
binary:affs-modules-4.9.0-9-4kc-malta-di is NEW.
binary:affs-modules-4.9.0-9-5kc-malta-di is NEW.
bin
linux_4.9.161-1_multi.changes uploaded successfully to localhost
along with the files:
linux_4.9.161-1.dsc
linux_4.9.161.orig.tar.xz
linux_4.9.161-1.debian.tar.xz
linux-doc-4.9_4.9.161-1_all.deb
linux-headers-4.9.0-9-common-rt_4.9.161-1_all.deb
linux-headers-4.9.0-9-common_4.9.161-1_all
linux_4.9.161-1_allonly.changes: binary upload requires Binary field
===
Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.
linux_4.9.161-1_allonly.changes uploaded successfully to localhost
along with the files:
linux_4.9.161-1.dsc
linux_4.9.161.orig.tar.xz
linux_4.9.161-1.debian.tar.xz
linux-doc-4.9_4.9.161-1_all.deb
linux-headers-4.9.0-9-common-rt_4.9.161-1_all.deb
linux-headers-4.9.0-9-common_4.9.161-1_a
Your message dated Wed, 27 Feb 2019 23:46:39 +0100
with message-id <20190227224639.f7qky5vxs2q7b...@inutil.org>
and subject line Closing
has caused the Debian Bug report #829541,
regarding Please backport *EDAC, ie31200_edac: Add Skylake support*
to be marked as done.
This means that you claim tha
Your message dated Wed, 27 Feb 2019 22:12:33 +
with message-id
and subject line Re: Bug#917524: initramfs-tools: Upgrade from initramfs-tools
package fails
has caused the Debian Bug report #917524,
regarding initramfs-tools: Upgrade from initramfs-tools package fails
to be marked as done.
T
Processing commands for cont...@bugs.debian.org:
> found 922306 4.9.144-3.1
Bug #922306 [src:linux] linux: btrfs corruption (compressed data + hole data)
Marked as found in versions linux/4.9.144-3.1.
> found 922306 4.9.144-3
Bug #922306 [src:linux] linux: btrfs corruption (compressed data + hole
Quoting Ben Hutchings (2019-02-27 19:37:41)
> Control: severity -1 wishlist
> Control: retitle -1 Add option to override filesystem type detection
>
> On Wed, 2019-02-27 at 18:38 +0100, Jonas Smedegaard wrote:
> > Quoting Jonas Smedegaard (2019-02-27 17:45:33)
> > > Building a system image using m
Control: severity -1 wishlist
Control: retitle -1 Add option to override filesystem type detection
On Wed, 2019-02-27 at 18:38 +0100, Jonas Smedegaard wrote:
> Quoting Jonas Smedegaard (2019-02-27 17:45:33)
> > Building a system image using multistrap,
> > including generating an initial ramdisk,
Processing control commands:
> severity -1 wishlist
Bug #923400 [initramfs-tools] initramfs-tools: failure inside chroot: W:
Couldn't identify type of root file system for fsck hook
Severity set to 'wishlist' from 'normal'
> retitle -1 Add option to override filesystem type detection
Bug #923400
Quoting Jonas Smedegaard (2019-02-27 17:45:33)
> Building a system image using multistrap,
> including generating an initial ramdisk,
> worked fine recently.
>
> Now it fails with this error message:
>
> W: Couldn't identify type of root file system for fsck hook
>
> It seems to me that git co
On Wed, 2019-02-27 at 03:01 +, Dmitry Bogatov wrote:
> [2019-02-25 05:45] shirish शिरीष
> > On 24/02/2019, Dmitry Bogatov wrote:
> >
> >
> >
> > > Interesting, you seems somehow got mountkernfs.sh script removed from
> > > runlevel S.
> > >
> > > Can you please invoke as root
> > >
> > >
Package: initramfs-tools
Version: 0.133
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Building a system image using multistrap,
including generating an initial ramdisk,
worked fine recently.
Now it fails with this error message:
W: Couldn't identify type of root file system
I ran a "btrfs check" on one of the partitions that had issues last night to
confirm that the file system was not damaged. No errors were found.
# btrfs check -p /dev/sdc1
Checking filesystem on /dev/sdc1
UUID: d6640b4b-bd59-47d5-bfd7-37b4c40fb3c6
checking extents [.]
checking free space cache
Package: linux-headers-4.9.0-8-amd64
I hit into the following bug when creating two VMs with virt-manager
configured with spice server. I started them sequentially, first
starts but the second fails to spawn with error:
Error starting domain: internal error: qemu unexpectedly closed the monitor:
Package: linux-image-4.19.0-2-amd64
Version: 4.19.16-1
I would like to try GVT like described in
https://github.com/intel/gvt-linux/wiki/GVTg_Setup_Guide to get native
3D accelaration in a KVM guest. Unfortunately, the kernel compile
options CONFIG_DRM_I915_GVT and CONFIG_DRM_I915_GVT_KVMGT are no
Two servers hung last night. Both events happened while a file was being copied
into the btrfs file system. No references or vm's were involved. It was a
simple file copy.
I had the opportunity to observe the system while it happened. It turns out
that the CPU time goes to 50% or more I/O wai
at bottom :-
On 27/02/2019, Dmitry Bogatov wrote:
>
>
> Seems there is no /etc/init.d/mountkernfs.sh on your system.
>
> Since your init system is systemd, I question, why do you need insserv
> in first place. Do you have bin:initscripts installed?
>
> My guess is that update-initramfs invokes
18 matches
Mail list logo
