Freeze Break Request: add distro.builders to nameservers zones.conf

Hi all, Could I get +1s for the following Ansible patch? This adds the domain distro.builders (used for tiny.distro.builders for the Fedora Minimization Content Resolver) to the nameserver zones configuration. This domain is being transferred to Red Hat/Fedora control. Thanks in advance,

Re: IMA signing questions

Hi Ken, > > I want to add "intro to IMA signing" instructions to > https://docs.pagure.org/koji/signing/ . I wrote a basic PR at > https://pagure.io/koji/pull-request/3206 but it lacks technical > details. That'd be cool! > > - How do I generate my own new keypair so I can IMA-sign an RPM?

Re: Fedora 34 Change: Signed RPM Contents (late System-Wide Change)

> https://fedoraproject.org/wiki/Changes/Signed_RPM_Contents > I'd like to point out that after many requests, I have updated the change page for this significantly, with more details as to the goals (and non-goals) of this feature, and answers to many other questions asked. Please have

Re: Fedora 34 Change: Signed RPM Contents (late System-Wide Change)

> * Peter Robinson: > > > If the signatures end up in RPM headers, they will land in the RPM > database, too. > > “rpm -qla | wc -l” shows around 28,589 files for me, in the Fedora 33 > container image. / seems to need 183 MiB right now. If the signatures > land in the RPM database and the

Re: [[FBR] Freeze Break Request: ] dns: add 2 rh nameservers that make a lot of legit queries against our dns.

+1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines:

Re: [[FBR] Freeze Break Request: ] dns: Actually drop the limit on the group we defined in the last commit.

+1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines:

Re: FBR: Fix nrpe/nagios so that datanommer is easier to debug

> I am retitleing as I should have said what the patch was for and make sure > it had agreed upon subject FBR for filtering > > On Wed, 24 Apr 2019 at 07:06, Stephen John Smoogen wrote: +1 ___ infrastructure mailing list --

Re: [Freeze Break Request: ] buildvmhost-aarch64-01/01: Add dhcp info for 2 thunderx2 aarch64 buildvmhosts.

> From: Kevin Fenzi > We need to add these in so pxe sees the right thing to boot them. > > Signed-off-by: Kevin Fenzi --- > .../files/dhcpd.conf.noc01.phx2.fedoraproject.org| 16 > > 1 file changed, 16 insertions(+) > > diff --git

Re: [FBR ] releng-compose: Just have compose-x86-01 get the default group values for mem and cpus

+1 > From: Kevin Fenzi > In recent months/years, pungi has started to use more and more memory when > gathering > package sets. > So, give it enough memory to avoid the OOM killer killing composes. > > Signed-off-by: Kevin Fenzi --- >

Re: FBR: upgrade oz on builders

Given the minimal impact of the latest patch unless the config is updated to use the F30 config, +1 from me. Also, if it does in fact break stuff, it's easy enough to revert. ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To

Re: [PATCH] bodhi-pungi: don't run silverblue compose for testing

> This is a temporary hack to workaround https://pagure.io/pungi/issue/1092. > Note this also just re-uses the f27 logic, which is no longer needed. > --- > roles/bodhi2/backend/templates/pungi.rpm.conf.j2 | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git

Re: NO INFRASTRUCTURE MEETING ON 2018-11-22

> Is there any particular reason? I am going to guess that this is since today is a national holiday in the US: Thanksgiving[1]. [1]: https://en.wikipedia.org/wiki/Thanksgiving ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org

Re: [Freeze Break Request: ] Explicitly set Protocol 2 on sshd for pagure.

+1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines:

FBR: Make clime be on the pager for COPR

Hi all, Can I get +1s for the patchset to allow clime to ack service and host issues in nagios, and to make the initial COPR notifs go to him? Patrick From 1994c662f8eabcec78f24a8d7b2edc155d25bac2 Mon Sep 17 00:00:00 2001 From: Patrick Uiterwijk Date: Sat, 20 Oct 2018 11:19:57 +0200 Subject:

FBR: Stop emailing puiterwijk for ticketkey and add nagios check

Hi all, Can I get +1s to make Nagios check the ticketkey age and to make it stop email me hourly? Thanks, Patrick commit 3fc57e699b9c524d5683fcc39231f7b1f425bbb9 (HEAD -> master) Author: Patrick Uiterwijk Date: Sat Oct 20 15:36:00 2018 +0200 Enable nagios checks for ticketkey, and

Re: Freeze Break Request: fix up registry

+1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines:

