Re: announcing HTTPS pushing to dist-git/src.fedoraproject.org for packagers and non-packagers

[Patrick Uiterwijk]

Hi Simo,

On Mon, 22 Apr 2019 at 20:39, Simo Sorce  wrote:
>
> Any reason why oidc is required instead of a simple GSSAPI (via
> mod_auth_gssapi) ?
> GSSAPI authentication won't require a graphical session to work.

The main reasons for going with OIDS rather than GSSAPI are:

1. User support: we have had a *lot* of contributors that had issues
using GSSAPI for Fedora, often because they have older or
employer-specific krb configurations: a lot of them are for example
missing the "includedir /etc/krb5.conf.d" and the dns_kdc_lookup
options.
One other very common occurrence are the dns_canonicalize_hostname and
rdns options: the Fedora defaults for these options are required for
the Fedora Infra krb5 to work, but a lot of employers set (or even
require) these to be set to "true". Fedora Infra is unable to work
with these options set to true, because we have a lot of nodes for
which we do not control recursive DNS, in addition to the fact that we
have the exact same set of entry points for all services, which means
reverse DNS is useless.

2. With the upcoming account system change (to be backed by FreeIPA)
our plan is to start requiring 2 factor auth for some groups
(primarily the system administrators, it'll be opt-in for other
users), and then we want to be able to enforce using the same 2fa
tokens for any access.
The 2FA scheme that we are solely planning to support is U2F/FIDO2,
and to the best of my knowledge there has so far not been any work on
integrating this with any krb5 server.
The current plan is to integrate the 2FA flow into the identity
provider, and have it enforce and check the tokens. Using OpenID
Connect for this login would mean that we get the 2fa enforcement "for
free".

Also, please note that there are concrete plans to lift the
requirement for a graphical session for OpenID Connect tokens, but
that would be part of the same authentication work.

Patrick
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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

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

[Patrick Uiterwijk]

>
>
> This does not affect traditional RPM/SRPM packages, right?

Correct, this only impacts modules.

>
> Thanks,
> -Mat
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

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

[Patrick Uiterwijk]

Hi all,

If you maintain any application in Fedora Infra (or outside) that
tries to parse things out of RPM names, you might be interested in
this.

For those wondering where I've been spending most of my time the last
few weeks: I've been deep in the internals of Bodhi fixing all kinds
of issues I've found between it and Modularity (turns out enabling
composing was just the beginning).

At some point, I was informed that for modules, they are throwing all
kinds of old assumptions out of the door.
One of those is the good old Name-Version-Release in RPM land.

Modules do not have an NVR, they have an NSVC: Name, Stream, Version, Context.
Name is the name of the module ("nodejs").
Stream is a stream, like "6", "7" or "8", these are crucial for the
parallel availability that modules are trying to accomplish.
Version is a date/time stamp, used to indicate new versions in the
same name-stream.
Context is a hash of some information in the built module that makes
it so that the nodejs-6-20170314 built for Fedora 28 has a different
identifier than the one built for Fedora 29.

There are some additional fields for installed things (arch and
profile), but those aren't really important for things trying to
parse/show module names I think.

One of the interesting things they wanted to also allow: dashes in streams.
As a consequence, when you get an N-S-V.C as modules are represented
in Koji builds, doing a .rsplit('-', 2) will not give you Name,
Stream, Version.Context per se.
You could totally have a module called
nodejs-my-stream-5-20170314.abcd, with name=nodejs,
stream=my-stream-5, version=20170314, context=abcd.
There is no way for you to independently figure out what the NSVC
components are, you will need to ask Koji, and use its name, version
and release fields (with name=name, version=stream,
release=version(.context)).

Also as a consequence, modules should not be dash-separated in
anything the users see.
For user consumption, they are Name:Stream:Version:Context, so you may
need to manually convert between one representation and the other if
you need to look up in koji or other systems versus display to users.

Also, note that if you are touching older modules in Koji (e.g.
because you go through all koji builds), modules before February 19th
will be lacking the Context field.
However, I've been told that those modules will not be used, so unless
you or your app goes spelunking in koji (for fun and profit), you
should never see those.

I hope that this is useful information for anyone else finding
themselves having to parse NVRs/NSVs.

Regards,
Patrick


p.s.: This is a forward of my email sent originally to the Infra list.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

2017-07-18 s390x build failures fixed

[Patrick Uiterwijk]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi all,

This is a quick email to let you know that we have isolated a pretty bad bug in 
the buildroot for s390x.
At Mon, 17 July 2017 17:13 UTC, binutils-2.28-11.fc27[1] was tagged into 
rawhide, which generated incorrect binaries for s390x.
Some of you might have noticed this because your build failed due to incorrect 
binary, but a lot of builds failed earlier in the process.
A new RPM build had gotten caught up with the incorrect binutils[2], which 
caused all builds after it to fail (for fun: a lot of the RPM tests failed 
during this build, but it seems the tests there don't actually make the build 
fail[3]).

After we untagged the broken binutils build, s390x binaries should have 
recovered.
We also untagge the broken RPM build to recover that part of the buildroot.
Anyone that made any builds during this time should resubmit them, note that 
just the fact that your build succeeded doesn't mean it works as intended (as 
with the RPM build).

We did file a bug against binutils[4].

Regards,
Patrick


[1]: https://koji.fedoraproject.org/koji/buildinfo?buildID=919634
[2]: https://koji.fedoraproject.org/koji/buildinfo?buildID=920080
[3]: 
https://kojipkgs.fedoraproject.org//packages/rpm/4.13.0.1/32.fc27/data/logs/s390x/build.log
  (search for Bastic Tests)
