Hi,
after posting bug reports and patches for quite some time, I
finally decided to set up a FAS account to see how I can
help with packaging and other tasks at hand.
I believe my Linux experience started with Vanderbilt af-
ter one encounter with DJ'ing Slackware onto my system and
giving up w
Kevin Fenzi wrote:
> Today we have retired fedorahosted.org.
> Please see the following wiki page for up to date information:
> https://fedoraproject.org/wiki/Infrastructure/Fedorahosted-retirement
> * ssh pushes will direct you to the above wiki page and not complete.
> * web access will redi
Hi,
IIRC fedora-review suggested to test packages on all sup-
ported Fedora releases. So, with a larger hard disk, I want
to install Fedora 19, 20 (soon) and Rawhide and throw in
(recent) Debian and Ubuntu as well. As my notebook doesn't
support VMs, I'm interested in best practices for partitio
Michael Catanzaro wrote:
>> Yes. This makes it work. Thanks a lot.
> Then it was probably broken by this update:
> https://bodhi.fedoraproject.org/updates/FEDORA-2016-606ca05253
The "LIBGL_DRI3_DISABLE=1" workaround fixed it for me as
well (running Iceweasel on a remote Debian box from a loc
Dennis Gilmore wrote:
> […]
> Cloud
> -
> We are working hard to make Fedora the best platform for containerized
> applications, from base Fedora container images to a full-featured
> platform as a service to run and manage them. To meet this goal, we are
> packaging OpenShift Origin so it
Chris Murphy wrote:
> I've been seeing this since clean installing Fedora 30. I don't recall
> ever seeing it before, including on a Fedora 29 -> Fedora 30 upgraded
> system (is now the clean installed system).
> [chris@flap ~]$ man rpm | grep -C 10 rpmverbosity
> :176: warning [p 3, 0.8i]: cann
Mattia Verga wrote:
> […]
> If the change is approved, if you not believe in who proposed the
> metrics good faith, if you don't want to send your metrics, if you don't
> believe that setting a simple switch to OFF will make you safe, well,
> goodbye. There are plenty of other linux distributions
Solomon Peachy wrote:
>> But with that knowledge comes the ability to work for a va-
>> riety of organizations who will spend many resources on
>> nudging their users to behave in a way that is not necessar-
>> ily in their best interests.
> What does "a developer's ability to choose who they wor
I wrote a very long time ago:
>> I've been seeing this since clean installing Fedora 30. I don't recall
>> ever seeing it before, including on a Fedora 29 -> Fedora 30 upgraded
>> system (is now the clean installed system).
>> [chris@flap ~]$ man rpm | grep -C 10 rpmverbosity
>> :176: warning [p
Kevin Kofler wrote:
>> This is not helpful in the slightest and the tone is not appreciated at
>> all.
> Well, I have been arguing against this exception (exempting prebuilt
> autotools output) from the "no prebuilt blobs" rule for years, and it
> saddens me that something like this had to happen
Zbigniew Jędrzejewski-Szmek wrote:
> […]
>> - use dynamic buildrequires to detect what plugins are needed
> My problem is that the binary is linked to the libpython3.12.so shared
> library… The detection part is easy, the hard part is how to have the
> binary work when the shared lib is not ins
John Reiser wrote:
>> New projection when we will be finished is 2025-04-06 (+5
>> days from last report). Pure linear approximation.
> Such a linear approximation, based on the entire tracked history,
> is the second worst possible estimate. (The worst possible estimate
> is the output of a r
Vít Ondruch wrote:
%patch otoh (now) is a regular (though internally
implemented) macro that is expanded with other macros
and though can be used in other macros and expressions.
>>> Do I read correctly that we can now use `%patch` in
>>> e.g. `%check` section? Interesting. Is thi
Kevin Fenzi wrote:
> […]
I really don't understand why we do this "batched" thing to begin with.
>>> To reduce the constant flow of updates that are very minor or affect
>>> very few mixed in with the major updates that affect lots of people and
>>> are urgent.
>> But the users were alrea
Igor Gnatenko wrote:
> […]
>> I was not fully aware of this and I've personally hit this difficulty
>> not on my proposal of the remove hicolor icon caches but on proposing,
>> for example, OpenIPMI or readline changes.
>> Most of my changes were by those packages maintainers simple discarded
>>
Tomasz Kłoczko wrote:
> […]
> This is like with with problems on taking care of the production issues or
> faults.
> Always needs to be someone who is controlling whole situation but this person
> does not need to to person doing all OS, HW, app, db related things which
> needs to be
> change
Tomasz Kłoczko wrote:
> […]
> Who said that I'm demanding something?
> Look one more time on https://pagure.io/packaging-committee/issue/736
> Igor took this tasks VOLUNTARILY and started working on necessary specs
> before I've delivered batch of patches.
> When I found that number of already
Greg Hellings wrote:
> I have a package that includes a group of Ansible playbooks embedded into a
> Python module. The playbooks include a number of templates that are designed
> to be
> uploaded into remote systems, templated out with appropriate variables, and
> then executed on the remote
"Martin Gansser" wrote:
> when compiling qarte-4.4.0 with this spec file
> https://martinkg.fedorapeople.org/Packages/test/qarte.spec
> '[' noarch = noarch ']'
> + case "${QA_CHECK_RPATHS:-}" in
> + /usr/lib/rpm/check-buildroot
> + /usr/lib/rpm/brp-compress
> + /usr/lib/rpm/brp-strip-static-arc
Josh Boyer wrote:
> I am looking for challenges for upcoming year - what I and my team should
> enhance. I have some ideas, but I want to hear
> yours.
> What you - as Fedora packager - find most time consuming on packaging?
> Where you will welcome more simplicity or automation?
> Deciphe
Hedayat Vatankhah wrote:
> […]
> Yes, but even if I'm forced to download locally, it is much
> better than being forced to upload it again. (Also, note
> that the current process doesn't prevent MITM if it happens
> when I download the source).
> Also, it is easier to schedule the download for a
Hi,
pytz has a Makefile in its package repository with the con-
tents
(https://src.fedoraproject.org/rpms/pytz/blob/master/f/Makefile):
| # Makefile for source rpm: pytz
| # $Id$
| NAME := pytz
| SPECFILE = $(firstword $(wildcard *.spec))
| define find-makefile-common
| for d in common ../common
Adam Jackson wrote:
>> I searched a bit in the wiki, and my sense is that at some
>> point in the past packages were maintained in a CVS reposi-
>> tory with Makefiles and that those have been replaced by Git
>> repositories and fedpkg.
>> Is that correct? Can such a Makefile then be deleted or
Adam Williamson wrote:
>> I tried to merge together all the changes we were facing during the
>> last time with regards to Changes Policy & Fedora Release Life Cycle.
>> The outcome is available in [1] and [2]. Before I will ask FESCo for a
>> review, I would like to ask anyone who is interested
Przemek Klosowski wrote:
> In MediaWiki, revisions compared in a diff do not need to
> belong to the same article. So for example, to compare the
> current revision of...(488139) to the current revision of
> ...(505754), you can use the URL
> https://fedoraproject.org/w/index.php?diff=505754&ol
James Hogarth wrote:
> […]
> FIrst thing when I fired up my test harness was that F28 has changed,
> and thus broken, kickstart for the user option compared to a standard
> minimal that worked going back to F22 and EL7 so that had to be
> debugged and fixed ... done
> Next things is the ansible
Todd Zullinger wrote:
> […]
> For example, the rpmlint's .gitignore contains the
> following¹:
> /*.rpm
> /results_rpmlint/
> /rpmlint-*/
> /rpmlint-*.tar.gz
> […]
Apropos: Many .gitignores only reference the source files,
i. e. not /results_${name} or /${name}-*.rpm. Therefore I
usually add
Todd Zullinger wrote:
> […]
> In case it's helpful (and not better documented elsewhere),
> it's possible to rename your existing local master branch to
> rawhide and adjust the upstream tracking branch.
> In a typical dist-git clone from the rpms tree, you'd do
> this:
> git fetch && git
Hi,
using "%forgemeta" with the "-i" option causes debug infor-
mation to be output which leads to %changelog entries being
garbled:
| [tim@passepartout ~/.cache/rpm-specs]$ grep -l '^.*%forgemeta.\+$' *.spec |
xargs -r fgrep 'Packaging variables read or set by %forgemeta'
| ddiskit.spec:* Tue J
Otto Urpelainen wrote:
> […]
> Like I said, I am not expert in forge macros, so if anybody thinks that
> my edit removal was a bad idea, wiki has an undo button.
Thanks!
Tim
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send
Kevin Kofler via devel wrote:
>> I don't think "documentation is harder to keep up to date there" is right,
> Well, I guess it does not apply that much to the pages which were already in
> an ACL-locked namespace, in particular, the packaging guidelines that can
> only be edited by FPC. I cannot
Kevin Fenzi wrote:
> […]
> The purpose here is to make the Fedora project a more welcoming place to
> people who _do_ find those terms unwelcome. That doesn't mean everyone
> does. It means we want to be welcoming and not jerks.
^
> I'm person
Miro Hrončok wrote:
> […]
>> 2. change %check not to rely on unpackaged files in buildroot
> That one is non-trivial and depends on the reason it is needed.
> For example, what is common for Python "namepsace" packages, e.g.
> pkg_name.foo.
> 1) We want to test installed files, not what is i
33 matches
Mail list logo