Re: [Freeze Break Request: ] Upgrade pagure.io to pagure 5.1.3

ack, +1. ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines:

FBR: Allow anonymous HTTPS pulling via in-Pagure systems

Hi all, This should be my last FBR for now, as with this I tested everything in staging, and I believe it works there (SSH pull/push and HTTPS pull, we don't have HTTPS push for pagure.io (yet)). This basically sets the username for anonymous access to something that would never be a valid

FBR: Switch to in-Pagure https cloning and enable keyhelper/aclchecker for prod

Hi all, Can I get +1s for these last two patches, which should make Pagure.io fully repoSpanner compatible? It switches the prod sshd to the new sshd_config with keyhelper, and the other patch disables the scriptalias, which means it hits the code in Pagure that multiplexes this to gitolite

Re: FBR: Switch Pagure over to aclchecker

(Actually, until a future PR where I apply the correct sshd_Config to pagure01, it won't even change anything on prod for now other than the existance of these config options.) ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org

FBR: Switch Pagure over to aclchecker

Hi, This is the next step of preparing pagure.io for repoSpanner: switch the entry command to aclchecker, which is a small script that calls either repoBridge for repos on repoSpanner (none at this moment) or gitolite for all others. This adds some configuration for repobridge, but that won't

Re: [Freeze Break Request: ] Upgrade pagure.io to pagure 5.1.2

+1 this should be simple enough to back out if it fails. ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct:

FBR: Enable keyhelper for pagure01

Hi, Can I get +1s to the following patch? This would enable keyhelper.py on pagure.io, which is an alternative to authorized_keys file, which need a gitolite recompile to get changes activated. If anything goes wrong with it, sshd will fall back to the authorized_keys file, which will still be

Re: FBR: Only use proxy101 for internal candidate-regsitry for now to debug

> No, I am hoping that once I figure out what's going on, we can drop this temp > workaround. And the root cause is found and fixed now: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/thread/7IGK2QIBT3JU3GD77UDDM5VZ4TWKHNQ4/

FBR: Add proxy101/proxy110 to the OSBS whitelsit

Hi all, Can I get +1s for the patch underneath? This adds proxy101/proxy110 to the whitelist for OSBS for candidate-registry pushing. Patrick commit ef9fa10389a6a60843c96e4855dbdcb604583baa (HEAD -> master) Author: Patrick Uiterwijk Date: Tue Sep 25 21:34:39 2018 +0200 Whitelist

FBR: Disable OCSP on non-proxies

Can I get +1s for the following patch? Explanation as to why this specific patch is in the commit message. commit d2688610419973cd519ef8f8f581a03215aaf73c (HEAD -> master) Author: Patrick Uiterwijk Date: Tue Sep 25 21:25:00 2018 +0200 Only do OCSP stapling on the proxies The

Re: FBR: Only use proxy101 for internal candidate-regsitry for now to debug

> +1 for temp fix. Do we need to make a host proxy111 which is an A > record of proxy101 and proxy110 so we can do failover? > On Tue, 25 Sep 2018 at 14:55, Patrick マルタインアンドレアス Uiterwijk > https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproj

FBR: Only use proxy101 for internal candidate-regsitry for now to debug

Hi all, Can I get +1s for the following DNS repo change? This will make it simpler to debug issues with the candidate-registry from OSBS. Patrick commit 103f8de1f81264568d74e256ea45588d553ddd31 Author: Patrick Uiterwijk Date: Tue Sep 25 18:52:47 2018 + Only use proxy101 for

Re: FBR: upgrading pagure to 5.0

Let's give this a try.. +1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List

Re: [PATCH] Raise the file limit on the RabbitMQ cluster

+1 looks fine to me. ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List

Re: [PATCH] bodhi-pungi: prevent NVR conflicts for image builds

So, I guess that the current patch will work just fine, so +1 on that, but it does make updates out of sync with updates-testing. Before changing these paths, we need to ask adamw whether this will break his tooling, and possibly coordinate with him.

Re: "invalid path: ~/.fedora-server-ca.cert"

Hi, You very likely have an /etc/koji.conf.rpmnew. Could you please move that over /etc/koji.conf? If not, maybe you have a ~/.koji, with custom config, you might need to remove. If you have neither, can you make sure you have at least these package versions (from [1]):

FBR: Update libmodulemd on bodhi-backend01

Hi, I have had to update libmodulemd on bodhi-backend01, because it requires the "modulemd_objects_from_file" function in libmodulemd, which was added in version 1.2, but it is lacking a (versioned) requirement on libmodulemd, and due to the freeze we still had modulemd v1.1. This should not

FBR: Make new-updates-sync resync on re-stage without need for state deletion

Hi, So, for now (until https://github.com/fedora-infra/bodhi/pull/1986 gets finished and merged), it might happen that Bodhi stages a repo a second time (if it crashed while waiting for sync), which new-updates-sync doesn't notice, meaning releng needs to manually clean up the state file. This

Re: FBR : Disable F28 branched compose and enable two week atomic, cloud and container nightlies

Looks reasonable to me, and easy to revert. +1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: Freeze Break Request: more new sync changes

+1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: [PATCH] bodhi-pungi: make FAW and FAH use same versioning

+1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: FBR for Bodhi F28 release status update

+1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: FBR: Remove jenkins from dns and noc

+1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: FBR: Make new-updates-sync print what it did and email to releng-cron

No, because the logger.info statements also output things like what the current state is, and we explicitly set logging to ERROR to only catch the errors. I want these specific output messages to print whatever the log level is set to. ___

Re: FBR: Make fpaste.org cert use letsencrypt

+1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: FBR fixes to bodhi-pungi configs for atomichost artifacts

> This is an attempt to fix https://pagure.io/dusty/failed-composes/issue/176 > > I'd like to get patrick and one other person to review these changes. Sure, the changes look fine and easily revertable. Also, all these artifacts are failable. So +1.

Re: FBR: Remove myself from scholarship email alias

Sure, +1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: FBR: Add bugzilla email sync exception for jbwillia

Sure, +1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: FBR: enable gating on fedora-27's Atomic CI results

Looks reasonably self-contained to me and shouldn't break release stuff, so that's fine, +1 on the change. I just think it would be a good idea to inform the maintainers of these packages of this? ___ infrastructure mailing list --

FBR: Update fedmsg on compose-x86-01

Hi, Last Friday, pungi got updated on compose-x86-01, but that requires fedmsg-1.1.0 (there's currently 1.0.1 on that box) because of json encoding issues. +1 to run "dnf update --refresh fedmsg" on compose-x86-01? Patrick ___ infrastructure mailing

Re: Freeze break request: refresh fedmsg crl.pem

+1, though I thought we'd set fedmsg CRL as "content", meaning it wouldn't fall under freeze. ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: Goodbye nvr.rsplit('-', 2), hello modularity

> Don't be afraid of koji. :) I couldn't agree more, Koji's a pretty nice project to work on. It might seems scary for newcomers because of all the ingrained knowledge and assumptions, but once you get close the community is nice and friendly :). > > It is under active development. Of course,

Re: Freeze Break Request: fix git hooks on new packages

+1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: f28 and rawhide ignoring static ip settings

> On 03/15/2018 01:23 PM, Tomasz Torcz ️ wrote: > > It's not. Now it's enp0s3. > > And renaming /etc/sysconfig/network-scripts/ifcfg-ens3 to ifcfg-enp0s3 > doesn't do anything. Note that the files themselves also contain a DEVICE= line that would need to be updated for it to apply again.

Re: Goodbye nvr.rsplit('-', 2), hello modularity

> On 15/03/18 15:30, Patrick Uiterwijk wrote: > > Well currently at any rate? What's the long term story? > > Only when some module rpms accidentally leaked into rawhide > recently they definitely had the kind of rather unhelpful names > that you described in your post and I got the impression

Re: Seems to be issue in f28 for obsoleting python [23]-modulemd and replacing with libmodulemd

> I updated today, and looked at the conflicts. One of them is for > python2-modulemd and python3-modulemd. They are obsolete, being > replaced by libmodulemd. But it isn't happening for some reason. > > package python2-dnf-2.7.5-8.fc28.noarch requires python2-modulemd, but > none of the

Re: Freeze Break Request: fix prerelease redirects on getfedora.org

+1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: FBR: Fix the broken fedimg hub config key

> Hi, > > After the last change for updating fedimg on stg. The config key in > the prod also broke. To fix this issue I would like to apply the > following patch so the it can listen to pungi messages. > > --- > roles/fedimg/templates/fedmsg.d/fedimg.py | 4 +--- > 1 file changed, 1

FBR: Update Bodhi tree filenames for atomic-workstation

Hi all, The filenames for atomic workstation treefiles changed from -ostree- to -atomic-. Can I get +1s? Patrick diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 index ff31d400e..1561360d6 100644 ---

Re: [PATCH] bodhi pungi ostree: point to different repos for f28

> On 03/09/2018 04:25 PM, Patrick マルタインアンドレアス Uiterwijk wrote: > > > ok I'm using a pull request for this: > > https://gitlab.com/dustymabe/fedora-infra-ansible/merge_requests/1/diffs?w=1 > > here is the updated patch if you want to fight with pulling it in from e

Re: [PATCH] bodhi pungi ostree: point to different repos for f28

> The f28 repos we need to tap into are not in the same locations > as for post release (f26/f27) runs. We also don't need to include > the 'updates' repo because there is no updates repo for f28 yet. > This is actually an f28 repo, but I had made a mistake moving things around (I accidentally

Re: FBR: fix hooks for new packages on src.fedoraproject.org

> Greetings. > > It was reported to me that a number of new packages were not showing up > in grokmirror on src.fedoraproject.org. On looking I noted that new > packages did not have the chained post-receive hook we normally put in > place. The cause seems to be a typo in the command. > > I'd

FBR: Restart collectd

Hi all, So, in ansible commit 2cce3883a34e5366e822fd581455f63344630c8c, Kevin disabled the graphite plugin for collectd. Unfortunately, at the same time, he removed the restart handler for collectd, which means that all of our boxes are still running with the old config, slowly filling up

Re: FBR: To update pungi on branched-composer.phx2.fedoraproject.org and rawhide-composer.phx2.fedoraproject.org to pungi-4.1.22-7.fc27

> We were having issues with modular rpms ending up in Everything repo and also > missing > Container variant, which should be fixed by pungi-4.1.22-7.fc27 update. > > koji build: https://koji.fedoraproject.org/koji/buildinfo?buildID=1055890 +1 > > Fixes: > https://pagure.io/pungi/issue/862 >

Re: Retroactive FBR : Increase packages host fedmsg backlog warning and critical threshold

> Hi, > > The current threshold are a little bit low and we receive warning when > there are a lot of package updates. I have already pushed the commit > thinking that this was impacting only packages hosts which is not the > case :) > > Looking for retroactive +1 ? > > Thanks > Clément > +1

FBR: Update module pungi conf with correct signing key

For F28+ modular, the modules are signed by the keys of the underlying platform rather than the fedora-modular key. +1s for this patch to set the correct key? diff --git a/roles/bodhi2/backend/templates/pungi.module.conf.j2 b/roles/bodhi2/backend/templates/pungi.module.conf.j2 index

Re: FBR: Update pungi and install python3-modulemd and pdc-client on bodhi-backend

This FBR is retracted. The issue is not fixed in the latest pungi, and will need emergency Bodhi patches instead, together with other fixes. So, instead, I'll be sending out an FBR for a Bodhi update soon. ___ infrastructure mailing list --

FBR: Update pungi and install python3-modulemd and pdc-client on bodhi-backend

Hi, Pungi 4.1.22 moved from py2 to py3 but is needed for modular update composes, so can I get +1s to update pungi and move the deps over to their py3 versions? These deps are not deps of the main package because they're only needed when running module updates. I think the biggest chance of

Re: FBR: Update new-updates-sync for f28(m) updates-testing

> On Tue, Mar 6, 2018 at 11:34 PM, Patrick Uiterwijk > > Comment inline below. > > > I think aarch64 should be up with the ['x86_64', 'armhfp', > 'source'] list now Right, imagine that I've done that. (lines of patch following). +

Re: [PATCH] move to unified atomic ostree repo structure

I asked Dusty to push a patch to fix the f26 and f27 dest directories. ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: [PATCH] move to unified atomic ostree repo structure

Okay, let's do this thing. Can you please push this change to ansible? ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: Koji build: cannot find spec file

> On 02/17/2018 08:22 PM, Jerry James wrote: > > Yeah, it's still broken. I looked at it a bit but couldn't see what the > exact cause of the breakage is. ;( > > If we cannot get it fixed by tomorrow morning, I'll revert us back to > the older koji version. ;( We have found and fixed the issue

Re: [PATCH] atomic host life support for f26

> Sync out the stable ref too, which is just aliased to > the updates ref at this point. > --- > roles/bodhi2/backend/files/new-updates-sync | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/roles/bodhi2/backend/files/new-updates-sync > b/roles/bodhi2/backend/files/new-updates-sync >

Re: Adding Dusty Access/Membership to Releng/Infra

> For Fedora Atomic we release content every two weeks. A lot of ducks > have to be in a row in order to do this and often times behind the > scenes work is time sensitive. I really need access to releng/infra > so that I can be more efficient in doing this. I'd like to be able to: Okay, here we

Re: FBR: bodhi-dequeue-stable dies

+1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: [PATCH 2/2] robosig: sign F27AH updates-testing refs

> The diff looks ugly but all I did was copy the updates > entries and s/updates/testing/ and then I deleted the one > existing testing entry that was below f27-workstation. > --- +1 ___ infrastructure mailing list --

Re: [PATCH] add syncing for f27-updates

> --- > roles/bodhi2/backend/files/new-updates-sync | 11 ++- > 1 file changed, 10 insertions(+), 1 deletion(-) > > diff --git a/roles/bodhi2/backend/files/new-updates-sync > b/roles/bodhi2/backend/files/new-updates-sync > index a241eeb..35c9d58 100755 > ---

Re: [PATCH] sync script: copy history of ostree ref

> If we happen to miss a sync for whatever reason there could be > gaps in the ostree history. Adding --depth=-1 will make sure that > the entire history for the ref is in the target repo. > --- > roles/bodhi2/backend/files/new-updates-sync | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-)

Re: FBR: Update pungi on branched-composer.phx2.fedoraproject.org and compose-x86-02.phx2.fedoraproject.org

> We need > https://pagure.io/pungi/c/c89f0334579aee68286d07d4b57f4df67510166c?branch... > patch to create live images for arm in modularity, which is included in Pungi > 4.1.20 > release. So, I would like to update the branched composer and try it out. And > if possible > include it in F27

Re: [FBR] support msi binaries released on pagure.io

> Good Morning Everyone, > > There was a report that releases.pagure.org doesn't serve .msi binaries > properly. > > I believe this diff should fix it: > > roles/pagure/frontend/templates/0_pagure.conf | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git

Re: Freeze Break Request: update rpm on builders

> Greetings. > > In order to allow the new rich deps that rust packaging requires we need > to update rpm on the builders to a version that has backported support > for 3 new rich deps. It needs these at srpm generation time to > understand the new rich deps. > > ignatenkobrain has created a rpm

Re: FBR: update dist-git for namespaced lookaside

> On Sat, Oct 28, 2017 at 01:41:32AM +0200, Patrick Uiterwijk wrote: > > +1 for me. Thanks > > Do you have the link handy for the path of the namespace support in dist-git? Yep: https://src.fedoraproject.org/rpms/dist-git/blob/master/f/ensure_gitrepo_namespaced.patch > > > Thanks, >

Re: Need your collaboration to release fedpkg

> Hello, > > On Fri, Oct 27, 2017 at 5:27 AM, Chenxiong Qi > > > We will probably need someone else here as well as I do not have permission > to run pkgs playbook, I think. Otherwise the new updated dist-git package > (1.4-3) > should already be in epel7-infra-stg

Re: FBR: Bodhi 3.0

> Sure, +1. > > It might be good to disable the sync script entirely at first so we can > examine the output and make sure it looks ok before syncing it anywhere. The new code will generate it somewhere else (in /mnt/koji/compose/updates/ instead of /mnt/koji/mash/updates/), so that will happen

Re: FBR - a timeout for the koji pkglist sync script

> +1, default timeout cant be 12 hours. It totally is, and for good reason. There *are* API calls that take literally hours. For example, the "Finish and import build" call that koji does as part of a build step for texlive (a package with lots of subrpms and big subrpms) takes about 6 hours at

Re: Any idea what happened to the Fedora 27 ostree refs yesterday?

> https://pagure.io/atomic-wg/issue/336 > > > Each ref only has one commit in it now: For the record, this is now fixed. Both the underlying cause and the results. This was caused by me forgetting to push a fix a while ago that means that robosignatory-signatomic overwrote the ref. In the

Re: FBR - ostree commit signing fixups for f27/rawhide

> A few fixes for ostree commit signing for f27/rawhide. > > [PATCH 1/3] robosig: add in commit signing for f27 > [PATCH 2/3] robosig: sign ostree rawhide with f28 key > [PATCH 3/3] robosig: add in ostree signing for rawhide ppc64le These patches look correct to me. +1

Re: Duplicates in package owner alias cronjob?

> I'm confused about something. Can any postfix experts help debug? > > On Friday I put a new package-owner-alias cronjob in place on bastion > (that Matt Prahl wrote). It generates the package owner list from > pagure over dist-git instead of generating it from pkgdb. > > >

Re: fedpkg new-sources broken?

> Hi, > > > I seem to be unable to upload a new tarball for freefem++: > > $ fedpkg new-sources freefem++-3.56.tar.gz > /usr/lib/python2.7/site-packages/fedora/client/bodhi.py:48: > DeprecationWarning: fedora.client.bodhi has been deprecated. Please use > bodhi.client.bindings instead. >

Re: s390x build failures

> Thanks and sorry for not searching first ;) I am the one who started a new thread :). Tried to make sure it stood out. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: How attached are we to branch ACLs? -- Should we kill pkgdb?

> As I already mentioned in person when this came up in a DevConf talk, I > think that this is a plan that will likely break a lot of things, especially > the expectations all our users rely on (that everything in Everything has a > consistent guaranteed life time), and that doing away with

Re: Packagers - Flag day 2016 Important changes

> On 12/12/2016 04:53 AM, Vít Ondruch wrote: > > There are patches still coming that will switch the fedora packaging tools to > use GSSAPI rather than Kerberos directly, which will handle auto-selecting the > right TGT. I'm not sure what the status is on this, but Patrick Uiterwijk > (CCed) >

Re: out of space on some builders

> Looks like there are problems on some builders: Then reporting koji errors, it would be great if you could attach the task link so that we can check. > > BuildrootError: could not init mock buildroot, mock exited with status > 1; see build.log for more information > > And there is no

Re: Creating an new update is failing

Hi, > Hello, > > I'm trying to create a new update and > I'm getting this error: > > Builds : Unable to create update. Parent instance is not bound to a Session; > lazy load > operation of attribute 'release' cannot proceed > > The build looks fine: >

Re: upcoming build and release developer flag day December 12 2016

> On 11/21/2016 03:51 PM, Patrick マルタインアンドレアス Uiterwijk wrote: > > > Exactly like that, yes. It isn't present (yet?) on Fedora 25, though I see now > it's been added to Rawhide. Right, I dropped the ball there for a bit while testing. However, I'm building for epel6,epel7,f2

Re: upcoming build and release developer flag day December 12 2016

> On 11/21/2016 08:07 AM, Vít Ondruch wrote: > > > So, it turns out that this doesn't work yet. It's complicated, but there's a > patch pending for Koji that will make this work. It hasn't landed yet. > Hopefully > that will change before the flag day. And I'm thrilled to say that my patch to

Re: upcoming build and release developer flag day December 12 2016

> Dne 21.11.2016 v 16:07 Alexander Bokovoy napsal(a): > > > $ KRB5_TRACE=/dev/stderr kinit vondruch(a)FEDORAPROJECT.ORG > [8655] 1479746886.252240: Resolving unique ccache of type KEYRING > [8655] 1479746886.252281: Getting initial credentials for > vondruch(a)FEDORAPROJECT.ORG > [8655]

Re: upcoming build and release developer flag day December 12 2016

> On 11/21/2016 10:32 AM, Florian Weimer wrote: > > Yes, as I mentioned elsewhere, we should probably have the fedora-packager RPM > ship with a krb5.conf.d snippet that sets the appropriate values. You mean something like

Re: upcoming build and release developer flag day December 12 2016

> On 2016-11-20, 01:11 GMT, Dennis Gilmore wrote: > > a) Is it possible to have multiple tickets, each from different > realm? When I do kinit mcepl(a)FEDORAPROJECT.ORG, klist lookslike my > @REDHAT.COM ticket has been knocked out (i.e., thereis only FPO > ticket there). Ah, klist -A

Re: Stuck PPC64 build

Hi, > On Mon, Nov 14, 2016 at 12:03:33PM -0700, Jerry James wrote: > > puiterwijk possibly. Yes. For now, you can just ping me on IRC, or create a ticket on https://pagure.io/fedora-infrastructure to get a PPC64(LE) instance on our Infrastructure cloud. In the near future, we hope to open up

Re: [PATCH] make /atomic-cd available on kojipkgs.fp.o

Looks sane to me. +1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: Freeze Break Request: update koji-builder

Looks reasonable and small enough to me. +1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: Freeze break request: add fedmsg bot in #fedora-admin

+1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: Freeze break request: allow .htaccess fileinfo override in getfedora.org

> Greetings. > > To fix issue https://pagure.io/fedora-infrastructure/issue/5502 > we need to allow .htaccess files "FileInfo" privs in > the /srv/web/getfedora.org dir on the proxies so the redirects work. > > +1s? > > From 5625ce807a7ffd294b145b0288846a7f75a42821 Mon Sep 17 00:00:00 2001 >

  1   2   >