kaging:Guidelines#Exceptions_2
| There is no need to include the following packages or their
| dependencies as BuildRequires because they would occur too often.
Regards
Till
--
devel mailing list
devel
On Mon, Aug 05, 2013 at 04:44:31PM +0100, Peter Oliver wrote:
> Does anyone know if there's way for me to force Koji to build a noarch
> package on ARM??
For testing purposes you can make the SPEC not-noarch, then create a
SRPM and use it for a scratch build.
Regards
Till
--
de
On Mon, Aug 05, 2013 at 08:25:43AM +, Petr Pisar wrote:
> On 2013-08-05, Till Maas wrote:
> > Actually the guidelines say otherwise:
> > https://fedoraproject.org/wiki/Packaging:Guidelines#Exceptions_2
> >| There is no need to include the follow
On Sun, Aug 04, 2013 at 03:05:21PM -0700, T.C. Hollingsworth wrote:
> On Sun, Aug 4, 2013 at 1:44 AM, Till Maas wrote:
> > The guideline should be to ask upstream to fix the meta data. In case of
> > missing license text (e.g. source code with a GPL header but no copy of
> >
it is unclear
> when, and also unclear if it will make it into EPEL. Luckily handling
Why is it so hard to just backport this change? And if it needs to be
decided why does FESCO not just do it? Or who needs to decide it?
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin
The following packages are orphaned and will be retired when Fedora 20
is branched, unless someone adopts them. If you know for sure that the
package should be retired, please do so already to add a proper reason
to the SCM:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Acc
On Wed, Aug 07, 2013 at 01:04:03PM +0200, Michael Schwendt wrote:
> On Tue, 6 Aug 2013 23:27:42 +0200, Till Maas wrote:
>
> > Package gnome-vfs2 (orphan)
>
> > List of deps left behind by packages which are orphaned or fail to build:
>
> Without examining the script,
On Tue, Aug 06, 2013 at 11:27:42PM +0200, Till Maas wrote:
> The following packages are orphaned and will be retired when Fedora 20
> is branched, unless someone adopts them. If you know for sure that the
> package should be retired, please do so already to add a proper reason
>
On Wed, Aug 07, 2013 at 10:39:53AM -0600, Kevin Fenzi wrote:
> On Tue, 6 Aug 2013 17:53:22 +0200
> Till Maas wrote:
> > Why is it so hard to just backport this change? And if it needs to be
> > decided why does FESCO not just do it? Or who needs to decide it?
>
> Wel
K and opening discussions on maybe re licensing it into
> a compatible licence; one in which conforms to Copy-left so that it
> will no longer be an issue. Any advice would be greatly appreciated.
Maybe someone from the fedora-legal list can give you some advice:
https://lists.fedoraproje
The following packages are orphaned or did not build for two
releases and will be retired when Fedora (F20) is branched, 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
Here is a status update, many orphans were adopted, but some new
appeared:
Package(co)maintainers
bluecoveorphan
cal3d orphan
dayplanner orphan, rakesh
derelictorphan, bi
ll data that
should be zero actually is a zero. It works well for unassigned file
systems blocks, but if there is a file containing zeroes in the file
system (that is not a sparse file) it might not contains zeroes
afterwards as far as I understand bmap. This does not sound like
something that i
packages already reviewed and have you been sponsored? If not,
it might help to post links to your review requests.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Wed, Aug 14, 2013 at 12:21:23PM +0300, Artem Bityutskiy wrote:
> On Wed, 2013-08-14 at 10:37 +0200, Till Maas wrote:
> > On Wed, Aug 14, 2013 at 09:31:22AM +0300, Artem Bityutskiy wrote:
> >
> > > Other things like reading from remote sites, progress indicator,
>
e.org/~ausil/f18-failures.html
was also in
http://ausil.fedorapeople.org/f20-failed.html
which is not the case (unless my script-fu was wrong).
> None of this is in the SOP, so I don't know if Till did it. (And it's my
> fault for not getting around to documenting it yet.)
I believe
Due to missing FTBFS bug reports for Fedora 18 and a bug in scripting,
FTBFS packages were missing in previous reports. According to
https://fedoraproject.org/wiki/Fails_to_build_from_source?rd=FTBFS#Package_Removal_for_Long-standing_FTBFS_bugs
removing long standing FTBFS packages might be delayed
(Sorry, I forgot to add the package maintainers address to Bcc,
therefore this message will appear twice on the devel mailing list)
Due to missing FTBFS bug reports for Fedora 18 and a bug in scripting,
FTBFS packages were missing in previous reports. According to
https://fedoraproject.org/wiki/Fai
On Fri, Aug 16, 2013 at 10:26:45PM +0200, Kalev Lember wrote:
> On 08/16/2013 10:15 PM, Till Maas wrote:
> > On Fri, Aug 16, 2013 at 03:17:42PM -0400, Bill Nottingham wrote:
> >
> >> FTBFS packages need:
> >>
> >> 1) a list gathered by pruning t
7;, '1.0.2', '4.fc20')
How did you create the list? At least this one seems to be a false
positive, because it is not retired:
https://admin.fedoraproject.org/pkgdb/acls/name/latexdiff
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Mon, Aug 19, 2013 at 07:55:26PM +0100, Peter Robinson wrote:
> On 19 Aug 2013 19:51, "Till Maas" wrote:
> > How did you create the list? At least this one seems to be a false
> > positive, because it is not retired:
>
> Isn't that what he says in th
On Mon, Aug 19, 2013 at 01:25:36PM -0600, Kevin Fenzi wrote:
> On Mon, 19 Aug 2013 21:22:49 +0200
> Till Maas wrote:
>
> > On Mon, Aug 19, 2013 at 07:55:26PM +0100, Peter Robinson wrote:
> > > On 19 Aug 2013 19:51, "Till Maas" wrote:
> >
> > >
_at_end_of_life
>
> In some cases, the dead package is only missing the koji block request
> in Fedora rel-eng trac. In other cases, the package has not even been
> marked a "dead.package" in git yet:
If there are no objections, I can just retire all of them.
Rega
scratch build because
libspeechd.h cannot be found, maybe this is an unrelated bug)
modplugtools needs to be changed to not ship modplugplay anymore, but
modplug123 should still work.
I will soon post a follow-up message regarding FTBFS packages.
Regards
Till
--
devel mailing list
devel
The following packages did not build for two releases and will be
retired around 2013-08-26 unless someone rebuilds them or announces to
actively working on fixing them.
Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one.
On Mon, Aug 19, 2013 at 11:21:38PM +0200, Dan Horák wrote:
> On Mon, 19 Aug 2013 23:05:32 +0200
> Till Maas wrote:
>
> > The following packages did not build for two releases and will be
> > retired around 2013-08-26 unless someone rebuilds them or announces to
> >
On Mon, Aug 19, 2013 at 10:51:34PM +0100, Peter Robinson wrote:
> No they can't, the sync of blocked/new packages is synced over all
> secondary arches. They could likely be untagged so they don't show up in
> the list.
Tagging is also synced, therefore it is more complicated. There is now a
tick
On Tue, Aug 20, 2013 at 12:17:50AM +0200, Michael Schwendt wrote:
> # repoquery --whatobsoletes openswan
> libreswan-0:3.3-1.fc19.x86_64
>
> That's strange, because openswan is a dead.package. :-/
FYI: openswan is now blocked for Fedora 20.
Regards
Till
--
devel m
this:
> http://mschwendt.fedorapeople.org/obscheck-remote.py
thank you for a pointer to the script.
> Output for Rawhide:
>
>
> Dead and all builds obsoleted:
> --
> chktex
> ff-utils
> jadetex
> rdate
These packages are now blocked in f20. They shou
On Mon, Aug 19, 2013 at 11:05:32PM +0200, Till Maas wrote:
> The following packages did not build for two releases and will be
> retired around 2013-08-26 unless someone rebuilds them or announces to
> actively working on fixing them.
>
> Note: If you received this mail directly y
On Wed, Aug 21, 2013 at 04:52:53PM +0200, Nicolas Mailhot wrote:
>
> Le Dim 4 août 2013 10:44, Till Maas a écrit :
> > The guideline should be to ask upstream to fix the meta data. In case of
> > missing license text (e.g. source code with a GPL header but no copy of
> >
ppear from Fedora.
>
> Damn... it's deprecated now. Can Dennis unretire it?
It is unblocked in koji now, but you need to file a SCM admin request:
https://fedoraproject.org/wiki/Package_SCM_admin_requests
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.
ng signing in the composing process. In general
I would welcome if some time could be freed to make sure that every code
that is produced by Fedora can be easily acquired via a secure and
verified way.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org
;s release process is not visible for most
people, making it very hard to improve stuff.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Fri, Aug 23, 2013 at 10:52:47AM -0400, Matthew Miller wrote:
> If you're maintaining EPEL packages, might I suggest having a VM with RHEL
> or CentOS handy?
Kevin does this already for everybody:
https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers
R
Hi,
On Fri, Aug 23, 2013 at 11:51:15AM +0300, Ville Skyttä wrote:
> On Tue, Aug 20, 2013 at 12:05 AM, Till Maas wrote:
>
> > smart athimm, scop
>
> Where does this information about maintainers come from? Once upon a
> time I (scop) was a co-maintainer
-poms
xiphmont: libgssglue
yyang: maven2-common-poms
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Hi,
On Fri, Aug 23, 2013 at 11:25:47PM +0200, Till Maas wrote:
> Depending on: maven2-common-poms
> antlr-maven-plugin (maintained by: spot, tradej)
> antlr-maven-plugin requires maven2-common-poms = 1.0-50.fc20
This is a BR, I reported it here:
https://bugzilla.r
st it yet.
A script to get all retired packages from datanommer is also already
working pretty good. It only needs integration to listen on fedmsg to
get it completely automated:
http://ur1.ca/f6xco
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
oquery --whatobsoletes libgssglue
> $
>
> https://lists.fedoraproject.org/pipermail/scm-commits/Week-of-Mon-20130624/1047519.html
There is a similar retired package, but I did not check which was first:
https://admin.fedoraproject.org/pkgdb/acls/name/libgssapi
Regards
Till
--
devel mailin
Hi,
The following packages did not build for two releases and will be
retired around 2013-08-26 unless someone rebuilds them or announces to
actively working on fixing them.
Here is a status update. There are now more packages than in the recent
report, because the packages are now hopefully bett
On Sat, Aug 24, 2013 at 05:33:15PM +0800, Christopher Meng wrote:
> Till, can you unblock libgssapi? I can maintain it for serf.
You first need to get it re-reviewed and then file an SCM admin request:
https://fedoraproject.org/wiki/Package_SCM_admin_requests
Also you should research whet
Hi,
the comps git repo currently contains comps files for EOL releases,
which makes "grep" more cumbersome, because one needs to specify the
current non-EOL releases to grep only in them. Also it makes the default
make target take unecessarily long, because it build all comps including
the EOL one
On Sun, Aug 25, 2013 at 09:54:59AM +0100, Subhendu Ghosh wrote:
> On Aug 25, 2013 12:17 AM, "Till Maas" wrote:
> >
> > Hi,
> >
> > the comps git repo currently contains comps files for EOL releases,
> > which makes "grep" more cumbersome,
On Sun, Aug 25, 2013 at 09:41:56PM +0200, Pierre-Yves Chibon wrote:
> On Sat, Aug 24, 2013 at 09:56:06AM +0200, Till Maas wrote:
> > On Fri, Aug 23, 2013 at 09:33:59AM +0100, Peter Robinson wrote:
> > > There's been discussion of adding "fedpkg retire-package&
On Mon, Aug 26, 2013 at 10:04:29AM +0200, Michal Schmidt wrote:
> On 08/24/2013 11:21 AM, Till Maas wrote:
> > The following packages did not build for two releases and will be
> > retired around 2013-08-26 unless someone rebuilds them or announces to
> > actively w
> >
> >> http://www.theverge.com/2013/6/26/4468050/facebook-follows-google-with-tough-encryption-standard
>
> and how can i quote from the URL?
> http://www.internetstaff.com/roller/blog/entry/enable_elliptical_curve_diffie_hellman
You do not use IPv6.
Regards
Till
--
devel
I retired the following packages that were reported earlier recently:
curry
eclipse-phpeclipse
fedora-package-config-smart
mod_mono
nautilus-sendto-trac
open-cobol
petitboot
simulavr
smart
tiobench
The following packages are did not build for two releases and will be
retired before the Alpha Chang
The following packages are currently retired but other packages depend
on them. Since the packages are not yet blocked in koji, this is not
very visible. Nevertheless, the packages need new maintainers or the
depending packages need to drop dependencies on them.
Remarks:
- There are no recursive d
On Wed, Aug 28, 2013 at 10:53:53PM +0200, Till Maas wrote:
> The following packages are currently retired but other packages depend
> on them. Since the packages are not yet blocked in koji, this is not
> very visible. Nevertheless, the packages need new maintainers or the
> depend
been renamed upstream and have been replaced with
> packages in Fedora with the new name 's/quantum/neutron' so
> openstack-quantum, python-quantum and python-quantumclient should all just
> be retired.
python-quantumclient openstack-quantum are now blocked in f20+, but I
di
On Thu, Aug 29, 2013 at 07:56:28AM +0200, Till Maas wrote:
> On Thu, Aug 29, 2013 at 12:32:19AM +0100, Peter Robinson wrote:
> > > python-quantumclient orphan, jruzicka, vaneldik, pbrady, apevec,
> > > gkotton,
> > >markmc, rkuk
On Wed, Aug 28, 2013 at 10:53:53PM +0200, Till Maas wrote:
> Package(co)maintainers
> ===
> directfb orphan
On Thu, Aug 29, 2013 at 11:09:12AM +0200, Michael Schwendt wrote:
> And retiring packages is too difficult in Fedora. The process is
> complex or not known by all packagers:
>
> http://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
>
> Some retire only in pkgdb (some create orph
ilus
> zeitgeist-datahub
> obsoleted by: zeitgeist
They should be retired, blocked and dead now.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
sh the new sources file.
Koji fetches only the tarballs that are mentioned in the sources file
and for security reasons they need to be added explicitly by packagers
to it.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On Tue, Aug 27, 2013 at 10:48:21PM +0200, Till Maas wrote:
> The following packages are did not build for two releases and will be
> retired before the Alpha Change Deadline 2013-09-03, unless someone
> adopts them. If you know for sure that the package should be retired,
> please do
t; If no response still, please release his ownership.
Please follow this procedure:
https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedor
On Sat, Aug 31, 2013 at 06:06:16PM +0200, Nicolas Chauvet wrote:
> 2013/8/29 Till Maas
>
> > On Wed, Aug 28, 2013 at 10:53:53PM +0200, Till Maas wrote:
> >
> > > Package
ed
> for more then two weeks.
The documentation about this sucks, the best I found so far is this:
https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#Claiming_Ownership_of_a_Deprecated_Package
Regards
Till
--
devel mailing list
devel@lists.fedoraproje
ong-time dependency breakage.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Mon, Sep 02, 2013 at 06:56:04AM +0200, Johannes Lips wrote:
> Till Maas wrote:
> >Most[0] of the following 56 packages need to be fixed to build in the next
> >five or six months to not be retired in prior to branching of Fedora 21:
still in the repos because they are unblocked in koji.
There are a lot of packages that depend on eg libgssglue. Therefore just
blocking them will cause dep errors but doing nothing does not improve
the situation.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
On Wed, Sep 04, 2013 at 10:39:07AM +0200, Tomas Mraz wrote:
> On Wed, 2013-09-04 at 08:22 +0200, Till Maas wrote:
> > On Tue, Sep 03, 2013 at 05:29:20PM -0400, Bill Nottingham wrote:
> >
> > > If you would like to add something to this agenda, you can reply to
>
The following packages are now blocked in F20+ as decided on today's
FESCo meeting:
libgssglue spacewalk-web
Please fix any resulting dependency issues.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Co
ot; boot entry and execute "dracut
> --regenerate-all". If you want your initramfs to be hardware independent,
> install the "dracut-nohostonly" rpm package. If you don't want rescue images
> at
> all (like in virtual machines), install the "dracut-norescue"
seems to be
only xfs_growfs on F19, but no tool to shrink it.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
did not build for two releases. Since the packages
cannot be installed on F20+, I will retire the packages in F20+ as well,
unless someone wants to pick them up.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of
On Mon, Sep 09, 2013 at 10:59:56PM +0200, Till Maas wrote:
> Most if not all packages depend on a package I recently retired,
> therefore because it did not build for two releases. Since the packages
Actually they depend on a retired package, that I blocked, because it
was not blocked. B
mary...
But this does not show the component in the "index" view, or can this be
changed as well? I always add the component to the summary for Bugs I
report to get this information before I need to open the mail itself.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.or
On Mon, Sep 16, 2013 at 01:26:55PM +0200, Karel Zak wrote:
> On Mon, Sep 16, 2013 at 12:34:50PM +0200, Till Maas wrote:
> > On Mon, Sep 16, 2013 at 10:36:41AM +0200, Karel Zak wrote:
> >
> > > For example if you use mutt then all you need is to add
> > >
> &
', 'orphan', '--retire',
> 'ql2100-firmware', 'devel']' returned non-zero exit status 5
> [jwboyer@zod ql2100-firmware]$
>
> I also tried running the pkgdb-cli command by itself with --user and
> --password specified, but that didn
in
Rawhide but not Branched (F20). Is this really intentional? Since F20 is
not yet released, it is still a good idea to retire it, because it seems
to be renamed.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Tue, Sep 17, 2013 at 03:52:51PM -0400, Paul Wouters wrote:
> On Tue, 17 Sep 2013, Till Maas wrote:
>
> >I just blocked the following packages in koji for F20+, because they
> >were retired some time ago, but not yet blocked:
>
> >autotrust
>
> >They might
It is now blocked and dead.packaged.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
d have both the old
> package's commits and the new one's.
This did already happen, but there is no idea what to do with the EPEL
branches. The old package does have some, where the package is orphaned,
but the new package maintainer does not intend to maintain the new
package in EPEL.
Reg
Hi,
the mupdf maintainer seems to be non-responsive and there seem to be
users requesting a new update:
https://bugzilla.redhat.com/show_bug.cgi?id=848904
Is someone interested in helping here? I only noticed this looking
through the upstream release monitoring mails.
Regards
Till
--
devel
utility
Please respond here, if you want to take a package over including your
FAS name and I will transfer the package if Jarod agrees.
Regards
Till
[0] https://bugzilla.redhat.com/show_bug.cgi?id=881976#c14
[1] https://bugzilla.redhat.com/show_bug.cgi?id=881976#c15
--
devel mailing list
devel
et-value=%{name}
This does not take subpackages into account. Not sure, how relevant it
is for the 50 packages you plan to adjust, but it would be an issue for
e.g. wireshark-gnome.
Nevertheless, if there is a way to do this properly automatically, I
would welcome this.
Regards
Till
--
devel mai
/forwarding
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
allow packaging RPM macros, therefore this should be fine.
> >
> > Also I am interested whether there are better options available.
> >
>
> Hi Till,
>
> Any news on packaging this? I'm interested to see what we can do with it.
no, sorry, I did not g
is packages, so you can pick lirc
up now:
https://admin.fedoraproject.org/pkgdb/acls/name/lirc
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Tue, Oct 01, 2013 at 07:50:45PM +0200, Till Maas wrote:
> cx18-firmware -- Firmware for Conexant cx23418-based video capture
> devices
> libcrystalhd -- Broadcom Crystal HD device interface library
> lirc -- The Linux Infrared Remote Control package
> rinputd -- A server for
invalid? How did you handle your bugs?
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
pulseaudio869 Full RELROCanary found NX enabled
> No PIE
>
Also it would be nice if you ask FESCo to update the list at
https://fedoraproject.org/wiki/Hardened_Packages
to include the packages you noticed are missing there.
Regards
Till
--
devel mailing l
/
References:
http://www.redhat.com/archives/rhl-devel-list/2008-November/msg01229.html
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On Thu, Apr 04, 2013 at 08:50:43AM -0600, Nathanael D. Noblet wrote:
> On 04/04/2013 06:44 AM, Till Maas wrote:
> >Hi everyone,
> >
> >I have been using smock.pl regularly and since it was not developed
> >recently. I wonder what everyone else is using, e.g. does someth
On Thu, Apr 04, 2013 at 09:34:22AM -0400, seth vidal wrote:
> On Thu, 4 Apr 2013 14:47:12 +0200
> Johannes Lips wrote:
>
> > On Thu, Apr 4, 2013 at 2:44 PM, Till Maas
> > wrote:
> > > I have been using smock.pl regularly and since it was not developed
> >
On Thu, Apr 04, 2013 at 12:34:51PM -0400, seth vidal wrote:
> On Thu, 4 Apr 2013 18:30:02 +0200
> Till Maas wrote:
> > Is it intended to be feature complete? Smock looks more like a simple
> > build system, because it supports to build multiple archs/distros at
> > onc
hy a central Fedora service is using third
party, probably non-FOSS services leading only to less security.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
ing characters: " to avoid any inaccuracies.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
h-de_nodeadkeys.map.gz
| sg.map.gz -> /lib/kbd/keymaps/xkb/ch-de_nodeadkeys.map.gz
| slovene.map.gz -> /lib/kbd/keymaps/xkb/si-us.map.gz
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
> case to the updated list of RFEs.
I would like it even more if RPM keeps a backup copy of every %config
file somewhere protected to allow to restore config files even without
having the original RPM available, because the RPM might not be
available anymore.
Regards
Till
--
devel mailing list
persisted ones with
permissions for users
Should I file RFEs for these in Red Hat Bugzilla or is there a
better place to communicate them to?
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
essary
information.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
wondering if there is anything special that I should test, therefore I
do not see any value at all in the update description. Maybe more
examples of good update description would help.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
f-list or br...@freenode.org.
>
> [1]
> https://fedoraproject.org/wiki/GSOC_2013/Student_Application_Blaskovic/Fedora_Gooey_Karma%284111%29
is this planned to be a replacement or an alternative to the command
line tool?
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://ad
we present to users in the default graphical update
> interface
You easily get a good minimal level of quality by just using the
available information in an update such as the type and mentioned bug
reports.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://ad
for special cases (and later per-package)?
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
o create a proper release to allow easy packaging for Fedora, I wonder
if I will find any obstacles when I package it. The packaging guidelines
allow packaging RPM macros, therefore this should be fine.
Also I am interested whether there are better options available.
Regards
Till
--
devel mailing
701 - 800 of 1153 matches
Mail list logo
