On Sun, 2018-04-15 at 00:48 +0200, Dominik 'Rathann' Mierzejewski
> On Saturday, 14 April 2018 at 03:30, po...@pouar.net wrote:
> > golang-github-dsnet-compress
> > httpd
> > php-pecl-http
> > python-httpbin
> > webkit2gtk3
> > woff2
> > So I just announce that I'm updating the package on the day I
> > update it
> > right?
yes, you did, Travis. Thanks for it.
> Have you rebuilt all dependent packages successfully beforehand?
> If not, and there are API and/or ABI changes that require porting
> to the new API, you'll be creating unexpected work for the
> maintainers of the above packages.
Well, I'd not call it unexpected. Once you announce API/ABI change it
is expected that at least a rebuild, or also a code change(s), will be
needed. The maintainer of the package which does that API/ABI change
can help with porting to the changes, either with a patch or at least
pointing to upstream guide with the port instructions to the new API,
of course, and it's highly welcome, but it's not always possible.
> Please do test rebuilds in COPR if you haven't
> already and try to fix any issues before actually doing the update.
I'm not sure it's fair to expect everyone doing this. First of all,
Travis doesn't seem to have commit rights to any of the referenced
packages, according to , neither he's part of provenpackagers group,
thus his best effort starts with this announcement and can be followed
by a pull-request or bug filling with a proposed change for the other
packages, but even that is sometimes not doable. Second, most/many
package maintainers are volunteers, kind of proxy for upstream work
they may not have any influence on, they just provide something useful
in Fedora for others, to make it easier to use for them. It doesn't
matter how large the package is or how many dependencies it has, from
my point of view. Compare it with something huge, like gcc updates,
mass rebuild(s) due to it and all the work involved around that. That
couldn't be done that smoothly with a group of volunteers "over the
I do not know Travis and his position in that what I imply above, I
only try to give my point of view on this. It's always nice to see the
help from the package maintainer, but I do not think you can force it
in general. Not talking that the dependencies can have available
upstream fix already and the other maintainer can be aware of it, thus
the work you want from Travis might be useless and duplicated. Maybe.
It's all about coordination and it starts with these announcements.
devel mailing list -- email@example.com
To unsubscribe send an email to devel-le...@lists.fedoraproject.org