OUTAGE: Koji system 2019-01-11 -> 2019-01-14
by Stephen John Smoogen
Planned Outage - Koji Services - 2019-01-11 22:00 UTC
There will be an koji outage starting at 2019-01-11 22:00 UTC, which
will last approximately 4 days.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run:
date -d '2019-01-11 22:00UTC'
Reason for outage:
The facility that houses the Fedora s390 server will have a major
power outage starting 2019-01-11 22:00 UTC and ending 2019-01-14 22:00
UTC. During this time the s390 builders will not be available and all
builds will be queued up until they are available and will not
complete.
Affected Services:
koji and related services which make composes and builds
Ticket Link:
https://pagure.io/fedora-infrastructure/issue/7429
Please join #fedora-admin or #fedora-noc on irc.freenode.net or add
comments to the ticket for this outage above.
--
Stephen J Smoogen.
5 years, 3 months
Why no wdune sponsoring ?
by J. Scheurich
Hi,
Are there any tips how to get wdune fedora sponsoring ?
We are working years on free software, but the distributors simply
ignore it
(or worse) use a more than 10 years old version (like in debian/ubuntu) 8-(
What is wrong with wdune ?
It uses old technologies like motif or X3D.
Motif has the advantage that the 2D-GUI did not change over the years
(a lot of interesting software under Linux died from changing versions of
QT or gtk for example).
X3D has been superseded by webgl, but X3D can be displayed via webgl
(X_ITE or x3dom).
What need to be done, to bring wdune to fedora ?
If i get no fedora sponsoring, are there some volunteers to add wdune to
fedora ?
It looks like, is not much work, it looks like wdune passed the review
process:
https://bugzilla.redhat.com/show_bug.cgi?id=1658153
What to do ?
so long
MUFTI
5 years, 3 months
Proposal: Add a separate “flatpaks/” namespace.
by Owen Taylor
Currently, the content for a Flatpak in Fedora can be found in
modules/<application>. E.g.:
https://src.fedoraproject.org/modules/quadrapassel/tree/master - I’d
like to propose creating a separate namespace in src.fedoraproject.org
- flatpaks/
Benefits:
* Allow automation to easily distinguish Flatpaks from other modules.
(https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...
)
* Make it easy to browse through the source of available Flatpaks
* Reduce some confusion. A Flatpak is a module, but it’s *also* a
container, and the dist-git repository will include files for both.
Downsides:
* We have a few graphical applications that are available as standard
loose-rpm macros (gimp, rawtherapee, skychart). While it should work
to have flatpaks/gimp and modules/gimp build different streams of the
gimp module, it’s going to be more confusing than different branches
in the same repository. (There are even possibilities for using the
*same* branch using module-stream-expansion, though that’s not
something I’d encourage at the moment.)
Needed steps:
* Remove special casing of flatpak => modules in Bodhi
https://github.com/fedora-infra/bodhi/blob/develop/bodhi/server/models.py...
* Adjust namespace special-casing in fedpkg
https://pagure.io/fedpkg/blob/master/f/fedpkg/cli.py
* Adjust namespace special-casing in fedscm_admin
https://pagure.io/fedscm-admin/blob/master/f/fedscm_admin/utils.py
* In fedscm_admin: Map flatpaks namespace to the ‘module’ PDC branch
type when storing the SLA into the PDC, to avoid PDC changes, and
because the SLA really is a module SLA.
* Adjust distgit pagure configuration to add flatpaks to
ALLOWED_PREFIX and REQUIRED_GROUPS
https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/dist...
* Add flatpaks/ to the kojid allowed_scms configuration
https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/koji...
* Add flatpaks/ to the module-build-service SCMS configuration
https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/mbs/...
* Adjust the owner-sync-pagure script to handle flatpaks/
https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/bodh...
* Move or reimport existing Flatpak repositories
(modules/eog, modules/feedreader, modules/flatpak-common,
modules/flatpak-runtime,
modules/gnome-clocks, modules/gnome-tetravex, modules/quadrapassel)
Potential issues:
* We should probably move flatpak-common to the flatpaks/ namespace
for ease of discovery, but it isn’t in any way a flatpak, it’s just a
module that Flatpaks can depend on.
* The ability of modules to include other modules won’t work without
further adjustments to the MBS config.py (MODULES_ALLOW_REPOSITORY) -
I don't see this as useful functionality for Flatpaks.
5 years, 3 months
dnf download misbehaving?
by Neal Becker
dnf download --source wireshark
[...]
No package wireshark-2.6.5-1.fc29.src available.
Exiting due to strict setting.
Error: No package wireshark-2.6.5-1.fc29.src available.
5 years, 3 months
New package not (yet) recognised by Bodhi
by Richard Fearn
Hi
I had a new package approved yesterday (perl-App-ccdiff) and I've
built packages for F29/rawhide. Bodhi doesn't know about the new
package yet, though, so I can't submit a new package update for F29.
How long does it normally take for Bodhi to start recognising a
newly-created package?
Thanks
Rich
--
Richard Fearn
richardfearn(a)gmail.com
5 years, 3 months