On 1/31/23 14:44, Miro Hrončok wrote:
> Dear maintainers.
>
> Based on the current fail to build from source policy, the following packages
> should be retired from Fedora 38 approximately one week before branching.
>
> 5 weekly reminders are required, hence the reti
Hi Miro,
Sorry I will fix and rebuild the packages below on the rawhide asap.
> bowtie jaruga, verdurin
...
> simde jaruga
--
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See
On Thu, 9 Feb 2023 at 08:56, Arun SAG wrote:
>
>
> >
> > Package(co)maintainers
> > ==
> > ArpON fab, sagarun
>
>
> There has been
On Tue, 31 Jan 2023 at 18:14, Miro Hrončok wrote:
>
> Dear maintainers.
>
> Based on the current fail to build from source policy, the following packages
> should be retired from Fedora 38 approximately one week before branching.
>
> 5 weekly reminders are required,
On Mon, Feb 6, 2023 at 6:50 PM Vít Ondruch wrote:
> Dne 06. 02. 23 v 1:13 Georg Sauthoff napsal(a):
> > Judging from the FTBFS mail/Bugzilla/
> https://src.fedoraproject.org/rpms/datamash it
> > looks like jhladky (Jiri Hladky) currently is the sole maintainer?
>
> You are looking at the right
On Mon, 6 Feb 2023, Miro Hrončok wrote:
I plan to orphan the packages now, so maintainers who want to fix them can
take them, and rerun the check later this week.
It is not enough to unorphan a package to save it from retirement, it must
also be built in rawhide.
In case you want to postpone
Dear maintainers.
Based on the current fail to build from source policy, the following packages
should be retired from Fedora 38 approximately one week before branching.
5 weekly reminders are required, hence the retirement will happen
approximately this week, i.e. around 2023-02-08.
Since
Dear maintainers.
Based on the current fail to build from source policy, the following packages
should be retired from Fedora 38 approximately one week before branching.
5 weekly reminders are required, hence the retirement will happen
approximately this week, i.e. around 2023-02-08.
Since
t; > > ago
> > > ocaml-mccsorphan 2 weeks
> > > ago
> > > ocaml-opam-file-formatorphan 2 weeks
> > > ago
> >
> > > Affected (co)maintainers (either direct
Dne 06. 02. 23 v 1:13 Georg Sauthoff napsal(a):
Hello,
On Thu, Feb 02, 2023 at 02:45:23PM -0300, Mathias Zavala wrote:
I’m sorry for not answering sooner! I’ll be glad to receive help with the
current state of the package. Thanks in advance
you are a datamash Fedora package maintainer?
Hi Georg,
On Mon, Feb 6, 2023 at 1:17 AM Georg Sauthoff wrote:
>
> In case this comes up again - how does unretirement work, exactly?
> Does one request to unretire a package via writing to this mailing list
> or does the process work differently?
These links are pertinent to your questions, it
Hello,
On Thu, Feb 02, 2023 at 12:58:11AM +, Sérgio Basto wrote:
> I built the package for you ...
thank you for helping to prevent datamash from early retirement! :)
Best regards,
Georg
--
'Programming X is like reading one of those French philosophers where
afterwards you start
Hello,
On Thu, Feb 02, 2023 at 09:18:51AM +0100, Vít Ondruch wrote:
[..]
> But other than that, retiring would not be that bad thing in your case,
> because after retirement, there is 8 weeks window to unretire the package
> without re-review, that way you could pick it up ...
ok, good to know.
Hello,
On Thu, Feb 02, 2023 at 02:45:23PM -0300, Mathias Zavala wrote:
> I’m sorry for not answering sooner! I’ll be glad to receive help with the
> current state of the package. Thanks in advance
you are a datamash Fedora package maintainer?
Judging from the FTBFS
hunderbirdtr
>
> This is built now.
>
> > libmobi avsej
>
> Fix available:
> https://src.fedoraproject.org/rpms/libmobi/pull-request/2
no packages depends on libmobi ...
> > mimic pbrobinson
&g
On Tue, Nov 22, 2022 at 11:24 PM Fabio Valentini wrote:
>
> On Tue, Nov 22, 2022 at 6:49 PM Josh Stone wrote:
> >
> > On 11/22/22 8:13 AM, Fabio Valentini wrote:
> > > List of Rust library-only packages,
> > >
> > > - rust-rustfilt
> >
On Fri, Feb 3, 2023 at 5:05 PM Pete Walter wrote:
>
> Today, we have 3 versions in rawhide (libgit2 was updated from 1.3.x to 1.4.x
> and then 1.5.x over the last month and the compat packages were added today):
>
> libgit2 package with version 1.5.1 (security supported stil
On 2/3/23 8:04 AM, Pete Walter wrote:
> I took over libgit2 from Igor when he gave up all his packages and have
> since tried to get it up to date. libgit2 is a bit special because it
> bumps soname every once in a while and then other packages often fail to
> rebuild against the new
On Tue, Jan 31, 2023 at 12:45 PM Miro Hrončok wrote:
> If you see a package that can be rebuilt, please do so.
> tpm2-tss-engine mzavalavz
No longer FTBFS. It can be removed from the
to be retired list.
Thanks!
I took over libgit2 from Igor when he gave up all his packages and have since tried to get it up to date. libgit2 is a bit special because it bumps soname every once in a while and then other packages often fail to rebuild against the new version both because of libgit2 API changes and because
On Tue, 2023-01-31 at 13:44 +0100, Miro Hrončok wrote:
> If you see a package that was built, please let me know.
> If you see a package that should be exempted from the process,
> please let me know and we can work together to get a FESCo approval for
> that.
>
> If you see a package that can be
I’m sorry for not answering sooner! I’ll be glad to receive help with the
current state of the package. Thanks in advance
On Thu, Feb 2, 2023 at 14:41 Sérgio Basto wrote:
> On Thu, 2023-02-02 at 12:14 +0100, Miro Hrončok wrote:
> > On 02. 02. 23 0:46, Georg Sauthoff wrote:
> > > Hello,
> > >
>
On Thu, 2023-02-02 at 12:14 +0100, Miro Hrončok wrote:
> On 02. 02. 23 0:46, Georg Sauthoff wrote:
> > Hello,
> >
> > On Tue, Jan 31, 2023 at 01:44:26PM +0100, Miro Hrončok wrote:
> >
> > > datamash jhladky
> >
> > I have a build fix ready and
On 02. 02. 23 0:46, Georg Sauthoff wrote:
Hello,
On Tue, Jan 31, 2023 at 01:44:26PM +0100, Miro Hrončok wrote:
datamashjhladky
I have a build fix ready and volunteer to maintain it such that I can
apply it.
My FAS handle is: gsauthof
Can you add
- all 31.01.2023, 12:44, "Miro Hrončok" :howl atim, pwalterI took over howl that was orphaned a few weeks ago and now rescued it and fixed it to build from source. I also created a fedora flatpak for it as it was missing. Pete___
devel mailing list --
Dne 02. 02. 23 v 0:46 Georg Sauthoff napsal(a):
Hello,
On Tue, Jan 31, 2023 at 01:44:26PM +0100, Miro Hrončok wrote:
datamashjhladky
I have a build fix ready and volunteer to maintain it such that I can
apply it.
My FAS handle is: gsauthof
Can
On Thursday, 02 February 2023 at 03:53, Gary Buhrmaster wrote:
> On Tue, Jan 31, 2023 at 12:45 PM Miro Hrončok wrote:
>
> > If you see a package that can be rebuilt, please do so.
>
> > tpm2-tss-engine mzavalavz
>
> I can fix this (up-lift to the current
On Tue, Jan 31, 2023 at 12:45 PM Miro Hrončok wrote:
> If you see a package that can be rebuilt, please do so.
> tpm2-tss-engine mzavalavz
I can fix this (up-lift to the current release), but I don't
see a way to do so before retirement as the current
> waffle ajax
rescued this,
Dave.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
On Thu, 2023-02-02 at 00:46 +0100, Georg Sauthoff wrote:
> Hello,
>
> On Tue, Jan 31, 2023 at 01:44:26PM +0100, Miro Hrončok wrote:
>
> > datamash jhladky
>
> I have a build fix ready and volunteer to maintain it such that I can
> apply it.
>
> My FAS
Hello,
On Tue, Jan 31, 2023 at 01:44:26PM +0100, Miro Hrončok wrote:
> datamashjhladky
I have a build fix ready and volunteer to maintain it such that I can
apply it.
My FAS handle is: gsauthof
Can you add me as a maintainer for the datamash package
more packages
use the v3 interface?
Normally older versions are broken out into versioned legacy packages
and the main package is upgraded. Then reverse dependencies are either
upgraded or pinned as needed.
Which is what we did for catch before - there is catch1 and catch now.
The slight
eral guidelines on this.
>
> For Catch, there was an upgrade from 1 to 2. Similarly for FFTW, the
> main package uses the name FFTW, but it was FFTW3 before hand. Maybe one
> could use Catch3 or Catch2v3? Then change names later once more packages
> use the v3 interface?
>
Norma
, the
main package uses the name FFTW, but it was FFTW3 before hand. Maybe one
could use Catch3 or Catch2v3? Then change names later once more packages
use the v3 interface?
On 2/1/23 13:44, Tom Hughes wrote:
> There is already precedent for doing it with catch and I've said
> that I plan
There is already precedent for doing it with catch and I've said
that I plan to do it again so I don't know what more you want.
Tom
On 01/02/2023 10:13, Benson Muite wrote:
Packages with breaking APIs between major version changes often keep
maintaining the older version for some time after
Packages with breaking APIs between major version changes often keep
maintaining the older version for some time after the new version is
released. An example is FFTW which has both FFTW (version 3) and FFTW2
(version 2) within Fedora:
https://packages.fedoraproject.org/search?query=fftw
On Mon, Jan 30, 2023 at 9:26 AM Jens-Ulrik Petersen
wrote:
> On Mon, Jan 30, 2023 at 4:09 AM Miro Hrončok wrote:
>
>> On 29. 01. 23 18:15, Jens-Ulrik Petersen wrote:
>> > llvm11 jistone, petersen,
>> sergesanspaille, tstellar
>> > llvm12
On Mon, Jan 30, 2023 at 6:47 PM Florian Weimer wrote:
> * Jens-Ulrik Petersen:
> > which are still needed by various packages, the latter also including
> > ghc8.10-compiler.aarch64, ghc9.0-compiler.aarch64,
> > ghc9.2-compiler.s390x, and ghc9.4-compiler.s390x
>
> Is
eeks ago
> > ocaml-opam-file-formatorphan 2 weeks ago
>
> > Affected (co)maintainers (either directly or via packages' dependencies):
> > andyli: ocaml-dose3, ocaml-opam-file-format, ocaml-mccs
>
> Jerry, I guess we still need these?
Dear maintainers.
Based on the current fail to build from source policy, the following packages
should be retired from Fedora 38 approximately one week before branching.
5 weekly reminders are required, hence the retirement will happen
approximately in 1 week, i.e. around 2023-02-08.
Since
Dear maintainers.
Based on the current fail to build from source policy, the following packages
should be retired from Fedora 38 approximately one week before branching.
5 weekly reminders are required, hence the retirement will happen
approximately in 1 week, i.e. around 2023-02-08.
Since
weeks ago
> Affected (co)maintainers (either directly or via packages' dependencies):
> andyli: ocaml-dose3, ocaml-opam-file-format, ocaml-mccs
Jerry, I guess we still need these? If so I will take over co-maintenance.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://pe
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/wiki/How_to_remove_a_package_at_end_of_life
Note
s for:
>
> llvm11 jistone, petersen,
> sergesanspaille, tstellar
> llvm12 petersen, sergesanspaille,
> tstellar
>
> which are still needed by various packages, the latter also including
> ghc8.10
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/wiki/How_to_remove_a_package_at_end_of_life
Note
tstellar
> > llvm12 petersen,
> sergesanspaille,tstellar
> >
> > which are still needed by various packages, the latter also including
> > ghc8.10-compiler.aarch64, ghc9.0-compiler.aarch64,
> ghc9.2-compiler.s390x, and
> > ghc9.4-compiler.s
ould like to request exemptions for:
llvm11 jistone, petersen,
sergesanspaille, tstellar
llvm12 petersen,
sergesanspaille,tstellar
which are still needed by various packages, the latter also
:
llvm11 jistone, petersen,
> sergesanspaille, tstellar
> llvm12 petersen, sergesanspaille,
> tstellar
>
which are still needed by various packages, the latter also including
ghc8.10-compiler.aarch64, ghc9.0-compiler.aarch64, ghc9.2-compi
that never happen, etc.
Perhaps ASSIGNED should not get rid of
reminders quite that easily?
I am certainly guilty of using ASSIGNED to get rid of reminders.
Generally, if I leave some packages in FTBFS state, there is probably
some reason and it is not because I just don't care of forget about
On Thu, Jan 26, 2023 at 11:07:34PM +0100, Miro Hrončok wrote:
>
> Unfortunately, as seen by the lenght of the packages listed in my emails,
> thsi is not always the case.
Yeah. ;(
> Some packagers do set the bugzillas to ASSIGNED to get rid of the reminders
> and then they for
On Thu, Jan 26, 2023 at 10:08 PM Miro Hrončok wrote:
> Some packagers do set the bugzillas to ASSIGNED to get rid of the reminders
> and
> then they forget to actually fix the FTBFS, cannot figure out how to fix it,
> are blocked on externalities that never happen, etc.
Perhaps ASSIGNED should
On Thu, Jan 26, 2023 at 11:08 PM Miro Hrončok wrote:
> Oh but they are different. FTBFS are not urgent and the policy is only set
> to
> retire packages that FTBFS for more than 2 release cycles.
>
> For a package to be considered for retirement in February 23, it would
> have
On 26. 01. 23 20:29, Kevin Fenzi wrote:
On Thu, Jan 26, 2023 at 10:21:27AM +0100, Miro Hrončok wrote:
On 26. 01. 23 4:51, Yaakov Selkowitz wrote:
On Tue, 2023-01-24 at 15:55 +0100, Miro Hrončok wrote:
Based on the current fail to build from source policy, the following
packages
should
On Thu, Jan 26, 2023 at 10:21:27AM +0100, Miro Hrončok wrote:
> On 26. 01. 23 4:51, Yaakov Selkowitz wrote:
> > On Tue, 2023-01-24 at 15:55 +0100, Miro Hrončok wrote:
> > > Based on the current fail to build from source policy, the following
> > > packages
> > &
ere:
> https://bugzilla.redhat.com/show_bug.cgi?id=2101964#c1. Apparently,
> the result is "that doesn't work". Thanks for fixing.
Ah right, I'd forgotten about that.
Dune is a strange package because it's mainly just a program
(/usr/bin/dune). But we sometimes use it by inst
On 26. 01. 23 4:51, Yaakov Selkowitz wrote:
On Tue, 2023-01-24 at 15:55 +0100, Miro Hrončok wrote:
Based on the current fail to build from source policy, the following
packages
should be retired from Fedora 38 approximately one week before branching.
5 weekly reminders are required, hence
On Tue, 2023-01-24 at 15:55 +0100, Miro Hrončok wrote:
> Based on the current fail to build from source policy, the following
> packages
> should be retired from Fedora 38 approximately one week before branching.
>
> 5 weekly reminders are required, hence the retirem
On Wed, Jan 25, 2023 at 2:43 AM Richard W.M. Jones wrote:
> I think we're fixed now. Here is the side tag & Bodhi update:
Thank you for taking care of that.
> - I have added support for rpmautospec
That's great.
> - There is now a cyclic dependency between ocaml-pp and ocaml-dune,
> which
On Tue, Jan 24, 2023 at 11:58 AM Richard W.M. Jones wrote:
> FYI debuginfo generation failed on several packages. I've had to
> disable it on a few to get around this. For example:
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=96625872
> https://kojipkgs.fedoraproject.
On 1/25/23 13:04, Alexander Ploumistos wrote:
> On Tue, Jan 24, 2023 at 3:56 PM Miro Hrončok wrote:
>>
>> IQmoljussilehtola
>
> I'm leaving this comment in case Susi (Cc) didn't get the previous
> mail like last time. I know that they're working with
On Tue, Jan 24, 2023 at 3:56 PM Miro Hrončok wrote:
>
> IQmoljussilehtola
I'm leaving this comment in case Susi (Cc) didn't get the previous
mail like last time. I know that they're working with upstream to
package the next version of IQmol, so this
lled "goals"):
http://git.annexia.org/?p=goals.git;a=summary
http://git.annexia.org/?p=fedora-ocaml-rebuild.git;a=summary
http://oirase.annexia.org/tmp/2020-02-rjones-goals-tech-talk.mp4
- I have added support for rpmautospec
- I added a way to choose either to blindly retry f
FYI debuginfo generation failed on several packages. I've had to
disable it on a few to get around this. For example:
https://koji.fedoraproject.org/koji/taskinfo?taskID=96625872
https://kojipkgs.fedoraproject.org//work/tasks/5943/96625943/build.log
I'm not clear exactly why this is happening
Dear maintainers.
Based on the current fail to build from source policy, the following packages
should be retired from Fedora 38 approximately one week before branching.
5 weekly reminders are required, hence the retirement will happen
approximately in 2 weeks, i.e. around 2023-02-08.
Since
Dear maintainers.
Based on the current fail to build from source policy, the following packages
should be retired from Fedora 38 approximately one week before branching.
5 weekly reminders are required, hence the retirement will happen
approximately in 2 weeks, i.e. around 2023-02-08.
Since
includes pom. I'm not
> > certain if this is an XMvn bug, or if the maven-scm pom.xml files are
> > wrong somehow.
> > - buildnumber-maven-plugin version 1.4 was too old, so I moved all the
> > way to 3.0.0. Even then, it needed a small patch to work with
> > maven
This is running now:
https://koji.fedoraproject.org/koji/builds?inherited=0=62208=-build_id=1
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual
ler flags changed, combined with the builds being
> > done out of order, means that most of the packages now have broken
> > deps.
> >
> > Will fix ...
> >
> > Rich.
> >
> > --
> >
On Mon, Jan 23, 2023 at 1:25 PM Richard W.M. Jones wrote:
> The OCaml package encodes the compiler flags into dependencies --
> which is done for fairly accidental reasons.
>
> Because the compiler flags changed, combined with the builds being
> done out of order, means that most
The OCaml package encodes the compiler flags into dependencies --
which is done for fairly accidental reasons.
Because the compiler flags changed, combined with the builds being
done out of order, means that most of the packages now have broken
deps.
Will fix ...
Rich
r-maven-plugin version 1.4 was too old, so I moved all the
> way to 3.0.0. Even then, it needed a small patch to work with
> maven-scm 2.0.0.
>
> Or we can all remove mvn-scm and buildnumber-maven-plugin from our
> respective packages' POMs.
I should note that I intend to
On Wed, Jan 18, 2023 at 5:58 AM Miro Hrončok wrote:
> Based on the current fail to build from source policy, the following packages
> should be retired from Fedora 38 approximately one week before branching.
[snip]
> maven-scm mizdebsk
On 18. 01. 23 14:29, Olivier Fourdan wrote:
On Wed, Jan 18, 2023 at 2:20 PM Miro Hrončok wrote:
[…]
I've triggered the build (any packager can do that):
$ koji build rawhide --nowait --fail-fast
On Wed, Jan 18, 2023 at 2:20 PM Miro Hrončok wrote:
> […]
>
> I've triggered the build (any packager can do that):
>
> $ koji build rawhide --nowait --fail-fast
> 'git+https://src.fedoraproject.org/rpms/xorg-x11-drv-qxl.git#d7716591515d97b5cc4a146fbcf3ee7ca18f1808'
> Created task: 96293694
> Task
On 18. 01. 23 14:16, Olivier Fourdan wrote:
Hi
On Wed, Jan 18, 2023 at 1:58 PM Miro Hrončok wrote:
Based on the current fail to build from source policy, the following packages
should be retired from Fedora 38 approximately one week before branching.
5 weekly reminders are required, hence
Hi
On Wed, Jan 18, 2023 at 1:58 PM Miro Hrončok wrote:
>
> Based on the current fail to build from source policy, the following packages
> should be retired from Fedora 38 approximately one week before branching.
>
> 5 weekly reminders are required, hence the retirem
On 18. 01. 23 14:06, Neal Gompa wrote:
ngompa: xorg-x11-drv-qxl, golang-gopkg-mgo-2
Uhh, what? Why am I associated with the QXL driver?
livecd-tools -> lorax -> lorax -> anaconda -> xorg-x11-drivers ->
xorg-x11-drv-qxl
livecd-tools (maintained by: bcl, bruno, ngompa)
On Wed, Jan 18, 2023 at 7:58 AM Miro Hrončok wrote:
>
> Dear maintainers.
>
> Based on the current fail to build from source policy, the following packages
> should be retired from Fedora 38 approximately one week before branching.
>
> 5 weekly reminders are required,
script may need to be re-run during the builds.
I'm afraid, as of today, that can't be generalized without human
intervention. This may work with difficulty for binary packages, but
even then not in the general case. Take alone circular dependencies
that are due to documentation being generated, but that wo
On 1/17/23 14:37, Björn Persson wrote:
So as things stand, these rebuilds need to be done by a human who knows
the dependency graph.
Requiring "a human who knows the dependency graph" is *severely* broken.
There should be a shell script which computes an acceptable order from the
old
ild is statically linked precisely to remain
functional each time GCC or XMLada is upgraded, so that it can rebuild
itself and the other Ada packages. Thus the dependency loop isn't
normally a problem. A bump and a rebuild per package should be
sufficient, but they must be done in the right order.
gt; >
>> > Apparently, the following packages now don't install:
>>
>> There is a mass rebuild tomorrow. The Ada soname changes every year
>> and we've never rebuilt Ada packages separately for that, just during the
>> mass rebuild.
>
> "Because
On Wed, Jan 11, 2023 at 8:59 PM Miro Hrončok wrote:
> llvm10 petersen, sergesanspaille
>
Probably okay to drop at this point.
> llvm11 jistone, petersen,
> sergesanspaille,
> tstellar
> llvm12
Co.
> > >
> > > Apparently, the following packages now don't install:
> >
> > There is a mass rebuild tomorrow. The Ada soname changes every year
> > and we've never rebuilt Ada packages separately for that, just during the
> > mass rebuild.
>
> Pavel an
Jakub Jelinek wrote:
> On Tue, Jan 17, 2023 at 01:24:45PM +0100, Miro Hrončok wrote:
> > Hello. GCC was updated to 13 in rawhide while the Fedora change was still
> > being voted about by FESCo.
> >
> > Apparently, the following packages now don't install:
>
>
On Tue, Jan 17, 2023 at 1:39 PM Jakub Jelinek wrote:>
> On Tue, Jan 17, 2023 at 01:24:45PM +0100, Miro Hrončok wrote:
> > Hello. GCC was updated to 13 in rawhide while the Fedora change was still
> > being voted about by FESCo.
> >
> > Apparently, the follow
On Tue, Jan 17, 2023 at 01:24:45PM +0100, Miro Hrončok wrote:
> Hello. GCC was updated to 13 in rawhide while the Fedora change was still
> being voted about by FESCo.
>
> Apparently, the following packages now don't install:
There is a mass rebuild tomorrow. The Ada soname change
Hello. GCC was updated to 13 in rawhide while the Fedora change was still being
voted about by FESCo.
Apparently, the following packages now don't install:
$ repoquery -q --repo=rawhide --whatrequires 'libgnat-12.so()(64bit)'
--whatrequires 'libgnarl-12.so()(64bit)'
GtkAda3-0:2020-7.fc37
:49, Matyáš Kroupa wrote:
> > Hi,
> > I use wine and steam (and some libraries which are required to run them)
> with total of 254 i686 packages.
> > Matyáš
> I'm also using them for wine and steam.
>
> --
> Arthur Bols
> fas/irc: principis
> _
On 17/03/2022 10:49, Matyáš Kroupa wrote:
Hi,
I use wine and steam (and some libraries which are required to run them) with
total of 254 i686 packages.
Matyáš
I'm also using them for wine and steam.
--
Arthur Bols
fas/irc: principis
___
devel
On Wed, Jan 11, 2023 at 1:59 PM Miro Hrončok wrote:
>
> Dear maintainers.
>
> Based on the current fail to build from source policy, the following packages
> should be retired from Fedora 38 approximately one week before branching.
>
> tabbed
On 16. 03. 22 15:15, Miro Hrončok wrote:
On 16. 03. 22 14:54, David Cantrell wrote:
Hi,
Our most recent FESCo meeting involved discussing the proposal to drop i686
builds of jdk8,11,17 from Fedora 37 onward. The topic quickly changed to the
larger question of "what do people use i686 pac
On 16. 01. 23 20:53, Simo Sorce wrote:
On Fri, 2023-01-13 at 12:28 +0100, Miro Hrončok wrote:
On 13. 01. 23 0:35, Chuck Anderson wrote:
For receiving/filtering emails, you can filter on the List-Id: header
rather than the To: or Cc: headers. In that way you can differentiate
between normal
On Fri, 2023-01-13 at 12:28 +0100, Miro Hrončok wrote:
> On 13. 01. 23 0:35, Chuck Anderson wrote:
> > For receiving/filtering emails, you can filter on the List-Id: header
> > rather than the To: or Cc: headers. In that way you can differentiate
> > between normal list distribution and Bcc:. If
On Sun, Jan 15, 2023 at 4:50 PM Kevin Kofler via devel
wrote:
>
> Olivier Fourdan wrote:
> > Actually… I suspect fixing that build failure would require a fix in
> > the xserver from ajax [1]
>
> Actually, this is the fix that is needed:
>
Olivier Fourdan wrote:
> Actually… I suspect fixing that build failure would require a fix in
> the xserver from ajax [1]
Actually, this is the fix that is needed:
https://gitlab.freedesktop.org/xorg/driver/xf86-video-qxl/-/commit/4e1963a812f2c1777ba5d56ea9e939a3e40a0496
(This is the
On 14. 01. 23 12:45, Susi Lehtola wrote:
On 1/12/23 20:57, Miro Hrončok wrote:
On 12. 01. 23 18:53, Susi Lehtola wrote:
On 1/12/23 19:48, Miro Hrončok wrote:
On 12. 01. 23 18:42, Susi Lehtola wrote:
On 12/5/22 13:36, Miro Hrončok wrote:
The following packages are orphaned
On 13. 01. 23 0:35, Chuck Anderson wrote:
For receiving/filtering emails, you can filter on the List-Id: header
rather than the To: or Cc: headers. In that way you can differentiate
between normal list distribution and Bcc:. If there is no List-Id:
header, the mail can be directed to your
On Monday, 05 December 2022 at 12:36, 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
On Thursday, 12 January 2023 at 18:42, Susi Lehtola wrote:
> On 12/5/22 13:36, 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 shou
801 - 900 of 13319 matches
Mail list logo
