Hello.
the owners of SPDX Change proposal want to have this Change as smooth as
possible. For this reason we set up Office Hours.
Do you have any questions about SPDX migration?
Do you hesitate about what steps you should take?
How to proceed with your package? We will do our best to help you.
Il 21/02/23 06:27, Robin Lee ha scritto:
> On Tue, Feb 21, 2023 at 11:14 AM Felix Wang wrote:
>> If I want to packaging a new package into Fedora repository, I did a koji
>> scratch build, which it failed on some architecture. Is there a minimum
>> architecture requirement, which builds success
* Kevin Fenzi:
> Greetings.
>
> We are running into some anoying limits on koji builds of chromium.
>
> First, since a long time ago, the koji.service file we are using has:
>
> TasksMax=infinity
>
> But yet, chromium was failing, seemingly hitting a task limit.
> "ninja: fatal: posix_spawn: Resou
On Tue, Feb 21, 2023 at 11:14 AM Felix Wang wrote:
>
> If I want to packaging a new package into Fedora repository, I did a koji
> scratch build, which it failed on some architecture. Is there a minimum
> architecture requirement, which builds successfully on some architecture
> (like x86_64?)
On 2/20/23 17:51, Richard Fontana wrote:
If anyone has
suggestions for what form such documentation could take that would be
helpful. :)
Presentation: a .ods spreadsheet with one row per identifiable hunk of software,
with columns: name, version, release, architecture(s), minimum date, maximum
If I want to packaging a new package into Fedora repository, I did a koji
scratch build, which it failed on some architecture. Is there a minimum
architecture requirement, which builds successfully on some architecture (like
x86_64?), in order to adopt the new package?
_
On Mon, Feb 20, 2023 at 7:17 PM Jilayne Lovejoy wrote:
> Let us know if you have any questions or suggestions for improvements. We've
> had two "office hours" so far with no attendees, but happy to schedule a few
> more for open discussion or questions!
We've also talked about developing more
Greetings.
We are running into some anoying limits on koji builds of chromium.
First, since a long time ago, the koji.service file we are using has:
TasksMax=infinity
But yet, chromium was failing, seemingly hitting a task limit.
"ninja: fatal: posix_spawn: Resource temporarily unavailable"
in
Thanks to all the package maintainers who have been diligently updating
their packages to SPDX identifiers! Here are a few interesting stats:
- 160 issues in the Fedora-license-data, which has resulted in 34 new
license/TOML files being added to the data, and 18 more ready to be
added
https:/
Your analysis of grpc/grpc-cpp and gtest seems reasonable to me. Thanks for
having a look at these cases.
– Ben
On Mon, Feb 20, 2023, at 4:28 PM, Gordon Messmer wrote:
> On 2023-02-20 12:57, Ben Beasley wrote:
>> This is one of the C libraries, which have a more conventional integer ABI
>> vers
On 2023-02-20 12:57, Ben Beasley wrote:
This is one of the C libraries, which have a more conventional integer ABI
version. For the C++ libraries, have a look at the grpc-cpp subpackage. You
will find libraries like:
libgrpc++.so.1.48()(64bit)
I see. That also looks like it's compatible wi
Am 20.02.23 um 19:14 schrieb Orion Poplawski:
On 2/20/23 10:46, Fabio Valentini wrote:
On Mon, Feb 20, 2023 at 6:43 PM Julian Sikorski
wrote:
Hello,
FTBFS bug was filed against mame [1]. Unfortunately, the corresponding
build [2] has already been deleted. This is not ideal from maintainer
pe
Hi Sergio,
Thanks! Yes, slim was retired but I just make my own RPM for F37 locally. It is
very straightforward and works fine. I would be happy to unretire it if that is
possible.
But that does not explain to me why the remix does not get created.
On Monday, February 20, 2023 at 03:00:31
On Mon, 2023-02-20 at 02:28 +, Globe Trotter via devel wrote:
> Hello,
>
> Since about Fedora 20 or so, I have been rolling my own Fedora spin
> without a desktop environment, and with openbox and slim (simple
> login manager). All worked well, because I did not need to roll these
> that often
On Mon, Feb 20, 2023, at 3:12 PM, Gordon Messmer wrote:
> On 2023-02-20 11:32, Ben Beasley wrote:
>> The grpc C++ libraries have CMake SOVERSION e.g. “1.48” for the 1.48.x minor
>> release. There is no attempt at ABI compatibility across minor releases, and
>> the entire string “1.48” is effecti
On 2023-02-20 11:32, Ben Beasley wrote:
The grpc C++ libraries have CMake SOVERSION e.g. “1.48” for the 1.48.x minor
release. There is no attempt at ABI compatibility across minor releases, and
the entire string “1.48” is effectively a major version for ABI purposes. The
“patch” relases of grp
As there is some discussion of whether the ELF dependency generator
should use the full version string presented by the library file name's
suffix, or should assume a SemVer-style major.minor and truncate the
requirement to the first two dot-separated numbers, questions about
rpminspect come to
The grpc C++ libraries have CMake SOVERSION e.g. “1.48” for the 1.48.x minor
release. There is no attempt at ABI compatibility across minor releases, and
the entire string “1.48” is effectively a major version for ABI purposes. The
“patch” relases of grpc only change internal implementation deta
On 2023-02-20 02:06, Petr Pisar wrote:
I applaud the struggle for ensuring compatibility. However, I worry that it
will make downgrading RPM packages less feasible. Imagine a user who updates
a system, finds a regression in a library, attempts to downgrade the library
and it will result into down
On 2023-02-20 10:01, Richard W.M. Jones wrote:
Does it have to be something which looks so much like it might be a
version number? For example it could be helpful for debugging if the
generated requires was something like:
Requires: libnghttp2.so.14()(64bit) >= soname.14.24.1
You mean the
On 2023-02-20 02:16, Daniel P. Berrangé wrote:
You mention 'libtool' multiple times through this thread. libtool
defines specific semantics for 3 digits in the version number.
Not all shared libraries are built with libtool, and even those
which did use libtool didn't neccesarily apply libtool's
On Mon, Feb 20, 2023 at 7:15 PM Orion Poplawski wrote:
>
> On 2/20/23 10:46, Fabio Valentini wrote:
> > On Mon, Feb 20, 2023 at 6:43 PM Julian Sikorski wrote:
> >>
> >> Hello,
> >>
> >> FTBFS bug was filed against mame [1]. Unfortunately, the corresponding
> >> build [2] has already been deleted.
On Mon, Feb 20, 2023 at 06:46:31PM +0100, Fabio Valentini wrote:
> On Mon, Feb 20, 2023 at 6:43 PM Julian Sikorski wrote:
> >
> > Hello,
> >
> > FTBFS bug was filed against mame [1]. Unfortunately, the corresponding
> > build [2] has already been deleted. This is not ideal from maintainer
> > pers
On Sun, Feb 19, 2023 at 01:33:33PM -0800, Gordon Messmer wrote:
> On 2023-02-19 12:30, Stephen Smoogen wrote:
> >
> > > - You mention "over the course of two releases" but don't
> > mention what
> > > is done in each one?
> >
> > I don't know the specifics of how package builds
On 2/20/23 10:46, Fabio Valentini wrote:
On Mon, Feb 20, 2023 at 6:43 PM Julian Sikorski wrote:
Hello,
FTBFS bug was filed against mame [1]. Unfortunately, the corresponding
build [2] has already been deleted. This is not ideal from maintainer
perspective as it effectively is a bug with no in
On 2023-02-20 03:08, Florian Weimer wrote:
* Gordon Messmer:
As you noted at the end of your message, that would involve querying
the rpm DB from the ELF dependency generator, which the rpm
maintainers want to avoid.
Not really. We could dump an extract of the RPM database to a text file
at th
On Mon, Feb 20, 2023 at 06:01:12PM +, Richard W.M. Jones wrote:
> On Sat, Feb 18, 2023 at 04:21:55PM -0800, Gordon Messmer wrote:
> > On 2023-02-18 15:53, Fabio Valentini wrote:
> > >I see a big hole in that problem (assuming that I understand
> > >Things correctly): What happens to packages w
On Sat, Feb 18, 2023 at 04:21:55PM -0800, Gordon Messmer wrote:
> On 2023-02-18 15:53, Fabio Valentini wrote:
> >I see a big hole in that problem (assuming that I understand
> >Things correctly): What happens to packages where this .so.x.y.z
> >pattern does not match their actual version?
>
> In
V Mon, Feb 20, 2023 at 11:04:43AM +, Zbigniew Jędrzejewski-Szmek napsal(a):
> On Mon, Feb 20, 2023 at 11:06:10AM +0100, Petr Pisar wrote:
> > V Sat, Feb 18, 2023 at 09:20:20AM -0800, Gordon Messmer napsal(a):
> > > For shared libraries without versioned symbols, the provides will change
> > > f
On Mon, Feb 20, 2023 at 6:43 PM Julian Sikorski wrote:
>
> Hello,
>
> FTBFS bug was filed against mame [1]. Unfortunately, the corresponding
> build [2] has already been deleted. This is not ideal from maintainer
> perspective as it effectively is a bug with no info provided whatsoever.
> Not to m
Hello,
FTBFS bug was filed against mame [1]. Unfortunately, the corresponding
build [2] has already been deleted. This is not ideal from maintainer
perspective as it effectively is a bug with no info provided whatsoever.
Not to mention being quite wasteful from the resources perspective as
ma
Builds are starting now.
On Thu, Feb 16, 2023 at 9:54 AM Thomas Rodgers wrote:
> We expect to start rebuilds for
> https://fedoraproject.org/wiki/Changes/F39Boost181
> in the f39-boost side tag Monday 2022-02-20.
>
> If your package depends on Boost, or just if you see a "Rebuilt for
> Boost 1.8
=
#fedora-meeting: Fedora Flatpak Packaging SIG
=
Meeting started by kalev at 15:00:22 UTC. The full logs are available
athttps://meetbot.fedoraproject.org/fedora-meeting/2023-02-20/flatpak-sig.2023-02-20-15.0
> I am big fan of using FAS for SIG membership:
>
> https://fedoraproject.org/wiki/SIGs/Ruby#Members
>
> Not that we would did some cleanup of that group, but in theory, the
> inactive members could be removed easier then just editing some random
> wiki page.
I am sure that maintaining members of
I put the following here, in case anyone wants to take a look. The LiveCD
formed does not boot.
fpaste fedora-shunya-common.ks
Uploading (3.7KiB)...
https://paste.centos.org/view/529252f8
$ fpaste fedora-live-shunya-37.ks
Uploading (3.2KiB)...
https://paste.centos.org/view/b73160cd
I also put
Hello,
I'm $SUBJ, as it's not used in Rails anymore:
https://github.com/rails/rails/pull/36377
Thanks to vonduch for updating the package!
Pavel
https://src.fedoraproject.org/rpms/rubygem-spring-watcher-listen
___
devel mailing list -- devel@lists.fedo
OLD: Fedora-38-20230219.n.0
NEW: Fedora-38-20230220.n.0
= SUMMARY =
Added images:0
Dropped images: 1
Added packages: 2
Dropped packages:0
Upgraded packages: 84
Downgraded packages: 0
Size of added packages: 57.97 KiB
Size of dropped packages:0 B
Size of
On Mon, Feb 20, 2023 at 11:04:43AM +, Zbigniew Jędrzejewski-Szmek wrote:
> On Mon, Feb 20, 2023 at 11:06:10AM +0100, Petr Pisar wrote:
> > V Sat, Feb 18, 2023 at 09:20:20AM -0800, Gordon Messmer napsal(a):
> > > For shared libraries without versioned symbols, the provides will change
> > > from
V Sat, Feb 18, 2023 at 11:58:58AM +0300, Benson Muite napsal(a):
> For builds on COPR and when using Fedora in the cloud, occasionally get
> an error when trying to read rawhide repository information:
>
> $ sudo dnf install wget
> Fedora - Rawhide - Developmental packages for t 13 MB/s | 21 MB
* Gordon Messmer:
> As you noted at the end of your message, that would involve querying
> the rpm DB from the ELF dependency generator, which the rpm
> maintainers want to avoid.
Not really. We could dump an extract of the RPM database to a text file
at the start of the build, after the depende
On Mon, Feb 20, 2023 at 11:06:10AM +0100, Petr Pisar wrote:
> V Sat, Feb 18, 2023 at 09:20:20AM -0800, Gordon Messmer napsal(a):
> > For shared libraries without versioned symbols, the provides will change
> > from:
> >
> > Provides: libnghttp2.so.14()(64bit)
> >
> > to:
> >
> > Provides: li
I'm afraid to make a mistake in the procedure.
пн, 20 февр. 2023 г. в 13:34, Sandro :
>
> On 20-02-2023 10:09, Vascom wrote:
> > This package can be retired. There is no need for anyone to take it.
>
> Why not retire it directly, if adoption makes no sense?
>
> https://docs.fedoraproject.org/en-US
On 20-02-2023 10:09, Vascom wrote:
This package can be retired. There is no need for anyone to take it.
Why not retire it directly, if adoption makes no sense?
https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/
-- Sandro
__
On 20-02-2023 08:39, Miro Hrončok wrote:
maildirproc orphan 0 weeks ago
Taken. I may have some personal use case for it.
-- Sandro
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe se
* Gordon Messmer:
> * Other developers:
>
> Other developers are not expected to make any specific changes, though
> if any package is manually creating versioned dependencies (as the
> curl package is), they can remove those and rely on the internal
> dependency generator when the change is compl
On Fri, Feb 17, 2023 at 07:03:26PM -0800, Gordon Messmer wrote:
> Following a recent thread discussing a reproducible failure caused by
> mismatched library interfaces, I proposed a change to the RPM ELF dependency
> generator. After discussion in the PR, I've provided an implementation
> suggeste
V Sat, Feb 18, 2023 at 09:20:20AM -0800, Gordon Messmer napsal(a):
> For shared libraries without versioned symbols, the provides will change
> from:
>
> Provides: libnghttp2.so.14()(64bit)
>
> to:
>
> Provides: libnghttp2.so.14()(64bit) >= 14.24.1
>
> ... while requirements on that package
OLD: Fedora-Rawhide-20230219.n.0
NEW: Fedora-Rawhide-20230220.n.0
= SUMMARY =
Added images:2
Dropped images: 0
Added packages: 2
Dropped packages:0
Upgraded packages: 102
Downgraded packages: 0
Size of added packages: 57.97 KiB
Size of dropped packages:0
BTW these are the packages currently depending on CoffeeScript:
~~~
$ sudo dnf repoquery --disablerepo=* --enablerepo=rawhide
--enablerepo=rawhide-source --whatrequires '*coffee-script*'
Last metadata expiration check: 0:22:49 ago on Mon Feb 20 09:48:42 2023.
coffee-script-0:1.10.0-20.fc38.noa
I have orphaned pulseeffects package because it replaced by
easyeffects at upstream and at Fedora.
This package can be retired. There is no need for anyone to take it.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email t
Hi all,
I have orphaned rubygem-coffee-script{,source}, which used to be used by
Ruby on Rails asset pipeline, but they are not anymore:
https://github.com/rails/ruby-coffee-script/issues/22#issuecomment-1162413725
And therefore I have made sure that nothing depends on them in Fedora.
There
51 matches
Mail list logo
