Hi,
i want to package the current version of speed-dreams 2.3.0, but i noticed that
jar files for the trackeditor are included in the package, but they already
exist in the system.
compilation error:
Checking for unpackaged file(s): /usr/lib/rpm/check-files
/home/martin/rpmbuild/BUILDROOT/spee
Hello,
The license for strawberry has been corrected and converted to SPDX
from "GPLv2 and GPLv3+ and LGPLv2 and ASL 2.0 and MIT and Boost" to
"MIT AND Apache-2.0 AND GPL-2.0-or-later AND GPL-3.0-or-later". Refer
to the spec file for the license breakdown by source files, which
should now correspo
On Mon, Jul 24, 2023 at 11:45:26AM -0400, Solomon Peachy via devel wrote:
> On Mon, Jul 24, 2023 at 04:00:21PM +0100, Daniel P. Berrangé wrote:
> > If I have a USB flash stick I plug in every day, it shouldn't ask me
> > about that after the first time I use it.
>
> Based on this "threat model" al
On 24-07-2023 17:38, Julio Faracco wrote:
I also need access to the packager group to claim maintainership.
Who could provide it to me?
The route you are looking at is described in "Adopting an orphaned or
freshly retired package":
https://docs.fedoraproject.org/en-US/fesco/Packager_sponsor_
I think it is better to do without the track editor for the time being and to
use SD with the option -DOPTION_TRACKEDITOR:BOOL=OFF
to compile.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedor
Am Di., 25. Juli 2023 um 10:19 Uhr schrieb Martin Gansser
:
>
> Hi,
>
> i want to package the current version of speed-dreams 2.3.0, but i noticed
> that jar files for the trackeditor are included in the package, but they
> already exist in the system.
Not really, there are two different things
The vhostmd package was mistakenly tagged as GPLv2+, and has
been corrected to LGPL-2.1-or-later during the SPDX conversion.
With regards,
Daniel
--
|: https://berrange.com -o-https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o-https://fstop138.berra
Hi all,
On 7/17/23 20:48, Miro Hrončok wrote:
> The following packages are orphaned and will be retired when they
> are orphaned for six weeks, unless someone adopts them. If you know for sure
> that the package should be retired, please do so now with a proper reason:
> https://fedoraproject.org/
* Samyak Jain:
> - GNU Toolchain Update (gcc 13.2, binutils 2.40, glibc 2.38, gdb 13.2)
This change has not yet been voted on by Fesco, so it's largely not
included in the rebuild: gcc was still using a 13.1 version, glibc was
at a 2.38 pre-release (not much we can do about that given the
schedul
On Tue, Jul 25, 2023 at 12:40:15PM +0200, Florian Weimer wrote:
> * Samyak Jain:
>
> > - GNU Toolchain Update (gcc 13.2, binutils 2.40, glibc 2.38, gdb 13.2)
>
> This change has not yet been voted on by Fesco, so it's largely not
> included in the rebuild: gcc was still using a 13.1 version, glib
On Mon, Jul 24, 2023 at 07:36:41AM -0700, Andrea Bolognani wrote:
> On Fri, Jul 21, 2023 at 08:20:21AM +, Zbigniew Jędrzejewski-Szmek wrote:
> > On Thu, Jul 20, 2023 at 07:40:08AM -0700, Andrea Bolognani wrote:
> > > Now, since this is clearly not a libvirt-specific issue, I believe
> > > this
On 25/07/2023 10:18, Martin Gansser wrote:
that is, remove the jar files from the speed-dreams package and link to the
Fedora jar files in the spec file.
JAR files must be compiled from sources. Bundled precompiled files must
be removed in %prep.
--
Sincerely,
Vitaly Zaitsev (vit...@easyc
On 25/07/2023 12:35, Hans de Goede wrote:
How do I proceed with this ? Should I run "fedpkg retire" for these 4,
or is orphaning them preferred ?
Orphaned packages will be retired automatically if no one adopts them
after 4 weeks.
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
__
Trying to figure out what has changed in Fedora land that causes NTFS
corruption for some time. This is with default workstation with GNOME
Shell auto-mounting external storage media when plugging them in.
A ticket in bugzilla suggests there has been a changed from ntfs-3g to ntfs3:
https://bugzi
On Wed, Jul 05, 2023 at 03:37:27PM +0100, Sebastian Crane wrote:
>
> As someone who does not use the Plasma desktop currently, I am a
> little confused as to why this is a change proposal. If I'm reading it
> correctly, Fedora configured Plasma to run on Wayland, which partially
> broke IBus suppo
On 25-07-2023 14:24, Miro Hrončok wrote:
5 weekly reminders are required, hence the retirement will happen
approximately in 2 weeks, i.e. around 2023-08-01.
1 August is exactly 1 week from now...
___
devel mailing list -- devel@lists.fedoraproject.org
On 25. 07. 23 14:33, Sandro wrote:
On 25-07-2023 14:24, Miro Hrončok wrote:
5 weekly reminders are required, hence the retirement will happen
approximately in 2 weeks, i.e. around 2023-08-01.
1 August is exactly 1 week from now...
Apologies, I forgot to update the number of weeks.
--
Miro
Hi all,
On 7/25/23 14:24, Miro Hrončok wrote:
> Dear maintainers.
>
> Based on the current fail to build from source policy, the following packages
> should be retired from Fedora 39 approximately one week before branching.
>
> 5 weekly reminders are required, hence the retirement will happen
>
> Actually, why wouldn't this be used everywhere? I could see this be
> useful when people remote into workstations and apply updates. I know
> of plenty of people that split their desktops between local and remote
> access/administration.
We could enable it everywhere but we've not reached out to
On Tue, Jul 25, 2023 at 8:52 AM Timothée Ravier wrote:
>
> > Actually, why wouldn't this be used everywhere? I could see this be
> > useful when people remote into workstations and apply updates. I know
> > of plenty of people that split their desktops between local and remote
> > access/administr
Hi All,
jansi-native depends on hawtjni which is unmaintained and will no longer build
after the maven2 to moven3 upgrade. Not having jansi-native will also break
jansi1 -> jline2 -> bsh all of which are currently maintained by me.
I no longer have a need for any of these pkgs so I'm orphaning
On 25. 07. 23 14:48, Hans de Goede wrote:
Miro can you hold of on retiring xmvn-connector-ivy please ?
ack
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to d
On Tue, Jul 25, 2023 at 2:48 PM Hans de Goede wrote:
> > xmvn-connector-ivymizdebsk
>
> This one has a long long list of deps which will break if it is
> retired and there is a pull-req here fixing the FTBFS:
>
> https://src.fedoraproject.org/rpms/xmvn-connector-ivy/pull-r
libotf was just bumped from libotf.so.0 to libotf.so.1.
$ dnf repoquery --whatrequires 'libotf.so.0()(64bit)' --disablerepo='*'
--enablerepo=rawhide
emacs-1:28.2-6.fc39.x86_64
emacs-lucid-1:28.2-6.fc39.x86_64
libotf-devel-0:0.9.13-22.fc38.x86_64
m17n-lib-tools-0:1.8.2-1.fc39.x86_64
Please annou
Hi,
On 7/25/23 15:52, Mikolaj Izdebski wrote:
> On Tue, Jul 25, 2023 at 2:48 PM Hans de Goede wrote:
>
>>> xmvn-connector-ivymizdebsk
>>
>> This one has a long long list of deps which will break if it is
>> retired and there is a pull-req here fixing the FTBFS:
>>
>> http
Am 25.07.23 um 13:29 schrieb Michael Schwendt:
Trying to figure out what has changed in Fedora land that causes NTFS
corruption for some time. This is with default workstation with GNOME
Shell auto-mounting external storage media when plugging them in.
A ticket in bugzilla suggests there has bee
> Would these messages show up, for example, if they opened the terminal app?
They only show up on the console / ssh login prompt if I'm not mistaken:
https://github.com/fwupd/fwupd/tree/main/data/motd
___
devel mailing list -- devel@lists.fedoraproject
* Miro Hrončok:
> glibc32 codonell, fweimer, jakub, mcermak
Is this about FTBFS issues? There isn't any recent build failure in
Koji, so I don't get why it's on this list?
Thanks,
Florian
___
devel mailing list -- dev
On Tue, Jul 25, 2023 at 10:51:04AM +, Zbigniew Jędrzejewski-Szmek wrote:
> I don't think Fedora would reject those changes, because in general
> we don't reject things unless they really break stuff for other people.
> Nevertheless, I agree with what Daniel P. Berrangé wrote in another reply:
>
On 25. 07. 23 16:42, Florian Weimer wrote:
* Miro Hrončok:
glibc32 codonell, fweimer, jakub, mcermak
Is this about FTBFS issues? There isn't any recent build failure in
Koji, so I don't get why it's on this list?
The build currently in Rawhide was done on
On Tue, Jul 25, 2023 at 10:53 AM Miro Hrončok wrote:
>
> On 25. 07. 23 16:42, Florian Weimer wrote:
> > * Miro Hrončok:
> >
> >> glibc32 codonell, fweimer, jakub, mcermak
> >
> > Is this about FTBFS issues? There isn't any recent build failure in
> > Koji, so I d
On Tue, 25 Jul 2023, Scott Talbert wrote:
libotf was just bumped from libotf.so.0 to libotf.so.1.
$ dnf repoquery --whatrequires 'libotf.so.0()(64bit)' --disablerepo='*'
--enablerepo=rawhide
emacs-1:28.2-6.fc39.x86_64
emacs-lucid-1:28.2-6.fc39.x86_64
libotf-devel-0:0.9.13-22.fc38.x86_64
m17n-
* Josh Boyer:
> On Tue, Jul 25, 2023 at 10:53 AM Miro Hrončok wrote:
>>
>> On 25. 07. 23 16:42, Florian Weimer wrote:
>> > * Miro Hrončok:
>> >
>> >> glibc32 codonell, fweimer, jakub,
>> >> mcermak
>> >
>> > Is this about FTBFS issues? There isn't any recent bu
* Miro Hrončok:
> On 25. 07. 23 16:42, Florian Weimer wrote:
>> * Miro Hrončok:
>>
>>> glibc32 codonell, fweimer, jakub, mcermak
>> Is this about FTBFS issues? There isn't any recent build failure in
>> Koji, so I don't get why it's on this list?
>
> The build c
On Tue, Jul 25, 2023 at 11:44 AM Florian Weimer wrote:
>
> * Josh Boyer:
>
> > On Tue, Jul 25, 2023 at 10:53 AM Miro Hrončok wrote:
> >>
> >> On 25. 07. 23 16:42, Florian Weimer wrote:
> >> > * Miro Hrončok:
> >> >
> >> >> glibc32 codonell, fweimer, jakub,
> >>
On Tue, Jul 25, 2023 at 4:44 PM Florian Weimer wrote:
>
> * Josh Boyer:
>
> > On Tue, Jul 25, 2023 at 10:53 AM Miro Hrončok wrote:
> >>
> >> On 25. 07. 23 16:42, Florian Weimer wrote:
> >> > * Miro Hrončok:
> >> >
> >> >> glibc32 codonell, fweimer, jakub,
> >> >
On Tue, 25 Jul 2023 at 11:54, Josh Boyer wrote:
> On Tue, Jul 25, 2023 at 11:44 AM Florian Weimer
> wrote:
> >
> > * Josh Boyer:
> >
> > > On Tue, Jul 25, 2023 at 10:53 AM Miro Hrončok
> wrote:
> > >>
> > >> On 25. 07. 23 16:42, Florian Weimer wrote:
> > >> > * Miro Hrončok:
> > >> >
> > >> >>
On Tue, Jul 25, 2023 at 02:23:00AM +0200, Sandro wrote:
> On 24-07-2023 20:30, Samyak Jain wrote:
> > 21426 builds have been tagged into f39, there are currently 1017 failed
> > builds
> > that need to be addressed by the package maintainers. FTBFS bugs will be
> > filed shortly.
>
> Will all the
On Tue, Jul 25, 2023 at 12:47:12PM +0200, Jakub Jelinek wrote:
> On Tue, Jul 25, 2023 at 12:40:15PM +0200, Florian Weimer wrote:
> > * Samyak Jain:
> >
> > > - GNU Toolchain Update (gcc 13.2, binutils 2.40, glibc 2.38, gdb 13.2)
> >
> > This change has not yet been voted on by Fesco, so it's larg
* Peter Robinson:
>> Are bootloaders fully treated as firmware and no longer built by Fedora?
>> At least the shim package does not come with corresponding source code
>> AFAICS. But I expect that there are other 32-bit pre-boot packages that
>> we still rebuild.
>
> There's shim-unsigned* which
On 25. 07. 23 17:49, Florian Weimer wrote:
* Miro Hrončok:
On 25. 07. 23 16:42, Florian Weimer wrote:
* Miro Hrončok:
glibc32 codonell, fweimer, jakub, mcermak
Is this about FTBFS issues? There isn't any recent build failure in
Koji, so I don't get why it'
Hey,
Thanks for raising the issue. It has been addressed and all the dashboards
should now contain up2date data from koschei.
Longer answer: The problem was the enablement of EPEL 9 Next in koschei,
oraculum (the backend for the Packager Dashboard) isn't ready for these
kinds of releases and I ha
Hi folks! Just wanted to drop a note for anyone who noticed their
Rawhide updates stuck in gating for an unusually long time
yesterday/today.
This is mainly due to the mass rebuild. Merging it in (which was done
without sending anything in it through openQA testing) resulted in two
separate proble
On Tue, Jul 25, 2023 at 10:39 AM Timothée Ravier
wrote:
>
> > Would these messages show up, for example, if they opened the terminal app?
>
> They only show up on the console / ssh login prompt if I'm not mistaken:
> https://github.com/fwupd/fwupd/tree/main/data/motd
That means they will show up
* Kevin Fenzi:
> ok. How big a problem is this? Do we need to schedule another mass
> rebuild (and push back the schedule most likely)?
>
> Or we can/should just rebuild things that failed due to already fixed
> issues?
I don't think it matters. I raised it mainly for accuracy.
We should adjus
Announcing the creation of a new nightly release validation test event
for Fedora 39 Rawhide 20230725.n.1. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki
On Tue, Jul 25, 2023, 21:36 Florian Weimer wrote:
> * Kevin Fenzi:
>
> > ok. How big a problem is this? Do we need to schedule another mass
> > rebuild (and push back the schedule most likely)?
> >
> > Or we can/should just rebuild things that failed due to already fixed
> > issues?
>
> I don't t
Access restored. Thanks to all.
___
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 Guideli
On Tue, Jul 25, 2023 at 3:58 PM Fabio Valentini wrote:
>
> As far as I can tell, the toolchain proposal was announced on the devel /
> devel-announce lists on July 7 but never submitted to FESCo for a vote. Looks
> like the process broke down somewhere along the way.
I think it was actually a c
Thank you very much Michel for going through the release.
It couldn't be easy.
There is a reported bug in Bodhi, so it will need some minor fixups
but we are close. Really looking forward to it.
Jakub
On Tue, Jul 25, 2023 at 4:48 AM Michel Alexandre Salim
wrote:
>
> Hi all,
>
> On Mon, Jul 17,
Hey there,
I plan to orphan these two packages:
python-uamqp
python-azure-eventhub
They were originally packaged to help with azure-cli packaging, but they are no
longer used by the upstream package. I couldn't find any other packages which
depend on these two packages.
--
Major Hayden
__
On 25-07-2023 04:47, Michel Alexandre Salim wrote:
Once this lands in F38, Fedora Review Service should be fixed, unless
I'm missing something.
First of all, thanks for bringing fedora-review back. I rely on it quite
a bit reviewing my own packages as well as for official reviews.
I noticed
On 25-07-2023 18:23, Kevin Fenzi wrote:
On Tue, Jul 25, 2023 at 02:23:00AM +0200, Sandro wrote:
On 24-07-2023 20:30, Samyak Jain wrote:
21426 builds have been tagged into f39, there are currently 1017 failed builds
that need to be addressed by the package maintainers. FTBFS bugs will be
filed s
On Wed, Jul 26, 2023 at 01:46:19AM +0200, Sandro wrote:
> On 25-07-2023 18:23, Kevin Fenzi wrote:
> > On Tue, Jul 25, 2023 at 02:23:00AM +0200, Sandro wrote:
> > > On 24-07-2023 20:30, Samyak Jain wrote:
> > > > 21426 builds have been tagged into f39, there are currently 1017 failed
> > > > builds
Am 23.07.23 um 00:39 schrieb Neal Gompa:
Actually, why wouldn't this be used everywhere?
Because fwupd only works on a small set of machines?
Ralf
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lis
On Wednesday, 26 July 2023 at 06:23, Ralf Corsépius wrote:
> Am 23.07.23 um 00:39 schrieb Neal Gompa:
> > Actually, why wouldn't this be used everywhere?
>
> Because fwupd only works on a small set of machines?
Define small. :)
It works, for example, on any machine that has a Logitech Unifying/
Hi, Adam!
On Tuesday, 25 July 2023 at 19:31, Adam Williamson wrote:
> Hi folks! Just wanted to drop a note for anyone who noticed their
> Rawhide updates stuck in gating for an unusually long time
> yesterday/today.
Thanks for the write-up. It shows how much hard work is being done in
the backgro
57 matches
Mail list logo