[4]: https://bugzilla.redhat.com/show_bug.cgi?id=1472486
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJZbo69AAoJEIZXmA2atR5QEikP+wWwgcJSAJrigzZQdNICFY80
Tw2QvVP+AQSdpppReSUf3PnXofiTKLpArd5Fv3Ck11DJLz1fEA4ABF+HRHZ4GmsM
Doxye1uK4+2O6QtHZEirCWUjKVHCBBMkAqyEpVKXQSML7n8+Gnw7Pr+ArtPFxgmY
Z6mX61EIwl1wO7bQ2Mi1IUHfZc1CBlvueWyB3OEYQViIEKB9RNdPvT1dDhkGXPYr
Rx65RXp9hhGnyhrNwTNNg8ckGUy6xsjaGUL/HAYCepisQU3kYj9Og4IHrkKn8d9g
1aqJhpckNSIJFLwZmHYNDuI6Z57ijpsne/sZc/G5c00+/Jp71IYfV0JiZ8IO82EU
wcOo0DD3fPLo81gDEUGx1P0EXRxsduS+o5jbZTPS0yTF1K2LWtTAlAui9jr3FvNU
zglNnAf2vixSnHj1gVnHtyxIqUajvZzAgaIMXBfBmo4RT82FkP0JCARMDdsw8d3A
idelhFd9RYgNo26lDaze36T4I+jtcN5sJKlHrgzWIN7aRQZoiSxQPSKRk4tdquHO
d+sVQIlnDN4qpWH+tMdHYGmXD8ZBOj+HEDPOC3WImCBR1UzobNVjKbi23edNF3Eb
h9RcxhS6ON1YZ1pwHzAqV3BOC/MdfXcWBCPGVCMUpogMutN3rjI9BzPSE61mX/p3
BJqKg/ydj2+GoTeAs498
=Ac63
-END PGP SIGNATURE-
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Fedora packager environment in a docker container

[Patrick Uiterwijk]

Hi,

On Mon, Apr 24, 2017 at 12:29 PM, Michal Minar  wrote:

> Did anyone successfully set up his fedora packaging environment in a
> docker container?
>
I didn't get past `kinit mimi...@fedoraproject.org` in a container. It
> gives me:
>
> Invalid UID in persistent keyring name while getting default ccache
>

This is caused because Docker installs a default seccomp policy that denies
access to the Kernel keyring because this is not namespaced.
You can work around this by "export KRB5CCNAME=/tmp/ticket".

Alternatively, you can allow the container access to your host keyring.
For this, you can start with my policy:
https://github.com/puiterwijk/development-environments/blob/master/docker/koji/policy.json
.
This is based on Docker 1.13.
For the 1.12 and earlier version, grab:
https://github.com/puiterwijk/development-environments/blob/ed497fbbd56432eca1b27ce41903ed2c33aaa051/docker/koji/policy.json
.

Then on the docker run command, add: --security-opt
seccomp=$HOME/Documents/Development/Environments/docker/koji/policy.json

Do note that if you want to do kinit, you will want to add the add_key call
as well (I just do kinit on my workstation, and use the seccomp policy to
allow my koji container access to it).


>
> I'd be very glad for any suggestion or advice. Until then, I'll stick with
> a VM.
>
> Regards,
> --
>
> MICHAL MINÁŘ
>
> SOFTWARE ENGINEER
>
> Red Hat Czech, s.r.o. 
>
> mimi...@redhat.com
>
>
Regards,
Patrick
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Test instances for Fedora Package Maintainers

[Patrick Uiterwijk]

> ppc64-test.fedorainfracloud.org f25 x86_64 cloud instance
>
> Is it emulated? Or is the "arch" column copy/paste error?

That was a copy-paste error.
These machines are virtual instances on hardware PPC64/PPC64LE machines.

>
>
> Vít
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: SSL: CERTIFICATE_VERIFY_FAILED

[Patrick Uiterwijk]

Hi,

On Fri, Dec 23, 2016 at 4:07 PM, gil  wrote:
>
> this mean remove entirely folder or only config* files?

Either way works. The important part is that ~/.koji/config doesn't
exist, since that
overrides /etc/koji.conf. Whether you remove the directory itself is up to you.

>
> $ cd ~/.koji/
> .koji]$ ls
> config  config.old
>>

Regards,
Patrick
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: SSL: CERTIFICATE_VERIFY_FAILED

[Patrick Uiterwijk]

Hi,

>>> $ koji build --scratch --arch-override x86_64 rawhide
>>> /home/gil/springframework/springframework-3.2.18-1.fc26.src.rpm
>>> SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed
>>> (_ssl.c:590)

This message indicates that you have an outdated koji config file.
Do you have koji 1.11.0?
If you do, you most likely have a /etc/koji.conf.rpmnew, please try
moving that to /etc/koji.conf.

If not, can you please email back your koji.conf?

Regards,
Patrick
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Planned Outage: fedorainfracloud.org / copr - 2016-04-08 02:00 UTC

[Patrick Uiterwijk]

Planned Outage: fedorainfracloud.org / copr - 2016-04-08 02:00 UTC

There will be an outage starting at 2016-04-08 02:00 UTC, which will
last approximately 6 hours.

To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run:

date -d '2016-04-08 02:00 UTC'

Reason for outage:

We will be updating our OpenStack? cloud, which will require all cloud
instances to be rebooted.

Affected Services:

fedorainfracloud.org copr.fedoraproject.org fedoramagazine.org
taiga.fedorainfracloud.org testdays.fedorainfracloud.org
jenkins.fedorainfracloud.org

various development instances

Contact Information:

Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/5215

Please join #fedora-admin or #fedora-noc on irc.freenode.net or add
comments to the ticket for this outage above.
___
devel-announce mailing list
devel-annou...@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel-annou...@lists.fedoraproject.org
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Planned Outage: fedorainfracloud.org / copr - 2016-01-12 17:00 UTC

[Patrick Uiterwijk]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Planned Outage: fedorainfracloud.org / copr - 2016-01-12 17:00 UTC

There will be an outage starting at 2016-01-12 17:00 UTC, which will last 
approximately 2 hours.

To convert UTC to your local time, take a look at 
http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run:

date -d '2016-01-12 17:00 UTC'

Reason for outage:

We will be adding more resources to our compute nodes, requiring the instances 
on those nodes to be turned off during maintenance on the specific node.

Affected Services:

fedorainfracloud.org copr.fedoraproject.org fedoramagazine.org 
taiga.fedorainfracloud.org testdays.fedorainfracloud.org 
jenkins.fedorainfracloud.org

