Sorry to chime in with another "is it working yet?" question, but I
couldn't resist:

I put in a CVS request a day or two before the whole recent mess
occurred. The cvs request was just granted (last night), but now it
tells me that I'm not on the ACL for the package (ocaml-ocamlgraph).
The pkgdb system (through the web interface) claims that I actually
am. I changed my RSA key, user cert, and CA certs beforehand
(yesterday), so I don't think there's an issue with not waiting long
enough for something to process. I can also use Koji (at least for
scratch builds, which is how I tested this) just fine. Am I forgetting
something? Are others experiencing something similar?

- Alan

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Alan Dunn wrote:

Sorry to chime in with another "is it working yet?" question, but I
couldn't resist:

I put in a CVS request a day or two before the whole recent mess
occurred. The cvs request was just granted (last night), but now it
tells me that I'm not on the ACL for the package (ocaml-ocamlgraph).
The pkgdb system (through the web interface) claims that I actually
am. I changed my RSA key, user cert, and CA certs beforehand
(yesterday), so I don't think there's an issue with not waiting long
enough for something to process. I can also use Koji (at least for
scratch builds, which is how I tested this) just fine. Am I forgetting
something? Are others experiencing something similar?

There have been some issues with pkgdb since we rebuilt everything. Let
me see if I can see any problems with ocaml-ocamlgraph.


-Toshio

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Alan Dunn wrote:

Sorry to chime in with another "is it working yet?" question, but I
couldn't resist:

I put in a CVS request a day or two before the whole recent mess
occurred. The cvs request was just granted (last night), but now it
tells me that I'm not on the ACL for the package (ocaml-ocamlgraph).
The pkgdb system (through the web interface) claims that I actually
am. I changed my RSA key, user cert, and CA certs beforehand
(yesterday), so I don't think there's an issue with not waiting long
enough for something to process. I can also use Koji (at least for
scratch builds, which is how I tested this) just fine. Am I forgetting
something? Are others experiencing something similar?


Okay, This is fixed.

As part of this rebuild we rebuilt the cvs server and put all the
configs into puppet. Unfortunately, if you interpret that to mean that
the old cvs server was not in puppet, you'd be correct. generating new
acls is on a cron job and that cron job was forgotten in the move. I've
fixed that so acls should once again be generated every hour and half hour.


-Toshio

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Hi,

> As part of this rebuild we rebuilt the cvs server and put all the
> configs into puppet. Unfortunately, if you interpret that to mean that
> the old cvs server was not in puppet, you'd be correct. generating new
> acls is on a cron job and that cron job was forgotten in the move. I've
> fixed that so acls should once again be generated every hour and half hour.

Can you check this please?

I'm trying to upload the new mono src rpm, but it's failing to upload
the tar ball

Checking: mono-2.0.tar.bz2 on
http://cvs.fedoraproject.org/repo/pkgs/upload.cgi
ERROR: could not check remote file status
make: *** [upload] Error 255
ERROR: Uploading the source tarballs failed!

TTFN

Paul
--
Sie können mich aufreizen und wirklich heiß machen!
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Works now - thanks! (Thus I suppose it's not the same thing as Paul's
problem...)

- Alan

2008/8/23 Toshio Kuratomi <a.badger@gmail.com>:
> Alan Dunn wrote:
>>
>> Sorry to chime in with another "is it working yet?" question, but I
>> couldn't resist:
>>
>> I put in a CVS request a day or two before the whole recent mess
>> occurred. The cvs request was just granted (last night), but now it
>> tells me that I'm not on the ACL for the package (ocaml-ocamlgraph).
>> The pkgdb system (through the web interface) claims that I actually
>> am. I changed my RSA key, user cert, and CA certs beforehand
>> (yesterday), so I don't think there's an issue with not waiting long
>> enough for something to process. I can also use Koji (at least for
>> scratch builds, which is how I tested this) just fine. Am I forgetting
>> something? Are others experiencing something similar?
>>
> Okay, This is fixed.
>
> As part of this rebuild we rebuilt the cvs server and put all the configs
> into puppet. Unfortunately, if you interpret that to mean that the old cvs
> server was not in puppet, you'd be correct. generating new acls is on a
> cron job and that cron job was forgotten in the move. I've fixed that so
> acls should once again be generated every hour and half hour.
>
> -Toshio
>
>
> --
> fedora-devel-list mailing list
> fedora-devel-list@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-devel-list
>

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Paul <paul@all-the-johnsons.co.uk> writes:
> Can you check this please?

> I'm trying to upload the new mono src rpm, but it's failing to upload
> the tar ball

> Checking: mono-2.0.tar.bz2 on
> http://cvs.fedoraproject.org/repo/pkgs/upload.cgi
> ERROR: could not check remote file status
> make: *** [upload] Error 255
> ERROR: Uploading the source tarballs failed!

FWIW, I successfully uploaded two new tarballs this afternoon, so it
seems to be working here. I suspect you have connection or
authentication issues --- have you updated ~/.fedora-upload-ca.cert
for instance?

regards, tom lane

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Paul wrote:


I'm trying to upload the new mono src rpm, but it's failing to upload
the tar ball

Checking: mono-2.0.tar.bz2 on
http://cvs.fedoraproject.org/repo/pkgs/upload.cgi
ERROR: could not check remote file status
make: *** [upload] Error 255
ERROR: Uploading the source tarballs failed!

As Tom Lane speculated in his reply, problems with uploading new
tarballs are most likely a certificate issue. We did invalidate all old
certificates (because we were not doing them correctly in the old
system) so you need to have a new user cert and new certs for the upload
and builder CA.


Dennis Gilmore sent out this message which might help you if you haven't
seen it yet:

https://www.redhat.com/archives/fedora-devel-announce/2008-August/msg00008.html

-Toshio

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list