accept such a change in rpmdevtools upstream.
>
>
You can add it with a --distro flag
Rahul
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://d
/ghasher
https://src.fedoraproject.org/rpms/wv
https://src.fedoraproject.org/rpms/python-bottle
https://src.fedoraproject.org/rpms/python-bottle-sqlite
Rahul
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le
't clarify what the end result is supposed to be.
Are you planning to maintain a symlink from DNF and Yum to DNF5 after the
transition is complete or not?
Rahul
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an em
FYI, the command in that page doesn't appear to be working because "latest"
is the default tag if you don't specify one for docker and it doesn't
exist, so you have to append ":stable" or something like that.
Rahul
___
devel maili
ms busted, no output at all
* "update" seems to have been dropped (and
/usr/lib/dnf5/aliases.d/compatibility.conf didn't appear to be user
configurable). update should really be kept as a compatibility alias
* Install is overtly verbose
Rahul
__
ower vs
rejected: we don't think this is fully baked yet or we want to get some
more clarity, come back after you have the answers.
Rahul
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedorapr
t someone is going to
do something unconditionally is just disclosure.
Rahul
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraprojec
stead of forcing a mandate to remove it, perhaps a migration to Copr
would be a better way out of this
Rahul
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
h
/667 as a first start...
>
I am surprised that security engineering folks aren't driving this but no
one else is volunteering, I can. It feels like there should be some easy
wins here even if we don't get hyper granular about the features we enable.
Rahul
__
and will try to keep an eye on PR's related to
this. Feel free to tag me for testing/feedback etc whenever this is being
worked on, would be happy to help.
Rahul
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-
Nagging is a
good starting point but doesn't go far enough. The adoption of these
features is still very low. We can do better.
Rahul
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fed
out of hardening features ie) the ability to set an override for all
systemd services such that it uses ProtectHome as an example and then
individual services can opt out.
Rahul
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send a
Hi
On Wed, Mar 2, 2022 at 12:31 PM Zbigniew Jędrzejewski-Szmek wrote:
> On Thu, Feb 24, 2022 at 02:28:56PM -0500, Rahul Sundaram wrote:
> > Ability to modify these policies via configuration (the above one looks
> > like a build config) and ability to do global ov
ility to modify these policies via configuration (the above one looks
like a build config) and ability to do global overrides and set the
hardening features across all services so distributions or sysadmins can
configure those would be helpful
Rahul
___
dev
a.)
>
https://fedoraproject.org/wiki/Changes/Filtered_Flathub_Applications is
intended to address that
Rahul
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of
it but are you able to participate? If not, you
haven't joined
Rahul
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-
Hi
On Fri, Nov 13, 2020 at 5:54 PM Matthew Miller
wrote:
> On Fri, Nov 13, 2020 at 05:46:46PM -0500, Rahul Sundaram wrote:
> > I think for a community distro, having it all in a single repo is
> > technically better as well because part of the problem that was being
> >
ed choices on what they are installing and that can be as flexible as
you want it to be. apt-listbugs etc does similar things.
Rahul
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedo
createrepo_c
Rahul
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guide
32 bit
Fedora still worked perfectly."
We are done here
Rahul
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.
If you want to reduce your claim to the "many
bugs that did exist and added additional maintenance burden didn't affect
me personally therefore I disagree with the decision made", now that would
be a more reasonable statement if one didn't keep bringing it up in
unrelat
ranted
> > ending 32 bit support while it still worked, and got nothing.
This isn't true. You did get a response with links to bugs and your other
claim that these systems worked perfectly isn't correct objectively.
Rahul
___
devel mailing l
/Stop_Building_i686_Kernels
"This was last proposed with Fedora 27, but it was deferred as an i686 SIG
was to be created to handle issues going forward. That SIG has been largely
unresponsive."
Rahul
___
devel mailing list -- devel@lists.fedorapro
d perhaps forming a community around their preferences is
pertinent. This isn't addressed just to you. Having said that, what do
you consider is the topic?
Rahul
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
n ansible playbook that sets
the defaults and configuration you want and gathering some feedback on
whether others find it useful.
Rahul
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproje
Self-Contained Change Request required, I need to be
> CLA+1, so that's the motivation behind joining the packaging group or
> whatever other group anyone feels is relevant to this project.
>
> Thanks for reading!
> Erich Eickmeyer
>
Thanks for joining. Sounds
the burden on the CPE team. Has CPE leadership
considered talking internally about that?
Rahul
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://doc
proper
> with rust and cargo is not very convenient.
>
A bit of a tangent but there was a proposal for systemd itself to start
using C++ at some point. Was that or Rust still in consideration?
Rahul
___
devel mailing list -- devel@lists.fedoraprojec
Hi
On Fri, Dec 20, 2019 at 7:43 PM John M. Harris Jr wrote:
> On Friday, December 20, 2019 5:33:59 PM MST Rahul Sundaram wrote:
>
> No, I mean the things that actually changed between the two. "What's new"
> or
> so on. This looks like it's just general documentation
Do you mean 30?
https://docs.fedoraproject.org/en-US/docs/ click on 30
Rahul
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraprojec
ould be to open a pull request if a scratch
build was successful. For minor version bumps, this can be helpful for
maintainers
Rahul
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.
Hi
On Wed, Oct 16, 2019 at 9:21 PM Neal Gompa wrote:
> On Wed, Oct 16, 2019 at 9:17 PM Stephen Gallagher
> wrote:
> >
> > On Wed, Oct 16, 2019 at 9:14 PM Rahul Sundaram
> wrote:
> > If that's the case, the most obvious way to inform you is to disallow
> >
, I don't really want it blocking my ability to upgrade. I would
certain like to be informed about the fact but I would want to get to the
next release anyway.
Rahul
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to dev
ansition between them, it induces a lot of pain. For instance, dnf
cannot install flatpak apps currently and I can't use kickstart to automate
installation in the same way etc.
Rahul
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe s
ble upstream
project.
Rahul
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
it and we should just ignore it or encourage
it anyway?
"My point wasn't restricted to this conversation"
Might be better to post a separate thread, preferably to the board list if
you want to raise a question on general moderation.
Rahul
_
On Wed, Feb 22, 2017 at 8:55 PM Gerald B. Cox wrote:
> It gets a bit tedious to read all the feigned outrage and the continuous
> aggrandisement of the Fedora Code of Conduct; it shouldn't be used as a
> construct to silence debate.
>
Vague accusations are not a de
On Tue, Feb 21, 2017 at 5:00 AM Ralf Corsepius wrote:
> On 02/21/2017 01:02 AM, Rahul Sundaram wrote:
> >
> >
> > On Mon, Feb 20, 2017 at 6:42 PM Ralf Corsepius
> >
> >
> > No. Mr. Williamson's attitude towards the Fedora community makes it
> >
On Mon, Feb 20, 2017 at 6:42 PM Ralf Corsepius
>
> No. Mr. Williamson's attitude towards the Fedora community makes it
> impossible to answer
Without details, a vague discussion adds nothing meaningful to the
conversation.
Rahul
___
deve
ses by default
as well. The yum -> dnf transition still feels like needless churn as a
end user tool but having a yum command just do the right thing as always
will help
Rahul
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe
On Tue, Dec 20, 2016 at 10:25 PM Gerald B. Cox wrote:
>
> On Tue, Dec 20, 2016 at 7:10 PM, Rahul Sundaram wrote:
>
> I don't see any context missing in a direct quote which I responded to.
> If you believe otherwise, feel free to summarize your position and include
> an
issed it. Again, you have to take that comment in context
> of the entire thread.
>
I don't see any context missing in a direct quote which I responded to. If
you believe otherwise, feel free to summarize your position and include any
context you need to.
Rahul
__
On Tue, Dec 20, 2016 at 9:33 PM Gerald B. Cox wrote:
>
>
> Right. I understand that but the solution of letting things stay in
> updates-testing for a long time isn't a great way to implement that. It an
> abuse of updates-testing.
>
>
> No one is doing that. You have to read
bsolutely require it and let everything else be updated piecemeal.
>
Right. I understand that but the solution of letting things stay in
updates-testing for a long time isn't a great way to implement that. It an
abuse of updates-testing.
Rahul
if
you need to push a bug fix or security fix that is not tied to a new major
upstream release?
Rahul
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
g feature by default and increase coverage over time.
If it requires every service to understand all the sandboxing features and
enable it manually, we aren't getting security features by default and we
really should.
Rahul
___
devel mailing list -- devel@l
rrides with services that can
opt out rather than opt-in
Rahul
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
look political even if you
have legitimate technical concerns about the quality of the software. Do
you want Canonical to pull the Flatpak PPA because the quality of Flatpak
on Ubuntu isn't perfect?
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedorapr
what Fedora legally can ship. That
has to be approved by Red Hat legal as well.
And ... Fedora does not ship third party kernel modules.
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Hi
On Fri, Nov 6, 2015 at 11:23 AM, Reindl Harald wrote:
>
> the same way as other packages to it?
>
> * see php
> * see httpd
>
More useful if you could submit a spec file patch
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mail
u file a bug report?
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
2 (and IMHO, for the worse, though if there's some official
Markdown spec that says it should be that way, meh…).
Markdown has no official spec. The closest you can get is commonmark.
Fairly sure, the current parsing is more correct.
http://commonmark.org/
Rahul
--
devel mailing list
devel
=* --enablerepo=updates clean metadata
dnf clean expire-cache
Rahul
--
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 Wed, Apr 22, 2015 at 11:19 AM, Richard Shaw wrote:
I'm not volunteering!
...but perhaps a yum-dnf transition guide on the Fedora wiki would be
nice which would cover things like this.
https://fedoraproject.org/wiki/Yum_to_DNF_Cheatsheet
Rahul
--
devel mailing list
devel
.
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
revisions of yum itself.
It would be much better if we can just stick to yum as the name of the
command esp now that the classic yum command itself has been renamed to
yum-deprecated resulting in no conflicts.
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https
eliminate it for countless other
things it is used for
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
of the bundling issues for example.
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
computers
Why dnf don't recognize that packages?
http://dnf.readthedocs.org/en/latest/user_faq.html#why-do-i-get-different-results-with-dnf-upgrade-vs-yum-update
dnf update --refresh might be what you are looking for
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https
that
I am the point of contact, feel free to drop a request in pkgdb and send me
a note off list as well. Thanks for those who have stepped in from time
to time.
The list of packages is at
https://admin.fedoraproject.org/pkgdb/packager/sundaram/
Rahul
--
devel mailing list
devel
Hi
On Thu, Feb 26, 2015 at 2:22 PM, Michael Cronenworth wrote:
I will take deluge.
FAS: mooninite
Done
Rahul
--
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 Thu, Feb 26, 2015 at 2:25 PM, Matthias Runge wrote:
Congrats to the new job!
I'd take
* python-kombu
* python-gdata
* python-billiard
Thanks and done.
* django-* packages should be all become retired.
I have orphaned them since they have EPEL branches.
Rahul
--
devel
for it first. So I have given it to him. You can request
co-maintainership if you are still interested
Rahul
--
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 Thu, Feb 26, 2015 at 4:22 PM, Sereinity wrote:
Hi,
I will take e_dbus and evas-generic-loaders.
Done. The e* stack is quite old in Fedora now. If you or anyone else
wants to keep it more current, that would be nice
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https
timeframe?
They intend to but no specific timeframe
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
://apps.fedoraproject.org/packages/python-ipython-notebook
It is purely because noone has stepped up to do the maintenance. It is not
explicitly excluded. That would only really happen if RHEL itself ships
the package or if there are licensing problems
Rahul
___
epel
Hi
On Mon, Feb 23, 2015 at 10:35 AM, Zbigniew Jędrzejewski-Szmek wrote:
And seriously, Rahul Sundaram is hardly a third party person. He's one
of the active maintainers of systemd package, which you can easily
check in the pkgdb, as well as your colleague from Red Hat.
Neither is correct
, people do have to
use older versions of libraries because debugging issues in newer versions
isn't a priority and won't be for a lot of users.
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http
folks affected by such changes. It is
a fairly simple change in this case but it affects more than just one
component and not everyone is aware of the details in the first place. A
simple announcement here or fedora devel announce list would go a long way.
Rahul
--
devel mailing list
devel
bundling
* Formalized bug reporting
* pkgdb, tagger, bodhi etc
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
.
This is sort of a situation we have by default, as it's simpler for
people to package into the SUSE public repo.
Not sure how. Please explain. If the goal is to make it easier to do
fire and forget builds, then koji scratch builds and perhaps copr seems to
be a good option.
Rahul
--
devel mailing
Hi
On Tue, Jan 20, 2015 at 7:25 PM, Ian Pilcher wrote:
How does this affect users of other display managers (or does it)?
It doesn't affect them afaik.
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct
what you mean here. Turning off direct root login in SSH
doesn't make SSHD itself run as that user. SSHD is still running as root.
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code
useful to be
able to deal with a consistent standard image and only provides deltas for
upgrades. Chrome OS does that for example and it is used in some of the
most popular laptops in Amazon with millions of consumers.
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https
their release is going EOL and we also need to
automatically prompt users to upgrade whenever there is a new release (ie)
some integration between GNOME Software/Apper and Fedup
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora
Hi
On Mon, Jan 5, 2015 at 4:18 AM, Richard Hughes wrote:
Also, if any UI changes need to happen, the time to talk to the
designers is NOW.
Which designers?
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code
Hi
On Mon, Jan 5, 2015 at 2:48 PM, Richard Hughes wrote:
I'd prefer either aday or jimmac in #gnome-design as they did most of
the original designs, but Mo and Ryan also know the UX well.
Pinged jimmac and ryan on that channel.
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
Hi
On Sun, Jan 4, 2015 at 8:46 AM, Richard Hughes wrote:
We're not filtering out packages that don't qualify as applications.
GNOME Software only searches the AppStream metadata
Yes. My suggestion was to change that
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https
or dnf.conf instead of
requiring its own configuration file for shared common options. Perhaps
you can talk to Richard Hughes about that
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http
need to be closed, period. Non-sysadmin users
shouldn't be allowed to open any ports.
That won't work in a world where users *are* the sysadmins as well. Even
in a small business where one has a sysadmin, they aren't focused on
internal issues all that much. Users are expected to cope up.
Rahul
of the packages.
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
that the target audience has that much.
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
a FAQ as of late in users list, Ask Fedora
etc.
Rahul
--
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 Mon, Dec 29, 2014 at 7:36 PM, Ian Malone wrote:
Minor correction, CentOS is unbranded RHEL and Fedora is not RHEL
upstream (so far as I am aware anyway).
That is incorrect. Fedora is upstream for RHEL and therefore upstream for
CentOS as well albeit, one step removed.
Rahul
is to disable any feature
unless there is some requirement to enable it. If you request something to
be enabled, you will have to be willing to do some amount of work to make
it happen. Eric has indicated what could convince Fedora kernel
developers. Would you be willing to do that?
Rahul
. The bugzilla on it
is active.
Does that mean you are unwilling to do any work to convince the Fedora
kernel developers?
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code
.
If you aren't volunteering that's perfectly fine but other distributions
enable all sort of things that aren't enabled in Fedora and vice versa for
a number of different reasons. So that by itself isn't going to be
convincing. Sorry.
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
working with you if you are interested/have that time. Thanks!
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-0.1.4-1.fc21,hawkey-0.5.2-1.fc21
As a general recommendation, always refer to specific bug reports when
talking about issues
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code
in this list,
a quick constructive summary of the pros or cons as you see them might be
useful, perhaps as a comment in the ticket.
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
alpha and beta test phases. I think there were
cases where 'yum' said there were updates and 'dnf' didn't. And it
seemed like 'dnf' was slower.
http://dnf.readthedocs.org/en/latest/user_faq.html?highlight=faq#why-do-i-get-different-results-with-dnf-upgrade-vs-yum-update
Rahul
--
devel mailing
packages from updates testing? Which packages?
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
have API info
potentially exported in the environment as well. This is going to be quite
tedious to filter out but just in case you want to blacklist them, you
want to blacklist the following
NOVA_*
DO_*
APPID_*
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https
setup. IIRC, the interactions between them were pretty non obvious already.
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
itself is trivial, there are multiple components that require
coordination with several teams (Anaconda, Fedora Security team, openSSH,
GNOME etc), testing and documentation. Having FESCo review a proposal is
useful as well.
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https
unavoidable but
breaking them in an update might too problematic. I would suggest avoiding
that if we can.
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
://dl.fedoraproject.org/pub/fedora/linux/updates/20/x86_64/repodata/
right now has primary.sqllite of 12M and filelists.sqlite of 19M not
sure how you got 32K
Not sure. Probably misread something
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman
reporters understand what is that they are
testing a little better. It also helps other distributions get upstream
reviewed bug fix releases.
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org
cycle?
Rahul
--
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
Just a heads up since I have run into this twice in a span of few days. It
probably makes sense from the satsolver perspective but I found it pretty
surprising behavior.
https://bugzilla.redhat.com/show_bug.cgi?id=1154202
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https
1 - 100 of 1121 matches
Mail list logo