various development instances

Contact Information:

Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/5056

Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to 
the ticket for this outage above.


- -- 
With kind regards,
Patrick Uiterwijk
Fedora Infra
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWkEznAAoJEIZXmA2atR5QIAYQAJvixAJ9laovKCDkFSQqKfr7
7z1ckYDOGEVoAz8rnUqlQI+5hB6nBqc1OjPfJy4vKNrLQe1gOGrKm0EHNhKJxtN3
zYu5YSQnNQRNQMOG3xhc2I2xZaLFdjB3sgXebMRFByEEGgBviPzo2f8YhVS9wZS5
XG5p7km+O6jlKmdtgHXoD1VYJeS/Y8tHOBU5Lc5ImL6FmhAwuOWAfk7cfdQI69bg
QsYCSd2JnzMSUV5etSqW0NqAAgFL3ImnjR5VWzuyM0qhFt2DLILfMdLAHW4wv5cK
cM8xzZ8BSVJwkztMwT1IW+achL7hOTFpSxnc38Xg5Ct9nO2gmRxQmq3Yktv6olBq
pEshIYWToNNLhHg/OQCgXM3IB4vbiqh+I/AVK6gAFAroUkraTWpV2Gx5fe1AfLxX
5wBIwarCZx5MrkNlkw4uwaDmtlCG4nz/BYuF1qnsNSRENv1Scy74hehSHSGohbUR
4Z8/fUW7lKlX7iYbJEsgpcjx+MBH1aMhLM/X6LdQl3/l3GLwsuhfydDspH7nS/cy
x3uOf6T4qRJPdCaooPsm4qzvfNg21jv7t6b0y7ohdZbchuyQLMLkBc03mteoWLA1
q2865vxdCMdFlba/L73rygkjcuB7N1ZadxDc94Q4yqf1Yi3INMf6JWCSll1sbBMr
5xKUp45B23nIAbmNveLX
=GbfW
-END PGP SIGNATURE-
___
devel-announce mailing list
devel-announce@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel-announce@lists.fedoraproject.org

Planned Outage: fedorainfracloud.org / copr - 2016-01-12 17:00 UTC

[Patrick Uiterwijk]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Planned Outage: fedorainfracloud.org / copr - 2016-01-12 17:00 UTC

There will be an outage starting at 2016-01-12 17:00 UTC, which will last 
approximately 2 hours.

To convert UTC to your local time, take a look at 
http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run:

date -d '2016-01-12 17:00 UTC'

Reason for outage:

We will be adding more resources to our compute nodes, requiring the instances 
on those nodes to be turned off during maintenance on the specific node.

Affected Services:

fedorainfracloud.org copr.fedoraproject.org fedoramagazine.org 
taiga.fedorainfracloud.org testdays.fedorainfracloud.org 
jenkins.fedorainfracloud.org

various development instances

Contact Information:

Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/5056

Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to 
the ticket for this outage above.


- -- 
With kind regards,
Patrick Uiterwijk
Fedora Infra
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWkEznAAoJEIZXmA2atR5QIAYQAJvixAJ9laovKCDkFSQqKfr7
7z1ckYDOGEVoAz8rnUqlQI+5hB6nBqc1OjPfJy4vKNrLQe1gOGrKm0EHNhKJxtN3
zYu5YSQnNQRNQMOG3xhc2I2xZaLFdjB3sgXebMRFByEEGgBviPzo2f8YhVS9wZS5
XG5p7km+O6jlKmdtgHXoD1VYJeS/Y8tHOBU5Lc5ImL6FmhAwuOWAfk7cfdQI69bg
QsYCSd2JnzMSUV5etSqW0NqAAgFL3ImnjR5VWzuyM0qhFt2DLILfMdLAHW4wv5cK
cM8xzZ8BSVJwkztMwT1IW+achL7hOTFpSxnc38Xg5Ct9nO2gmRxQmq3Yktv6olBq
pEshIYWToNNLhHg/OQCgXM3IB4vbiqh+I/AVK6gAFAroUkraTWpV2Gx5fe1AfLxX
5wBIwarCZx5MrkNlkw4uwaDmtlCG4nz/BYuF1qnsNSRENv1Scy74hehSHSGohbUR
4Z8/fUW7lKlX7iYbJEsgpcjx+MBH1aMhLM/X6LdQl3/l3GLwsuhfydDspH7nS/cy
x3uOf6T4qRJPdCaooPsm4qzvfNg21jv7t6b0y7ohdZbchuyQLMLkBc03mteoWLA1
q2865vxdCMdFlba/L73rygkjcuB7N1ZadxDc94Q4yqf1Yi3INMf6JWCSll1sbBMr
5xKUp45B23nIAbmNveLX
=GbfW
-END PGP SIGNATURE-
___
devel-announce mailing list
devel-annou...@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel-annou...@lists.fedoraproject.org
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Planned Outage: fedorainfracloud.org / copr - 2016-01-12 02:00 UTC

[Patrick Uiterwijk]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Planned Outage: fedorainfracloud.org / copr - 2016-01-12 02:00 UTC

There will be an outage starting at 2016-01-12 02:00 UTC, which will last 
approximately 4 hours.

To convert UTC to your local time, take a look at 
http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run:

date -d '2016-01-12 02:00 UTC'

Reason for outage:

We will be upgrading our OpenStack? cloud, which will require all cloud 
instances to be rebooted.

Affected Services:

fedorainfracloud.org copr.fedoraproject.org fedoramagazine.org 
taiga.fedorainfracloud.org testdays.fedorainfracloud.org 
jenkins.fedorainfracloud.org

various development instances

Contact Information:

Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/5055

Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to 
the ticket for this outage above.

