Dne 10. 01. 23 v 23:44 Richard W.M. Jones napsal(a):
On Tue, Jan 10, 2023 at 02:13:37PM -0500, David Cantrell wrote:
https://pagure.io/fesco/issue/2870
https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5
This change proposal has been under discussion and revision for a while. A
lot of
Hi Folks,
> On Tue, Jan 10, 2023 at 11:12:22PM +0800, 孙海勇 wrote:
> > I want to add LoongArch to the official Fedora support architecture,
>
> This is really cool -- welcome, and I'd love to help make sure you succeed!
>
> > I'm currently a newbie in the Fedora community, so I need help from
> >
All dependent packages have successfully rebuilt in COPR and will be
completed in a side tag.
The following dependencies will be rebuilt:
OpenImageIO
usd
blender
krita
luxcorerender
Thanks,
Richard
___
devel mailing list --
https://bugzilla.redhat.com/show_bug.cgi?id=2159571
Upstream Release Monitoring
changed:
What|Removed |Added
Summary|perl-Email-Stuffer-0.019 is |perl-Email-Stuffer-0.020
On Tue, Jan 10, 2023 at 7:17 PM Fabio Valentini wrote:
> Speaking for myself, the only way in which the _FORTIFY_SOURCE change
> impacted my opinion on -fno-omit-frame-pointers is that it made me
> think about it again, and that the level of scrutiny myself - and
> other members of FESCo - had
On Tue, Jan 10, 2023 at 09:15:41PM -0500, Siddhesh Poyarekar wrote:
...snip...
>
> Finally, another voting member commented, this time on the re-vote
> ticket[1], again indicating that the reason for the revote is the
> misdirection in the _FORTIFY_SOURCE proposal discussion.
Just to set the
On Tue, Jan 10, 2023 at 4:31 PM Zbigniew Jędrzejewski-Szmek
wrote:
> That description assumes that FESCo members are preschoolers who are
> easy to trick and also need to be reminded who said what every day.
> That's certainly not the case. The objections against the proposal
> were made very
On Tue, Jan 10, 2023 at 06:00:59PM -0600, Michael Catanzaro wrote:
> On Tue, Jan 10 2023 at 03:19:10 PM -0800, Kevin Fenzi
> wrote:
> > Is there something wrong with that approach that I am not understanding?
>
> No, I don't think you're missing anything. That should work fine for
> PackageKit.
The following Fedora EPEL 7 Security updates need testing:
Age URL
6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-afa80a1455
cacti-1.2.23-1.el7 cacti-spine-1.2.23-1.el7
5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-96ef72f1b2
viewvc-1.1.30-1.el7
4
https://bugzilla.redhat.com/show_bug.cgi?id=2157775
Fedora Update System changed:
What|Removed |Added
Status|MODIFIED|ON_QA
--- Comment #5 from
On Wed, Jan 11, 2023 at 1:59 AM Michael Catanzaro wrote:
>
> On Wed, Jan 11 2023 at 01:33:18 AM +0100, Fabio Valentini
> wrote:
> > Also, given that it is now apparently considered "allowed" to enable
> > unfiltered flathub with the "Enable third-party repositories" switch,
> > I wonder if that
https://bugzilla.redhat.com/show_bug.cgi?id=2156199
Fedora Update System changed:
What|Removed |Added
Status|ON_QA |CLOSED
Fixed In
On Wed, Jan 11 2023 at 01:33:18 AM +0100, Fabio Valentini
wrote:
Also, given that it is now apparently considered "allowed" to enable
unfiltered flathub with the "Enable third-party repositories" switch,
I wonder if that reasoning also applies to the equivalent situation
for RPMFusion repos?
On Tue, Jan 10, 2023 at 7:34 PM Ben Cotton wrote:
>
> https://fedoraproject.org/wiki/Changes/UnfilteredFlathub
>
> Note that I am processing this proposal past the deadline because 1. I
> think it could reasonably be considered a Self-Contained Change
> proposal and 2. the reasons outlined by
On Wed, Jan 11, 2023 at 12:15 AM Kevin Kofler via devel
wrote:
>
> Michael Catanzaro wrote:
> > (In particular, I doubt the _FORTIFY_SOURCE=3 change was really a major
> > consideration here.)
>
> What was, then? That was literally the only thing that has changed between
> the two diametrically
On Tue, Jan 10 2023 at 03:19:10 PM -0800, Kevin Fenzi
wrote:
Is there something wrong with that approach that I am not
understanding?
No, I don't think you're missing anything. That should work fine for
PackageKit. But of course it won't do a thing to help with for other
services that are
Zbigniew Jędrzejewski-Szmek wrote:
> That description assumes that FESCo members are preschoolers who are
> easy to trick and also need to be reminded who said what every day.
> That's certainly not the case. The objections against the proposal
> were made very clearly and they certainly weren't
On Mon, Jan 09, 2023 at 08:45:43PM +, Zbigniew Jędrzejewski-Szmek wrote:
>
> The current default is mostly arbitrary. It was just selected as a nice round
> value, in the spirit of "let's pick something large enough to be larger than
> any
> realistic process will ever need".
>
> I think
Michael Catanzaro wrote:
> (In particular, I doubt the _FORTIFY_SOURCE=3 change was really a major
> consideration here.)
What was, then? That was literally the only thing that has changed between
the two diametrically different votes.
Kevin Kofler
Michael Catanzaro wrote:
> You've previously indicated that developers should just 'dnf
> distro-sync' to an alternative Fedora that has frame pointers, as if
> building two alternate versions of Fedora, one for developers and one
> for users, is a reasonable thing to do. The cost of this is just
On Tue, Jan 10, 2023 at 02:13:37PM -0500, David Cantrell wrote:
> https://pagure.io/fesco/issue/2870
> https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5
>
> This change proposal has been under discussion and revision for a while. A
> lot of work has gone in to this plan to minimize the
Hi,
Porting Fedora to a new architecture is quite a challenge but a lot of
fun. It sounds as if you've made a lot of progress already. A few
thoughts from the Fedora/RISC-V effort ...
(1) Cross-compiling RPMs (eg. from x86-64 to LoongArch) isn't really
useful. Almost any significantly complex
On 10/01/2023 20:13, David Cantrell wrote:
https://pagure.io/fesco/issue/2870
https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5
This change proposal has been under discussion and revision for a while. A
lot of work has gone in to this plan to minimize the disruption. Still, dnf
is a
On Tue, Jan 10, 2023 at 4:58 PM Vitaly Zaitsev via devel
wrote:
>
> On 10/01/2023 19:33, Ben Cotton wrote:
> > In the graphical software manager app, Flathub
> > packages will only be selected by default when no Fedora package is
> > available.
>
> Thanks for implementing that. Looks good for me
On Tue, Jan 10, 2023 at 11:48 AM Miro Hrončok wrote:
> On 10. 01. 23 13:52, Richard Shaw wrote:
> > Second, how exactly are you building the package?
> > Looking at [1], you used "Source Type: SRPM or .spec file upload".
> > How was it generated?
> >
> > [1]
>
https://bugzilla.redhat.com/show_bug.cgi?id=2159835
Bug ID: 2159835
Summary: perl-IO-Zlib-1.14 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: perl-IO-Zlib
Keywords: FutureFeature, Triaged
On 10/01/2023 19:33, Ben Cotton wrote:
In the graphical software manager app, Flathub
packages will only be selected by default when no Fedora package is
available.
Thanks for implementing that. Looks good for me now.
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
On Tue, Jan 10, 2023 at 08:30:25AM -0500, Siddhesh Poyarekar wrote:
> On Tue, Jan 10, 2023 at 3:05 AM Zbigniew Jędrzejewski-Szmek
> wrote:
> > Exactly, you're just confirming what I wrote above.
> >
> > A "vote being rigged" means that either the people who should be allowed to
> > vote
> >
On 10. 01. 23 20:41, Kevin Kofler via devel wrote:
So FESCo is willing to prevent this from happening again in the future, but
NOT to remedy the existing wrongdoing?
Would you prefer if we ignored this altogether?
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
On 1/10/23 2:25 PM, Hans de Goede wrote:
ATM there is no replacement for uvcdynctrl which is still necessary for
some Logitech webcams. uvcdynctrl uses a userspace database to map
some Logitech custom control GUIDs to standard v4l2-controls.
This allows various extra functionality on Logitech
On Tue, Jan 10, 2023 at 5:35 AM wrote:
>
> You are kindly invited to the meeting:
>Prioritized bugs and issues on 2023-01-11 from 10:00:00 to 11:00:00
> America/Indiana/Indianapolis
>At fedora-meetin...@irc.libera.chat
>
> More information available at:
>
Hi Michael,
On 1/10/23 18:04, Michael Cronenworth wrote:
> Hi all,
>
> Unless someone speaks up in the next week I am going to retire the
> libwebcam[1] package.
>
> Background: Some of the first USB web cameras using the "UVC" protocol needed
> a user-space driver for controlling the
Hi,
On 1/10/23 20:48, Kevin Kofler via devel wrote:
> Hans de Goede wrote:
>> lua-5.4.4-4.fc37 in F37 release provides both:
>>
>> liblua-5.3.so()(64bit)
>> liblua-5.4.so()(64bit)
>>
>> aka both of:
>>
>> /usr/lib64/liblua-5.3.so
>> /usr/lib64/liblua-5.4.so
>
> This was a compatibility hack that
Hello everyone!
Does anyone know how to contact Juston Li (jhli)? I have tried to reach out via
email but have not received a response.
https://bugzilla.redhat.com/show_bug.cgi?id=2159807
--
Ali Erdinc Koroglu
Linux OS Systems Engineering
___
devel
On Tue, Jan 10 2023 at 01:12:35 AM +0100, Kevin Kofler via devel
wrote:
For speed:
https://valgrind.org/info/tools.html#cachegrind
or
https://valgrind.org/info/tools.html#callgrind
with (in both cases)
https://apps.kde.org/kcachegrind/
For memory (RAM) usage:
Simo Sorce wrote:
> Soname breakage should not happen in stable releases...
There are exceptions, including but not limited to security updates, which
is relevant for Lua.
> liblua should be rebuilt to provide the older so name and if not
> possible with the new code, reverted back via epoch
On Mon, Jan 9 2023 at 06:54:09 PM +0100, Florian Weimer
wrote:
No one spoke out when the tools team was called untrustworthy on the
FESCo ticket.
That was one of my comments. [1] I should have worded that more
carefully, but didn't because I was very frustrated. I apologize. What
I meant
Hans de Goede wrote:
> lua-5.4.4-4.fc37 in F37 release provides both:
>
> liblua-5.3.so()(64bit)
> liblua-5.4.so()(64bit)
>
> aka both of:
>
> /usr/lib64/liblua-5.3.so
> /usr/lib64/liblua-5.4.so
This was a compatibility hack that was accidentally left enabled:
Miro Hrončok wrote:
> * ACTION: bcotton to make a proposal on the mailing list to explicitly
> require full resubmission of rejected proposals (and then bring it
> to a FESCo ticket once discussion has happened) (mhroncok,
> 18:36:36)
So FESCo is willing to prevent this from happening again in
On Tue, 2023-01-10 at 20:29 +0100, Hans de Goede wrote:
> Hi,
>
> lua-5.4.4-4.fc37 in F37 release provides both:
>
> liblua-5.3.so()(64bit)
> liblua-5.4.so()(64bit)
>
> aka both of:
>
> /usr/lib64/liblua-5.3.so
> /usr/lib64/liblua-5.4.so
>
> but the recent update to lua-libs-5.4.4-7.fc37 only
Hi,
On Monday, 2021-10-04 13:03:27 -0400, Matthew Miller wrote:
> But beyond that: What other things might be limits? Are there key bits of
> the distro which don't build yet?
Fwiw, I learned just yesterday that apparently to stay on the cheap side
they underspecified RISC-V FPU to omit some
Hi,
lua-5.4.4-4.fc37 in F37 release provides both:
liblua-5.3.so()(64bit)
liblua-5.4.so()(64bit)
aka both of:
/usr/lib64/liblua-5.3.so
/usr/lib64/liblua-5.4.so
but the recent update to lua-libs-5.4.4-7.fc37 only provides:
liblua-5.4.so()(64bit)
/usr/lib64/liblua-5.4.so
And the same appears
https://pagure.io/fesco/issue/2870
https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5
This change proposal has been under discussion and revision for a while. A
lot of work has gone in to this plan to minimize the disruption. Still, dnf
is a core piece of software and we want to make
===
#fedora-meeting: FESCO (2023-01-10)
===
Meeting started by Eighth_Doctor at 17:00:24 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting/2023-01-10/fesco.2023-01-10-17.00.log.html
.
Meeting
https://fedoraproject.org/wiki/Changes/UnfilteredFlathub
Note that I am processing this proposal past the deadline because 1. I
think it could reasonably be considered a Self-Contained Change
proposal and 2. the reasons outlined by Mattias in another thread:
On Tue, Jan 10, 2023 at 12:53 PM Stephen Gallagher wrote:
>
> I agree, this should be fine to consider. We still should give it a
> week in the devel list before voting on it. I haven't seen the
> official announcement email go out yet.
It has now!
https://fedoraproject.org/wiki/Changes/UnfilteredFlathub
Note that I am processing this proposal past the deadline because 1. I
think it could reasonably be considered a Self-Contained Change
proposal and 2. the reasons outlined by Mattias in another thread:
On Tue, Jan 10, 2023 at 12:00 PM Neal Gompa wrote:
>
> On Tue, Jan 10, 2023 at 11:39 AM Matthias Clasen wrote:
> >
> > https://fedoraproject.org/wiki/Changes/UnfilteredFlathub
> >
> > Before xmas, when the deadline for system-wide changes came near,
> > I flipped this change proposal to the
On 10. 01. 23 13:52, Richard Shaw wrote:
Second, how exactly are you building the package?
Looking at [1], you used "Source Type: SRPM or .spec file upload".
How was it generated?
[1] https://copr.fedorainfracloud.org/coprs/hobbes1069/OIIO/build/5210045/
Most of the issues are resolved now. There is one remaining ticket [0]
that is returning 500 on branch creation. I will continue investigation
on this ticket tomorrow.
I'm sorry for the rough start.
On behalf of CPE Team,
Michal
[0] - https://pagure.io/releng/fedora-scm-requests/issue/50370
Most of the issues are resolved now. There is one remaining ticket [0]
that is returning 500 on branch creation. I will continue investigation
on this ticket tomorrow.
I'm sorry for the rough start.
On behalf of CPE Team,
Michal
[0] - https://pagure.io/releng/fedora-scm-requests/issue/50370
The documentation would need to be updated in multiple places, but I
didn't know about this one. Thanks for sharing.
Michal
On 10. 01. 23 14:08, Richard Shaw wrote:
On Tue, Jan 10, 2023 at 5:26 AM Michal Konecny
wrote:
Hi everyone,
this automation is now in place and new SCM
On Tue, 10 Jan 2023 at 11:55, Stuart S wrote:
> I've just tried this for Fed 35 >> Fed 37
>
> Got the following errors
>
> Problem: conflicting requests
> - nothing provides module(platform:f35) needed by module
> php:remi-7.4:20230104141955:.x86_64
>
You have an outside module
Hi all,
Unless someone speaks up in the next week I am going to retire the libwebcam[1]
package.
Background: Some of the first USB web cameras using the "UVC" protocol needed a
user-space driver for controlling the hardware features. Logitech developed the
libwebcam library as an interface
On Tue, Jan 10, 2023 at 11:48 AM Neal Gompa wrote:
>
> Following is the list of topics that will be discussed in the
> FESCo meeting Tuesday at 18:00UTC in #fedora-meeting on
> irc.libera.chat.
This is, in fact, at 17:00 UTC. I missed updating this on my local
template. Sorry.
--
Neal Gompa
On Tue, Jan 10, 2023 at 11:39 AM Matthias Clasen wrote:
>
> https://fedoraproject.org/wiki/Changes/UnfilteredFlathub
>
> Before xmas, when the deadline for system-wide changes came near,
> I flipped this change proposal to the ChangePageReadyForWrangler category,
> and thereby send it to
On Tue, Jan 10, 2023 at 11:13 PM 孙海勇 wrote:
>
> Hi everyone,
>
> I am Sun Haiyong, from China. I want to port Fedora for the LoongArch
> architecture.
> LoongArch is a RISC ISA released by Loongson Technology Corporation Limited,
> and has supported a series of (Binutils, GCC, Linux, Glibc, LLVM,
Following is the list of topics that will be discussed in the
FESCo meeting Tuesday at 18:00UTC in #fedora-meeting on
irc.libera.chat.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2023-01-10 17:00 UTC'
Links to all issues to be
https://fedoraproject.org/wiki/Changes/UnfilteredFlathub
Before xmas, when the deadline for system-wide changes came near,
I flipped this change proposal to the ChangePageReadyForWrangler category,
and thereby send it to neverneverland, since the correct category is
ChangeReadyForWrangler :(
I've just tried this for Fed 35 >> Fed 37
Got the following errors
Problem: conflicting requests
- nothing provides module(platform:f35) needed by module
php:remi-7.4:20230104141955:.x86_64
Error:
Problem 1: package php-pecl-imagick-im6-3.7.0-1.fc35.remi.7.4.x86_64 requires
On Tue, Jan 10, 2023 at 11:12:22PM +0800, 孙海勇 wrote:
> I want to add LoongArch to the official Fedora support architecture,
This is really cool -- welcome, and I'd love to help make sure you succeed!
> I'm currently a newbie in the Fedora community, so I need help from
> community developers,
On 10. 01. 23 0:44, Kevin Kofler via devel wrote:
Miro Hrončok wrote:
Considering the mass rebuild is happening really soon, I feel like
repeating the vote later is not helpful, but if people want to, we can
surely run the vote again. However, I am confident the result will be the
same.
With
V Wed, Dec 07, 2022 at 04:31:36PM -0500, Stephen Gallagher napsal(a):
> On Wed, Dec 7, 2022 at 8:40 AM Petr Pisar wrote:
> ...
> > As you can see, there are no separate documents for modules and default
> > streams. Everything is kept inside one document. That enables
> > properties (e.g.
Dear all,
You are kindly invited to the meeting:
EPEL Steering Committee on 2023-01-11 from 16:00:00 to 17:00:00 US/Eastern
At fedora-meet...@irc.libera.chat
The meeting will be about:
This is the weekly EPEL Steering Committee Meeting.
A general agenda is the following:
#topic aloha
On Tue, Jan 10, 2023 at 10:13 AM 孙海勇 wrote:
>
> Hi everyone,
>
> I am Sun Haiyong, from China. I want to port Fedora for the LoongArch
> architecture.
> LoongArch is a RISC ISA released by Loongson Technology Corporation Limited,
> and has supported a series of (Binutils, GCC, Linux, Glibc, LLVM,
On Tue, Jan 10, 2023 at 8:14 AM David Howells wrote:
> Also, the isl package was split out from gcc so that cross-gcc could use it
> also, but gcc now seems to be carrying its own isl package of a different
> version (0.12.2 rather than 0.16.1). Do we still build with isl support or
> could this
V Wed, Dec 07, 2022 at 02:45:28PM -, Daniel Alley napsal(a):
>
> In practice I am not certain that Satellite (and similar tools) can prefer
> the XML metadata precisely because it is cut down, so in repos which contain
> both Yaml and XML metadata it will not be possible to recreate the
V Wed, Dec 07, 2022 at 02:43:32PM +0100, Ewoud Kohl van Wijngaarden napsal(a):
> On Wed, Dec 07, 2022 at 02:23:18PM +0100, Petr Pisar wrote:
> > Those who should be concerned most are DNF5 developers and relengs producing
> > composes.
>
> There are third party repositories which also publish
I wonder if we should drop the cloog package from Fedora. It was separated
from gcc so that both gcc and cross-gcc could use it. However neither of them
now do.
Also, the isl package was split out from gcc so that cross-gcc could use it
also, but gcc now seems to be carrying its own isl package
Hi everyone,
I am Sun Haiyong, from China. I want to port Fedora for the LoongArch
architecture.
LoongArch is a RISC ISA released by Loongson Technology Corporation Limited,
and has supported a series of (Binutils, GCC, Linux, Glibc, LLVM, QEMU,
etc.)
core open source projects.
Currently,
On Mon, Jan 09, 2023 at 10:08:11PM +0100, Mark Wielaard wrote:
> > ... and I won't quote all of that, but looking at
> > https://docs.fedoraproject.org/en-US/fesco/#_ticket_policy...
> > I don't see any violations, either in the letter or the spirit of what is
> > written.
[...]
> It does feel to
I have a roundabout way to make COPR and rpmautospec work with any git repo :)
1. Create a new COPR project
2. Add a new COPR package with source type Custom
- Script
#! /bin/sh -x
git clone
cd
spectool -g
#other stuff you need to prepare
rpmautospec process-distgit
- Build dependencies:
On Mon, Jan 9 2023 at 11:04:11 AM +0100, Lennart Poettering
wrote:
That said: dumping core is potentially extremely expensive (web
browsers have gigabytes of virtual memory that we might end up
processing and compressing). Quite often the stuff that is slow when
exiting is also the stuff that
https://bugzilla.redhat.com/show_bug.cgi?id=2157099
Bug 2157099 depends on bug 2157628, which changed state.
Bug 2157628 Summary: Review Request: perl-DateTime-HiRes - Create DateTime
objects with sub-second current time resolution
https://bugzilla.redhat.com/show_bug.cgi?id=2157628
Am Dienstag, 10. Jänner 2023 08:25:27 CET schrieb Zbigniew
Jędrzejewski-Szmek:
On Mon, Jan 09, 2023 at 11:53:17PM +0100, Kevin Kofler via devel wrote:
No, the result is NOT why I got the impression that the vote
was rigged. The way that result was obtained is.
Exactly, you're just confirming
On Tue, Jan 10, 2023 at 3:05 AM Zbigniew Jędrzejewski-Szmek
wrote:
> Exactly, you're just confirming what I wrote above.
>
> A "vote being rigged" means that either the people who should be allowed to
> vote
> couldn't, or that people who are not allowed to vote did, or that voters were
>
On Tue, 10 Jan 2023 at 04:41, Sebastian Albrecht <
sebastian.albre...@agido.com> wrote:
> Hi Dan,
> thank you for answering. Is there a known reason, why it was removed for
> the x86_64 arch but not for aarch64? Because i can still find it there.
>
>
aarch64 is a 'dead' release for EL-7 with no
On Tue, Jan 10, 2023 at 5:26 AM Michal Konecny wrote:
> Hi everyone,
>
> this automation is now in place and new SCM requests will be processed
> automatically. If you find any issue with the automation, please report it
> to toddlers issue tracker [0].
>
> On behalf of CPE Team,
> Michal
>
>
On Tue, Jan 10, 2023 at 5:11 AM David Abdurachmanov
wrote:
>
> On Mon, Jan 9, 2023 at 3:22 PM Josh Boyer wrote:
> >
> > On Mon, Jan 9, 2023 at 9:15 AM Neal Gompa wrote:
> > >
> > > On Mon, Jan 9, 2023 at 8:47 AM Josh Boyer
> > > wrote:
> > > >
> > > > On Sun, Jan 8, 2023 at 2:42 AM David
Hi everyone,
after deployment we had some issues with API tokens for
src.fedorapoject.org and pagure.io. Those issues are now solved.
Only one issue remains and that is missing list of epel9 packages on
https://infrastructure.fedoraproject.org/repo/json
We are currently working on that.
All
Hi everyone,
this automation is now in place and new SCM requests will be processed
automatically. If you find any issue with the automation, please report
it to toddlers issue tracker [0].
On behalf of CPE Team,
Michal
[0] - https://pagure.io/fedora-infra/toddlers/issues
On 08. 12. 22
Hi everyone,
after deployment we had some issues with API tokens for
src.fedorapoject.org and pagure.io. Those issues are now solved.
Only one issue remains and that is missing list of epel9 packages on
https://infrastructure.fedoraproject.org/repo/json
We are currently working on that.
All
On Tue, Jan 10, 2023 at 1:16 AM Zbigniew Jędrzejewski-Szmek <
zbys...@in.waw.pl> wrote:
> On Mon, Jan 09, 2023 at 09:37:44PM -0600, Richard Shaw wrote:
> > Now I'm getting bit by the rpmautospec and COPR issue.
>
> Please be more precise. How are you building the rpms?
>
The SRPMS? I'm using
On Tue, Jan 10, 2023 at 4:39 AM Miroslav Suchý wrote:
>
> Dne 10. 01. 23 v 9:29 Vitaly Zaitsev via devel napsal(a):
> > On 10/01/2023 08:16, Zbigniew Jędrzejewski-Szmek wrote:
> >> If rpmautospec is used in COPR, and the build is started in a
> >> compatible way, the release field should be the
jplesnik merged a pull-request against the project: `perl-HTTP-Daemon-SSL` that
you are following.
Merged pull-request:
``
Fix for IO::Socket::SSL 2.078
``
https://src.fedoraproject.org/rpms/perl-HTTP-Daemon-SSL/pull-request/1
___
perl-devel mailing
On 10/01/2023 10:38, Miroslav Suchý wrote:
But in your case you should rather use DistGit instead of SCM method
(the first row of tabs):
https://docs.pagure.org/copr.copr/user_documentation.html#distgit
Looks interesting. Thank you very much for the info. I will use it in
the future.
--
https://bugzilla.redhat.com/show_bug.cgi?id=2157775
Fedora Update System changed:
What|Removed |Added
Status|ASSIGNED|MODIFIED
--- Comment #4 from
This is incredible, thank you all so much for the work!
On Tue, Jan 10, 2023, 5:26 AM Michal Konecny wrote:
> Hi everyone,
>
> this automation is now in place and new SCM requests will be processed
> automatically. If you find any issue with the automation, please report it
> to toddlers issue
Hi everyone,
this automation is now in place and new SCM requests will be processed
automatically. If you find any issue with the automation, please report
it to toddlers issue tracker [0].
On behalf of CPE Team,
Michal
[0] - https://pagure.io/fedora-infra/toddlers/issues
On 08. 12. 22
On Tue, Jan 10, 2023 at 5:11 AM David Abdurachmanov
wrote:
>
> On Mon, Jan 9, 2023 at 3:22 PM Josh Boyer wrote:
> >
> > On Mon, Jan 9, 2023 at 9:15 AM Neal Gompa wrote:
> > >
> > > On Mon, Jan 9, 2023 at 8:47 AM Josh Boyer
> > > wrote:
> > > >
> > > > On Sun, Jan 8, 2023 at 2:42 AM David
On Mon, Jan 9, 2023 at 3:22 PM Josh Boyer wrote:
>
> On Mon, Jan 9, 2023 at 9:15 AM Neal Gompa wrote:
> >
> > On Mon, Jan 9, 2023 at 8:47 AM Josh Boyer wrote:
> > >
> > > On Sun, Jan 8, 2023 at 2:42 AM David Abdurachmanov
> > > wrote:
> > > >
> > > > On Sun, Jan 8, 2023 at 2:28 AM Jeff Law
* Vitaly Zaitsev via devel:
> On 10/01/2023 08:16, Zbigniew Jędrzejewski-Szmek wrote:
>> If rpmautospec is used in COPR, and the build is started in a
>> compatible way, the release field should be the same as in koji.
>
> Steps to reproduce:
>
> 1. Create a new COPR project.
> 2. Add a new COPR
Hi Dan,
thank you for answering. Is there a known reason, why it was removed for the
x86_64 arch but not for aarch64? Because i can still find it there.
BR,
Sebastian.
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe
Dne 10. 01. 23 v 9:29 Vitaly Zaitsev via devel napsal(a):
On 10/01/2023 08:16, Zbigniew Jędrzejewski-Szmek wrote:
If rpmautospec is used in COPR, and the build is started in a
compatible way, the release field should be the same as in koji.
Steps to reproduce:
1. Create a new COPR project.
https://bugzilla.redhat.com/show_bug.cgi?id=2159569
Fedora Update System changed:
What|Removed |Added
Status|MODIFIED|CLOSED
Fixed In Version|
https://bugzilla.redhat.com/show_bug.cgi?id=2159569
Fedora Update System changed:
What|Removed |Added
Status|NEW |MODIFIED
--- Comment #2 from
On Mo, 09.01.23 15:18, Simo Sorce (s...@redhat.com) wrote:
> If I remember correctly the claim was that umh is robust if the user
> space fails and just terminates. As then the kernel know user space is
> gone, whether it got the data it needed or not and can stop waiting.
>
> While messages may
OLD: Fedora-Rawhide-20230108.n.1
NEW: Fedora-Rawhide-20230109.n.0
= SUMMARY =
Added images:0
Dropped images: 4
Added packages: 1
Dropped packages:1
Upgraded packages: 29
Downgraded packages: 0
Size of added packages: 22.08 KiB
Size of dropped packages:
On 10/01/2023 08:16, Zbigniew Jędrzejewski-Szmek wrote:
If rpmautospec is used in COPR, and the build is started in a
compatible way, the release field should be the same as in koji.
Steps to reproduce:
1. Create a new COPR project.
2. Add a new COPR package with building from SCM:
- Type -
99 matches
Mail list logo
