Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1186702

Bug#1060700: Requesting advice regarding the impact of problems caused by aliasing on declared Conflicts

From Matthew Vernon <matthewv@chiark.greenend.org.uk>
Newsgroups linux.debian.bugs.dist
Subject Bug#1060700: Requesting advice regarding the impact of problems caused by aliasing on declared Conflicts
Date 2024-02-19 11:00 +0100
Message-ID <I98Bk-baK3-7@gated-at.bofh.it> (permalink)
References <HVGCR-2KMn-1@gated-at.bofh.it> <HVGCR-2KMn-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Hi,

On 12/01/2024 12:31, Helmut Grohne wrote:

> For the gzip case, we have the additional question whether we tolerate
> the temporary policy violation for the trixie upgrade or halt the
> /usr-move and retry with a modified dpkg (that could land in trixie, so
> we could complete in forky).

What's the scope of dpkg modification needed here? And is likely the 
sort of thing the dpkg maintainers would accept. Were we not already in 
a bit of a mire here, it's not clear to me that policy is wrong here 
(and thus that we should set it aside).

> I also note that there may be unknowns beneath. In May last year, things
> looked good, then we found empty directory loss and m-a:same shared file
> loss. Then things looked good again until October when we found this.
> Chances are, there are more unknowns.

This continues to make me worry we are not on the path of robust 
engineering. But I appreciate I'm in a very small minority in that regard.

Regards,

Matthew

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Bug#1060700: Requesting advice regarding the impact of problems caused by aliasing on declared Conflicts Helmut Grohne <helmut@subdivi.de> - 2024-01-13 08:30 +0100
  Bug#1058937: Bug#1060700: Requesting advice regarding the impact of problems caused by aliasing on declared Conflicts Helmut Grohne <helmut@subdivi.de> - 2024-01-17 15:20 +0100
    Bug#1060700: Requesting advice regarding the impact of problems caused by aliasing on declared Conflicts Matthew Vernon <matthewv@chiark.greenend.org.uk> - 2024-02-19 11:00 +0100
      Bug#1060700: Requesting advice regarding the impact of problems caused by aliasing on declared Conflicts Helmut Grohne <helmut@subdivi.de> - 2024-02-19 12:20 +0100
  Bug#1060700: Requesting advice regarding the impact of problems caused by aliasing on declared Conflicts Sam Hartman <hartmans@debian.org> - 2024-01-17 17:40 +0100
    Bug#1060700: Requesting advice regarding the impact of problems caused by aliasing on declared Conflicts Helmut Grohne <helmut@subdivi.de> - 2024-01-17 18:40 +0100
  Bug#1060700: Requesting advice regarding the impact of problems caused by aliasing on declared Conflicts Matthew Vernon <matthewv@chiark.greenend.org.uk> - 2024-02-19 11:00 +0100
    Bug#1060700: Requesting advice regarding the impact of problems caused by aliasing on declared Conflicts Helmut Grohne <helmut@subdivi.de> - 2024-02-19 12:20 +0100
    Bug#1060700: Requesting advice regarding the impact of problems caused by aliasing on declared Conflicts Sam Hartman <hartmans@debian.org> - 2024-02-20 16:30 +0100
      Bug#1060700: Requesting advice regarding the impact of problems caused by aliasing on declared Conflicts Russ Allbery <rra@debian.org> - 2024-02-20 17:20 +0100

csiph-web