On Mon, Feb 18, 2019 at 2:48 PM Kevin Fenzi kevin@scrye.com wrote:

On 2/18/19 12:56 PM, Kaleb Keithley wrote:

...

https://bodhi.fedoraproject.org/updates/FEDORA-2019-1c53f1a6c8 https://bodhi.fedoraproject.org/updates/FEDORA-2019-6a2e72916a

Would someone please give them a kick?

For some reason autosign likes to not process these correctly.

Is there any error message from Sigul or somewhere else?

- Ken

On Tue, Feb 19, 2019 at 10:47 AM Kevin Fenzi kevin@scrye.com wrote:

Sadly, not that I can find. ;(

Thanks for looking into it.

On 3/21/19 5:45 PM, Kaleb Keithley wrote:

On Tue, Feb 19, 2019 at 3:18 AM Kevin Fenzi kevin@scrye.com wrote:

...

On 2/18/19 12:56 PM, Kaleb Keithley wrote:

...

https://bodhi.fedoraproject.org/updates/FEDORA-2019-1c53f1a6c8 https://bodhi.fedoraproject.org/updates/FEDORA-2019-6a2e72916a

Would someone please give them a kick?

For some reason autosign likes to not process these correctly.

I've retagged them to get it to do another pass...

Sorry for not fixing them sooner.

Looks like another Ceph build is stuck.

https://bodhi.fedoraproject.org/updates/FEDORA-2019-16c36506c1

Would someone kick it please? Thanks

Fixed, and I looked and asked upstream and this is fixed in sigul 1.0.

So, hopefully we won't have to keep doing this too much longer.

kevin

Two more are stuck again.

https://bodhi.fedoraproject.org/updates/FEDORA-2019-dddd3b8418 https://bodhi.fedoraproject.org/updates/FEDORA-2019-399f5bd105

On Fri, Mar 22, 2019 at 3:08 PM Kevin Fenzi kevin@scrye.com wrote:

On 3/21/19 5:45 PM, Kaleb Keithley wrote:

...

On Tue, Feb 19, 2019 at 3:18 AM Kevin Fenzi kevin@scrye.com wrote:

...

On 2/18/19 12:56 PM, Kaleb Keithley wrote:

...

https://bodhi.fedoraproject.org/updates/FEDORA-2019-1c53f1a6c8 https://bodhi.fedoraproject.org/updates/FEDORA-2019-6a2e72916a

Would someone please give them a kick?

For some reason autosign likes to not process these correctly.

I've retagged them to get it to do another pass...

Sorry for not fixing them sooner.

Looks like another Ceph build is stuck.

https://bodhi.fedoraproject.org/updates/FEDORA-2019-16c36506c1

Would someone kick it please? Thanks

Fixed, and I looked and asked upstream and this is fixed in sigul 1.0.

So, hopefully we won't have to keep doing this too much longer.

kevin

---

devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

On 3/22/19 3:07 PM, Kevin Fenzi wrote:

On 3/21/19 5:45 PM, Kaleb Keithley wrote:

...

On Tue, Feb 19, 2019 at 3:18 AM Kevin Fenzi kevin@scrye.com wrote:

...

On 2/18/19 12:56 PM, Kaleb Keithley wrote:

...

https://bodhi.fedoraproject.org/updates/FEDORA-2019-1c53f1a6c8 https://bodhi.fedoraproject.org/updates/FEDORA-2019-6a2e72916a

Would someone please give them a kick?

For some reason autosign likes to not process these correctly.

I've retagged them to get it to do another pass...

Sorry for not fixing them sooner.

Looks like another Ceph build is stuck.

https://bodhi.fedoraproject.org/updates/FEDORA-2019-16c36506c1

Would someone kick it please? Thanks

Fixed, and I looked and asked upstream and this is fixed in sigul 1.0.

So, hopefully we won't have to keep doing this too much longer.

kevin

Hey Kevin, might I ask what fp.o is using for hosting sigul or package signing these days?  I have a private setup that works on EL7 using a special builder-rpms.repo, thanks to your help some years ago, but that version seems to be quite dated now.  I've tried recently putting both on F29 but the Server was an absolute no go -- IIRC due to the whole gpgme incompatibilty mess.  I can get the Bridge to run on F29 but it goes wonky if left inactive for too long ... something like overnight is enough.  Meanwhile, things like [0] make it look orphaned (see Assignee) and FTBFS for F30 [1].

[0] https://bugzilla.redhat.com/show_bug.cgi?id=1701923

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1675996