Hi *,
since yesterday (roughly, probably earlier) some of my live-build images
fail due to a new and faulty version of shim-signed.
After a quick look on packages.d.o, I was pretty confused: nothing new
listeded there for stable. Only 'apt-cache policy shim-signed' revealed
to me that a new
Hi,
not sure against which package to file a bug so I'm posting here.
Since today on apt update I get:
E: Release file for
http://ftp.de.debian.org/debian-debug/dists/bullseye-debug/InRelease is
expired (invalid since 4h 32min 12s). Updates for this repository will
not be applied.
E: Release
I haven't received a reply so far, so forwarding to -devel.
Thanks
Daniel
Forwarded Message
Subject: nvidia-driver meta package missing from stretch bpo
Date: Sat, 13 Apr 2019 20:32:20 +
From: Daniel Reichelt
To: Andreas Beckmann , Debian NVIDIA Maintainers
Hi
Thanks for your detailed explanation!
> PS: today I uploaded src:nvidia-graphics-drivers with transitional
> packages nvidia-driver, xserver-xorg-video-nvidia added on i386,armhf
> that depend on the corresponding legacy driver packages.
> I could do that for nvidia-smi as well. Any other
Hi Axel,
I'm wondering why there's no nvidia-smi:i386=410.104-1~bpo9+1 but only
390.87-8~bpo9+1.
Has the binary package just not been built yet for i386/stretch-bpo or
is nvidia-smi no longer supported for i386 by upstream?
Thanks!
Daniel
signature.asc
Description: OpenPGP digital signature
> And surely we support other, strange and not so strange, choices,
> sometimes more and sometimes less, but yawn.
And yet Debian claims to support - pardon - offer init systems other
than systemd for usage.
Either: make a clean cut, kick out everything that has been obsoleted™
by pötterd,
> Shouldn't that be the other way around? Having .timer but not a cronjob is
> a nasty bug, having a cronjob but not .timer is fine (at least unless you
> have no cron implementation at all).
+1!
signature.asc
Description: OpenPGP digital signature
Hi,
why does libnss3/buster depend on libc6 >= 2.28 for i386 but for amd64,
>= 2.14 suffices?
I'm running stretch/amd64 with libnss3 pinned to buster, using stretch's
libc6. On that machine, live-build'ing an i386 stretch image no longer
works since the current libnss3 migrated to buster a few
On 11/22/18 1:56 PM, Ian Jackson wrote:
> (Bear in mind of course that happily our build machines
> *can* be reverted because they are frequently re-imaged.[…])
Using code from a debian package? Some script being hand-knitted using
hot needles? Anyways, I'm interested in how this is done…"this"
On 01/23/2018 10:56 AM, Philipp Kern wrote:
> On 01/23/2018 01:34 AM, Daniel Reichelt wrote:
>> In order to not interfere with the modules provided by the linux-image-*
>> packages, [...]
>> (An alternative to changing module names might be to use
>> update-alternati
Hi,
what about ripping out the affected kernel modules and provide the
patched sources in a separate package and have them built at install
time via DKMS?
In order to not interfere with the modules provided by the linux-image-*
packages, you could
- rename the kernel modules provided by your
On 01/07/2018 07:47 PM, Boyan Penkov wrote:
> and a backport (4.14.0-bpo2) -- in light of meltdown --
To avoid a false sense of security: according to [1], [2], [3], the
current stretch-bpo kernel (linux-image-4.14.0-0.bpo.2-$arch) does *NOT*
yet include any mitigations against meltdown.
Daniel
On 10/25/2017 08:03 PM, Felipe Sateler wrote:
> Mea Culpa. This was a bug in the "defaults-disabled" implementation. I
> have just uploaded a fixed version.
>
> Thanks for reporting.
Don't sweat it, big thanks for your quick response from me, too.
signature.asc
Description: OpenPGP digital
Thanks a lot, Adam, for your detailed answer!
With your information I could hunt this down and just filed #879771.
Cheers
Daniel
signature.asc
Description: OpenPGP digital signature
Hi *,
for development purposes I frequently create xen-vms via
xen-create-image (jessie, stretch, buster, sid - each in 32 and 64bit)
on a stretch Dom0. In a custom role script for xen-tools, I install
sysvinit-core. (For non-users of xen-tools: this happens after
debootstrap has completed.)
On 08/12/2017 02:16 PM, Tollef Fog Heen wrote:
> While I think we might want to ship buster with TLS 1.0 available, I
> think running with it disabled for parts of the development cycle is
> very useful, since it exposes bugs we have in packages that will use
> that version out of the box (isync
Hi folks,
when I do 'apt-get source linux' with jessie+sid enabled in sources.list,
there's no way to select jessie's ksrc version by target release. Neither
of these work:
- apt-get source linux
- apt-get -t jessie source linux
- apt-get source linux/jessie
Everytime the result is:
17 matches
Mail list logo
