Hi Andreas,
On Sun, Aug 06, 2023 at 06:44:47PM +0200, Andreas Metzler wrote:
> Somehow related: If I introduce a new systemd unit should I work
> around dh_installsystemd and ship it in /usr/lib/systemd/system/?
Doing this is extra work now. If done correctly, it is compatible with
the file move
On 2023-08-01 Helmut Grohne wrote:
[...]
> In moving crontab_setgid from lib to libexec, you effectively evade the
> moratorium and are entitled to also move from / to /usr. This is an
> action you can do right now. The move from /lib to /usr/libexec prevents
> the file loss scenario that spurred
Hi Alexandre,
On Mon, Jul 31, 2023 at 01:37:12PM +0200, Alexandre Detiste wrote:
> [systemd-cron]: after a carefull review, I took a third option:
> these scriptlets belong neither in /lib nor /usr/lib but in /usr/libexec .
>
> This is now implemented this way in the upstream repository.
>
> The
Le ven. 21 juil. 2023 à 16:48, Helmut Grohne a écrit :
> TL;DR: dpkg-statoverride detection cannot be automated, but there are
> only 5 affected packages.
>
> On Wed, Jul 12, 2023 at 03:34:38PM +0200, Helmut Grohne wrote:
> > * DEP17-P5: dpkg-statoverrides not matching the files shipped.
> >P
Hi,
TL;DR: dpkg-statoverride detection cannot be automated, but there are
only 5 affected packages.
On Wed, Jul 12, 2023 at 03:34:38PM +0200, Helmut Grohne wrote:
> * DEP17-P5: dpkg-statoverrides not matching the files shipped.
>Possibly, I can extend dumat to cover unconditional statoverrid
Hi Andreas and Ralf,
On Mon, Jul 17, 2023 at 04:08:48PM +0200, Ralf Treinen wrote:
> > Moving the usertag to the qa namespace sounds like a good idea.
>
> I agree
Thank you
> Sounds like a good idea. However, I do not think that usertags support
> a hierarchy of tags. So maybe different specif
On Mon, 2023-07-17 at 07:16 +0200, Helmut Grohne wrote:
> Then I found trei...@debian.org using edos-file-overwrite. That latter
> one seems like what I need here. Should we move it to the qa space and
> drop the edos part? I suggest debian...@lists.debian.org usertags
> file-overwrite. Otherwise
Hello,
On Mon, Jul 17, 2023 at 10:35:24AM +0200, Andreas Beckmann wrote:
> On 17/07/2023 07.16, Helmut Grohne wrote:
> > Then I found trei...@debian.org using edos-file-overwrite. That latter
> > one seems like what I need here. Should we move it to the qa space and
> > drop the edos part? I sugge
On 17/07/2023 07.16, Helmut Grohne wrote:
Then I found trei...@debian.org using edos-file-overwrite. That latter
one seems like what I need here. Should we move it to the qa space and
drop the edos part? I suggest debian...@lists.debian.org usertags
file-overwrite. Otherwise, Ralf are you ok wit
Hi,
On Wed, Jul 12, 2023 at 03:34:38PM +0200, Helmut Grohne wrote:
> ## Usertagging bugs
>
> In order to avoid filing duplicates, I need a usertagging scheme for
> bugs. Are there opinions on what user I should use for this? In the
> simplest instance, I can use my DD login. Roughly speaking ever
Hi Helmut,
thanks for your continuious work on this!
On Wed, Jul 12, 2023 at 03:34:38PM +0200, Helmut Grohne wrote:
> To make matters worse, an upload to bookworm-backports
> is immediately available to users and there is no migration that some
> check (such as dumat) could hook into.
there is
On Wed, 12 Jul 2023 at 22:23:08 -0400, Theodore Ts'o wrote:
> On Wed, Jul 12, 2023 at 03:34:38PM +0200, Helmut Grohne wrote:
> > There is one major issue where I don't have a good answer:
> > bookworm-backports. When this originally surfaced, Luca Boccassi
> > suggested that we do not canonicalize
Hi Ted,
On Wed, Jul 12, 2023 at 10:23:08PM -0400, Theodore Ts'o wrote:
> For those packages that are likely to be backported, would ti be
> possible provide some tools so that the package maintainers can make
> it easy to have the debian/rules file detect whetther it is being
> built on a distro v
Hi Luca,
On Thu, Jul 13, 2023 at 01:38:16AM +0100, Luca Boccassi wrote:
> On Wed, 12 Jul 2023 at 14:35, Helmut Grohne wrote:
> > "risky" ones from becoming practically relevant). There is one kind of
> > issue that may be actionable right now and that's the class of "empty
> > directory" issues.
On Wed, Jul 12, 2023 at 03:34:38PM +0200, Helmut Grohne wrote:
> ## No good solution for bookworm-backports
>
> There is one major issue where I don't have a good answer:
> bookworm-backports. When this originally surfaced, Luca Boccassi
> suggested that we do not canonicalize in backports. That's
On Wed, 12 Jul 2023 at 14:35, Helmut Grohne wrote:
>
> Hi,
>
> I'm doing yet another /usr-merge thread even though we already have too
> many, I know.
>
> The first one was about general discussion and problem analysis. In that
> first thread, I posted a number of scripts for analyzing problems an
Hi,
Quoting Helmut Grohne (2023-07-12 15:34:38)
> This thread hopefully becomes more of a FYI than a discussion. I've turned
> those hacky scripts into some Python code that continuously (4 times a day)
> analyzes the archive for some of the problems summarized in DEP17. Interested
> parties may f
17 matches
Mail list logo