- -- 
With kind regards,
Patrick Uiterwijk
Fedora Infra
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWkEyTAAoJEIZXmA2atR5QbTUP/1x9fMwKa56Z6i3UhWhDjq0S
j7TkXP8qRL3+1zPAEFWTn25QouO3CfJUWv2Tk1VehSVbIJqkqQX+gHS+Ych4AF8I
3rHTG30E1XogQxbaw36oqqLlVMpYgQJMlgLoaAiBJ4v8NcworNvE5lKehiqMGdkO
fmdMul0E/o80jWF0nFJuDNM1jYuYjbexjCjy8bgvNr8Ygqtemr7cYoWNvtY4/6f6
TvaQbqIAPP+troEwONICTxhVlehnIUUCNWUYV2Va8vEiA6h58Z9WxsIzzSeVunX7
iEGJkev5fKIjcJi95hNOw8cGAdDorFeyuOT2ymXUwnbmMIFVXNxfpbLwKveqO4Ve
aIqwYCjUCHcaGvHReTGf+p7GvyQT1Og/LqzyoBBhe51c1JSurp8YN7u2AHlDf/Ih
iWSCLVyiFIrC3OZtPo8V1mHGLv2VsGkHAnsHWe/RJrQACVW7hM/xiTtNmtZC2Q24
l0+eF2bxmowQRw0TbykQiA4ev2Vsn+SIUbpnIxnfvoSUg0ssXw2a0qVIyX1aifo+
FFn7WzlRHuiNIBrLE/KLy0lXktqvUjhS/dH7tLDo1g9gIzUFxuAMXPVAj3KvCpG9
IEomG3MBXoV7dUVtBR4VkF5LNOyp/yl3qnGMoP7B5Z9aOUJG3KLnLE093JsSqFWk
E7RK0Lk/Zb4zrENS/DOW
=/rmh
-END PGP SIGNATURE-
___
devel-announce mailing list
devel-annou...@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel-annou...@lists.fedoraproject.org
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Emergency Planned Outage: lists.fedorahosted.org - 2015-12-23 07:30 UTC

[Patrick Uiterwijk]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Planned Outage: hardware maintenance lists.fedorahosted.org - 2015-12-23 07:30 
UTC

There will be an outage starting at 2015-12-23 07:30 UTC, which will last 
approximately 1 hours.

To convert UTC to your local time, take a look at 
http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run:

date -d '2015-12-23 07:30'

Reason for outage: Emergency hardware checks and maintenance

Affected Services:

lists.fedorahosted.org - Web URL and mailing lists. Email will be queued for 
delivery after maintenance finishes.

Services not listed are not affected by this outage.

Contact Information:

Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/5043

Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to 
the ticket for this outage above.

- -- 
With kind regards,
Patrick Uiterwijk
Fedora Infra
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWekuBAAoJEIZXmA2atR5QnuAQAKgj+mFB/8OVLeCs7lpdKZYf
l02okVkqoBI30wrR7+DBCBNytm9E4cxkuxM+dCXBWyHy1VjrnavTH4Rj2/iMq4pe
Eod0tF5itEL9fLRxf/byf2XVZbnIJyRgxJ4TFcW5+e3n/aSn39mqWtjteqYlUb++
w3LEPjb4oXct9RyU3LL7hDi1U8lDQ7O/GWrnkdATjhmuEjqpNx+oijeKSKaIIIn8
gBsMgK9pBVVRjMdN4Oc2Bb6EjlPJh1SvAjbokr31bQj/B7zFH+6bZWEJfGsvP1SK
nQES3ZgezQCpKha3MLDLBbdcJrMBNyAbCFSLSw2ZelaJZnEjLPgg+ScjPNpKKH06
DbedeCjJ7cKMalaA90oujQDhjoe/idBGvT5HIegphR6vGxYC2xVUF9iTdhzH4ZiA
GEW3gUu9LftDWL48FGbzw2t17+zgqDjIxOyLzuJgaVyuS07NWJgjqe/5mit1Oiyc
/m/KK15XILWb8kvGq6t3r4NeCcOr9heHhEmTbFkoFbYLPTs36OdHy0Rz3VVmJywN
ZYUOD1xX8Fa9VSsuyWMwGQAivoGJhxjBYVL5hA3JcdeqUNAFT1uT/yBQR68Z4PMO
axSJBWsUuTcENcussjQ58195tP5YE+SXtKkIU0yke65L1rbvZtHvFGjSYso9eFPh
apGIuIq4xCNna30Nd+HP
=f+St
-END PGP SIGNATURE-
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

COPR service announcement: builds failed last night

[Patrick Uiterwijk]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi all,

Due to issues with the metalink for f22 and f23 updates on ppc64 last night,
a lot of COPR tasks have failed their ppc64le chroot builds.
If you see that the x86_64 builds of of your task have succeeded, but the
ppc64le builds failed, please resubmit you job to COPR.

End of service announcement.

With kind regards,
Patrick Uiterwijk
Fedora Infra
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWQV7NAAoJEIZXmA2atR5QXY0QAK8i8kjYCvsNUNbqE1A3/Slr
Jw0I+x4C9bzmTwUrRojCsknOQV1+Ym/8M4zyCJ+vwwaPxOe+/yVynK5geA/pCgq+
WJAzxco2Uad9B1/ETMF7224bwPsIvZsbGQiQPklPWi7rB6wXmJd7GNKyUpvhPiwR
HPhgW6RjZ5Y0kA0Aeo7okFCxigdenpRDMHppOJlsvl/JFe2gQAZ4kylTKN9aJE60
8x/vVDb4dSyTu1/0DixLyn+O282el7UJo4hzyLocyHcpWlmeBQ5RHcdx2H3PrV1i
P5LG8r6PqCmM6AXPGGxK0WCEuYZyXsR8FfuvuHOwBdRnPwhDPmi9N+7rKa5PPAce
1bLcqgJunzCX00oNYfzd2sBURapHthByIY3ldtcZe+XfC420QDr2R3vFh/rpHcVa
Jdw6SQXzeRX8cCumDz+PtabXEp67aAPSy7Skxynz4z//tq1zWm0Z3OUDKBPlRd/u
iKdEZ7DYhniC5oQfkE4mLjxCc23epkgXsH973Vkod5s7V1I8OMSqCOPMamrRCwsn
Onuip/V0xWeQuvzZGWIL38iqR2EJs1FD1yeHr5/10ydM0ynYiXCBjQxJv5c31JCn
c9B1Cqso2x7U2WIuk2NODv9vpKvAXzYmzfsyRCDXzzo21cMaMR9eRFPyDIAweIfz
r2k8uClm5snsV9/1lSXn
=cu1n
-END PGP SIGNATURE-
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

