Re: How should I coordinate the package updates with you guys?

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

 



I suggest you look at the wiki page describing the package update process, specifically the section for rawhide:

https://fedoraproject.org/wiki/Updates_Policy#Rawhide_.2F_devel_.2F_master

It outlines the actions recommended / needed for updates with and without implications for dependent packages.

Jason already posted a link to a script which you can use to determine affected packages and their maintainers.

Fabio

On Fri, Apr 13, 2018, 00:07 <pouar@xxxxxxxxx> wrote:
On Thu, 12 Apr 2018 15:43:28 -0500
Jason L Tibbitts III <tibbs@xxxxxxxxxxx> wrote:

> >>>>>  <pouar@xxxxxxxxx> writes:
>   
> > Brotli apparently just got a new update, and I was told I have to
> > coordinate package updates with you guys in Rawhide instead of just
> > uploading the updates unannounced. How should I proceed?
> ] 
>
> Well, there's only really a need to coordinate if the versioning of the
> library changes, or if there's an ABI change and (boo) upstream doesn't
> bother to bump the soversion when they break the ABI, or if there's
> something else that people need to know about like an API change which
> is going to break users of the library when they next rebuild.
>
> If you're just releasing a compatible update, then there's no real need
> to say much of anything.  Otherwise this list would be flooded with
> update notices.
>
> If you do need to make an announcement, you should say what is changing,
> what needs to be done to accommodate it, and provide a list of packages
> which will need rebuilding.  You can use the find-package-maintainers
> script from
> https://pagure.io/fedora-misc-package-utilities/blob/master/f/find-package-maintainers
> to give a nice list of packages and their owners so that people can
> easily see if they'll need to do anything.
>
> (This really needs to be put into the wiki if it isn't already there.)
>
>  - J<
> _______________________________________________
> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx

How do I find out what packages depends on it? Would
`dnf repoquery --whatrequires brotli`
provide that? or is there a different command that I should run? Do I just
make an announcement after uploading with the list of packages that need to
rebuild or is there something else that I need to do first?

--
GPG Keys: https://keybase.io/pouar
Tox ID:
2EA7A6D5494C10B2E0F32004A1E9CBD971777E551A902059E5EA7E73E5A299272F29D9FF5F6A
Matrix ID: @Pouar:matrix.org Social Links: https://www.pouar.net/social.php
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux