not find a sponsor, you can write me directly and I will
see what I can do as time permits.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
gs and where the sources of the script can be found.
Thank you
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On Mon, Jul 08, 2013 at 10:00:04AM +, nob...@fedoraproject.org wrote:
> Change in ownership over the last 168 hours
How about changing the report time to to last 48-216 hours, then ongoing
ownership transfers would be recognised as long as they happen within 48
hours.
Regards
Till
--
de
On Tue, Jul 09, 2013 at 07:01:12PM +0200, Pierre-Yves Chibon wrote:
> On Tue, 2013-07-09 at 18:23 +0200, Till Maas wrote:
> > On Mon, Jul 08, 2013 at 10:00:04AM +, nob...@fedoraproject.org wrote:
> > > Change in ownership over the last 168 hours
> >
> > How abo
On Tue, Jul 09, 2013 at 06:56:03PM +0200, Pierre-Yves Chibon wrote:
> On Tue, 2013-07-09 at 18:06 +0200, Till Maas wrote:
> > and where the sources of the script can be found.
> That would be there:
> https://github.com/pypingou/fedora-owner-change
Thank you. Have you considered
ed here:
https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers
f17-arm-test.scrye.com is currently not reachable for me.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On Tue, Jul 09, 2013 at 10:36:39PM +0100, Peter Robinson wrote:
> On Tue, Jul 9, 2013 at 10:11 PM, Till Maas wrote:
> > Which hardware is supported by ARMv7 hfp 32bit builds? Will there be
>
> http://fedoraproject.org/wiki/Architectures/ARM
>
> The list is expanding regula
edhat.com/show_bug.cgi?id=1338140, but this fails also with
> "You must provide a valid review URL to un-retire master"
Not sure why it fails, but anyhow the review needs to be finished before
the unretirement request will be approved.
Kind regards
Till
--
devel mailing l
ation, visualization,
planning, scripting and control.
I'd be glad to review a package in return.
Thanks,
Till
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
trigi-analyzers (maintained by: than, group::kde-sig,
jgrulich, mbriza, rdieter)
|kdesdk-strigi-analyzers-16.04.1-1.fc25.i686 requires
libstreamanalyzer.so.0, libstreams.so.0
|kdesdk-strigi-analyzers-16.04.1-1.fc25.src requires
pkgconfig(libstreamanalyzer) = 0.7.8, pkgco
eng to get it unretired within two weeks without
needing a re-review.
Kind regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
needed.
Kind regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
at we can rebuild smb4k in rawhide and fix
AFAICS you do not need to rebuild smb4k once the other packages do not
depend anymore on strigi.
Kind regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
eems to be not
properly working right now. If it does not work or if you need
additional packages, please file a ticket at the releng trac and
specify which packages you need for which branches. Packages can be
unretired for two weeks after their retirement without any re-review.
Kind regards
Till
--
xbackup:
https://bugzilla.redhat.com/show_bug.cgi?id=1342737
Thanks,
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
tiring the dependencies
might not be necessary anymore.
Kind regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
fication that a bugfix
is pending, I immediately downloaded the package, tested it and gave my
feedback. Now, if there was a freeze, I would have to come back later
and see if I'm already allowed to give feedback. Most likely, I would
have never given my +1.
Regards,
Till
[1] https://bodhi.fe
nymore.
I'd be glad to do a review in return.
Kind regards,
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
master)
I've taken gprolog.
@Roberto, Jochen: You are co-maintaining gprolog. If you want to take
the package, please let me know, I'd be glad to give the package to you.
Regards,
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
general tipps how to debug gcc segfaults? I've never
seen this type of problem and I don't know how to tackle this issue.
Any help is appreciated. You can also ping me on IRC: morxa
Thanks,
Till
[1] https://kojipkgs.fedoraproject.org//work/tasks/7060/15227060/build.log
[2] https://gcc.gn
On 08/12/2016 11:43 AM, Florian Weimer wrote:
> On 08/12/2016 11:36 AM, Till Hofmann wrote:
>> Hi all,
>>
>> gprolog has been FTBFS for a while due to a segfault on i686, see this
>> build [1] for an example. I followed advice on [2] to add some debugging
>> fl
ki page about packaging with cmake, although it's not
very elaborate: https://fedoraproject.org/wiki/Packaging:Cmake
Kind regards,
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
w 18 weeks unmaintained and
needs to be retired now which means that asterisk and the nagios-plugins
will be retired as well or it needs to get a maintainer. Also if there
is a secret plan to make asterisk or nagios not depend on
freeradius-client, it is now the time to do so (actually it was a few
weeks ago).
Kind regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
retire it later if nobody adopts it.
Kind regards
Till
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
y round, i.e. if a keyboard layout is
specified at the kernel command line, it should not be necessary to
specify one in a local config file. Then if everything should use the
same keyboard layout, there is only one place to set this instead of
several ones that might diverge unintended.
Regards
Ti
onally to the script.
All faulty bugs should be closed and new bugs created if appropriate.
Sorry for the trouble.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
ertheless, once anaconda is capable of installing only proper
packages from a verified environment, a patch do also do this if the
environment has been verified by a human should be trivial.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
e to be secure, also checking for secure boot does not
seem to provide any benefit.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On Thu, Jan 10, 2013 at 02:41:54PM -0500, Adam Jackson wrote:
> On Thu, 2013-01-10 at 17:56 +0100, Till Maas wrote:
> > But why should anaconda not verify packages if secure boot is disabled?
>
> For the same reason Firefox doesn't automatically accept self-signed SSL
&
to boot with
this feature enabled.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On Thu, Jan 10, 2013 at 04:42:36PM -0600, Michael Cronenworth wrote:
> Till Maas wrote:
> > SecureBoot does not do this automatically, as it would allow to run a
> > F18 install image that does no signature checking on packages. Therefore
> > users still need to verify th
trust between Fedora gpg keys/get old gpg keys revoked, get
packages signed in koji/for rawhide). At least for fedup there is hope
that the required data will be produced to be able to write a patch for
it.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
update the master branch you can easily let the computer do all
the work to also build for e.g. f18:
for b in master f18; do fedpkg switch-branch $b; git merge master;
git push; fedpkg build --nowait; done
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
ou file a bug against filesystem, it will probably be included. Then
the other packages can be fixed to not own it.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
referring to my general knowledge
> of how webapps are packaged in Fedora (e.g. wordpress, which I do
> run). Thanks.
Trac behaves similarly. There is also some environment setup and
deployment involved that creates/copies files, which are usually not
common to all instances.
ib/debug
But it shows that a lot (all?) debuginfo packages own the directory
which probably needs to be fixed in rpm itself.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
l that can be used to boot
a different kernel by reconfiguring the boot loader and initiating a
reboot? Then it is possible to get both, nearly zero boot delay and a
boot menu.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
rn to sanity.
> >
> >charles zeitler
>
> Setting aside the drama, you can manually partition F18.
Unless anaconda crashes (live image) or does not recognise the
partitions (DVD image). :-/
Reference: https://bugzilla.redhat.com/show_bug.cgi?id=905669
Btw.: Ideas how to install F18 anyhow ar
httpd_totpcgi_script_t syslog_client_type;
| #line 41
https://github.com/mricon/totp-cgi/issues/27
https://bugzilla.redhat.com/show_bug.cgi?id=1107456
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: h
On Thu, Nov 13, 2014 at 07:40:19PM +0100, Till Maas wrote:
> On Thu, Nov 13, 2014 at 03:20:03PM +0200, Kalev Lember wrote:
>
> > totpcgi
>
> This requires an selinux export to make it build again:
>
> | + make NAME=mls -f /usr/share/selinux/devel/Makefile
> | C
ere are not packages listed that were just recently
broken? Also do you propose to retire the package only in F21 or also in
Rawhide?
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.
1:36)
What happens with packages that get broken after the warning but before
the Final Freeze?
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
one is trying to use it while it does
not work, it can be easily enabled. And if someone does not want it but
would accidently click, the message just needs to be ignored once.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
when my system
is docked and the lid is closed, there is no such thing afaik.
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
ns in Fedora. If you use some application which utilizes
Thank you for your work. Please follow the process about mass bug filing
in the future:
https://fedoraproject.org/wiki/Mass_bug_filing
Should the proposed changes be pushed upstream or is this a Fedora-only
thing?
Regards
Till
--
deve
for this is:
| Your package accepts/processes untrusted input.
This seems to be about every package that I use, because I most if not
all tools process untrusted data from the Internet.
Kind regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailm
t need to be considered.
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
u for promoting GPG usage. Did you think about
adding unique uids to Fedora release GPG keys to make them available
this way as well?
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraprojec
On Wed, Jan 28, 2015 at 06:10:13PM -0500, Paul Wouters wrote:
> On Wed, 28 Jan 2015, Till Maas wrote:
>
> >The keyid is part of the fingerprint, so with the fingerprint one can
> >download the key and verify it. Therefore it is the only right thing to
> >do.
>
>
s is going to change soon:
https://fedorahosted.org/rel-eng/ticket/5931
There is at least an interface that allows to not select the devel
branch. But I am not sure what is happening then.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listin
ently delayed.
Also we do not have someone doing pushing updates every weekend. It also
requires manual signing.
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
t to happen faster. However, there is developer manpower missing
to fix and improve tools, that nobody can make magically appear.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.
; > Rawhide configs.
>
> But then you will not be warned that your results may differ from Koji.
Since koji builds against RHEL and mock against CentOS, the results may
differ regularly anyhow.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedorapr
Hi,
On Wed, Jan 28, 2015 at 06:10:13PM -0500, Paul Wouters wrote:
> I could put them under fedor...@fedoraproject.org ?
Please use fedora-xx-primary and fedora-xx-secondary, these are now used
starting with Fedora 23.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
ht
et some development
done for sigul, which needs someone fixing some issues for rel-eng.
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
-ld
>
> #_hardened_build0
I plan to change this to 1 now in Rawhide for the upcoming Fedora 23
feature:
https://bugzilla.redhat.com/show_bug.cgi?id=1192183
Since I did not get any feedback from the redhat-rpm-config maintainers
on the bug, do you want to comment on the change?
Re
are
slowed down much?
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
o something to attract users that care about security
very much to Fedora.
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
edora 23 development process,
there is still a lot of time to do tests.
> Fedora users tend to keep hardware around for longer time than a lot
> of enterprises, it's also a distro used a lot in the developing world
> on low end cheap hardware because the rest of the world isn
uses ASLR, see eg the first Google hit:
https://www.duosecurity.com/blog/exploit-mitigations-in-android-jelly-bean-4-1
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, Feb 20, 2015 at 07:28:50PM +, Peter Robinson wrote:
> On Fri, Feb 20, 2015 at 6:55 PM, Till Maas wrote:
> > On Fri, Feb 20, 2015 at 05:21:59PM +, Peter Robinson wrote:
> How is a PDF with a binary payload any different? Sounds like we need
> to be running pdf reade
t from the user to do it insecurely. However, fedup
should probably make the security problem more obvious so one can get
insecure packages if wanted.
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
1 weeks ago
because of branching, the change values are wrong for branched. If a
package is also orphaned in Rawhide, the Rawhide status change date
applies here as well.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listi
remaining packages will be taken
care of in the full mass rebuild that will happen because of the GCC5
Change for Fedora 23.
Kind regards
Till
___
devel-announce mailing list
devel-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman
don't want
> > to overstep my role as a reviewer.
>
> I'd personally agree. Can they not at least make it only listen on
> localhost unless configured otherwise?
Yes, I agree here, access to elasticsearch allowed to execute arbitrary
code in the past.
Regards
Till
--
dev
but a link to the domain
405n.mj.am (maybe a redirect?). The same holds for the link in your
signature.
(My) Thunderbird also warns me that your email is scam. You should
really check your email.
Regards,
Till
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
s is not true only for dillo, but also for a bunch of other packages
> (eg: revelation, xplanet, spacefm, etc). Is there a way to get things to
> move at all?
This should help:
https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_mai
update would bring major changes, a re-review would probably a
good idea anyway.
Regards,
Till
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
ained upstream, so I
don't see a reason for retirement.
Regards,
Till
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1433290
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
other blog
post [4], I should be able to use COPR with dist-git. Unfortunately, I
couldn't find any further information on COPR + dist-git. Is there some
documentation that I missed? In particular, does anyone have a sample
configuration for using COPR + Tito + dist-git?
Thanks for any poin
On 28.03.2017 14:23, Miroslav Suchý wrote:
> Dne 28.3.2017 v 10:40 Till Hofmann napsal(a):
>> I'm playing around with Tito and COPR following [1,2]. It works great so
>> far, but I'm still having problems with loading the sources to a
>> lookaside cache. I've f
(or use a better
threshold) and support using multiple drpms to generate the final RPM:
e.g. use foo-1_2.drpm and foo-2_3.drpm to generate foo-3.rpm from
foo-1.rpm
2) generate drpms for all recent (up to 10 days old) update paths if the
drpm chain from 1) is bigger/close to the
Hi William,
On Thu, Apr 06, 2017 at 03:43:00PM -0600, William Moreno wrote:
> The icaro project have moved theirs documentation from publican o sphinx I
> am orphaning the icaro-theme.
this sounds like it would be a good idea to just retire it directly.
Kind regard
> Please correct me, if I'm mistaking.
Besides logwatch that was already mentioned, there is also logcheck that
parses logfiles and will break. Other tools might be things like
fail2ban or denyhosts that scan logs for failed login attempts to blo
PRs but I do not
yet understand to the full package workflow when moving to just pagure
instead of pkgdb I must confess. I added my open questions about the
workflow to the wiki so the answers can be made available to everyone:
https://fedoraproject.org/wiki/Infrastructure/WhatHappenedToPkgdb#How_
bout this one.
Kind regards
Till
signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
m using the
script for finding long-time orphaned packages and states the time for
the last owner change in pkgdb. For this report it would be better if I
removed it.
Kind regards
Till
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubsc
d meson are not necessarily EOL'd :)
lldb seems to be broken on aarch64, i686, x86_64 and armv7hl because of
unsatisfied dependencies for clang and llvm-libs. But I guess it will be
fixed once
https://bodhi.fedoraproject.org/updates/FEDORA-2017-10971fa7a7
will be properly in F26
Arch tags to packages that we cannot fix for the
Final Freeze. If this is not possible I am sure we will find a solution
that does not require to retire well-maintained packages.
Kind regards
Till
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
ate...
>
> ... so because only one particular subpackage (which otherwise perfectly
> working, noarch thingy) can't have satisfied dependencies on only one of
> many supported architectures -> are going to drop the entire package (all
> subpackages) from Fedora, I mean entir
On Mon, Jun 26, 2017 at 08:56:20AM +0100, Richard W.M. Jones wrote:
> On Mon, Jun 26, 2017 at 07:02:25AM +, t...@fedoraproject.org wrote:
> > libguestfs (maintained by: rjones, agk, group::virtmaint-sig, mdbooth,
> > ptoscano)
> > libguestfs-1.36.4-1.fc26.src requires java-1.8.
py support there causing a
broken dep. I rebuilt the package now but it will still need a freeze
exception to be included into the F26 Everything repo.
Kind regards
Till
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an e
cleanup process to get a better balance between removing broken
packages and ensuring a safe delivery. There will be new notifications
when things are worked out. The relevant ticket is:
https://pagure.io/releng/issue/6877
Kind regards
Till
___
devel mailing
provided links to your review together with a list of preliminary
reviews, you can increase your chances to find a sponsor.
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
guidelines are built
differently than packages using autoconf.
Do we need a %ldflags macro for packages not using %configure (or other
build systems with proper RPM macros)? Or do the LDFLAGS not matter if
CFLAGS are set properly?
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://adm
://admin.fedoraproject.org/pkgdb/acls/bugs/wipe
The oldest bug is from March 2010 without any response so far.
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
pmdevtools/curlrc"
IMHO the default should be to check certificates, especially since
spectool is the usual tool to update source files in dist-git. Only if
there is no need to check the certificate, this should be disabled.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https:
ows:
curl http://people.fedoraproject.org/~halfie/rebuild-logs.txt | cut -d/ -f1 |
rev | cut -d- -f 3- | rev | sort -u | fedoradev-pkgowners | sort
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
them to use other
out-of-band validation techniques to verify that the tarball they
downloaded is the same they uploaded unless they have reasonable doubt
about their system.
However, if you do not want to use HTTPS to verify the transfered
contents then just use plain HTTP. Using HTTPS but not
Trac's display of the commit message).
Will it add a notification in the issue tracker?
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
change to a browser and to re-login there.
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
pkgdb.
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, Nov 27, 2013 at 12:35:13PM -0600, Bruno Wolff III wrote:
> On Wed, Nov 27, 2013 at 19:21:53 +0100,
> Till Maas wrote:
> >
> >What are your opinions about this? I already checked with Dennis
> >Gilmore, he is ok with this.
>
> Is there a fail against d
ight be
required. Also it happens less often than retirement and it is easily
possible to retire a large amount of packages by administrative users if
required. Therefore I do not see the need for improvements.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedorap
I ran out of time,
therefore the incomplete heads up.
Regards
Till
___
epel-devel mailing list
epel-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel
itialized
> variables, memory & resource leaks etc) in each of them. I have reported
Btw. it seems like Debian intends to run checks like this automatically:
http://qa.debian.org/daca/
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listi
as described in
https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#Claiming_Ownership_of_a_Retired_Package
I already unblocked it for you now, but please keep it in mind for
the future.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org
ld
remove the current kernel when a new kernel is installed. Is this really
what you expect and what dnf should do? Currently it installs a new
kernel without removing the old one as I know it from yum.
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
re requires different versions, then this
should be made possible e.g. within RPM or a different central packaging
tool to provide proper version tracking, central updates and uniform
build flags.
Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/
r this is not very obvious. Who would expect that a
service intended to handle temporary files is used for configuration?
For example the man page says:
| tmpfiles.d — Configuration for creation, deletion and cleaning of
| volatile and temporary files
Regards
Till
--
devel mailing list
devel@list
801 - 900 of 1153 matches
Mail list logo
