On Fri, 23 Jun 2023, Matthew Vernon wrote:
>> Nothing for orphan-sysvinit-scripts, which *really* surprises me,
>> as I’m certain we discussed this earlier.
>
> You may be remembering bullseye? After quite a lot of wrangling, we got a
> short
> note added to the release notes[0] and installation
Hi,
On 23/06/2023 02:11, Thorsten Glaser wrote:
Nothing for orphan-sysvinit-scripts, which *really* surprises me,
as I’m certain we discussed this earlier.
You may be remembering bullseye? After quite a lot of wrangling, we got
a short note added to the release notes[0] and installation
Hi,
sysvinit-core in bookworm Recommends: orphan-sysvinit-scripts ; have you
told apt to ignore recommends?
I think I agree with others who have said that it wouldn't be
appropriate for all sysvinit systems to install orphan-sysvinit-scripts
(which would warrant a Depends: ); obviously that
Hi,
On 23/06/2023 01:24, Mason Loring Bliss wrote:
On Fri, Jun 23, 2023 at 02:14:40AM +0200, Thorsten Glaser wrote:
The choice to use a nōn-default setup (using rsyslogd at all
in bookworm) is up to the local admin.
It's not obvious from the release notes that rsyslog is deprecated. Maybe
On Thu, 22 Jun 2023, Mason Loring Bliss wrote:
>What part of the release notes are you referring to? It might be useful to
>reference that specifically, in addition to the pointer.
>
>Nothing relevant is obvious here for rsyslogd:
[-]
>It's not obvious from the release notes that rsyslog is
On Thu, 22 Jun 2023, Mason Loring Bliss wrote:
On Fri, Jun 23, 2023 at 01:30:30AM +0200, Thorsten Glaser wrote:
On Thu, 22 Jun 2023, David Griffith wrote:
This was prompted when I found that rsyslog stopped working on Bullseye when
upgraded to Bookworm. What sort of depenency would you
On Fri, Jun 23, 2023 at 02:14:40AM +0200, Thorsten Glaser wrote:
> The choice to use a nōn-default setup (using rsyslogd at all
> in bookworm) is up to the local admin.
It's not obvious from the release notes that rsyslog is deprecated. Maybe
it's too late now for Bookworm, but this speaks to
On Fri, Jun 23, 2023 at 01:30:30AM +0200, Thorsten Glaser wrote:
> On Thu, 22 Jun 2023, David Griffith wrote:
>
> > This was prompted when I found that rsyslog stopped working on Bullseye when
> > upgraded to Bookworm. What sort of depenency would you suggest to implement
> > the following?
>
On Fri, 23 Jun 2023, David Griffith wrote:
> More verbosely: "Which package should have a dependency upon
> orphan-sysvinit-scripts to ensure that if sysvinit is used that rsyslog
> doesn't
> break?"
None because that’s not the scope of dependencies in Debian.
The choice to use a nōn-default
On Fri, 23 Jun 2023, Thorsten Glaser wrote:
On Thu, 22 Jun 2023, David Griffith wrote:
This was prompted when I found that rsyslog stopped working on Bullseye when
upgraded to Bookworm. What sort of depenency would you suggest to implement
the following?
“Read the release notes.”
Or use
On Thu, 22 Jun 2023, David Griffith wrote:
> This was prompted when I found that rsyslog stopped working on Bullseye when
> upgraded to Bookworm. What sort of depenency would you suggest to implement
> the following?
“Read the release notes.”
Or use inetutils-syslogd ;-)
bye,
//mirabilos
--
On Fri, 23 Jun 2023, Thorsten Glaser wrote:
On Thu, 22 Jun 2023, David Griffith wrote:
of no use unless sysvinit is being used and its absence leads to random
packages (some important) not working at all; orphan-sysvinit-scripts
should be a prerequisite.
Huh? No. Currently,
On Thu, 22 Jun 2023, David Griffith wrote:
>of no use unless sysvinit is being used and its absence leads to random
>packages (some important) not working at all; orphan-sysvinit-scripts
>should be a prerequisite.
Huh? No. Currently, orphan-sysvinit-scripts doesn’t contain init scripts
for
Package: initscripts
Version: 3.06-4
Severity: important
When doing an upgrade of a Bullseye machine to Bookworm, I noticed that
rsyslog stopped writing log entries. There was no immediate clue as to
what was going on. After poking around online, I found Bug#1037039
which said that
14 matches
Mail list logo
