[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#948375: marked as done (buster-pu: package ceph/12.2.12+dfsg-1)

Your message dated Fri, 05 Aug 2022 20:04:27 +0100
with message-id <adb121f403b37d81a950c427e83bfae7e511d542.camel@adam-barratt.org.uk>
and subject line Re: Bug#948375: buster-pu: package ceph/12.2.12+dfsg-1
has caused the Debian Bug report #948375,
regarding buster-pu: package ceph/12.2.12+dfsg-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
948375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948375
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian.org@packages.debian.org
Usertags: pu


Hi release-team!

I have a bit complicated idea for a buster-pu: ceph.
Buster shipped with 12.2.11 and last April upstream released 12.2.12 as
bugfix release. As usual with ceph, the diff is *huge*, but it is a
bugfix-only release. So here are a few facts:

- upstream changes: https://ceph.io/releases/v12-2-12-luminous-released/
  
- proposed diff:
  https://salsa.debian.org/ceph-team/ceph/compare/luminous%2Funstable...debian%2Fbuster

- I've basically imported the changes the Ubuntu people have done in
  Ubuntu together with 12.2.12. So I assume this should work well, I did
  not yet test it properly as I want to wait for a reply from you. I'll
  prepare a backport of 14.2.x as soon as it migrates to testing anyway.

- The issue with ceph is that upstream doesn't do QA for 32bit and our
  selection of unusual architectures. I don't know if it builds on all
  buildds without trying...

- 12.2.X is already EOL at ceph upstream.... I just took over the
  maintenance of ceph, so... everything is late. Things should be better
  for bullseye.

- The packaging is not yet as close to the upstream packaging as I'd
  like to have it. Upstream's packaging is very well tested and
  supported, we should stick to that as far as possible.
 
For bullseye we'll have the same question: Big updates from upstream as
their pointrelease. Target will probably be 15.2.X (Octopus), which is
not yet released, but I hope it will be before bullseye will go into
freeze.


So... whats your opinion on that?


Thanks,

Bernd

-- 
 Bernd Zeimetz                            Debian GNU/Linux Developer
 http://bzed.de                                http://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F

--- End Message ---
--- Begin Message --- 
On Sun, 2020-04-26 at 20:31 +0200, Bernd Zeimetz wrote:
> Hi Julien,
> 
> > That's kind of unreadable.  We like to have the proposed diff
> > directly
> > in the p-u bug, along with a description of the changes, what they
> > fix,
> > what the risks are.
> 
> 
[...]
> > > 
> > A reply from us tends to not be forthcoming before the proposed
> > changes
> > have been tested, so there's a bit of a chicken and egg issue.
> 
> But I'm not wasting an enourmous amount of time if there is a chance
> that you say no anyway.
> 

Apologies for letting this sit for so long without further response. :-
(

As we're now in the process of preparing the final point release for
buster as support for it transitions over to the LTS team, I'm afraid
that it's now too late to do this via pu.

Regards,

Adam

--- End Message ---
Reply to: