The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
requires
libQtCore.so.4, libQtDBus.so.4
diffpdf (maintained by: till)
diffpdf-2.1.3-10.fc26.i686 requires libQtCore.so.4
dnssec-nodes (maintained by: hardaker)
dnssec-nodes-2.1-6.fc26.i686 requires libQtCore.so.4,
libQtNetwork.so.4
dnssec
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
In preparation for the Final Freeze on 2017-06-27 Release
Engineering will retire all packages in Branched with broken dependencies and
all packages depending on these. If you get this e-mail directly this affects
at least one of your packages. Please fix the broken dependency as soon as
possible.
requires scrollkeeper = 0.4
gobby05 (maintained by: till, kevin)
gobby05-0.5.0-8.fc27.src requires rarian-compat = 0.8.1-16.fc26
gparted (maintained by: nonamedotc, deji)
gparted-0.28.1-2.fc27.src requires rarian-compat = 0.8.1-16.fc26
, ignatenkobrain)
gnotime-2.4.1-10.fc26.i686 requires scrollkeeper = 0.4
gnotime-2.4.1-10.fc26.src requires scrollkeeper = 0.4
gobby05 (maintained by: till, kevin)
gobby05-0.5.0-8.fc26.src requires rarian-compat = 0.8.1-16.fc26
gparted (maintained
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If y
On Mon, Jan 11, 2010 at 05:17:20AM -0500, Jens Petersen wrote:
> > I guess I would be fine with it being in @base or something.
>
> Just wondered does it have any implications for mock?
Mock uses the buildsys-build group iirc.
Regards
Till
pgpBpwH1XyXcy.pgp
Description: P
ng URL is this:
http://downloads.sourceforge.net/expat/expat-2.0.1.tar.gz
^
You used the wrong hostname previously. Maybe an admonition should be
added to the SourceURL guidelines to emphasize that there hostname
contains an extra "s".
Regards
Till
pgp7s3Op3Wn5T.pgp
De
e
2009-11-07 with a working patch attached.
The original maintainer is:
Sindre Pedersen Bjørdal aka sindrepb
https://admin.fedoraproject.org/pkgdb/users/packages/sindrepb
Regards
Till
pgpFAhXtSyckq.pgp
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
On Wed, Jan 13, 2010 at 10:51:56AM -0600, Matt Domsch wrote:
> 44 Open Bugs which now build, and can be marked CLOSED RAWHIDE:
Is there any reason to not close them automatically except that it is
not yet coded?
Regards
Till
pgpeTwLtbCO7A.pgp
Description: PGP signature
--
devel mailing l
unless the package is made to build
> in rawhide before that.
This is in a month (2010-02-16).
Regards
Till
pgpSo0whzEIfW.pgp
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On Fri, Jan 15, 2010 at 12:00:50AM -0600, Matt Domsch wrote:
> perl-SVN-Simple-0.27-7.fc11.src.rpm
> https://bugzilla.redhat.com/show_bug.cgi?id=511729
Fixed.
Regards
Till
pgp2qGC6vBFrw.pgp
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
t least easily spot which maintainers owned the packages
before the orphage, so non responsive maintainers can be found easier.
Or tell all maintainers in question and orphan all their packages. But
the current solution seems to be only half-baked.
Regards
Till
pgp50CIpi30sI.pgp
Descript
On Fri, Jan 15, 2010 at 02:06:09PM -0600, Matt Domsch wrote:
> On Fri, Jan 15, 2010 at 09:01:20PM +0100, Till Maas wrote:
> > What about the other packages of these maintainers? E.g. in the
> > recordmydesktop case, there were four bugs open with working patches
> > attache
On Fri, Jan 15, 2010 at 04:05:04PM -0700, Kevin Fenzi wrote:
> On Fri, 15 Jan 2010 22:58:54 +0100
> Till Maas wrote:
> > > perl-SVN-Mirror iburrell (fixed by Till Maas; spot says kill it)
> > > perl-SVN-Simple iburrell
> >
> > There is a minor error: I fi
tained packages earlier and to detect packages
> with non-responsive owners.
There are the probably not working anymore scripts that were used ages
ago for the weekly(?) Fedora package status reports:
http://cvs.fedoraproject.org/viewvc/status-report-scripts/?root=fedora
Regards
Till
pgpHIN
:
#! /usr/bin/python.bar
then /usr/bin/python.bar can be made to either point to /usr/bin/python
or /usr/bin/python3 using alternatives.
Regards
Till
pgpnlSAuovvpd.pgp
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
e created, e.g. these
tickets could have been created for all maintainers still having FTBFS
packages without commenting on their bug reports recently. But there
could also be other conditions that trigger this, which still need to be
implemented.
Regards
Till
pgp8fjBzhp4NE.pgp
Description: PGP s
gzilla regularly and the client certificate to create builds and
upload to the lookaside cache expire every 6 months iirc.
Imho the solution to detect whether a package is still maintained should
support maintainers as much as much is possible and not just be created
in a way that's
ave a clue what really
happened. From past experiences reporting such bugs does not bring a big
benefit. The bugs will rot till the release is EOL and because I don't
know how to reproduce it, I cannot test, whether it is fixed on a newer
release.
But I just found abrt pretty confortable when repoque
On Sat, Jan 16, 2010 at 10:39:50AM -0700, Kevin Fenzi wrote:
> On Sat, 16 Jan 2010 10:39:54 +0100
> Till Maas wrote:
>
> > > Indeed. I don't see much activity from them.
> > > Have you tried sending them an email?
> > > If not, I can.
> >
> &g
On Fri, Jan 15, 2010 at 02:06:09PM -0600, Matt Domsch wrote:
> On Fri, Jan 15, 2010 at 09:01:20PM +0100, Till Maas wrote:
> > On Fri, Jan 15, 2010 at 01:17:28PM -0600, Matt Domsch wrote:
> > > On Fri, Jan 15, 2010 at 12:00:50AM -0600, Matt Domsch wrote:
> > > > T
I am not sure how the ratio is for others, but it does not seem to be
such a got criterion.
Regards
Till
pgpJ3zn66b6aD.pgp
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
tleneck could be the connection to your Fedora mirror.
Regards
Till
pgppfGQIDqV8z.pgp
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
es
it, otherwise he would just drop it. If upstream is dead but the
maintainer fixes bugs, when they are found, I do not see a problem,
either.
Regards
Till
pgprqFWzcPR35.pgp
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
ainer can run to close all
bugs for all of his packages at once, even for the packages he does not
maintain properly. So you will still only track down, whether or not a
packager is still around and not whether he cares about a certain
package.
Regards
Till
pgpUQ1OGz3liF.pgp
Description: PGP signa
emented
to get the information I am interested in.
Also I cannot remember any argument from you that explains why your
solution is superior to the other solutions.
Regards
Till
pgpHW48v52mha.pgp
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedo
On Mon, Jan 18, 2010 at 11:55:13AM -0800, Jesse Keating wrote:
> On Mon, 2010-01-18 at 20:44 +0100, Till Maas wrote:
> >
> > Imho the only real problem from your list is, if a package is
> > unmaintained, because if it is maintained, the maintainer usually uses
> >
Hiyas,
now that F12+ is built for i686, can I expect that all Fedora x83
supported CPUs in F12+ support MMX? I have a package (john) that can
then be made simpler.
Regards
Till
pgpVVgY0nqkQi.pgp
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https
change after a
#agreed command was used (or some other command except the #action
command, that creates a helpful notice in the logs). For the init
process, something like "x of y Fesco members present" and list of
absent members could be used.
Regards
Till
pgpFwJ4rU78cm.pgp
D
l mail (1st paragraph)
again with this in mind, you will understand the reason for the change.
Regards
Till
pgpd7CltO6Ete.pgp
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
would not be writeable, most often using mode 0555.
> What do you think?
Is there a tracker about what else needs to be done to finish this up?
E.g. non-executable interpreted libraries will then still be writable:
/usr/lib/python2.6/site-packages/yum
Regards
Till
pgprFmho8lxgt.pgp
D
l paths
> where content differs.
How can one both get the file "coloring" and add own dependencies with a
script to an rpm? Iirc the internal dependency generator needs to be
disabled to be able to specify a special script to add dependencies.
Regards
Till
pgpSk4vwo99ET.pgp
Descriptio
attempted, only with different intervals than one week.
List of packages:
https://admin.fedoraproject.org/pkgdb/users/packages/pwouters
Regards
Till
pgpCWGXvfAly2.pgp
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo
On Tue, Jan 19, 2010 at 02:42:58PM -0700, Kevin Fenzi wrote:
> On Sun, 17 Jan 2010 20:52:12 +0100
> Till Maas wrote:
>
> > The list of packages you announced that are going to be orphaned and
> > the list of packages that were orphaned are not the same.
> > recor
not for the other branches as the qtiplot case shows.
Regards
Till
pgpepk0ifIc9j.pgp
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On Tue, Jan 19, 2010 at 02:42:17PM -0700, Kevin Fenzi wrote:
> On Sun, 17 Jan 2010 20:48:25 +0100
> Till Maas wrote:
>
> > On Sat, Jan 16, 2010 at 10:39:50AM -0700, Kevin Fenzi wrote:
> > > On Sat, 16 Jan 2010 10:39:54 +0100
> > > Till Maas wrote:
> >
On Wed, Jan 27, 2010 at 10:39:38AM -0700, Kevin Fenzi wrote:
> On Wed, 27 Jan 2010 15:43:40 +0100
> Till Maas wrote:
>
> > On Tue, Jan 19, 2010 at 02:42:58PM -0700, Kevin Fenzi wrote:
> > > On Sun, 17 Jan 2010 20:52:12 +0100
> > > Till Maas wrote:
> &
y for
pdf. And the last time I tried to use it, I gave up due to lack of
documentation.
Regards
Till
pgpAW5jGcZPfD.pgp
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
tainer tracker bug, where he
was pinged once and did not respond:
https://bugzilla.redhat.com/show_bug.cgi?id=516797
Also Kevin Fenzi tried to contact him via e-mail recently, but did not
get a response.
He owns 50 Packages:
https://admin.fedoraproject.org/pkgdb/users/packages/sindrepb?acls=
recommended procedure to claim the other
branches? Is it a ticket to FESCo trac or a CVS Admin procedure request?
Regards
Till
pgpdKj5OViGWB.pgp
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
CC'ing the maintainer: Did you mean to orphan recordmydesktop, sindrepb?
recordmydesktop was orphaned, because of an neglected FTBFS bug. I
started a fast track non responsive maintainer process for sindrepb, I
guess all his packages will be orphaned after next FESCo meeting.
Regards
Till
On Fri, Jan 29, 2010 at 12:07:35AM +0200, Panu Matilainen wrote:
> On Tue, 26 Jan 2010, Till Maas wrote:
>
> > On Tue, Jan 26, 2010 at 12:13:33PM +0200, Panu Matilainen wrote:
> >
> >> %global _use_internal_dependency_generator 0
> >>
> >> The external
certain restrictions /var/spool/{cron,mail,cups,at}.
Regards
Till
pgpKqy5veaWpi.pgp
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
ake a rule.
IIRC this change was not announced, was it?
Regards
Till
pgpCeiwWuoCNJ.pgp
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
also remove the
PackageKit-yum-plugin dependency from PackageKit? The plugin seems not
to be necessary, as it can be disabled in
/etc/yum/pluginconf.d/refresh-packagekit.conf and still the gnome applet
indicates when there are new updates.
Regards
Till
pgpZLmscAeUKc.pgp
Descrip
On Tue, Feb 02, 2010 at 09:47:13AM -0600, Mike McGrath wrote:
> On Tue, 2 Feb 2010, Till Maas wrote:
>
> > On Tue, Feb 02, 2010 at 09:01:25AM -0600, Mike McGrath wrote:
> >
> > > It's not automatically enforcable that's true but we catch you doing it
>
multiple packages are affected, there should be a guideline
to document how something needs to be done to work, e.g. if someone
wants to package a new software that contains fips checksums.
Regards
Till
pgpH0W92gI7Fd.pgp
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.
On Tue, Feb 02, 2010 at 07:59:38PM +, Richard Hughes wrote:
> On 2 February 2010 15:44, Till Maas wrote:
> > While you are fixing PackageKit dependencies, can you also remove the
> > PackageKit-yum-plugin dependency from PackageKit? The plugin seems not
> > to be ne
On Tue, Feb 02, 2010 at 09:30:44PM +0100, Tomas Mraz wrote:
> On Tue, 2010-02-02 at 20:13 +0100, Till Maas wrote:
> > On Tue, Feb 02, 2010 at 10:28:11AM +0100, Tomas Mraz wrote:
> >
> > > I am sorry, but I do not see a real need for special guideline for the
> > >
ch any of the selected filter
criteria. The filter criteria are displayed on the right hand side of
the page.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
d, a upload of a bad tarball and modification of the sources file
might be unnoticed.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On Thu, Aug 05, 2010 at 02:55:05PM -0400, David Malcolm wrote:
> workflow, or merely an RFE I need to file against Bodhi?
The RFE is already there:
https://fedorahosted.org/bodhi/ticket/343
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.
On Thu, Aug 05, 2010 at 01:11:24PM -0600, Kevin Fenzi wrote:
> On Wed, 04 Aug 2010 22:03:14 +0200
> Till Maas wrote:
> > The attack is quite trivial:
> > 1) clone the git pkg Fedora repos
> > 2) commit some nasty change
> > 3) publish the repo on some server
>
On Thu, Aug 05, 2010 at 04:32:36PM -0500, Mike McGrath wrote:
> On Thu, 5 Aug 2010, Till Maas wrote:
> > Yes ssh is secure if used properly. To get the proper known_hosts entry,
> > one has to download https://admin.fedoraproject.org/ssh_known_hosts btw.
> >
>
> We
ra doesn't support that hardware anymore (the minimum is i686 = Pentium
> Pro).
How much faster is a Pentium Pro running at 150 MHz? According to
Wikipedia[0] it is 25-35% faster than the older Pentiums and 1.35 * 150
MHz = 202.50 Mhz, so it might be that both perform very similar.
Regard
On Fri, Aug 06, 2010 at 04:31:00AM -0500, Mike McGrath wrote:
> On Fri, 6 Aug 2010, Till Maas wrote:
>
> > On Thu, Aug 05, 2010 at 04:32:36PM -0500, Mike McGrath wrote:
> > > On Thu, 5 Aug 2010, Till Maas wrote:
> >
> > > > Yes ssh is secure if used proper
On Sat, Aug 07, 2010 at 10:56:49AM +0100, Ilyes Gouta wrote:
> http://fedoraproject.org/wiki/Kernel
>
> So fedpkg is only available in updates-testing. Any direct link?
fedpkg is included in the package fedora-packager and it is already in
the updates repo.
Regards
Till
pgpeEjB7
for all operations that need only read access to the server
repo.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
600992
Imho the bug report should be as informative as the other one you filed
earlier and explain why you want to get the package updated:
https://bugzilla.redhat.com/show_bug.cgi?id=600925
It might even help to get a response...
Also the bug blocks a closed bug, which contradicts the meaning o
erify the autokarma thresholds if it is enabled (Thanks to
>Till Maas)
This is still faulty. Is there a way to get access to a running bodhi
instance that I can patch and test directly? A local instance set up
according to
https://fedorahosted.org/bodhi/wiki/Development
does not allow to
a value and unless it is
implemented differently (or has changed again), you can just use a
stable karma value of 1 and ask someone except the update submitter to
provide the +1 karma and the update can be pushed to stable. This is
imho reasonable even after only a one line change t
On Fri, Aug 13, 2010 at 05:54:30PM +0200, Kevin Kofler wrote:
> Till Maas wrote:
> > Bodhi also allows you to edit the stable karma value and unless it is
> > implemented differently (or has changed again), you can just use a
> > stable karma value of 1 and ask someone except
On Tue, Aug 10, 2010 at 09:07:21AM -0600, Stephen John Smoogen wrote:
> On Sun, Aug 8, 2010 at 14:04, Matt McCutchen wrote:
> > On Thu, 2010-08-05 at 22:23 +0200, Till Maas wrote:
> >> Yes ssh is secure if used properly. To get the proper known_hosts entry,
> >>
1 - 100 of 1153 matches
Mail list logo
