Hey users,
To follow up on my previous email, on behalf of the Ceph team, we apologize
for any confusion about pre-released packages. We are working on
streamlining the release process to avoid this next time.
- Laura
On Wed, Aug 30, 2023 at 2:14 PM Paul Mezzanini <pfmeec@xxxxxxx> wrote:
> -> "At the minimum, publishing the versioned repos at
> $repourl/debian-16.2.14 but not cutting the symlink over for
> $repourl/debian-pacific until “ready” seems like a very easy and useful
> release process improvement to prevent these specific issues going forward."
>
> This should be standard procedure for new releases. Numerous linux
> distributions already operate this way to make sure mirrors get copes
> before the thundering herds do upgrades.
>
>
> --
>
> Paul Mezzanini
> Platform Engineer III
> Research Computing
>
> Rochester Institute of Technology
>
> “End users is a description, not a goal.”
>
>
>
>
>
> ________________________________________
> From: Reed Dier <reed.dier@xxxxxxxxxxx>
> Sent: Wednesday, August 30, 2023 1:16 PM
> To: Yuri Weinstein
> Cc: ceph-users
> Subject: Re: Pacific 16.2.14 debian Incomplete
>
> This is more the sentiment that I was hoping to convey.
>
> Sure, I have my finger on the pulse of the mailing list and the packages
> coming down the pipe, but assuming that everyone does and/or will is not a
> safe assumption.
> At the minimum, publishing the versioned repos at $repourl/debian-16.2.14
> but not cutting the symlink over for $repourl/debian-pacific until “ready”
> seems like a very easy and useful release process improvement to prevent
> these specific issues going forward.
>
> Likewise, $repourl/rpm-pacific is already pointing to $repourl/rpm-16.2.14
> as well, so its not a debian specific issue, albeit it looks like there
> were no issues with missing packages on el8.
> But the packages were still “pre-released” before we are supposed to use
> them.
>
> Anything making it to $repourl/{deb,rpm}-$named_release should be “safe.”
> Because the documentation<
> https://docs.ceph.com/en/pacific/install/get-packages/#configure-repositories-manually>
> uses the named repos, as it should, and right now the documentation is
> effectively broken.
>
> ubuntu@mini-pacific:~$ cat /etc/apt/sources.list.d/ceph.list ; sudo apt
> update | grep ceph ; sudo apt install ceph ceph-osd ceph-mon ceph-mgr
> deb https://download.ceph.com/debian-pacific/ focal main
>
> WARNING: apt does not have a stable CLI interface. Use with caution in
> scripts.
>
> Hit:5 https://download.ceph.com/debian-pacific focal InRelease
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
> ceph-mgr : Depends: ceph-base (= 15.2.17-0ubuntu0.20.04.4) but it is not
> going to be installed
> ceph-mon : Depends: ceph-base (= 15.2.17-0ubuntu0.20.04.4) but it is not
> going to be installed
> ceph-osd : PreDepends: ceph-common (= 15.2.17-0ubuntu0.20.04.4) but it is
> not going to be installed
> Depends: ceph-base (= 15.2.17-0ubuntu0.20.04.4) but it is not
> going to be installed
> E: Unable to correct problems, you have held broken packages.
>
> Reed
>
> On Aug 30, 2023, at 11:33 AM, Burkhard Linke <
> Burkhard.Linke@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx<mailto:
> Burkhard.Linke@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>> wrote:
>
> Hi,
>
> On 8/30/23 18:26, Yuri Weinstein wrote:
> 16.2.14 has not been released yet.
>
> Please don't do any upgrades before we send an announcement email.
>
>
> Then stop pushing packets before the announcement. This is not the first
> time this problem occurred. And given your answer I'm afraid it won't be
> the last time.
>
> It can't be that hard to coordinate releases.....
>
>
> Regards,
>
> Burkhard
>
> _______________________________________________
> ceph-users mailing list -- ceph-users@xxxxxxx<mailto:ceph-users@xxxxxxx>
> To unsubscribe send an email to ceph-users-leave@xxxxxxx<mailto:
> ceph-users-leave@xxxxxxx>
>
> _______________________________________________
> ceph-users mailing list -- ceph-users@xxxxxxx
> To unsubscribe send an email to ceph-users-leave@xxxxxxx
>
>
--
Laura Flores
She/Her/Hers
Software Engineer, Ceph Storage <https://ceph.io>
Chicago, IL
lflores@xxxxxxx | lflores@xxxxxxxxxx <lflores@xxxxxxxxxx>
M: +17087388804
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
