On Tue Mar 18, 2025 at 10:04 AM GMT, Roger Price wrote:
I removed my /etc/updatedb.conf, uninstalled package locate, installed
package plocate, and ran updatedb as root. The command locate is now
defined as /usr/bin/locate -> /etc/alternatives/locate* ->
/usr/bin/plocate*
I didn´t need to mo
"Andrew M.A. Cater" writes:
> On Mon, Mar 17, 2025 at 10:03:48AM +0100, Loris Bennett wrote:
>> Hi,
>>
>> I have a machine which I have updated since Wheezy in 2013 and has thus
>> accumulated a bit of cruft. It is currently running Bookworm but seems
>> to have become stuck at 12.7.
>>
>> I h
Le 3/19/25 à 15:50, Richard Owlett a écrit :
A quick DuckDuckGo search of https://www.emacswiki.org didn't find it.
I changed the search parameters a bit: javascript org-mode folding
First google hit: https://orgmode.org/manual/JavaScript-support.html
First link in that page: https://orgmode.or
On 3/19/25 8:59 AM, Yassine Chaouche wrote:
Le 3/19/25 à 14:52, Richard Owlett a écrit :
[...]
I has a *problem*. The PDF can collapse sub-points. The HTML *cannot*.
I think I saw a javascript code on emacswiki that does that for html
exports from org-mode documents,
but sorry, I didn't take
Le 3/19/25 à 14:52, Richard Owlett a écrit :
[...]
I has a *problem*. The PDF can collapse sub-points. The HTML *cannot*.
I think I saw a javascript code on emacswiki that does that for html exports
from org-mode documents,
but sorry, I didn't take any notes about it...
Best,
--
yassine -- s
On 18/03/2025 14:11, Loris Bennett wrote:
Max Nikulin writes:
apt policy
[...]
My sources.list was correct, but 'apt update/upgrade' failed to install
anything, so I assume Andrew is correct in pointing the finger at some
sort of caching issue which removing /var/lib/apt/lists/* resolved.
On Mon, 17 Mar 2025, Charles Curley wrote:
> charles@hawk:~$ apt show plocate
> Package: plocate
...
> Replaces: mlocate (<< 1.1.7)
...
> Description: much faster locate
I removed my /etc/updatedb.conf, uninstalled package locate, installed package
plocate, and ran updatedb as root. The command
Xiyue Deng writes:
> "Loris Bennett" writes:
>
>> Dan Ritter writes:
>>
>>> Loris Bennett wrote:
Hi,
I have a machine which I have updated since Wheezy in 2013 and has thus
accumulated a bit of cruft. It is currently running Bookworm but seems
to have become stuck at
Max Nikulin writes:
> On 18/03/2025 02:24, Andrew M.A. Cater wrote:
>> As ever with apt problems, it's really useful if you can copy you
>> *actual* /etc/apt/sources.list file to the mailing list.
>
> Output of
>
> apt policy
>
> while being more "noisy", is a more reliable source for
> troub
On 18/03/2025 02:24, Andrew M.A. Cater wrote:
As ever with apt problems, it's really useful if you can copy you
*actual* /etc/apt/sources.list file to the mailing list.
Output of
apt policy
while being more "noisy", is a more reliable source for troubleshooting.
The first step is to chec
"Loris Bennett" writes:
> Dan Ritter writes:
>
>> Loris Bennett wrote:
>>> Hi,
>>>
>>> I have a machine which I have updated since Wheezy in 2013 and has thus
>>> accumulated a bit of cruft. It is currently running Bookworm but seems
>>> to have become stuck at 12.7.
>>>
>>> I have a second
On Mon, Mar 17, 2025 at 10:03:48AM +0100, Loris Bennett wrote:
> Hi,
>
> I have a machine which I have updated since Wheezy in 2013 and has thus
> accumulated a bit of cruft. It is currently running Bookworm but seems
> to have become stuck at 12.7.
>
> I have a second machine on which I install
On Mon, 17 Mar 2025 17:51:33 +0100 (CET)
Roger Price wrote:
> Debian 12 doesn´t include the /etc/updatedb.conf file.
charles@hawk:~$ apt-file search updatedb.conf
plocate: /etc/updatedb.conf
plocate: /usr/share/man/man5/updatedb.conf.5.gz
charles@hawk:~$ cat /etc/debian_version
Dan Ritter writes:
> Loris Bennett wrote:
>> Hi,
>>
>> I have a machine which I have updated since Wheezy in 2013 and has thus
>> accumulated a bit of cruft. It is currently running Bookworm but seems
>> to have become stuck at 12.7.
>>
>> I have a second machine on which I installed a fresh
Loris Bennett wrote:
> Hi,
>
> I have a machine which I have updated since Wheezy in 2013 and has thus
> accumulated a bit of cruft. It is currently running Bookworm but seems
> to have become stuck at 12.7.
>
> I have a second machine on which I installed a fresh Bookworm a few
> weeks ago. T
Sorry to not having replied earlier.
As a result of much tearing of hair and many instances of unmitigated
terror that I had just destroyed my Windows partition, I have
successfully installed Debian on a 2tB SSD.
Windows 11is still there and doing what it does so poorly.
On 3/11/2025 11:11
On 3/11/25 10:19, Stephen P. Molnar wrote:
I have recently put a new computer into service. It is a Dell Vostro
3910 running Windows 11. In addition to the C:\ drive , I have a 2TB SSD
for Linux which the OS found as the D:\ drive.
The installation went as I have come to expect, until it got
Am Mittwoch, 5. März 2025, 18:53:07 CET schrieb Matthias Böttcher:
> Hi Hans,
>
> maybe this caused your problem:
> Nov 06, 2024
> Commit 30d39f81 "lb config: --distribution defaults to testing"
> https://salsa.debian.org/live-team/live-build/-/commit/30d39f812e41eb81928a0
> fe1f3a4f686eb30dfa
Hi Hans,
maybe this caused your problem:
Nov 06, 2024
Commit 30d39f81 "lb config: --distribution defaults to testing"
https://salsa.debian.org/live-team/live-build/-/commit/30d39f812e41eb81928a0fe1f3a4f686eb30dfa9
Bye
Matthias
I believe, the problem is been caused by wrong informations
in /var/lib/dpkg/info from the native installed debian/stable, where I qant to
build it.
ALL *.postinst files are pointing to trixie and not to bookworm (although, the
installed packages are all from bookworm).
So, with the view on t
Hi Hans,
which version of lb are you using?
I am using the version from the Debian package live-build from "bookworm":
$ lb --version
20230502
The first thing I learned with that version from "bookworm" was that I
had to set all config directives regarding the distribution to
"bookworm" bec
On Mon 03 Mar 2025 at 22:24:57 (+0100), Hans wrote:
> So, I rechecked.
>
> After purging everything and building again, I checked the chroot. And what
> did I find?
>
> A lot of entries with "trixie" in */chroot/var/lib/dpkg/info which are mostly
> "*.postinst" files.
>
> Where are they comin
So, I rechecked.
After purging everything and building again, I checked the chroot. And what
did I find?
A lot of entries with "trixie" in */chroot/var/lib/dpkg/info which are mostly
"*.postinst" files.
Where are they coming from? These are all from installed packages, but all
packages shoul
Am Montag, 3. März 2025, 19:05:19 CET schrieben Sie:
Hi Matthias,
> Am Mo., 3. März 2025 um 13:32 Uhr schrieb Hans :
>
> At first my advice: please try debian-l...@lists.debian.org
>
done!
> My way to build debian live is not with git but according to
>
> https://live-team.pages.debian.net/li
On Mon, 3 Mar 2025 09:40:35 -0500
Jeffrey Walton wrote:
> On Mon, Mar 3, 2025 at 7:32 AM Hans wrote:
> >
> > I believe, that one of the following packages needs the missing
> > package. Please see the last output (sorry, it is bit longer):
>
> Something looks a bit off:
>
> $ apt-cache r
Am Mo., 3. März 2025 um 13:32 Uhr schrieb Hans :
At first my advice: please try debian-l...@lists.debian.org
My way to build debian live is not with git but according to
https://live-team.pages.debian.net/live-manual/html/live-manual/index.en.html
Usually I start with "sudo lb clean" and then
On Mon, Mar 3, 2025 at 7:32 AM Hans wrote:
>
> I believe, that one of the following packages needs the missing package.
> Please see the last output (sorry, it is bit longer):
Something looks a bit off:
$ apt-cache rdepends grub-efi-amd64-unsigned
E: No packages found
> __
So, tried agian without the */packages-lists/mylist.list.chroot and without
any added packages at */packages.chroot = same issue again.
This excludes the cause by any changes from me or by any added packages.
It is proven, the issue is in the live-build environment itself.
Hans
Good idea, Matthias, so I rechecked. There are only two packages in
packages.chroot in the last build I sent the output from.
These were "kali-undercover_2023" and "rustdesk-1.3.7". In both I checked the
"control" file, but none of them pointed to or named "grub-efi-amd64-*".
But to clear thi
On 2025-03-03 David Wright wrote:
> On Sun 02 Mar 2025 at 20:32:24 (+0100), Hans wrote:
>
> > The only thing I got, was the message from "lb build", that a ncessary
> > package
> > could not be downloaded. And the necessary package was named
> > "grub-efi-amd64-
> > unsigned".
>
> That suggests t
Hello again,
I believe, that one of the following packages needs the missing package. Please
see the last
output (sorry, it is bit longer):
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
dmsetu
On Sun 02 Mar 2025 at 20:32:24 (+0100), Hans wrote:
> The only thing I got, was the message from "lb build", that a ncessary
> package
> could not be downloaded. And the necessary package was named "grub-efi-amd64-
> unsigned".
That suggests to me (with no experience of this) that its a script
Hi David,
yes, that is, what I meant.
But now, I am a litle bit lsot. How shall I get, which package depends grub-
efi-amd64-unsigned? I thought, you might know.
The only thing I got, was the message from "lb build", that a ncessary package
could not be downloaded. And the necessary package wa
On Sun 02 Mar 2025 at 17:44:37 (+0100), Hans wrote:
> So my idea was just to write to the live-file-maintainers, to ask them, to
> remove the dependency of the missing package in theire configurations or
> point
> it to another package, i.E. grub-efi-amd64-signed.
Presumably you meant "remove
Am Sonntag, 2. März 2025, 13:37:20 CET schrieb Matthias Böttcher:
> PS.
>
> Hans, maybe you put another package from trixie/testing into
> packages.chroot, which depends directly or indirectly on
> grub-efi-amd64-unsigned?
>
Hi Mathias,
I already had this idea, too, but putting it from testing w
Sorry for my bad grammar:
Maybe you *had* put another package from trixie/testing into
packages.chroot?
PS.
>
> Hans, maybe you put another package from trixie/testing into
> packages.chroot, which depends directly or indirectly on
> grub-efi-amd64-unsigned?
>
> Possible packages in testing/trixie
PS.
Hans, maybe you put another package from trixie/testing into
packages.chroot, which depends directly or indirectly on
grub-efi-amd64-unsigned?
Possible packages in testing/trixie main are:
- grub-efi-amd64-bin depends on grub-efi-amd64-unsigned
- grub-efi-amd64 depends on grub-efi-amd64-bin
-
Chris Jölly composed on 2025-02-28 21:28 (UTC+0100):
> So, modesetting is the real thing?
Since about a decade or so ago. It originally was provided as a separate packge,
but was moved into the Xorg server .deb as a default for all GPUs for which an
appropriate kernel module exists, mainly radeon
> Dear maintainers,
>
> it is no more possible to build debian-live/stable (bookworm). The reason is a
> missing package in bookworm: grub-efi-amd64-unsigned.
>
> I rechecked and yes, it is no more in bookworm.
Hi Hans,
I'm sorry, but here are debian users, not maintainers.
And grub-efi-amd64-un
On 2/24/25 22:25, Felix Miata wrote:
Chris Jölly composed on 2025-02-24 21:52 (UTC+0100):
modestting is the X display driver required by either the in use Intel 530 GPU
or
the inactive NVidia GPU.
Ok, so modesetting is the X display driver, not how I expected the intel
or nouveau driver, righ
On Thu Feb 27, 2025 at 2:23 PM GMT, Greg wrote:
On 2025-02-27, Jonathan Dowland wrote:
On Tue Feb 25, 2025 at 1:38 PM GMT, Greg wrote:
Did I read somewhere that the maintainer of the nouveau driver
resigned due to the toxic atmosphere among the kernel developers, or
did I dream that?
The le
On 2025-02-27, Jonathan Dowland wrote:
> On Tue Feb 25, 2025 at 1:38 PM GMT, Greg wrote:
>> Did I read somewhere that the maintainer of the nouveau driver
>> resigned due to the toxic atmosphere among the kernel developers, or
>> did I dream that?
>
> The lead of the Asahi project (providing sup
On Tue Feb 25, 2025 at 1:38 PM GMT, Greg wrote:
Did I read somewhere that the maintainer of the nouveau driver
resigned due to the toxic atmosphere among the kernel developers, or
did I dream that?
The lead of the Asahi project (providing support for Apple-silicon Macs)
recently resigned. Perh
On Wed, 2025-02-26 at 20:41 +1300, Lee Hinkleman wrote:
> Hi debian-user:
> Updates of Trixie stop on a technical issue, as quoted below.
> Thank you.
> Sincerely,
> Lee
>
>
> "
> DDependency resolution failed:
>
> The following packages have unmet dependencies: libkdecorations3-6:
> Breaks: lib
On Wed, Feb 26, 2025 at 04:28:22AM +, Han, Yuguang wrote:
> Hi:
>
> Hope this email find you well.
>
> This is an AWS user. Here my customer wants to use Debian12 latest AMI in AWS
> Malaysia region ap-southeast-5. But didn’t see it in the marketplace support
> list.
>
> https://aws.amazon
On 2025-02-24, Greg Wooledge wrote:
>
>> Shouldnt one of intel or nouveau drivers get loaded?
>
> No, because it's using modeset (for the Intel device at least).
>
Did I read somewhere that the maintainer of the nouveau driver resigned due to
the toxic atmosphere among the kernel developers, or d
Chris Jölly composed on 2025-02-24 21:52 (UTC+0100):
> I have a Lenovo Thinkpad P50, which has the following setup:
> chris@laptop:~$ inxi -Gaz --za
> Graphics:
> Device-1: Intel HD Graphics 530 vendor: Lenovo driver: i915
i915 is the kernel module (hardware driver) required by your Intel 530
On Mon, Feb 24, 2025 at 21:52:43 +0100, Chris Jölly wrote:
> chris@laptop:~$ inxi -Gaz --za
> Graphics:
> Device-1: Intel HD Graphics 530 vendor: Lenovo driver: i915 v: kernel
> arch: Gen-9 process: Intel 14n built: 2015-16 ports: active: eDP-1
> empty: none bus-ID: 00:02.0 chip-ID: 8086:
On 2025-02-21, Jonathan Dowland wrote:
> On Fri Feb 21, 2025 at 2:36 PM GMT, Greg wrote:
>> If you had to pick a man page to be inscrutable, this wouldn't be the
>> one.
>
> I mean, for me, it is: don't tell me worse ones. I don't think I want to
> see them…
>
It is? How odd.
I've never used it
On 22/2/25 06:49, Tom Dial wrote:
On 2/20/25 22:17, jeremy ardley wrote:
On 21/2/25 09:40, Tom Dial wrote:
The TL;DR here is that for maintaining personal workstations and
servers it makes more sense to log in as root, do the work as
required, then log out. Or there is "sudo -i" to get an in
On 2/20/25 22:17, jeremy ardley wrote:
On 21/2/25 09:40, Tom Dial wrote:
The TL;DR here is that for maintaining personal workstations and servers it makes more sense to log in as root, do the work as required, then log out. Or there is "sudo -i" to get an interactive root shell and avoid prepe
On Fri Feb 21, 2025 at 2:36 PM GMT, Greg wrote:
If you had to pick a man page to be inscrutable, this wouldn't be the
one.
I mean, for me, it is: don't tell me worse ones. I don't think I want to
see them…
--
Please do not CC me for listmail.
👱🏻 Jonathan Dowland
✎j...@debian.o
On Fri, Feb 21, 2025 at 9:37 AM Greg wrote:
>
> On 2025-02-21, wrote:
> >
> >> > The straight, but blunt, answer here, I think, is to read the man pages
> >> > for sudo and sudoers
>
> >> In principle I agree with this advice but the sudoers manpage is
> >> notoriously, famously inscrutable.
> >
On 2025-02-21, wrote:
>
>> > The straight, but blunt, answer here, I think, is to read the man pages
>> > for sudo and sudoers
>> In principle I agree with this advice but the sudoers manpage is
>> notoriously, famously inscrutable.
>
> Start with the EXAMPLES section. Work from there. It'll com
On Fri, Feb 21, 2025 at 09:12:49AM +, Jonathan Dowland wrote:
> On Fri Feb 21, 2025 at 1:40 AM GMT, Tom Dial wrote:
> > The straight, but blunt, answer here, I think, is to read the man pages
> > for sudo and sudoers
>
> In principle I agree with this advice but the sudoers manpage is
> notori
On Fri Feb 21, 2025 at 1:40 AM GMT, Tom Dial wrote:
The straight, but blunt, answer here, I think, is to read the man
pages for sudo and sudoers
In principle I agree with this advice but the sudoers manpage is
notoriously, famously inscrutable.
--
Please do not CC me for listmail.
👱🏻
On 21/2/25 09:40, Tom Dial wrote:
The TL;DR here is that for maintaining personal workstations and
servers it makes more sense to log in as root, do the work as
required, then log out. Or there is "sudo -i" to get an interactive
root shell and avoid prepending every command with "sudo."
L
On 21/2/25 09:40, Tom Dial wrote:
The TL;DR here is that for maintaining personal workstations and
servers it makes more sense to log in as root, do the work as
required, then log out. Or there is "sudo -i" to get an interactive
root shell and avoid prepending every command with "sudo."
A
On Thu, Feb 20, 2025 at 5:46 PM Nicolas George wrote:
> Jeffrey Walton (HE12025-02-20):
> >and members of sudo can run any command.
>
> Is it because of this last line:
>
> > rootALL=(ALL:ALL) ALL
> >
> > sudoALL=(ALL:ALL) ALL
>
# User privilege specification
rootALL=
On Thu, Feb 20, 2025 at 6:42 PM Jeffrey Walton wrote:
>
> Hi Everyone,
>
> I have a fresh Debian 12.9 install. My user account is part of sudo
> group, and members of sudo can run any command.
No... the "sudo" user can run any command:
> sudoALL=(ALL:ALL) ALL
I have
%sudo ALL=(ALL:ALL)
The straight, but blunt, answer here, I think, is to read the man pages for
sudo and sudoers (i.e., the /etc/suduoers file that does access control for the
sudo command. The command is very flexible and can be tuned to allow specified
sudoers to use elevated privilege only to execute specific c
Jeffrey Walton writes:
> Hi Everyone,
>
> I have a fresh Debian 12.9 install. My user account is part of sudo
> group, and members of sudo can run any command. However, I get an
> error when trying to use sudo:
>
> $ sudo ls
> [sudo] password for jwalton:
> jwalton is not in the sudoe
On Thu, Feb 20, 2025 at 5:46 PM Nicolas George wrote:
>
> Jeffrey Walton (HE12025-02-20):
> >and members of sudo can run any command.
>
> Is it because of this last line:
>
> > rootALL=(ALL:ALL) ALL
> >
> > sudoALL=(ALL:ALL) ALL
>
> ? But does it mean the previous one gives
Jeffrey Walton (HE12025-02-20):
>and members of sudo can run any command.
Is it because of this last line:
> rootALL=(ALL:ALL) ALL
>
> sudoALL=(ALL:ALL) ALL
? But does it mean the previous one gives sudo privileges to all members
of the root group? Or is it that the last
On 21.02.2025 03:29, Jeffrey Walton wrote:
...
sudoALL=(ALL:ALL) ALL
I've rebooted the machine twice. I know the failure is not due to
stale login information.
Does anyone know why I cannot use sudo in this case?
Jeff
Your line misses % for some reason.
sudo in your case is the nam
On Tuesday, 11-02-2025 at 13:20 Peter Barnes wrote:
> Hi everyone,
>
> Newbie here. I have a DVD Debian 11.6 Bullseye 64bit and installed it
I usually take "newbie" to mean "I am new to Debian", so I would ask did you
know the current production of Debian was Bookworm.? I was curious why yo
On Tue, Feb 11, 2025 at 12:42 AM Peter Barnes wrote:
>
> Newbie here. I have a DVD Debian 11.6 Bullseye 64bit and installed it
> successfully on my PC. I have downloaded later versions of Debian and when I
> go to install nothing happens. Am I missing a step? Is it possible for you to
> give me
On Tue, 11 Feb 2025 13:20:13 +1100
Peter Barnes wrote:
> Newbie here. I have a DVD Debian 11.6 Bullseye 64bit and installed it
> successfully on my PC. I have downloaded later versions of Debian and
> when I go to install nothing happens.
Do you want to do a brand new installation, wiping your
Peter Barnes wrote:
> Hi everyone,
>
> Newbie here. I have a DVD Debian 11.6 Bullseye 64bit and installed it
> successfully on my PC. I have downloaded later versions of Debian and when I
> go to install nothing happens. Am I missing a step? Is it possible for you
> to give me step by step instru
On Fri 31 Jan 2025 at 23:30:52 (+), Andrew M.A. Cater wrote:
> On Fri, Jan 31, 2025 at 02:55:56PM +0900, Mailing List wrote:
> > I believe I've found a bug in the DVD ISO installer logic which affects
> > 11.11 and earlier but in theory could affect 12.x as well.
> >
> > Description:
> >
> >
On Fri, Jan 31, 2025 at 02:55:56PM +0900, Mailing List wrote:
> I believe I've found a bug in the DVD ISO installer logic which affects
> 11.11 and earlier but in theory could affect 12.x as well.
>
> Description:
>
> A default installation of Debian 11.11 (Bullseye) from the official DVD ISO
> f
On Fri 31 Jan 2025 at 14:55:56 (+0900), Mailing List wrote:
> I believe I've found a bug in the DVD ISO installer logic which affects
> 11.11 and earlier but in theory could affect 12.x as well.
>
> Description:
>
> A default installation of Debian 11.11 (Bullseye) from the official DVD ISO
> fai
On 1/21/25 23:23, Johannes Krottmayer wrote:
Hi!
I have planned to upgrade my (very old) system. The new system will be
a mainboard with X870-E chipset and a AMD Ryzen 9 9950X3D (the CPU isn't
currently available), so have written AMD Ryzen 9 9950X in the mail
subject.
Has somebody such a combi
Jonathan Dowland wrote:
> On Wed Jan 29, 2025 at 10:52 AM GMT, songbird wrote:
>> Setting up openjdk-17-jre-headless:amd64 (17.0.14+7-1) ...
>> update-binfmts: warning: current package is openjdk-21, but binary format
>> already installed by openjdk-9
>
> What do you have in /usr/share/binfmts ?
On Wed Jan 29, 2025 at 10:52 AM GMT, songbird wrote:
Setting up openjdk-17-jre-headless:amd64 (17.0.14+7-1) ...
update-binfmts: warning: current package is openjdk-21, but binary format
already installed by openjdk-9
What do you have in /usr/share/binfmts ?
--
Please do not CC me for listmail
Cindy Sue Causey wrote:
...
> In my case these days, I have two things I would do to take a poke at
> this in hopes something obvious presents itself:
>
> $ apt-cache policy openjdk-9
>
> I might even try the much busier "apt-cache policy openjdk-*" to see if
> anything else is lingering. My setup
On 29/01/2025 17:52, songbird wrote:
update-binfmts: warning: current package is openjdk-21, but binary format
already installed by openjdk-9
Likely it is related to running of .jar files without explicit java
command. In a similar way wine may install a handler for .exe files in
addition to
ra...@siliconet.pl wrote:
>
>On 29.01.2025 4:16 PM, Roberto C. Sánchez wrote:
>> Yes, it still means that. The minizip binary package you are seeing
>> comes from a different source package, also called minizip:
>>
>> https://packages.debian.org/source/bookworm/minizip
>
>Aha! Got it :-)
>
>And th
On Wed, 2025-01-29 at 12:10 +, Brad Rogers wrote:
> On Wed, 29 Jan 2025 05:52:34 -0500
> songbird wrote:
>
> Hello songbird,
>
> > warning: current package is openjdk-21, but binary format already
> > installed by openjdk-9
>
> I've seen similar messages. Certainly about openjdk, maybe oth
On 29.01.2025 4:16 PM, Roberto C. Sánchez wrote:
Yes, it still means that. The minizip binary package you are seeing
comes from a different source package, also called minizip:
https://packages.debian.org/source/bookworm/minizip
Aha! Got it :-)
And there are no binary components in Debian b
On Wed, Jan 29, 2025 at 04:15:16PM +0100, Rafał Lichwała wrote:
>
>But still don;t understand "Debian itself does *not* build the affected
>component" as I can find "minizip" (and maybe other) package based on that
>vulnerable library - see my previous post above as Re- to Hanno.
>
Yo
On Wed, Jan 29, 2025 at 04:04:26PM +0100, Rafał Lichwała wrote:
>
> On 29.01.2025 3:35 PM, Hanno 'Rince' Wagner wrote:
> > > The notes say:
> > > [bookworm] - zlib (contrib/minizip not built and src:zlib not
> > > producing binary packages)
> > > In other words, there's no point in fixing it bec
On 29.01.2025 3:30 PM, Roberto C. Sánchez wrote:
On Wed, Jan 29, 2025 at 03:22:02PM +0100, Rafał Lichwała wrote:
On 29.01.2025 2:43 PM, Dan Ritter wrote:
CVSS are often bogus.
Hmmm... I'm not sure what you mean. All security announcements in DSAs are
referring to CVSS, so... what's
On 29.01.2025 3:35 PM, Hanno 'Rince' Wagner wrote:
The notes say:
[bookworm] - zlib (contrib/minizip not built and src:zlib not
producing binary packages)
In other words, there's no point in fixing it because Debian doesn't build the
vulnerable binary component.
Very low priority.
so, this
On Wed, Jan 29, 2025 at 03:22:02PM +0100, Rafał Lichwała wrote:
>On 29.01.2025 2:43 PM, Dan Ritter wrote:
>
> CVSS are often bogus.
>
> Hmmm... I'm not sure what you mean. All security announcements in DSAs are
> referring to CVSS, so... what's the source of such opinion?
>
>
> Most rec
On Wed, Jan 29, 2025 at 08:43:12AM -0500, Dan Ritter wrote:
>
> Most recently: https://daniel.haxx.se/blog/2025/01/23/cvss-is-dead-to-us/
I was going to post a link to this very article when I saw that you
already had :-)
Regards,
-Roberto
--
Roberto C. Sánchez
On 29.01.2025 2:43 PM, Dan Ritter wrote:
CVSS are often bogus.
Hmmm... I'm not sure what you mean. All security announcements in DSAs are
referring to CVSS, so... what's the source of such opinion?
Most recently:https://daniel.haxx.se/blog/2025/01/23/cvss-is-dead-to-us/
Yeah, another blog and
On 29.01.2025 2:39 PM, Hanno 'Rince' Wagner wrote:
How does your "automatically scanned for possible vulnerabilites"
actually work?
I don't know, but it does not matter in that context.
It does matter because you have to interpret the output of your
scanner and understand it.
Well, not really
Rafał Lichwała wrote:
>
> On 29.01.2025 2:12 PM, Dan Ritter wrote:
> > The notes say:
> >
> > [bookworm] - zlib (contrib/minizip not built and src:zlib not
> > producing binary packages)
> >
> > In other words, there's no point in fixing it because Debian
> > doesn't build the vulnerable bina
On Wed, 29 Jan 2025 05:52:34 -0500
songbird wrote:
Hello songbird,
>warning: current package is openjdk-21, but binary format already
>installed by openjdk-9
I've seen similar messages. Certainly about openjdk, maybe others, I
can't recall. As everything seems to be working as expected, I don
On 29.01.2025 1:57 PM, David wrote:
How does your "automatically scanned for possible vulnerabilites"
actually work?
I don't know, but it does not matter in that context. The fact is, that
the result of this "magic scan" properly found and points out the real
critical security vulnerabilitie
On 29.01.2025 2:12 PM, Dan Ritter wrote:
The notes say:
[bookworm] - zlib (contrib/minizip not built and src:zlib not
producing binary packages)
In other words, there's no point in fixing it because Debian
doesn't build the vulnerable binary component.
Very low priority.
Could you please
Rafał Lichwała wrote:
> Hi,
>
> I've prepared some docker image based on Debian 12 (bookworm, fully updated)
> and after upload it to local registry it has been automatically scanned for
> possible vulnerabilities.
> Then I was really surprised when discovered that according to this scan
> there
On Wed, 29 Jan 2025 at 12:40, Rafał Lichwała wrote:
> I've prepared some docker image based on Debian 12 (bookworm, fully
> updated) and after upload it to local registry it has been automatically
> scanned for possible vulnerabilities.
> Then I was really surprised when discovered that according
On Fri, 24 Jan 2025, e...@gmx.us wrote:
> >> OK. My crontab has this:
> >>
> >> XDG_RUNTIME_DIR="/run/user/$(id -u)"
> >> At the minute, no sound. I tried
> >> id=$(id -u)
> >> XDG_RUNTIME_DIR=/run/user/$id
> >> and
> >> id=1000
> >> XDG_RUNTIME_DIR=/run/user/$id
> >>
> >> and no dice. I tried
On Sunday, 26-01-2025 at 21:29 Frank Guthausen wrote:
> On Sun, 26 Jan 2025 19:50:23 +1100
> George at Clug wrote:
> > On Sunday, 26-01-2025 at 18:29 Max Nikulin wrote:
> > >
> > > That is why I would check what is recommended for
> > > RHEL, Fedora, Ubuntu. RedHat and Canonical certainly hav
On Sun, 26 Jan 2025 19:50:23 +1100
George at Clug wrote:
> On Sunday, 26-01-2025 at 18:29 Max Nikulin wrote:
> >
> > That is why I would check what is recommended for
> > RHEL, Fedora, Ubuntu. RedHat and Canonical certainly have customers
> > who need access to VM desktops.
>
> I would expec
On Sunday, 26-01-2025 at 18:29 Max Nikulin wrote:
> On 26/01/2025 12:31, George at Clug wrote:
> >
> > Today I changed my KDE host and guest VM to both use X11 and not Wayland.
> [...]
> > Cut/Paste clip board between host and guest did not work, in either
> > direction. Very disappointing.
>
On 26/01/2025 12:31, George at Clug wrote:
Today I changed my KDE host and guest VM to both use X11 and not Wayland.
[...]
Cut/Paste clip board between host and guest did not work, in either
direction. Very disappointing.
We are going to hijack Rafał's Wayland topic for the *X11* case. Debian
Max,
Today I changed my KDE host and guest VM to both use X11 and not Wayland.
(spice-vdagent is installed in VM)
Cut/Paste clip board between host and guest did not work, in either direction.
Very disappointing.
XFCE supports Cut/Paste clip board between host and guest.
I should give Cinnam
1 - 100 of 9423 matches
Mail list logo
