On Sat, 10 May 2025 14:07:27 +0200 Daniel =?utf-8?Q?Gr=C3=B6ber?= <
d...@darkboxed.org> wrote:
> Usually I have better things to do than debugging what package messed up
> resolv.conf *today* hence my use-case, but it's just a symptom of a more
> general problem in our DNS ecosystem IMO.
Well, if
Hi all,
The raised severity wasn't intended to remove the package just to raise
this bug's visibility.
Clearly I got sidetracked during the BSP. This seems to happen to me a lot
at events unfortunately since talking to people about how to solve the many
large problems in Debian is very effective
On Fri, 25 Apr 2025 22:28:37 +0100 Roy Marples wrote:
> On Fri, 25 Apr 2025 22:24:18 +0200 Martin Hostettler
> wrote:
> > On Fri, 11 Apr 2025 10:18:16 +0200 Daniel =?utf-8?Q?Gr=C3=B6ber?=
> > wrote:
> > > Control: severity -1 serious
> > > Justification: Breaks unrelated software
> > > Control
On Fri, 25 Apr 2025 22:24:18 +0200 Martin Hostettler
wrote:
> On Fri, 11 Apr 2025 10:18:16 +0200 Daniel =?utf-8?Q?Gr=C3=B6ber?=
> wrote:
> > Control: severity -1 serious
> > Justification: Breaks unrelated software
> > Control: owner -1 d...@darkboxed.org
> > Control: user debian-rele...@lists.
On Fri, 11 Apr 2025 10:18:16 +0200 Daniel =?utf-8?Q?Gr=C3=B6ber?=
wrote:
> Control: severity -1 serious
> Justification: Breaks unrelated software
> Control: owner -1 d...@darkboxed.org
> Control: user debian-rele...@lists.debian.org
> Control: usertag -1 + bsp-2025-04-at-vienna
>
> I'm raising
Control: severity -1 serious
Justification: Breaks unrelated software
Control: owner -1 d...@darkboxed.org
Control: user debian-rele...@lists.debian.org
Control: usertag -1 + bsp-2025-04-at-vienna
I'm raising the severity of this bug after reading up on rc_policy.
On Mon, Dec 04, 2023 at 12:30:03
Daniel,
Em 09/09/2024 10:28, Daniel Gröber escreveu:
My understanding is that in the "Debian" salsa group we're all maintainers,
that's the whole point of it :-)
Consequently I was going to do this as a "Debian" Team
upload. cf.
https://wiki.debian.org/Salsa/Doc#Collaborative_Maintenance:_.22
Hi Fabio,
On Mon, Sep 09, 2024 at 10:16:22AM -0300, Fabio A. De Muzio Tobich wrote:
> > Do you have a reason?
>
> Making the fork was just a suggestion, you can do the direct push if you
> wish, without any problems.
>
> As for uploading, you are not the maintainer of the package, so if you
> wa
Em 09/09/2024 10:00, Daniel Gröber escreveu:
I don't see a reason not to just upload to unstable and push to
debian/openresolv.
Do you have a reason?
Making the fork was just a suggestion, you can do the direct push if you wish,
without any problems.
As for uploading, you are not the mai
Hi Fabio,
On Mon, Sep 09, 2024 at 09:47:52AM -0300, Fabio A. De Muzio Tobich wrote:
> Sorry for the long delay in responding.
No worries :)
> Yes, openresolv is in salsa and open to collaborative maintenance. If you
> decide to contribute, I suggest you fork it in your own userspace, make
> your
Hi Daniel,
Sorry for the long delay in responding.
Yes, openresolv is in salsa and open to collaborative maintenance. If you
decide to contribute, I suggest you fork it in your own userspace, make your
changes, and then submit a merge request.
Your contributions will be most welcome.
Cheers.
Hi Fabio,
a ping on this.
Heads up: I notice openresolv is in the [salsa debian group], so I may
decide to upload fixes for this bug and #1057387.
[salsa debian group]:
https://wiki.debian.org/Salsa/Doc#Collaborative_Maintenance:_.22Debian.22_group
--Daniel
On Mon, Dec 04, 2023 at 12:30:03PM
On Mon, Dec 04, 2023 at 11:41:57AM +0100, Daniel Gröber wrote:
> This is similar to how networkmanager and systemd-resolvd handle
> ownership conflicts and following this protocol will ensure only one
> (or none in my case :) managment system will try to change
> resolv.conf.
Additional datapoint
Package: openresolv
Version: 3.12.0-3
Severity: important
X-Debbugs-Cc: d...@darkboxed.org
Hi Fabio,
I manage my resolv.conf by hand and as such I don't want to excercise
any daemons messing with it :)
I've noticed that openresolv seems to (non-atomically) overwrite
/etc/resolv.conf as the file
14 matches
Mail list logo
