On Sat, 2011-08-20 at 16:17 +0200, Andreas Barth wrote:
> * Henrique de Moraes Holschuh (h...@debian.org) [110820 14:39]:
> > Yes. And we can easily maintain a current one for Debian-packaged software,
> > although the initial build of such a blacklist will take some work.
>
> Actually, the exist
On Wed, 2011-08-31 at 11:57 +0200, Lucas Nussbaum wrote:
[...]
> But a different thread library that has clear POSIX compliance bugs[*]
> is the kind of things that make me fear that many more packages than we
> see currently are broken on kfreebsd. And I'm not sure that it's where
> we want to spe
kept on the signers' own systems, not on kernel.org. So I
am confident that our upstream sources were not modified by the
intruder.
Ben.
--
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
On Tue, 2011-09-06 at 14:44 +0200, Daniel Bayer wrote:
> Package: linux-libc-dev
> Version: 3.0.0-3
> Severity: normal
> File: /usr/include/x86_64-linux-gnu/asm/errno.h
>
> Hi,
>
> since asm/errno.h was moved to the arch specific sub directory it is
> no longer possible to create 32 Bit Binaries
>
> Is this the right address?
> Any ideas concerning this problem?
This may be a bug in the firewire_ohci driver.
Please send the output of 'lspci -vnn', the output of
'cat /proc/version', and a summary of the information you sent to the
debian-user list.
Ben
0:0/block/sr0'
> Sep 9 22:00:48 debian2 udevd-work[21697]: no reference left, remove
> '/dev/dvdrw'
> [... no attempt to create a new /dev/dvdrw ...]
> Sep 9 22:00:48 debian2 udevd[435]: seq 1275 done with 0
>
> --
>
> It looks as if xorriso's activi
to improve the relationship of my burn software with udev.
>
> But i need instructions. Where to ask for them ?
Have you asked the udev developers *why* it is doing this problematic
and apparently redundant work in case of a 'change' event on a CD drive?
Ben.
--
Ben Hutchings
If m
olve, due to the PCI ID overlap with r8169.ko
> shipped by the kernel packages themselves. This driver claims
> 10ec:8168, which is also taken by the in-kernel r8169.ko module.
[...]
Agree, this should not be added to the archive.
If people are in a hurry to get new support for new dev
roper
alignment for struct foo and to optimise the memcpy() accordingly. And
yes, this is something that gcc really does.
Pointers to an unaligned instance of a structure generally need to be
declared as void *, char * or unsigned char * (or const-qualified
versions).
Ben.
--
Ben Hutchings
Never put off till tomorrow what you can avoid all together.
signature.asc
Description: This is a digitally signed message part
r it's attached. This might need a workaround in the driver.
> All of this is of course speculation without any knowledge of how stuff
> works in reality, so could be pure imagination.
>
> My working hypothesis is that once I know the answer to the Q: above,
> I'll know t
o keep up to date.
It is up to the customers to demand this. (And if end users find they
are exposed to known security issues because product and SoC
manufacturers don't feel any moral obligation to update them, a few
lawsuits might get their attention.)
Ben.
--
Ben Hutchings
On Sun, 2014-11-30 at 21:48 +0800, Paul Wise wrote:
> On Sun, Nov 30, 2014 at 3:11 AM, Ben Hutchings wrote:
>
> > working upstream
>
> Are there any vendors of ARM-based devices who are doing that?
Most of the SoC vendors seem to be doing *some* work to get their chips
support
ernel/git/torvalds/linux.git/commit/?id=da3b0ab75aadab63d1ffd5563100c9386e444dad
Maybe.
> Broadwell
> commit:
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=afdb74fd708fb4330485212f76a70b91967b1f70
Maybe. (But that's just audio.)
Please open bugs against src:linux fo
-gnu/libc.so.6
GNU C Library (Debian GLIBC 2.19-13) stable release version 2.19, by Roland
McGrath et al.
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULA
t serves as a reminder of the old Unix workstations of the 90s
and the infatuation of the some of the workstation vendors with Windows
NT. (Now we know that making Windows portable doesn't mean applications
get ported, and the workstations largely got replaced by PCs rather than
just changing OS. But then some of those PCs ended up running Linux...)
Ben.
--
Ben Hutchings
Lowery's Law:
If it jams, force it. If it breaks, it needed replacing anyway.
signature.asc
Description: This is a digitally signed message part
But the acknowledgement mail should tell you how to subscribe, if you
aren't already subscribed.
Ben.
--
Ben Hutchings
Larkinson's Law: All laws are basically false.
signature.asc
Description: This is a digitally signed message part
On Wed, 2015-01-21 at 17:07 +1300, Chris Bannister wrote:
> On Mon, Jan 19, 2015 at 01:03:52AM +0000, Ben Hutchings wrote:
> > On Mon, 2015-01-19 at 08:37 +0800, Paul Wise wrote:
> > > On Mon, Jan 19, 2015 at 8:06 AM, Don Armstrong wrote:
> > >
> > > > I
ssie can not be used in a production environment on a
> Corporate Network, for example...
[...]
Please, don't exaggerate. Debian is already widely used with the Linux
3.16. Apparently certain configurations don't work properly, but we can
probably fix that.
Ben.
--
Ben Hutchings
H
On Thu, 2015-02-12 at 21:13 +0100, Jaromír Mikeš wrote:
>
>
> 2014-10-06 23:21 GMT+02:00 Jaromír Mikeš :
> 2014-10-06 18:28 GMT+02:00 Ben Hutchings
> :
> On Mon, 2014-10-06 at 09:04 +0200, Jaromír Mikeš
>
]
Yes, exactly. Laying any blame on systemd for this is completely
unreasonable.
(It might be more reasonable to blame initramfs-tools if it didn't give
you any warnings.)
Ben.
--
Ben Hutchings
Never attribute to conspiracy what can adequately be explained by stupidity.
signature.asc
Description: This is a digitally signed message part
asn't perfect but it was useful
to laptop users for a long time.
Ben.
--
Ben Hutchings
Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer
signature.asc
Description: This is a digitally signed message part
system will be run.
If Windows is not listed in the menu, it has probably been erased and
you will need to use Windows installation media (such as a DVD) to
reinstall it.
Ben.
--
Ben Hutchings
Editing code like this is akin to sticking plasters on the bleeding stump
of a severed limb. - me, 29 Jun
t; Squeeze-lts version of debian-archive-keyring doesn't contain the
> jessie's key, so verifying the second signature will fail.
>
> I think this is a bug, but i was not sure about which package should i
> fill against.
I think that would be ftp.debian.org.
Ben.
--
Ben Hutchi
ing and base maintenance.
>
>
> I understand the need to plan python3 switch, however we cannot block
> tools used by the community.
[...]
Yes we can. There are many popular programs not packaged in Debian
because they do not meet our standards.
Ben.
--
Ben Hutchings
A free so
y on installation, thus
> keeping the system bootable, with the documentation that the
> configuration change should be (a) manually and (b) atomically?
[...]
We don't currently have a way for packages to install kernel parameters
that boot loaders should append to the command line. I think we s
nce systemd 215-14. Previously there was another race condition
in updating that file (#765577).
> If the answer of the last question is "no", whatever the default
> that will be chosen, I will configure my systems to use MAC-based
> names but with a different template (enX
hardware that gets a different locally-
assigned address at each boot or hotplug?
Ben.
--
Ben Hutchings
For every action, there is an equal and opposite criticism. - Harrison
signature.asc
Description: This is a digitally signed message part
r architecture using Device Tree) the on-board
indices should be specified as aliases 'ethernet0', 'ethernet1', etc.
The aliases will be listed in the uevent as OF_ALIAS_0 (or OF_ALIAS_1,
etc., as a device can have multiple aliases).
Ben.
--
Ben Hutchings
For every action, there
On Mon, 2015-05-11 at 12:16 +0200, Josselin Mouette wrote:
> Ben Hutchings wrote:
> > The NM configuration is based on MAC addresses and doesn’t care
> about
> > the interface name at all. This is the exact opposite of “handling
> > dy
sed program as the default network configuration system.
> For a start it would make python transitively important.
I do, it's about time we had a decent scripting language in the base
system.
Ben.
--
Ben Hutchings
Unix is many things to many people,
but it's never been everything to anybody.
signature.asc
Description: This is a digitally signed message part
to do the
> conversion?
It gave the option to retry conversion (assuming you manually fix
something before answering) or to continue without automatic conversion.
In that case the old kernel version would generally still be available
as a fallback, whereas this is of course not true with udev.
Ben.
--
]
Installation of a package from the 'metapackages' section does *not*
mark its dependencies as automatically installed.
Ben.
--
Ben Hutchings
Hoare's Law of Large Problems:
Inside every large problem is a small problem struggling to get out.
signature.asc
Description: This is a digitally signed message part
table (hyperv-daemons built from linux
-tools source), and could possible be backported to jessie if they are
that important. However, I think some more work is needed to integrate
them properly.
Ben.
--
Ben Hutchings
[W]e found...that it wasn't as easy to get programs right as we had tho
On Sun, 2015-08-16 at 21:49 +0200, Hideki Yamane wrote:
> On Sun, 16 Aug 2015 10:43:17 +0200
> Ben Hutchings wrote:
> > They are now packaged in unstable (hyperv-daemons built from linux
> > -tools source), and could possible be backported to jessie if they are
> > tha
d append by default?
There are plenty of packages that this would be useful for. For x32
the installer (or maybe a package such as base-files) could add the
'syscall.x32=y'.
Ben.
--
Ben Hutchings
Always try to do things in chronological order;
it's less confusing that way.
signature.asc
Description: This is a digitally signed message part
binaries
> > could only be used with an appropriate boot option? This however isn't
> > any issue with the i386-architecture, but only on using this arch in
> > an chroot in an amd64-installation.
> x32 is not just i386 binaries (though I'm curious why this should be
&
though it has a few modern instruction set extensions
> (notably for security). So, i386 needs to stick around for the
> foreseeable future.
[...]
The last I heard, all Quark chips have serious bugs that prevent Debian
i386 from running on them.
Ben.
--
Ben Hutchings
Always try to do things in c
On Thu, 2015-08-27 at 10:45 -0700, Josh Triplett wrote:
> Ben Hutchings wrote:
> > On Wed, 2015-08-26 at 12:08 -0700, Josh Triplett wrote:
> > > Andreas Barth wrote:
> > > > Specific issues:
> > > > - for i386, there is still sold new hardware with 32bit
tion as "modem".
The download behaviour should not be dependent on 'is the default route
going through a cellular modem', but 'is the default route [relatively]
expensive'.
Plenty of people use cellular data as their primary Internet connection
and would therefore
eived patches for these headers (usually spelling fixes) I would
make the corresponding change to the unpublished file as well. I think
that, given the choice, outside developers would still have preferred
editing the C header files, so I was fairly comfortable with this.
Ben.
> [1] https:
age in both of the
> cases outlined above?
We should not do in this in the second case, since it is supposed to
work. (But a warning might be reasonable.)
Ben.
--
Ben Hutchings
The obvious mathematical breakthrough [to break modern encryption]
would be
we refer
to jessie's status (and future releases when regular security support
for them ends).
Ben.
--
Ben Hutchings
The obvious mathematical breakthrough [to break modern encryption]
would be development of an easy way to factor large prime numbers.
but "supported by LTS", which might be confusing to these users. So,
> maybe just fix this nitpick?
[...]
Although Freexian organises funding for LTS work, there are other LTS
contributors paid directly by other organisations or working on their
own time. So the best name we have for those
nizations, complete with the restrictions that might come
> with that.
Debian can't afford to pay developers in general, and previous
proposals to pay specific developers were not well received. So, I
don't this happening.
Ben.
> Another way is for Debian websites to not solic
lightly. So what about
> reverting it now so things don't degrade, then having a flamewar what to do?
We already know what to do, which is to prioritise our upcoming release
and the architectures that will be included in it. We do not allow
Debian ports to hold back changes
On Sun, 2018-11-04 at 13:15 +0100, Manuel A. Fernandez Montecelo wrote:
> Hi,
>
> 2018-11-04 01:13 Ben Hutchings:
> > On Sat, 2018-11-03 at 23:46 +0100, Adam Borowski wrote:
[...]
> > > A regression of this scale shouldn't be done lightly. So what about
> >
On Sun, 2018-11-04 at 22:05 +0100, Michael Biebl wrote:
> Am 04.11.18 um 20:30 schrieb Jeremy Bicha:
> > On Sun, Nov 4, 2018 at 11:33 AM Ben Hutchings wrote:
> > > I do like the proposal of adding a librsvg-c for just the architectures
> > > that don't have
other hand, most of my reply to willy's mail was not addressed to
> him, but to debian-devel@ at large, to have everybody else understand
> how silly what he did was.
[...]
This is the problem. Whether or not it's "silly", that doesn't justify
making a public examp
is no longer supported by
> Debian contrib/non-free.
I'm not aware of any gap. In fact, at the kernel level, there is some
overlap where the newest models supported by radeon are also supported
(on an opt-in basis) by amdgpu.
The proprietary AMD graphics stack now depends on the amdgpu ker
o support a minority of
users, but we try to follow them anyway.
Yesterday's special case (SMP, hotplug, mobile, 64-bit, ...) often
becomes tomorrow's common case.
Ben.
--
Ben Hutchings
Lowery's Law:
If it jams, force it. If it breaks, it needed replacing anyway.
signa
On Sat, 2018-11-24 at 21:51 +0100, Adam Borowski wrote:
> On Sat, Nov 24, 2018 at 06:06:16PM +0000, Ben Hutchings wrote:
> > On Sat, 2018-11-24 at 15:21 +, Simon McVittie wrote:
> > [...]
> > > Recent AMD GPUs use the "amdgpu" kernel driver and its accompa
icularly good term to describe the unique feature of the new
> repo either. In my eyes, 'fastpaced' makes the point far better.
>
> But as said, the main argument against calling it 'rolling' is that it
> would create confusion due to the name already being used in other
> (Debian-related) contexts.
At the risk of bikeshedding, some alternate names that might be less
confusing:
- fresh-apps
- evergreen
- rolling-apps
Ben.
--
Ben Hutchings
Power corrupts. Absolute power is kind of neat. - John Lehman
signature.asc
Description: This is a digitally signed message part
nvestigate the bugs. You said
> you provided links, but I couldn't find any in your e-mail messages or
> earlier ones on this thread. Perhaps I missed them; in which case, my
> apologies. Can you please send/resend those links?
[...]
I sent you a bunch of bug links in mes
ous software entropy gathering daemons.
We should also document this so that users that distrust certain
entropy sources will know how to disable them.
Ben.
--
Ben Hutchings
Klipstein's 4th Law of Prototyping and Production:
A fail-safe circuit will destro
inks, and many other
kinds of security hardening changes. We made them anyway and took the
temporary pain for a long-term security gain.
Ben.
--
Ben Hutchings
The most exhausting thing in life is being insincere.
- Anne Morrow Lindberg
signature.asc
Description: This is a digitally signed message part
On Mon, 2019-01-21 at 21:46 +, Ben Hutchings wrote:
> On Mon, 2019-01-21 at 20:49 +, Andy Simpkins wrote:
> [...]
> > Should we add to or change the possible entropy sources?
> [...]
>
> Yes, we should (by default) enable use of available hardware RNGs to
> produc
And it has HSTS, which is nice, but it is missing the redirection
that's needed to make that work completely.
Ben.
--
Ben Hutchings
When in doubt, use brute force. - Ken Thompson
signature.asc
Description: This is a digitally signed message part
n 2011 (Ivy Bridge core) and AMD only implemented in 2015
(Excavator core).
Ben.
--
Ben Hutchings
The obvious mathematical breakthrough [to break modern encryption]
would be development of an easy way to factor large prime numbers.
- Bil
file contents is the old seed file
contents. You are adding very little entropy on x86, and possibly
almost none on other architectures.
Please reconsider this, as this description sounds dangerously
insecure.
Ben.
--
Ben Hutchings
The obvious mathema
On Mon, 2019-02-25 at 18:27 +0200, Uoti Urpala wrote:
> Ben Hutchings wrote:
> > The major input into the new seed file contents is the old seed file
> > contents. You are adding very little entropy on x86, and possibly
> > almost none on other architectures.
> >
>
On Mon, 2019-02-25 at 16:48 +, Thorsten Glaser wrote:
> Ben Hutchings dixit:
>
> >> ‣ writes between 32 and 256 bytes to /dev/urandom (but does not
> >> accredit them yet, just remembers the amount written)
> >
> >How do you determi
ndom() without also unblocking /dev/random. If the seed
files used in two different boots are somewhat correlated, and the
entropy estimation doesn't account for that, the output of /dev/random
may also be somewhat correlated between the boots, which is not
supposed to happen.
Ben.
--
Ben Hu
On Mon, 2019-02-25 at 14:36 -0500, Sam Hartman wrote:
> > > > > > "Ben" == Ben Hutchings writes:
>
> Ben> The output of the RNG may well become public, for example in
> Ben> document UUIDs. So when estimating the entropy that the new
>
On Tue, 2019-02-26 at 22:29 +0200, Uoti Urpala wrote:
> On Tue, 2019-02-26 at 19:10 +0000, Ben Hutchings wrote:
> > But if the input to the seed doesn't provide enough entropy, the seed
> > is not completely secret (that is, you can recover it with less work
> > than a
On Thu, 2019-02-28 at 11:56 +, Ian Jackson wrote:
> Ben Hutchings writes ("Re: FYI/RFC: early-rng-init-tools"):
> > On Mon, 2019-02-25 at 19:37 +0200, Uoti Urpala wrote:
> > > Generally you don't ever
> > > need to use /dev/random instead of /dev/urand
"arc4random" functions really use ChaCha20 today, anyway.
Ben.
> I hope you have found this review helpful.
--
Ben Hutchings
This sentence contradicts itself - no actually it doesn't.
signature.asc
Description: This is a digitally signed message part
l problems with doing this: some of these hardware
RNGs are probably quite weak, so we have to be very conservative, but
then the less entropy we credit the more CPU time will be spent in the
hardware RNG reader thread.
Ben.
--
Ben Hutchings
No political challenge can be met by shopping. - George Mo
On Sun, 2019-03-03 at 22:55 +0100, Kurt Roeckx wrote:
> On Sun, Mar 03, 2019 at 08:19:44PM +0000, Ben Hutchings wrote:
> > On Sun, 2019-03-03 at 18:59 +0100, Kurt Roeckx wrote:
> > [...]
> > > Most people will actually have at least 2 hardware RNGs: One in
> > > t
Control: summary -1
GRUB and Linux images are now signed by the production key trusted by
shim-signed. Debian-installer apparently installs the signed packages,
but other installation systems are not yet ready.
Ben.
--
Ben Hutchings
Quantity is no substitute for quality, but it's the onl
-updates suite will not be removed until end of LTS.
As for jessie-backports, the removal was announced in July 2018.
Ben.
> OK, I am a little late to pick up on this, but I'm sure there are
> other people still running some Jessie systems who only run update
> commands on them every mo
the
-updates suite will not be removed until end of LTS.
As for jessie-backports, the removal was announced in July 2018.
Ben.
> OK, I am a little late to pick up on this, but I'm sure there are
> other people still running some Jessie systems who only run update
> commands on the
ging that I raised in
October. (I say "we" because I realise you are likely to need me or
someone else to spend time explaining and testing the specific
scenarios that didn't work.)
Ben.
--
Ben Hutchings
It is easier to write an incorrect program
than to understand a correct one.
r from *any* stretch pointrelease) by adding a "pre-depends:
> debian-security-support (>= 2019.04.25)" to base-files in buster.
[...]
This makes debian-security-support transitively essential, whereas it
used to be optional.
Is "Conflicts" not strong enough?
Ben.
--
random developers can do the
NMU.
Ben.
--
Ben Hutchings
For every complex problem
there is a solution that is simple, neat, and wrong.
signature.asc
Description: This is a digitally signed message part
On Mon, 2019-05-13 at 19:08 +, Holger Levsen wrote:
> reassign -1 base-files
> retitle -1 base-files: please add a break on d-s-s < 2019.04.25
> thanks
>
> On Mon, May 13, 2019 at 01:00:14PM +0100, Ben Hutchings wrote:
> > On Mon, 2019-05-13 at 11:52 +, Holger
d/rules file?
linux is one.
I did a lot of work to address lintian warnings last year, and most of
that did not involve debian/rules*.
Ben.
--
Ben Hutchings
I haven't lost my mind; it's backed up on tape somewhere.
signature.asc
Description: This is a digitally signed message part
On Tue, 2019-05-14 at 12:54 +0200, Andreas Tille wrote:
> On Tue, May 14, 2019 at 10:38:06AM +0100, Ben Hutchings wrote:
> > On Tue, 2019-05-14 at 11:07 +0200, Andreas Tille wrote:
> > > Can you give an example for a package that has a non-dh rules file
> > > "wo
own or non-free dataset [...]
> 3. A model is Non-free Model as long as any of the following
> conditions is satisfied: (1) trained from unknown/non-free data [...]
Is category 2 intended to be a subset of category 3, or am I missing
some distinction?
Ben.
--
Ben Hutchings
Any sufficient
beside debian/control.
I have an unmerged branch that changes various things to be compatible
with dgit. It adds debian/control and debian/tests/control to git and
defers generation of other things to build time.
Ben.
--
Ben Hutchings
Horngren's Observation:
Among economist
tignore but
> not usually Makefile.in).
[...]
Perhaps we should update policy to say that the .orig tarball may (or
even "should") be generated from an upstream release tag where
applicable.
Ben.
--
Ben Hutchings
Horngren's Observation:
Among economists, the real
19.37
>
> https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.19.38
>
> The commit also affects ZFS 0.7 because SIMD is used for checksum operations.
>
> There might be a performance penalty in ZFS only if Debian Buster
> upgrades to 4.19.38.
Which we will, some time soon.
counts, regardless of
whether the vendor is interested in being a sponsor.
Ben.
--
Ben Hutchings
Unix is many things to many people,
but it's never been everything to anybody.
signature.asc
Description: This is a digitally signed message part
gt; Petter for further input.
Linux doesn't distinguish between devices found in an initial
enumeration or hot-plugged later, so I doubt that isenkram is limited
in that way.
Ben.
--
Ben Hutchings
Any sufficiently advanced bug is indistinguishable from a feature.
signature.asc
Descr
that (might) need a security update.
Obviously I build them in a jessie chroot, but it seems like overkill
to do that for the initial source download too. And back when I was
doing triage for Debian LTS I wouldn't build at all - I would only look
at the source to see if a bug was present in the ol
y and other programs/games with
> IAPs?
>
> Cheers, Bagas
>
--
Ben Hutchings
friends: People who know you well, but like you anyway.
signature.asc
Description: This is a digitally signed message part
> privileged. But I would not go that route as I see it as destructive
> one.
[...]
We can't force individual developers to do anything, and yet we manage
to release with a large number of packages that mostly follow policy.
If it's our policy that packages must support cron (
kages.
See
<https://manpages.debian.org/buster/cgit/cgitrc.5.en.html#SIGNATURES>
and the "git-archive-signer" script in
<https://git.kernel.org/pub/scm/linux/kernel/git/mricon/korg-helpers.git/>.
Ben.
--
Ben Hutchings
If God had intended Man to program,
we'd have been born with serial I/O ports.
signature.asc
Description: This is a digitally signed message part
ssages aren't very helpful.
Ben.
--
Ben Hutchings
If God had intended Man to program,
we'd have been born with serial I/O ports.
signature.asc
Description: This is a digitally signed message part
P if you net-boot
without an initramfs.
Ben.
--
Ben Hutchings
You can't have everything. Where would you put it?
signature.asc
Description: This is a digitally signed message part
ny comments, ideas, or help here?
[...]
1a. Require 32-bit build environments to be multiarch with the
related 64-bit architecture also enabled.
Ben.
--
Ben Hutchings
Experience is directly proportional to the value of equipment destroyed
- Carolyn Scheppner
signature.asc
Description: This is a digitally signed message part
On Fri, 2019-08-09 at 00:28 +0200, Aurelien Jarno wrote:
> On 2019-08-08 22:23, Ben Hutchings wrote:
[...]
> > 1a. Require 32-bit build environments to be multiarch with the
> > related 64-bit architecture also enabled.
>
> Indeed, but that looks like the first step. Fr
_0.17.orig.tar.gz, but the file differs:
> in dsc: 82c115920b5570e1e33c613b008736086db210bc8f9b2c2e75f970e9696d8ec5
> found: 64ca6eeb1d646e9992b134b4c89c7b0da5d2f9e141d03ffe29ff76729c4a4975
>
> Please, rebuild your package against the correct file.
>
> Please try to fix it and re-upload. Thanks,
>
> -- mentors.debian.n
nstall haveged, and
> this helps for general cases. But then I have corner cases like when
> the root filesystem is readonly then haveged doesn't work.
>
> I'm not using ancient hardware I'm on a modern arm64 processor, but it
> is an embedded environment with no keyboard or
Package: wnpp
Severity: wishlist
Owner: Ben Hutchings
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-ker...@lists.debian.org,
Steve Dickson , Chuck Lever III
* Package name: ktls-utils
Version : 0.9
Upstream Contact: kernel-tls-handsh...@lists.linux.dev
* URL
ee we should not have UDisks probing for any of the (many) kernel
filesystems that aren't being actively maintained including responding
to security issues.
Beyond that, I would also like to see libmount limiting the filesystems
that it will probe when the fstab type is "auto". But
-compatible).
[...]
ENDBR32 uses one of the previously reserved hint encodings that i686
processors are supposed to ignore if they don't specifically support
them. The release notes for Debian 12 "bookworm" state that the i386
architecture now requires that:
https://www.debian.org
On Tue, 2023-10-17 at 20:03 +0200, Ben Hutchings wrote:
> On Tue, 2023-10-17 at 10:57 -0500, Justin wrote:
> > Hello all,
> >
> > I have recently encountered a case where a VIA C3 Nehemaiah CPU returns
> > "Illegal
> > Instruction" when trying to
On Wed, 2023-10-18 at 14:01 +0200, Ben Hutchings wrote:
> On Tue, 2023-10-17 at 20:03 +0200, Ben Hutchings wrote:
> > On Tue, 2023-10-17 at 10:57 -0500, Justin wrote:
> > > Hello all,
> > >
> > > I have recently encountered a case where a VIA C3 N
this point.
>
> The T60 will do amd64.
[...]
According to thinkwiki, the T60 had CPU options of Core Solo/Duo (32-
bit) and Core 2 Duo (64-bit) CPUs, so this may or may not be correct.
Ben.
--
Ben Hutchings
Horngren's Observation:
Among economists, the real world is often a special case.
signature.asc
Description: This is a digitally signed message part
erry Trail devices in Debian amd64. Bookworm has added it (moved it from
> multi-arch iso to amd64 isos), but trixie seems to be dropping it. If Debian
> thinks 2015 is ancient enough in 2025, this suggestions can be ommited.
[...]
You should ask about that on the debian-cd or debian-boot list.
901 - 1000 of 1223 matches
Mail list logo