COPR infrastructure issues caused build failures

[Patrick Uiterwijk]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi everyone,

Throughout the day of October 31st, 2015there have been multiple build failures 
in COPR
because of problems with the COPR infrastructure.
If your build failed with only a mockchain.log.gz file which contains the 
following line:
"Failed to obtain srpm from dist-git", or something alike that, that was caused 
by this
infrastructure issue.

We have just found and fixed the root cause of this problem, so any builds from 
now on
should be successful.
If you have any builds that failed and only produces a mockchain.log.gz, please 
resubmit
your build and it should go through correctly.

If you have any build failures where you are unsure whether they're caused by 
this issue,
or have any other questions, feel free to email me or come by on IRC 
(#fedora-buildsys).

With kind regads,
Patrick Uiterwijk
Fedora Infra
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWNWelAAoJEIZXmA2atR5Q6q0P/jDaMtcMbudD5TNCGuSbjkCk
GKb5E0ax1Oux/HKqxyWrOknlc7aXWcc5AB3SWQUUk3ByhEnwfJIkYb+rr98fNxYL
AM83cTrVaOEiQ6nouXrQdoorEpwo4v9/jC1mwhyGyq7IGytYeIzW9XkOBIvtI3pg
ramiezOjQRWMDGswVuqGYwiF94+GaDv8sCS/OUQsCQ+6XVcyw8QnEiUcZRDM2Xun
FEGWKUGb12UdCw32iCPptlXvC9npuWZyFMwPyaHHnqGhYjpFrvnUClaGh5LmwqiY
PQPnAbKwrLYelGKDGVv9qpJg2LdjuCAplajDiEnu6GM5z+V3xYhoq5pVfAAOqao3
DyHBKh0sSC+rRB1pdGaDNsMBcTFDy9QN+NDKmEPJzg13LaOxtx8SKfmzpfTDLba/
9oMSPOWSPv3dMm2dlYDwOIJY6bcjFYcWTLMfy4kyE7E5Kfwb20bVr+LLXFT+TvE5
z1ELeu/IiYYk4seGNrMKQx0PgpZRhe13pfpburO1IQDvfWn7dPzJRG+7hzGOOUPG
SEDEsHejWHO5eVJGpbWokmIdojNzzXfcSB8yoOWy8CWMXg6Sjowt5ex136RdW1QG
VLDqMGNUE5qGJx+qslJcgl1AjUIkLyuNQeK6PtTMTPEqoqUajD+ZctbqnZUZpc0P
Al11cfVxLFPM0bhwu8oi
=YgO+
-END PGP SIGNATURE-
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Google Code and Gitorous shutting down: update upstream URLs please

[Patrick Uiterwijk]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

As you might have heard, Google Code and Gitorious are both going to be 
closed: Google Code on January 25th, 2016[1] and Gitorious on May 2015[2].

We have some packages in Fedora that use either of those as homepage.
To give an overview of these packages, I ran a script to gather information
from anitya and pkgdb.

The output, in the form of packagename: homepage, is printed below this.
If any of your packages are in this list, please check upstream what their
new homepage will be.

When you find the new upstream URL, please update the spec file in distgit
and anitya with the new URL.

The script used to generate this information is available at [3].

With kind regards,
Patrick Uiterwijk



[1]: http://google-opensource.blogspot.nl/2015/03/farewell-to-google-code.html
[2]: https://about.gitlab.com/2015/03/03/gitlab-acquires-gitorious/
[3]: https://puiterwijk.fedorapeople.org/gcode-gitourous-finder.sh


=== Package list ===
abootimg: https//gitorious.org/ac100/abootimg
amora: http//code.google.com/p/amora
apanov-edrip-fonts: http//code.google.com/p/edrip/
apiviz: http//code.google.com/p/apiviz/
arduino: http//code.google.com/p/arduino
argyllcms: http//gitorious.org/hargyllcms
arora: http//code.google.com/p/arora/
atf: http//code.google.com/p/kyua/wiki/ATF
atinject: http//code.google.com/p/atinject/
augeas-vala: http//www.gitorious.org/valastuff/augeas-vala/
autokey: http//code.google.com/p/autokey
backup-light: http//code.google.com/p/backup-light/
ballz: http//code.google.com/p/db-tins07/
baloo-kcmadv: https//gitorious.org/baloo-kcmadv
batti: http//code.google.com/p/batti-gtk
BEDTools: http//code.google.com/p/bedtools/
bionetgen: https//code.google.com/p/bionetgen/
bluecove: http//code.google.com/p/bluecove/
bmpanel2: http//code.google.com/p/bmpanel2/
boilerpipe: http//code.google.com/p/boilerpipe/
bonesi: https//code.google.com/p/bonesi/
brise: http//code.google.com/p/rimeime/
bunny: http//code.google.com/p/bunny-the-fuzzer/
cagraph: https//code.google.com/p/cagraph/
cantata: http//code.google.com/p/cantata/
cardpeek: http//code.google.com/p/cardpeek/
cave9: http//code.google.com/p/cave9
cellwriter: http//code.google.com/p/cellwriter/
chipmunk: http//code.google.com/p/chipmunk-physics/
chm2pdf: http//code.google.com/p/chm2pdf/
chmsee: http//code.google.com/p/chmsee
clementine: http//code.google.com/p/clementine-player
cli-parser: http//code.google.com/p/cli-parser/
clusterpy: http//code.google.com/p/clusterpy
code-editor: http//qt.gitorious.org/~ilyesgouta/qt-creator/code-editor
concurrentlinkedhashmap-lru: http//code.google.com/p/concurrentlinkedhashmap/
contextkit: http//gitorious.org/maemo-af/contextkit
cookcc: http//code.google.com/p/cookcc/
ctemplate: http//code.google.com/p/ctemplate
curlpp: http//code.google.com/p/curlpp
dataparksearch: http//code.google.com/p/dataparksearch
dbus-tools: http//code.google.com/p/dbus-tools/
decentxml: http//code.google.com/p/decentxml
deltarpm: http//gitorious.org/deltarpm/deltarpm
dircproxy: http//code.google.com/p/dircproxy/
dissy: http//code.google.com/p/dissy
django-dpaste: http//code.google.com/p/django-paste/
django-mako: http//code.google.com/p/django-mako/
django-mptt: http//code.google.com/p/django-mptt/
django-recaptcha: https//code.google.com/p/recaptcha-django/
django-simple-captcha: http//code.google.com/p/django-simple-captcha/
django-tagging: http//code.google.com/p/django-tagging/
dnsmap: http//code.google.com/p/dnsmap/
dot2tex: http//code.google.com/p/dot2tex
double-conversion: http//code.google.com/p/double-conversion
elfinfo: http//code.google.com/p/elfinfo/
ell: http//code.google.com/p/ell/
emacs-irsim-mode: http//code.google.com/p/irsim-mode/
emacspeak: http//code.google.com/p/emacspeak
epris: http//code.google.com/p/epris/
eqntott: http//code.google.com/p/eqntott
erlang-log4erl: http//code.google.com/p/log4erl/
espresso-ab: http//code.google.com/p/eqntott
esteid-browser-plugin: http//code.google.com/p/esteid/
faience-icon-theme: https//code.google.com/p/faience-theme
fbterm: http//code.google.com/p/fbterm/
fcitx-fbterm: http//code.google.com/p/fcitx/
fcitx-kkc: http//code.google.com/p/fcitx/
fcitx-skk: http//code.google.com/p/fcitx/
fcitx-ui-light: http//code.google.com/p/fcitx/
fdupes: https//code.google.com/p/fdupes/
FlightCrew: http//code.google.com/p/flightcrew/
flow-tools: http//code.google.com/p/flow-tools/
flyingsaucer: http//code.google.com/p/flying-saucer/
font-manager: http//code.google.com/p/font-manager
forbidden-apis: http//code.google.com/p/forbidden-apis/
fpdns: http//code.google.com/p/fpdns/
freemedforms: http//code.google.com/p/freemedforms
fspy: https//code.google.com/p/fspy
ftop: http//code.google.com/p/ftop/
fuse-zip: http//code.google.com/p/fuse-zip/
fvkbd: http//gitorious.org/fvkbd/pages/Home
game-music-emu: http//code.google.com/p/game-music-emu
gdata-python-client: http//code.google.com/p/gdata-python-client
gdata-sharp: http//code.google.com/p

Re: New Fedora openid provider (fas-openid) in service

[Patrick Uiterwijk]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

This should now be fixed in production as well.
If you see the same bug, please notify me.

Patrick
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.13 (GNU/Linux)

iQIcBAEBCgAGBQJRgr8YAAoJEIZXmA2atR5Q6sIQAIFBBDDFAD74g1lMJcW9g+3y
43dzhcvlnn+4xXcimWlUOHO2oasP5vU6S4UqFUgoLbn3VUP2yCCnmeUDGbp0dTB6
O0CbFRBOk0tUEKUSppYfcII7yhLiMKCFK6y/Vxh9g6QqEbYR5XdSgI7E2LvfrAy8
cYjOB2CVeBQeAPkTt2HKSmrryI7czny9IrVHxtc4f3xaheQ4ZcOgcbKdEScDDM0U
mux3lN+krflN5vJRE9xTeHwKNbVXkrq4EPvIXxx7yP0Rpx26XSSG/qqP73dBWrfj
b8fxYYDysQ39yEaTmHRnO9oxkjWUA6yeAN7sT3o2cZnMowpy3uTmit71NH7U/4SW
uRydQCRx8rltM3KdSt/ra9nsZCdfLo0YWIA3OVxelk8Y82y4t3EiOdAOj8TQXKY2
Sb/DR8vv8Rhk+LlbJwXUAzkf8+1ty8P2hpn2o5IeJlso9cTvmEGla/8Enz/rEF0e
KXFdoqGm2ekWVY9gZvGhjUHKjfY7DroOeoCETi2S11H9Dyw/HxczyOCocNOU56j7
8N+aoS4+BEwoLlRV0ijnFaZKuOIgkbxuRc0dMeDDaFNK1GHuIt5Z9OjKDmBdaVC2
Z7Ze/Wr72sb4D+rMz5Yc4GSBAdwDrORtyzcemCrnRrbnWsNLIhKPiRp2OCqUyf8O
slFN5V0UpELAlELmmptG
=4/vQ
-END PGP SIGNATURE-
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Fwd: Re: Packages in need of new maintainers

[Patrick Uiterwijk]

Hello,

I would like to take over NetworkManager-pptp.

Patrick
On Oct 4, 2012 6:01 AM, gil punto...@libero.it wrote:

 hi
 i take (made a request to become a co-maintainer)
 these lkundrak's packages:

 java_cup
 jazzy
 mercury
 microba
 patricia-trie

 if there aren't requests from other people. I'll take ownership

 thanks
 regards




 --
 devel mailing list
 devel@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/devel

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Does anyone know how to contact Axel Thimm (ath...@atrpms.net)

[Patrick Uiterwijk]

Hello,

Currently I am following the non-responsive maintainer policy[1], and
have submitted a bugzilla bug for athimm two weeks back, with no
response until now[2].
So hereby I ask if anyone on this list knows how to contact him, or if
Axel himself could respond?

With kind regards,
Patrick Uiterwijk


[1]: http://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers
[2]: https://bugzilla.redhat.com/show_bug.cgi?id=850937
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Packaging software compatible with only one Fedora release

[Patrick Uiterwijk]

Hello M.M.,

As soon as you request the git repo, you will automatically get the
devel (F19) branch.
You could do two things:
1. Just make no builds for any other branches, then it won't get in there.
2. Request rel-eng to block the package for the devel branch.

With kind regards,
Patrick
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Packaging software compatible with only one Fedora release

[Patrick Uiterwijk]

Dear M.M.,

1. You can untag them (koji untag-pkg) if the builds where made this
day. If not, you'll need to get it blocked. For the f16/f18 branches,
you can also just make sure not to add it to Bodhi, but I would
suggest untagging them anyway.
2. Yes, they can block package for specific branches, and thus can
block it for any branch except one. But if you do this, I would
suggest to explain this in the ticket so they won't accidentally
remove the branch you do want.

Adding the specific version can be useful to prevent someone from
installing it over a koji- or local build of gnome-shell indeed.

Regards,
Patrick
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Packaging software compatible with only one Fedora release

[Patrick Uiterwijk]

Dear M.M.,

Unblocking a blocked branch is just as easy as blocking: just creating a
releng work ticket.

Regards,
Patrick
On Aug 26, 2012 10:37 AM, M.M. hal8...@hotmail.it wrote:

 OK, I've untagged the packages zukini, zukitwo and zukiwi from
 f18-updates-candidate and f19 through koji-untag-pkg -v --all
 f18-updates-candidate/19 zukini/zukitwo/zukiwi (I couldn't untag
 them from f18 since admin privileges are needed for that).
 When a version compatible with i.e. Fedora 18 or 19 is published by
 the developers, will I be allowed to I ask rel-eng to un-block the
 package for the related branch?
 Thank you again.

 2012/8/26 Patrick Uiterwijk puiterw...@gmail.com:
  Dear M.M.,
 
  1. You can untag them (koji untag-pkg) if the builds where made this
  day. If not, you'll need to get it blocked. For the f16/f18 branches,
  you can also just make sure not to add it to Bodhi, but I would
  suggest untagging them anyway.
  2. Yes, they can block package for specific branches, and thus can
  block it for any branch except one. But if you do this, I would
  suggest to explain this in the ticket so they won't accidentally
  remove the branch you do want.
 
  Adding the specific version can be useful to prevent someone from
  installing it over a koji- or local build of gnome-shell indeed.
 
  Regards,
  Patrick
  --
  devel mailing list
  devel@lists.fedoraproject.org
  https://admin.fedoraproject.org/mailman/listinfo/devel
 --
 devel mailing list
 devel@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/devel
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Exchanging reviews.

[Patrick Uiterwijk]

 * https://bugzilla.redhat.com/823105 - erlang-riak_control - Admin UI for Riak
 * https://bugzilla.redhat.com/841766 - erlang-riak_search - Full-text
 search engine based on Riak

I'll review these.
If you could check
* https://bugzilla.redhat.com/show_bug.cgi?id=841418 - prey -
Open-source anti-theft solution
* https://bugzilla.redhat.com/show_bug.cgi?id=839170 - devtodo2 -
Manage a prioritized list of to do items organized by directory
I'd be grateful!

With kind regards,
Patrick
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: [ACTION REQUIRED v3] Retiring packages for F-18

[Patrick Uiterwijk]

On Tue, Jul 24, 2012 at 9:36 PM, Bill Nottingham nott...@redhat.com wrote:
 Package healpix (fails to build)
My patch fixing this has been accepted, and this package is now built correctly.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: [ACTION REQUIRED v4] Retiring packages for F-18

[Patrick Uiterwijk]

 Package Panini (fails to build)
 Package fedora-idm-console (fails to build)
 comaintained by: rmeggins
 Package gdmap (fails to build)
For these packages, I have filed patches to fix them in the bugzilla bugs.

 Package python-batchhttp (orphan)
I have taken over this one.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Review swap needed for rtirq

[Patrick Uiterwijk]

Hey,

I will take this.
Could you take devtodo2 or prey?

Greetings,
Patrick
Op 19 jul. 2012 14:42 schreef Brendan Jones brendan.jones...@gmail.com
het volgende:

 Hi all,

 this package is required for the forthcoming Fedora audio spin. Would be
 great to get this reviewed before the Spin review.

 rtirq - realtime IRQ threading
 https://bugzilla.redhat.com/**show_bug.cgi?id=839527https://bugzilla.redhat.com/show_bug.cgi?id=839527

 regards,

 Brendan
 bsjones

 --
 devel mailing list
 devel@lists.fedoraproject.org
 https://admin.fedoraproject.**org/mailman/listinfo/develhttps://admin.fedoraproject.org/mailman/listinfo/devel
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: koji build help

[Patrick Uiterwijk]

Op 18 jul. 2012 14:53 schreef Raymond Pete rayandkate...@gmail.com het
volgende:

 Hi,

 I have a package which builds fine on my host, as I have my required
rpm's installed. How do I install my dependencies in koji so the package
compiles.
 For example, I need zlib-devel to be installed and lapack-devel


 Cheers,

 Ray

 --
 devel mailing list
 devel@lists.fedoraproject.org

Hello Ray,

You should add them to the Build-Requires line of the spec file.
Then koji (and mock) will download them before building.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: [ACTION REQUIRED v2] Retiring packages for Fedora 18

[Patrick Uiterwijk]

 Anyone interested in

   gnusim8085 -- A graphical simulator for Intel 8085 microprocessor

I would be interested in taking gnusim8085.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Orphaning packages

[Patrick Uiterwijk]

I have taken tcptrack
Op 12 jul. 2012 19:08 schreef Jitesh Shah jitesh.1...@gmail.com het
volgende:

 django-recaptcha
 gnome-rdp
 libdwarf
 tcptrack

 Jitesh
 --
 devel mailing list
 devel@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/devel
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: [ACTION REQUIRED] Retiring packages for Fedora 18

[Patrick Uiterwijk]

On Fri, Jul 6, 2012 at 10:55 PM, Bill Nottingham nott...@redhat.com wrote:
 Package devtodo (orphan)
I will take this package.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: [ACTION REQUIRED] Retiring packages for Fedora 18

[Patrick Uiterwijk]

Hello,

Would it be a possibility for me to pick up one of the orphaned
packages, without being sponsored into the packager group yet?
I do have an accepted package, but the reviewer is now in the process
of getting sponsor status.
Would it be possible for me to already request it, or should I wait to
get sponsored and then apply for the orphaned package?

Thanks in advance,
Patrick Uiterwijk


On Fri, Jul 6, 2012 at 10:55 PM, Bill Nottingham nott...@redhat.com wrote:
 Before we branch for Fedora 18, as is custom, we will block currently
 orphaned packages and packages that have failed to build since Fedora 16.

 The following packages are currently orphaned, or fail to build. If
 you have a need for one of these packages, please pick them up.
 If no one claims any of these packages, they will be blocked before
 we branch for Fedora 18. That is currently scheduled to happen on
 or around August 7th.

 Package Pound (orphan)
 Package ape (fails to build)
 Package asylum (orphan)
 Package cmucl (orphan)
 comaintained by: green
 Package cmucl (orphan)
 comaintained by: green
 Package debmirror (orphan)
 Package devtodo (orphan)
 Package drupal6-video (orphan)
 Package eclipse-m2m-qvtoml (fails to build)
 Package emacs-common-proofgeneral (fails to build)
 Package eruby (orphan)
 Package fbterm (orphan)
 comaintained by: dchen
 Package fdupes (orphan)
 comaintained by: hobbes1069
 Package fillmore-lombard (fails to build)
 comaintained by: salimma
 Package fuse-encfs (orphan)
 Package gant (fails to build)
 Package gpsdrive (orphan)
 Package hardinfo (fails to build)
 Package healpix (fails to build)
 Package hexter-dssi (orphan)
 comaintained by: oget
 Package html401-dtds (orphan)
 comaintained by: gnat
 Package innotop (orphan)
 Package json (orphan)
 Package kadu (fails to build)
 comaintained by: gajownik radekl
 Package libcrystalhd (fails to build)
 comaintained by: kwizart
 Package libhid (fails to build)
 Package libinfinity (orphan)
 Package libqttracker (fails to build)
 comaintained by: jreznik
 Package libsoup22 (orphan)
 Package logback (orphan)
 Package mcabber (orphan)
 comaintained by: mmahut
 Package monkeysphere (orphan)
 Package natus (fails to build)
 Package ncpfs (orphan)
 Package ntfs-config (fails to build)
 Package papyon (orphan)
 comaintained by: itamarjp
 Package perl-Beanstalk-Client (orphan)
 Package perl-CSS-DOM (orphan)
 Package perl-Cache-Memcached (orphan)
 Package perl-Nagios-Plugin-Beanstalk (orphan)
 Package pfqueue (orphan)
 Package pino (fails to build)
 Package python-pywt (fails to build)
 Package qtparted (fails to build)
 Package radeontool (orphan)
 comaintained by: pknirsch
 Package raptor (orphan)
 comaintained by: oget kkofler
 Package selenium-remote-control (fails to build)
 Package sonata (orphan)
 Package svn2cl (orphan)
 Package svnmailer (orphan)
 Package torque (orphan)
 Package upstart (orphan)
 Package vorbisspi (fails to build)
 Package whatsup (orphan)

 List of deps left behind by packages which are orphaned or fail to build:

 Removing: emacs-common-proofgeneral
 coq requires xemacs-proofgeneral = 3.7.1-5.fc15
 coq requires emacs-proofgeneral = 3.7.1-5.fc15
 coq-emacs requires emacs-proofgeneral = 3.7.1-5.fc15
 coq-xemacs requires xemacs-proofgeneral = 3.7.1-5.fc15

 Removing: fbterm
 ibus-fbterm requires fbterm = 1.6-5.fc17

 Removing: fuse-encfs
 cryptkeeper requires fuse-encfs = 1.7.4-6.fc18

 Removing: healpix
 skyviewer requires chealpix-devel = 2.13a-2.fc14
 skyviewer requires libchealpix.so

 Removing: html401-dtds
 w3c-markup-validator-libs requires html401-dtds = 4.01-19991224.12.fc17.1

 Removing: libinfinity
 gedit-collaboration requires libinfinity-0.5.so.0
 gedit-collaboration requires libinfgtk-0.5.so.0
 gedit-collaboration requires libinftextgtk-0.5.so.0
 gedit-collaboration requires libinfinity-devel = 0.5.0-2.fc15
 gedit-collaboration requires libinfinity-gtk-devel = 0.5.0-2.fc15
 gedit-collaboration requires libinftext-0.5.so.0

 Removing: libsoup22
 libopensync-plugin-syncml requires libsoup22-devel = 2.2.105-9.fc15
 libsyncml requires libsoup-2.2.so.8
 libsyncml requires libsoup22-devel = 2.2.105-9.fc15

 Removing: ncpfs
 hydra requires ncpfs-devel = 2.2.6-16.fc17
 hydra requires libncp.so.2.3
 hydra requires libncp.so.2.3(NCPFS.2.2.0.17)
 hydra requires libncp.so.2.3(NCPFS_2.2.0.19)
 hydra requires libncp.so.2.3(NCPFS_2.2.1)
 medusa requires ncpfs-devel = 2.2.6-16.fc17
 medusa requires libncp.so.2.3
 medusa requires libncp.so.2.3(NCPFS.2.2.0.17)
 medusa requires libncp.so.2.3(NCPFS_2.2.0.19)
 medusa requires libncp.so.2.3(NCPFS_2.2.1)

 Removing: papyon
 emesene requires papyon = 0.5.6-3.fc18

 Removing: perl-Cache-Memcached
 perl-CGI-Session-Driver-memcached requires perl(Cache::Memcached) = 1.29

Self introduction

[Patrick Uiterwijk]

Hello,

I would like to introduce myself as a hopefully new packager for Fedora.

My current residence is in the Netherlands, where I'm studying for my
Bachelors degree for Computer Science at the Radboud University
Nijmegen.
I have been running Red Hat Linux since version 9, and am now running Fedora 17.

Currently, I am packaging the compiler for the Clean programming
language, which is designed and implemented by the Radboud University,
for which my package review request has been submitted
(https://bugzilla.redhat.com/show_bug.cgi?id=834069), and I plan on
building and packaging more libraries for Clean.


My GPG Key ID is 9AB51E50.

With kind regards,
Patrick Uiterwijk
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel