https://ausil.fedorapeople.org/Fedora-Workstation-Live-aarch64-40-20240417.n.0.iso
is the last ISO built for a nightly compose for F40. It gives you the
prerelease warning but is very close to GA.
Dennis
On Wed, May 22, 2024 at 7:40 AM Adam Williamson
wrote:
>
> On Tue, 2024-05-21 at
e sole maintainer of package aunit.
So, would you be willing to have a look at the PR and consider it for updating
the package?
- Dennis
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to de
to contact him
by email [2] but did not receive a reply.
As I have no other way to get in contact, and as the PR has been open for
months, I've decided to submit a bug [3] and post here as per Fedora guidelines
on non-responsive maintainers.
- Dennis
[1] https://src.fedoraproject.org/rpms/aunit
d it allow that. We recently had
> a discussion about adding support for creating "normal" users from
> systemd-sysusers, and the conclusion was that we can add a basic mode
> where /etc/skel is copied and the user is written to file databases.
> If people think this would be u
age
1) [ ] Language settings 2) [x] Time settings
(Language is not set.) (America/New_York timezone)
3) [x] Network configuration 4) [!] Root password
(Connected: enp1s0) (Root account is disabled)
5) [!] User creation
All of the Arm disk images use initial-setup to configure the image.
There would need to a concrete plan on how to manage the transition to
something else.
Dennis
On Tue, Nov 21, 2023 at 6:35 AM Jiri Konecny wrote:
>
> Hello everyone,
>
> We (anaconda team) are considering dis
I think it is fair to say it is a system wide change
Dennis
On Wed, Aug 2, 2023 at 1:40 PM Amit Shah wrote:
>
>
> On Wed, 2023-08-02 at 10:50 -0500, Dennis Gilmore via devel wrote:
> > Given https://fedoraproject.org/wiki/Changes/BINUTILS_GOLD and
> > https://fedoraproj
Given https://fedoraproject.org/wiki/Changes/BINUTILS_GOLD and
https://fedoraproject.org/wiki/Features/GoldLinkerDefault it seems
reasonable that to remove the feature we have a change to ensure wide
notice and documentation of the change
Dennis
On Wed, Jun 21, 2023 at 10:08 AM Amit Shah wrote
gt;
I do not understand how this is at all possible. If a build has the tag to
be stable it will show up freeze or not. it may not be in the beta compose,
but will be in the nightly composes and being tested and available there.
Dennis
Fabio
> ___
> d
nstances, the first or last results are typical. I
think it is time to say goodbye. Times are very different from what they
were when we added support.
Dennis
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le.
On Thu, Dec 22, 2022 at 5:25 AM Zbigniew Jędrzejewski-Szmek
wrote:
>
> On Wed, Dec 21, 2022 at 11:56:32AM -0600, Dennis Gilmore via devel wrote:
> > In my case, I have Network Manager config files included in my initrd
> > and bootargs to bring up the network so that I
for cloud and different use cases.
Dennis
On Tue, Dec 20, 2022 at 9:22 AM Ben Cotton wrote:
>
> https://fedoraproject.org/wiki/Changes/Unified_Kernel_Support_Phase_1
>
> This document represents a proposed Change. As part of the Changes
> process, proposals are publicly announced in o
# dnf --releasever=37 --setopt=module_platform_id=platform:f37
--enablerepo=updates-testing $(rpm -q fedora-repos-modular >/dev/null
&& echo --enablerepo=updates-testing-modular) --assumeno distro-sync
Fedora 37 - x86_64
22 MB/s |
81 MB
We do not support running 32-bit arm software on an AArch64 system. We
should look at places that suggest a 32 bit version of Fedora for a
raspberry pi and update that to use AArch64 versions. Possibly adding
a dnf plugin to all 32 bit arm systems giving users a warning that the
EOL of 32 bit arm i
On Wed, Aug 18, 2021 at 3:11 PM Florian Weimer wrote:
>
> * Dennis Gilmore:
>
> > We intentionally never looked at enabling that and always had no plans
> > to support multi-lib on Arm
>
> It's not multilib. Buildroots aren't multilib.
>
> I'm pretty sure no one
gt; I expect that 64-bit kernel bugs will get more attention upstream.
>
> > At least rpm rejects trying to install a aarch64 kernel on a 32bit
> > userspace.
>
> The host (including kojid) should probably be 64-bit, and only the
> chro
hide rebuild and until the side tagged is tagged over things are
not built against the new builds in the side tag.
Dennis
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
F
vecot team decided to deprecate "fts_squat"
+included in the dovecot core, and due to the complexity of the Solr plugin
+capabilitles, un-needed for most users.
Dennis
On Sun, Apr 25, 2021 at 10:04 AM Joan Moreau wrote:
>
> > you probably sent the same srpm
>
> No, it is a
you probably sent the same srpm,
https://koji.fedoraproject.org/koji/taskinfo?taskID=2020 builds
just fine, I did make a few changes to the spec file. with a correct
changelag entry it should pass review
Dennis
On Sun, Apr 25, 2021 at 8:58 AM Joan Moreau via devel
wrote:
>
> Same
> ./configure --with-dovecot=/usr/lib64/dovecot
>
> to:
>
> %configure --with-dovecot=/usr/lib64/dovecot
probably should actually be
%configure --with-dovecot=%{_libdir}/dovecot
Dennis
> Thanks,
> Richard
> ___
> devel maili
perhaps you should look at how ceph has dealt with a similar issue,
they set the max number of cpus based on the system ram.
https://src.fedoraproject.org/rpms/ceph/blob/rawhide/f/ceph.spec#_1246
Dennis
On Fri, Mar 26, 2021 at 7:49 PM Michel Alexandre Salim
wrote:
>
> Hi all,
>
> Th
On Mon, 2021-03-08 at 19:07 +0100, Miro Hrončok wrote:
> On 08. 03. 21 18:33, Mattia Verga via devel wrote:
> > I'm just wondering: what's the benefit of packaging Python noarch
> > projects in Fedora?
>
> You can use them as requirements for packaged applications.
>
> > I can see the reason
yum distro-sync --releasever 34
Last metadata expiration check: 0:10:11 ago on Wed 24 Feb 2021 11:55:46 AM CST.
Error:
Problem: package gnome-tour-40~beta-3.fc34.x86_64 obsoletes
gnome-getting-started-docs < 3.38.1-2 provided by
gnome-getting-started-docs-3.38.0-2.fc34.noarch
- package
conversation. I think that devel list would benefit from
having all automated reports sent to a reports-list and letting people
bring reports over when there is something to discuss. I was asked to
bring the request to the list for people to weigh in.
Thanks
Dennis
Good feedback. I'll adjust the document to integrate your suggestions.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
It would require https://bugzilla.redhat.com/show_bug.cgi?id=1768206
to be fixed. Right now the design in dnf for supporting gpg keys is
quite user hostile, especially in automated unattended use cases.
Dennis
On Mon, Nov 2, 2020 at 6:25 PM Marek Marczykowski-Górecki
wrote:
>
> Hel
This is very sad news, he was a very enthusiastic tester.
Dennis
On Sun, Aug 2, 2020 at 5:49 PM Adam Williamson
wrote:
>
> Hi, folks. I'm sad to report that Thomas Gilliard (satellit), who was a
> valued member of the QA team for many years, passed away last week. His
> wife
. It is also critical that the local nuances though
looking at what is in place on disk all the other languages are
symlinks to en_GB except for en_CA and en_US
Dennis
On Sat, Jul 18, 2020 at 7:45 AM Germano Massullo
wrote:
>
> All desktop oriented Fedora installers install on the system pa
.
- Dennis
___
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 Guidelines: https
will not work.
Dennis
___
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 Guidelines: https
io/koji/blob/master/f/builder/kojid#_544 it looks like
mock has started using different return codes and koji will need to
learn them all
Dennis
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fed
.
--
John Dennis
___
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 Guidelines: https
kind of refs, be it branches or
> tags. It still works, it's just things like 'git log' get kind of
> expensive.
koji stores the git hash for all builds, writing a script to get the
hash for a given nvr would be trivial. it just means you have to be
online to retrieve the data than being a
the system. If we disallow password logins for root, then many
> installs will be inaccessible and users will get... grumpy.
I usually ssh in and enroll my machines to my ipa server, I am not
sure how we can do that in the arm cases where we use pre-generated
images. I know I can use cockpi
ectory"
> ```
you should just run
$ docker run --rm -t fedora:30 uname -m
on all arches, we push manifest listed containers to dockerhub so that
command will work everywhere.
Dennis
> But below commands should work on your x86_64 host OS.
> As it is not officially released
for ci on mainframe.
Dennis
On Thu, Apr 4, 2019 at 4:41 PM Neal Gompa wrote:
>
> On Thu, Apr 4, 2019 at 3:27 PM Kevin Fenzi wrote:
> >
> > On 4/4/19 1:16 PM, Neal Gompa wrote:
> > > On Thu, Apr 4, 2019 at 10:02 AM Kevin Fenzi wrote:
> > >>
> > >> G
The team was able to get koji 1.17 released today. :) So, while the YUM
deprecation got moved out to F31, you may want to pull 1.17 into F30.
Cheers
-- Dennis
On Fri, Mar 1, 2019 at 3:18 PM Dennis Gregorovic wrote:
>
>
> On Fri, Mar 1, 2019 at 4:25 AM Michal Domonkos
> wrote:
On Fri, Mar 1, 2019 at 4:25 AM Michal Domonkos wrote:
> On Fri, Mar 1, 2019 at 2:24 AM Dennis Gregorovic
> wrote:
> >
> > I have an update on the koji end. The 1.17 release will not only drop
> the yum dependency, it will also have full python 3 support (except for
>
on
Tuesday. It depends on whether QE uncovers any issues in its final
testing. If we're not able to land the release on Tuesday, what is the
backup plan?
On Sat, Feb 2, 2019 at 4:33 PM Dennis Gregorovic wrote:
> I chatted with the Koji team and they are planning on having the yum
> depe
n your numbers
it looks like there is a total of 1225 srpms that have a .fc2? disttag
in them
$ ls /mnt/koji/compose/rawhide/latest-Fedora-
Rawhide/compose/Everything/source/tree/Packages/*/*fc2?.src.rpm|wc -l
1225
but people should fix the FTBFS for t
t; To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@
e koji builders are still
python2. ImageFactory is running there and needs to be same python version
as kojid (it is used as library, not separate process).
"""
On Wed, Jan 2, 2019 at 2:24 PM Dennis Gregorovic wrote:
> There has been some progress as Tomas Kopecek added py3 p
to it in the past and may be able to help.
-- Dennis
On Mon, Dec 3, 2018 at 2:02 PM Neal Gompa wrote:
> On Mon, Dec 3, 2018 at 1:39 PM Clement Verna
> wrote:
> >
> > Hi all,
> >
> > I would like to get feedbacks on the following proposal. Use OSBS to
> > build the
https://pagure.io/releng/issue/4084 its an issue that has existed for
nearly a decade and not been solved. Time was not taken to fixing it
after we disabled installing multilib by default as there was no
reports of it for years.
Dennis
El mié, 12-12-2018 a las 11:32 +0100, Florian Weimer
ity on a subset of arches. How many packages
are we talking about?
Dennis
> PROPOSAL:
> 1. make fedora-release archful
> 2. add Provides: system-architecture($arch) to fedora-release, where
> $arch is architecture name
> 3. use Requires: (foo if (system-architecture(x86_64) or
>
El lun, 26-11-2018 a las 19:44 -0500, Paul Frields escribió:
> On Mon, Nov 26, 2018 at 5:47 PM Dennis Gilmore
> wrote:
> > El lun, 26-11-2018 a las 17:14 -0500, Josh Boyer escribió:
> > > Because the people that would be tasked with doing the
> > > development are
&
I don't see an alternative. Not doing a release to focus
> on
> our tech debt seems like a good tradeoff. If there are others that
> really WANT to continue cranking the release with the tools as they
> are today... that might be something that could be pursued. I
small as possible,
our only use case was uploading to EC2 and we delivered them as part of
the release solely to make sure they were available and people could
compare what was in EC2 to what is available for verification
processes. The only other use case we considered was people downloading
and
libc-all-
langpacks is pulled into the buildroot entirely by dependencies, the
only change needed is to whatever package is pulling in glibc-all-
langpacks to no longer pull it in.
Dennis
signature.asc
Description: This is a digitally signed message part
___
ng representive I
think there needs to also be a strong focus on the other things like
Fedora CoreOS, emerging technologies (some are coverd with objectives
like IoT), as well as the other technical challenges fedora is facing.
I also know Petr has a lot on his plate already. Are we perhaps asking
El lun, 10-09-2018 a las 14:58 +, Martin Gansser escribió:
> every time I edit my account, the public ssh key is missing.
>
> the FSA public SSH-key and the key in .ssh/id_rsa.pub are the same.
Can you ssh to fedorapeople.org?
Dennis
signature.asc
Description: This is a digital
feels like an unnecessary hurdle (IMHO).
FWIW as a Python extension author and maintainer I have taken advantage
of these deubg builds, it's very useful.
If you're developing at the level of CPython you probably also have the
skill to build your own version but why?
--
John Dennis
t on all the supported
> bootloaders, but all of them have support to parse BLS fragments now.
> So we can default to install BLS files on kernel installation and
> drop
> grubby.
There is no BLS support in u-boot, how is it planned to support ARM
systems? it is not an issue for aarch64
see
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproje
> ct.org/thread/CIKK4WEF5ACVWZ6EWBKNHSKKKCDTV27C/#CIKK4WEF5ACVWZ6EWBKNH
> SKKKCDTV27C
> https://pagure.io/fedora-release/pull-request/119
> https://pagure.io/releng/issue/7293
>
> I made the changes
ther problem.
Theory will always become reality at some point. I think there is very
good reasons to keep the staggered approach to electing FESCo members.
Dennis
signature.asc
Description: This is a digitally signed message part
___
devel ma
El mar, 05-06-2018 a las 15:59 -0400, Adam Jackson escribió:
> On Tue, 2018-06-05 at 13:20 -0500, Dennis Gilmore wrote:
>
> > as part of this change I suspect we would need to make kernel
> > changes
> > to stop building a i686 kernel, and all i686 deliverables would
El mar, 05-06-2018 a las 15:59 -0400, Adam Jackson escribió:
> On Tue, 2018-06-05 at 13:20 -0500, Dennis Gilmore wrote:
>
> > as part of this change I suspect we would need to make kernel
> > changes
> > to stop building a i686 kernel, and all i686 deliverables would
what the plan is to test the 32 bit bits. they are
likely to get significantly less testing than the little they get
today.
Dennis
El lun, 04-06-2018 a las 10:35 +0200, Jan Kurik escribió:
> = Proposed System Wide Change: i686 Is For x86-64 =
> https://fedoraproject.org/wiki/C
===
#fedora-meeting: FESCO (2018-06-01)
===
Meeting started by dgilmore at 15:00:53 UTC. The full logs are
available
at
https://meetbot.fedoraproject.org/fedora-meeting/2018-06-01/fesco.2018-
06-01-15.00.log.html
.
Meeting
Following is the list of topics that will be discussed in the
FESCo meeting Friday at 15:00UTC in #fedora-meeting on
irc.freenode.net.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2018-06-01 15:00 UTC'
Links to all issues below
> > * my mock: real 0m56.595s Could not resolve host
> > * Koji:real 0m0.030s Could not resolve host
>
> And copr: real 0m40.578s Could not resolve host
>
You could try using --old-chroot the koji builders also have the
internet firewalled off. they ips that they c
On 05/01/2018 10:00 AM, Matthew Miller wrote:
It's almost Mother's Day, and that means it's time for Fedora 28,
which is officially released today.
FWIW, there is a broken link to the install documentation.
If you visit:
https://getfedora.org/en/workstation/download/
and click on
I am forwarding to devel list as Sushma was not subscribed and it was
rejected.
Dennis
- Mensaje reenviado
De: Sushma Gajanur Shivakumar <sgaja...@redhat.com>
Para: devel-annou...@lists.fedoraproject.org
Cc: Ben Breard <bbre...@redhat.com>, den...@ausil.us, Mohan
extcloud 13 from 10, you
upgrade to 11 then to 12 then finally to 13. you have to run the
upgrade process in order to keep things working. they do not support
skipping versions
Dennis
signature.asc
Description: This is a digitally signed message part
___
devel m
k into supporting
all architectures. The architecture teams can help you in getting
things working.
Dennis
signature.asc
Description: This is a digitally signed message part
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send
El vie, 16-03-2018 a las 15:19 -0700, Adam Williamson escribió:
> On Fri, 2018-03-16 at 16:04 -0400, Dennis Gregorovic wrote:
> > modules are not RPMs. I would not expect them to necessarily use
> > the same
> > format as RPMs. If we take koji out of the equation,
>
&
://pagure.io/koji/issue/851 was implemented would that
resolve the challenge you were facing? If not, it might be worth reaching
out to koji-de...@lists.fedorahosted.org and discussing it further there.
Cheers
-- Dennis
On Fri, Mar 16, 2018 at 6:21 PM, Adam Williamson <adamw...@fedoraproject.
is that we consider the N-V-R format of
modules to be a representation internal to koji and that N:S:V:C is the
format used to represent modules to users. If that means tweaking the Koji
UI we can look into that.
Cheers
-- Dennis
On Fri, Mar 16, 2018 at 3:40 PM, Randy Barlow <bowl
] or taiga[2] to be groomed, prioritised and scoped.
I have posted a blog post[3] with some of my thoughts in reflection
looking back at the last 8 or so years.
Thank you all for you support over the years and your continued support
of Mohan and the rest of the Release Engineers in Fedora.
Dennis
[1
] or taiga[2] to be groomed, prioritised and scoped.
I have posted a blog post[3] with some of my thoughts in reflection
looking back at the last 8 or so years.
Thank you all for you support over the years and your continued support
of Mohan and the rest of the Release Engineers in Fedora.
Dennis
[1
nts to
> the
> build against f27-candidate.
>
> Footnotes:
> [1] https://bugzilla.gnome.org/show_bug.cgi?id=793299
>
have you rebuilt your packages? if not yes you need to rebuild them
Dennis
signature.asc
Description: This is a digitally signed message part
___
olve this by adding glibc32 to the mass rebuild
blacklist. then it will not be rebuilt. the sources for it is
precompiled binaries so rebuilding does nothing
Dennis
signature.asc
Description: This is a digitally signed message part
___
devel mailing list -- d
nd I never want to go do that
again. We do need to make sure that as new rpm/dnf features are
supported that we have everything in place to fully support them, that
means waiting for a short period of time from being in RPM to being
something we can tell packagers to go and use.
Dennis
signature.asc
Description: This is a digitally signed message part
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
El mar, 06-03-2018 a las 17:20 +0100, Germano Massullo escribió:
> Il 06/03/2018 16:35, Dennis Gilmore ha scritto:
> > El mar, 06-03-2018 a las 15:29 +0100, Germano Massullo escribió:
> > > During package firefox-pkcs11-loader build, the following two
> > >
ules
> File not found: /builddir/build/BUILDROOT/firefox-pkcs11-loader-
> 3.13.0-2.fc27.x86_64/usr/lib64/mozilla/pkcs11-
> modules/onepinopenscpkcs11.json
noarch only builds do not have %{_lib} or %{_libdir} defined
Dennis
signature.asc
Description: This is a digitally signed message p
use it to a different purpose rather than
throwing it out.
Dennis
signature.asc
Description: This is a digitally signed message part
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
dnf update --relasever=29 distro-sync --disablerepo=* --
enablerepo=rawhide
Dennis
El sáb, 03-03-2018 a las 21:15 +, Philip Kovacs escribió:
> I would settle for knowledge of where the f29/rawhide gpg keys are
> hidden so I import them.
>
> The "To Rawhide" instructi
;
> Would be awesome if maintainers could have a look and see if they can
> make their packages pass!
>
We were supposed to make builds fail if the appstream metadata failed,
why has that not been done?
Dennis
signature.asc
Description: This is a
ame
bumps are handled in side tags because we know that the ABI will break
or a very large amount of packages will be affected. I would like us to
figure out how to deal with soname breakages in a more automated way.
It however needs people to write new tooling to be able to cope with
it, I currently do not have enough cycles to take on doing the work.
So if someone wants a project to do please come and talk to me about
it.
Dennis
signature.asc
Description: This is a digitally signed message part
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
l/pungi.global.log
>
> it probably was, but it is not obvious from the log.
>
the status of the compose can always be found in the STATUS file of the
root of the compose https://kojipkgs.fedoraproject.org/compose/rawhide/
Fedora-Rawhide-20180228.n.0/STATUS is todays for instance
Dennis
El lun, 19-02-2018 a las 10:56 +0100, Vít Ondruch escribió:
>
>
> Dne 19.2.2018 v 00:52 Dennis Gilmore napsal(a):
> > El vie, 16-02-2018 a las 12:56 +0100, Jan Kurik escribió:
> > > Proposed System Wide Change: Remove GCC from BuildRoot
> > > https
El vie, 16-02-2018 a las 12:56 +0100, Jan Kurik escribió:
> Proposed System Wide Change: Remove GCC from BuildRoot
> https://fedoraproject.org/wiki/Changes/Remove_GCC_from_BuildRoot
>
>
> Owner(s):
> * Igor Gnatenko
>
>
> Removing gcc and gcc-c++ from default buildroot in Koji and mock.
>
e past, there is a long way to go. We may even need to take a
time out in order to focus on making fundamental changes to how we
manufacture Fedora.
Dennis
signature.asc
Description: This is a digitally signed message part
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
nothing provides /usr/bin//usr/bin/python3 needed by glib2-devel-
> 2.55.2-1.fc28.x86_64
that looks like a packaging bug in glib2
Dennis
signature.asc
Description: This is a digitally signed message part
___
devel mailing list -- devel@lists.fedorapr
> Where I can find failed build? Or I must run it manually?
>
> I see the same with my "maradns". GIT shows version bump in spec,
>but there is no build in Koji.
Please submit the build in this case. If the srpm for instance failed to create
there is no task in koji. I do
and enabling Bodhi on
the 6th of March, So expect to see a 28 branched compose in about a
week from now.
Many Thanks
Dennis
[1] https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
[2] https://kojipkgs.fedoraproject.org/mass-rebuild/f28-failures.html
[3] https://kojipkgs.fedoraproject.org/mass
on the blue side of the Fence :D I am looking forward
to seeing how Fedora and CentOS can work better together
Dennis
signature.asc
Description: This is a digitally signed message part
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
led (because I can
> maintain my modules with whatever commitments I feel comfortable
> with,
> even with an EL target). And at least initially the RPM/DNF
> functionality
> should be on par with modern Fedora.
agreed.
Dennis
signature.asc
Description: This is a digi
The only way to really do this would be to make rpmfusion-release
require it. However that will mean users have to download and install
two packages to make it all work. That may break things for people who
intentionally remove gnome-software and PackageKit
Dennis
El mar, 16-01-2018 a las 18:08
ch. I'm not
> actually sure if Taskotron currently covers 32-bit ARM, though, even.
currently taskotron is x86 only. I am not sure what it would take to
extend it beyond x86, it would be a worthwhile investigation. It would
be useful to have all arches in openQA regardless of primary or
seco
Following is the list of topics that will be discussed in the
FESCo meeting Friday at 16:00UTC in #fedora-meeting on
irc.freenode.net.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2017-12-15 16:00 UTC'
Links to all issues below
El mar, 05-12-2017 a las 07:31 +, Zbigniew Jędrzejewski-Szmek
escribió:
> On Mon, Dec 04, 2017 at 12:49:48PM -0600, Dennis Gilmore wrote:
> > El vie, 10-11-2017 a las 09:12 -0500, Neal Gompa escribió:
> > > On Fri, Nov 10, 2017 at 9:04 AM, Zbigniew Jędrzejewski-Szmek
> &
e and generic-release
this is because generic-release is there just to provide an example of
how you would setup a -release package for a custom forked OS. it is
not intended to be a complete drop in for fedora-release.
Dennis
> And as long has it has a "system-presets" Provides, downs
El dom, 22-10-2017 a las 11:39 -0400, Randy Barlow escribió:
> On 10/22/2017 09:04 AM, Dennis Gilmore wrote:
> > updates does not have composes it has mashes, the behaviour is
> > expected
> > to be different, the problem boils down to the fact that if a
> > package
>
El jue, 19-10-2017 a las 19:29 +0200, Florian Weimer escribió:
> On 10/19/2017 06:42 PM, Dennis Gilmore wrote:
>
> > There is long standing 8+ year old bugs we have never gotten around
> > to
> > to ensure multilib is correct in all cases. It is unfortuantly
&g
ot over the yearsm, but since
defaulting to turning off installing multilib by default we have not
had and issues filed in years, until you asked earlier this year. we
may be able to resolve the issues with the move to use pungi for
updates pushes rather than mashing the repos.
Dennis
elopers
> in
> general? The last time I tried it, I got a permission error.
>
> Thanks,
> Florian
It is in the -pending tags, you need to be in Release Engineering to
untag from f28.
Dennis
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
ts of how we manage the ditro and update
process. It would need discussions with Release Engineering and
Infrastructre, that came with resources to support the work.
Dennis
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
I have ensured that it
is good. You would need to work with release engineering and
infrastucture to come up with some way to sign off on the code being
used.
Given that many times the big tarballs actually only have a small
amount of change. using explod
El lun, 04-09-2017 a las 12:56 -0400, Neal Gompa escribió:
> On Mon, Sep 4, 2017 at 12:33 PM, Richard Hughes <hughsi...@gmail.com>
> wrote:
> > On 4 September 2017 at 17:15, Dennis Gilmore <den...@ausil.us>
> > wrote:
> > > The correct way to deal with appst
1 - 100 of 8606 matches
Mail list logo
