Highlights from the latest Copr release
by Pavel Raiskup
Hello,
recently (on Feb 06, 2020) a new Copr release landed production. Here is
the list of visible changes:
- Users now can build packages against explicitly enabled modules. Go to
`Project -> Settings -> Build Options -> [Edit] button (near _enabled_
chroot) -> Enable module: textarea`. Note that fedora modular
repositories do not behave entirely good in mock (and copr) so we had to
disable before by default. So to actually bring the modules into copr,
you need to also configure the "external repositories" textarea for the
fedora-modular repo.
- Module builds were historically done only against Fedora dist-git. Now
the `copr-cli build-module` command was enhanced to accept `--distgit`
option which allows users to specify which dist-git instance to build
the module against. For now we have only the "fedora" distgit
configured. If you have ideas what external dist-git we should add to
our configuration, let us know.
- The EOL chroot policy scripts responsible for notifying users about
upcoming removals were fixed, users should now always be notified - and
if for some reason they are not, the EOL chroot will not be removed.
- Several fixes were done in copr-rpmbuild so the builds should be more
reliable, especially when the builder VM is heavily re-used for many
builds.
- News from yesterday - @msuchy enabled CDN for copr backend repositories.
You, or your users, likely want to re-enable the copr repositories
(dnf copr enable <owner/project>).
Happy building!
Pavel
4 years, 3 months
Announcing multi-builds updates gating
by Pierre-Yves Chibon
Good Morning Everyone,
We are pleased to announce that the work to gate rawhide packages has leveled
up!
Back in July we announced the first phase where bodhi got the support to gate
single-build updates. We can now officially announce that bodhi can gate
multi-builds updates. This is achieved through the use of side-tags, which can
be created on demand via ``fedpkg request-side-tag``. The package can then be
built using ``fedpkg build --target=<your side-tag>`` or via ``fepdkg
chain-build --target=<your side-tag>``. Once all your packages are built, you
can create a bodhi update from this side-tag using either the ``Use Side-Tag``
drop-down or in the CLI by using the ``--from-tag`` argument to the ``bodhi
updates new`` command.
Every build in the update will then be tested by the CI system which will report
the outcome. Bodhi will then query greenwave which will rely on the collection
of these individual results to make a decision about whether to gate the update
or not.
More detailed documentation is available at:
- https://fedoraproject.org/wiki/Package_update_HOWTO
- https://docs.fedoraproject.org/en-US/rawhide-gating/
Note: this is not the end of rawhide-gating. We still have some changes planned
to make it easier for greenwave to make a decision about an update containing
multiple builds, we want to improve the documentation for on-boarding new CI
systems and make them matter for rawhide as well as for stable releases.
We then have all the work ahead to improving our tests, including enabling some
of them distribution-wide, looking at the reverse dependencies or testing for
the impact of an update on our composes.
Looking forward for your feedback!
Pierre
For the rawhide gating team
_______________________________________________
devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedora...
4 years, 3 months
Please, IMHO, resolve in some way the Samba MIT kerberos problem.
by Dario Lesca
Too many people (like also me) try to use samba-dc on fedora for deploy
a production AD DC controller, without know that MIT kerberos is
experimental and some useful things cannot work (es. win to win
access).
An recent last example:
https://lists.samba.org/archive/samba/2019-November/226845.html
> On 01/11/2019 22:23, Vex Mage wrote:
> > The script is expecting dpkg however this is a Red Hat
> > derived distro (Fedora Server.)
>
> Where did you get the Samba packages from ?
>
> If they are the default OS packages, then you should stop using
> them, they use MIT kerberos and are experimental.
There is many approach for resolve this issue:
a) Stop use MIT kerberos and rebuild samba with Heimdal Kerberos.
b) Produce a samba alternative package version (like, for example,
firefox-x11) build it with Heimdal Kerberos (es samba-hk-*)
c) Stop enable DC on Fedora, like RH/Centos do.
d) Notify users at the end of the installation that Fedora Samba DC is
experimental.
e) Solve the problems that make MIT kerberos experimental and put us in
a position to ask for help on the samba team.
f) ... some other proposal ?
What is the best approach chosen by Fedora ?
Many thanks
--
Dario Lesca
(inviato dal mio Linux Fedora 31 Workstation)
4 years, 3 months
Re: Non-responsive maintainer: devrim (gdal, proj, geos)
by Tom Hughes
On 12/02/2020 07:29, Devrim Gündüz wrote:
>
> Hi Sandro (and Tom),
>
> On Wed, 2020-02-12 at 00:01 +0000, Tom Hughes wrote:
>>> I've attempted to contact devrim directly 2019-11-27 offering to take
>>> care of updating these packages, but received no reply. My recent PR to
>>> update gdal [2] also received no reply.
>>
>> ...and postgis as well which is FTBFS after the mass rebuild and already
>> needed rebuilding for dependencies which is blocking a bunch of stuff.
>
> Please keep me as co-maintainer. I'm already maintaining these packages in the
> upstream repository (https://yum.PostgreSQL.org) with more options there, and
> I'd like to keep things in sync as much as possible.
I'd just like a fixed build so I can rebuild all my FTBFS things which
failed because of postgis... I don't care who does it...
Tom
--
Tom Hughes (tom(a)compton.nu)
http://compton.nu/
4 years, 3 months