.1-0.12.fc28
> from the 9th...
>
> What gives? It can't just be slow mirror propagation...
Try with --enablerepo local.
There hasn't been any successful rawhide compose in a couple days.
--
Mikolaj Izdebski
Senior Software Engineer, Red Hat
IRC: mizdebsk
fix}/lib and put plugins there.
--
Mikolaj Izdebski
Senior Software Engineer, Red Hat
IRC: mizdebsk
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
plain what's so complicated about it?
--
Mikolaj Izdebski
Senior Software Engineer, Red Hat
IRC: mizdebsk
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Co
eric way. Once that was eliminated as a possible requirement, the rest
> fell into place fairly neatly.
Allowing parallel installation of two distinct package sets, provided
that they don't conflict in any way - how is that impossible? I get
that it's not a goal for modularity to support this, but I don
On 06/20/2018 04:15 PM, Stephen Gallagher wrote:
> On Wed, Jun 20, 2018 at 10:06 AM Mikolaj Izdebski
> wrote:
>
>> On 06/20/2018 02:30 PM, Petr Šabata wrote:
>>> Parallel installation of streams on a single system indeed
>>> isn't supported at this point and isn'
-backend01.phx2.fedoraproject.org
koschei-polling[4264]: Deleting build Build(id=5052601, package=python3,
collection=f29, state=running, task_id=28608653) because it was canceled
>
>
> [0] https://bugzilla.redhat.com/show_bug.cgi?id=1609291
> [1] https://apps.fedoraproject.org/kosch
On 07/30/2018 01:49 PM, Miro Hrončok wrote:
> On 30.7.2018 12:42, Mikolaj Izdebski wrote:
>> On 07/30/2018 11:19 AM, Miro Hrončok wrote:
>>> Hi,
>>>
>>> I've filled this bugzilla: [0] and I clearly remember seeing a failed
>>> build in koschei - I
eatures, do bootstrap builds etc.).
* auto-provides (packages are built before generating final build order)
* rich deps (for dependency solving it uses libsolv via hawkey API)
[1]
https://github.com/fedora-java/modularity-utils/blob/master/generate-modulemd.py
--
Mikolaj Izdebski
Senio
] https://github.com/fedora-java/javapackages/pull/63
[3] https://bugzilla.redhat.com/show_bug.cgi?id=1600426
--
Mikolaj Izdebski
Senior Software Engineer, Red Hat
IRC: mizdebsk
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send
tter choice can be pickup zopfli again?
>
> [1]
> https://src.fedoraproject.org/rpms/fedora-logos/blob/master/f/fedora-logos.spec#_30
>
--
Mikolaj Izdebski
Senior Software Engineer, Red Hat
IRC: mizdebsk
___
devel mailing list -- de
ou're an admin then you can click the "Give the XXX project" button
> at the bottom. That will change the "main admin", and I'm pretty sure
> you can use it to promote yourself from admin to main admin.
I don't think that's true. You can change main admin of any package
On 08/29/2018 11:23 AM, Adam Samalik wrote:
> On Tue, Aug 28, 2018 at 1:23 AM Mikolaj Izdebski
> wrote:
>
>> Some modules are built in MBS/Koji but are never released to users.
>> Currently such modules can only be used as build dependencies of other
>> modules.
https://release-engineering.github.io/mbs-ui/
(not hosted by Fedora Infrastructure)
--
Mikolaj Izdebski
Senior Software Engineer, Red Hat
IRC: mizdebsk
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fe
[2]
https://src.fedoraproject.org/modules/javapackages-tools/blob/201801/f/javapackages-tools.yaml
--
Mikolaj Izdebski
Senior Software Engineer, Red Hat
IRC: mizdebsk
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email t
to non-retired
arbitrary branches? I assume yes, but I'd rather ask in advance.
[1] https://fedoraproject.org/wiki/Changes/ArbitraryBranching
--
Mikolaj Izdebski
Senior Software Engineer, Red Hat
IRC: mizdebsk
___
devel mailing list -- devel
sn't have a Group: tag" check
> in fedora-review, instead of rpmlint?
Fedora-Review doesn't need to be run during package review. It's not
even recommended in review guidelines. On the other hand running rpmlint
is mandatory, it's the very first MUST item in the guidelines.
--
Mikolaj Izdebski
rom the default system settings, or if koji sets is specifically.
When LANG is not set mock sets it to en_US.UTF-8.
Fedora Koji doesn't configure LANG, AFAIK.
--
Mikolaj Izdebski
Senior Software Engineer, Red Hat
IRC: mizdebsk
___
devel mailing list
oji mock-config --tag f29-build --arch x86_64 >my.cfg
mock -r ./my.cfg [...]
--
Mikolaj Izdebski
Senior Software Engineer, Red Hat
IRC: mizdebsk
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.f
chroot
setup can take about 30 seconds.
Once this is optimized, another slow part is loading repodata into
memory - uncompressing it, parsing and creating internal libsolv data
structures. This could be speeded up by including solv/solvx files in
repodata, but I think that would require some code
On 07/11/2018 07:31 PM, Andrew Lutomirski wrote:
> On Wed, Jul 11, 2018 at 10:08 AM, Mikolaj Izdebski
> wrote:
>>
>> On 07/11/2018 06:37 PM, Andrew Lutomirski wrote:
>>> From my perspective as an occasional Fedora packager, I'm regularly
>>> surprised by just
On 07/11/2018 09:26 PM, Kevin Fenzi wrote:
> On 07/11/2018 10:53 AM, Mikolaj Izdebski wrote:
>> On 07/11/2018 07:31 PM, Andrew Lutomirski wrote:
>>> On Wed, Jul 11, 2018 at 10:08 AM, Mikolaj Izdebski
>>> wrote:
>>>>
>>>> The slowest par
On 07/12/2018 10:17 PM, Richard W.M. Jones wrote:
> On Thu, Jul 12, 2018 at 02:10:37PM -0400, Cole Robinson wrote:
>> On 07/11/2018 04:37 PM, Kevin Fenzi wrote:
>>> On 07/11/2018 12:57 PM, Mikolaj Izdebski wrote:
>>>> On 07/11/2018 09:26 PM, Kevin Fenzi wrote:
>
License of glassfish-el-javadoc package was changed
from: CDDL-1.1 or GPLv2 with exceptions
to: (CDDL or GPLv2 with exceptions) and ASL 2.0
https://src.fedoraproject.org/rpms/glassfish-el/c/a6128b12aa9e18b5adc9701fcfe36d68b3c764b8
--
Mikolaj Izdebski
Senior Software Engineer, Red Hat
IRC
that nosync is implemented with a LD_PRELOAD. I wonder if it wouldn't be
> more robust to use nspawn's syscall filter to filter the fsync calls.
> (If nspawn is already used by koji, not sure.)
Koji does not use systemd-nspawn. It uses plain old chroot.
--
Mikolaj Izdebski
Senior Software Eng
e koji repos
(or new kind of buildroot compose) to install packages from
[1] https://pagure.io/releng/issue/7840
>
> On Mon, Sep 24, 2018, 13:11 Mikolaj Izdebski wrote:
>
>> TL;DR I am planning to orphan Java packages listed below soon after
>> Fedora 29 GA. Let me know if you want
On 09/27/2018 04:34 PM, Neal Gompa wrote:
> On Mon, Sep 24, 2018 at 3:39 PM Mikolaj Izdebski wrote:
>>
>> Java SIG is dying slowly, this package set recently lost another
>> co-maintainer and I don't have time to maintain all these packages by
>> myself. Switc
On 09/24/2018 11:25 PM, Ben Rosser wrote:
> On Mon, Sep 24, 2018 at 3:39 PM, Mikolaj Izdebski wrote:
>> On 09/24/2018 08:52 PM, Miro Hrončok wrote:
>>> On 24.9.2018 19:09, Mikolaj Izdebski wrote:
>>>> I'm in the process of transitioning maintenance of all software to
On 09/26/2018 04:17 AM, Kevin Kofler wrote:
> Mikolaj Izdebski wrote:
>> I'm in the process of transitioning maintenance of all software to
>> modules only. The reason is that module maintenance is much easier
>> compared to maintenance of non-modular, "ursine" packa
On 09/26/2018 08:01 AM, Raphael Groner wrote:
>>> Mikolaj Izdebski wrote:
>>>
>>> This is exactly what I feared when the modules were first proposed:
>>> essential packages moving to modules only.
>>>
>>> I think this is abso
On 09/28/2018 02:50 AM, Kevin Kofler wrote:
> Mikolaj Izdebski wrote:
>> Modules with their API specifications at least make it more clear what
>> are expectations about packages. Something user may consider essential
>> is only a build dependency for a packager and the p
I've just orphaned rpms/fedora-review-plugin-java.
This package was recently assigned to me in mass ownership reassignment
and I did not realize I was the owner, until now.
I never intended to maintain this package.
--
Mikolaj Izdebski
Senior Software Engineer, Red Hat
IRC: mizdebsk
can help with the
> 2 new Java packages required to upgrade antlr4, and the actual upgrade
> itself?
>
--
Mikolaj Izdebski
Senior Software Engineer, Red Hat
IRC: mizdebsk
___
devel mailing list -- devel@lists.fedoraproject.org
T
-ant-tasks
jenkins-openid-plugin
keytool-maven-plugin
pmd
pmd-build-tools
tycho-pomless
werken-xpath
xpp2
--
Mikolaj Izdebski
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le
er if it would be one repo with
> branches 0.6, 0.7 instead of multiple separate git repos.
>
> If not, what are the limitations?
There are no technical limitations for building packages like that in
Koji, but you won't be able to tag them unless %{name} is added to
appropriate tag.
--
Mi
he-commons-jxpath apache-commons-lang
apache-commons-logging apache-commons-net
yyang maven-plugin-testing maven-plugin-tools maven-wagon modello
plexus-containers
--
Mikolaj Izdebski
Senior Software Engineer, Red Hat
IRC: mizdebsk
___
devel ma
On 09/24/2018 08:52 PM, Miro Hrončok wrote:
> On 24.9.2018 19:09, Mikolaj Izdebski wrote:
>> I'm in the process of transitioning maintenance of all software to
>> modules only. The reason is that module maintenance is much easier
>> compared to maintenance of non-modul
On Mon, Dec 3, 2018 at 5:55 AM David Airlie wrote:
>
> So we ship a jenkins in F29 at least that is broken on install due to
> what looks like an incompatability with dom4j.
>
> Upstream it looks like jenkins via stapler-jelly uses a fork of dom4j,
> and the standard dom4j shipped in Fedora
On Thu, Mar 28, 2019 at 12:49 AM Miro Hrončok wrote:
>
> On 05. 02. 19 11:07, Mikolaj Izdebski wrote:
> > I've just orphaned 259 packages listed below. Almost all of them are
> > Java packages which I will continue to maintain as part of modules.
> > Intent to orphan th
On Thu, Mar 28, 2019 at 8:44 AM Vít Ondruch wrote:
> Trying to take look from the other side, the java.yaml might need some
> love [1], because the GH links are broken [2, 3]
java module doesn't have any complete builds. It is not actively maintained.
--
Mikolaj Iz
On Thu, Mar 28, 2019 at 3:04 PM Miro Hrončok wrote:
> On 28. 03. 19 14:49, Mikolaj Izdebski wrote:
> > On Thu, Mar 28, 2019 at 12:49 AM Miro Hrončok wrote:
> >>
> >> I took over google-gson, but I see no stream branch.
> >
> > IIRC google-gson is
On Thu, Mar 28, 2019 at 7:46 PM Christopher wrote:
>
> On Thu, Mar 28, 2019 at 9:50 AM Mikolaj Izdebski wrote:
> > - javapackages-tools, stream 201801 (buildroot-only module, not
> > intended to be delivered to users)
>
> How do I enable/install this module locally?
bility"
and other policies and documents. By limiting "supported" use case of
the module to only building other Fedora package I can reduce the work
required to maintain the module by at least a factor of two.
--
Mikolaj Izdebski
___
On Sat, Mar 30, 2019 at 1:34 AM Christopher wrote:
>
> On Fri, Mar 29, 2019 at 5:24 AM Mikolaj Izdebski wrote:
> >
> > On Thu, Mar 28, 2019 at 7:46 PM Christopher
> > wrote:
> > >
> > > On Thu, Mar 28, 2019 at 9:50 AM Mikolaj Izdebski
> > >
ursine" buildroots. plexus-utils is a modular package
and I will continue to maintain it as part of modules. Making it
possible to use modular packages as build dependencies will allow
plexus-utils (and hundreds of other packages) to be safely retired
without affecting other
On Fri, Mar 1, 2019 at 11:31 AM Fabio Valentini wrote:
>
> On Fri, Mar 1, 2019 at 11:28 AM Mikolaj Izdebski wrote:
> >
> > On Fri, Mar 1, 2019 at 10:29 AM Fabio Valentini
> > wrote:
> > > I agree, this change to mock-core-configs seems to have been rushed
&g
e modules.
--
Mikolaj Izdebski
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject
proper modulemd document
- build some (zero or more) RPM packages using rpmbuild
- create YUM repodata from built packages using createrepo_c
- attach modulemd to repodata using modifyrepo_c
--
Mikolaj Izdebski
___
devel mailing list -- devel@lists.f
t generates a
new config dynamically. These generated configs don't include any
modular repos.
--
Mikolaj Izdebski
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of
On Wed, Mar 13, 2019 at 11:59 AM Florian Weimer wrote:
>
> * Mikolaj Izdebski:
>
> > On Tue, Mar 12, 2019 at 4:42 PM Miroslav Suchý wrote:
> >> Alternative sum up:
> >> * People (not just Mikolaj) started using modules, while Koji cannot use
> >&
ut 185 packages in that module. That set
of packages is self-hosting (doesn't depend on any other Java packages
except OpenJDK) and gives you two basic build systems (Maven, Ant)
with RPM integration.
--
Mikolaj Izdebski
___
devel mailing list --
On Wed, Mar 13, 2019 at 12:49 PM Florian Weimer wrote:
>
> * Mikolaj Izdebski:
>
> >> As far as I understand it, under the Koji model, one of the tags wins,
> >> and which one determines whether you get the Python 2 subpackage or the
> >> Python 3 subpackage.
rchitectures.
And it is still used by third parties to rebuild Fedora packages.
--
Mikolaj Izdebski
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfed
On Tue, Mar 12, 2019 at 12:36 PM Neal Gompa wrote:
> This whole process was handled in the worst possible way. To sum up:
> * No one knew Java SIG was having manpower issues because Mikolaj
> didn't know how to ask for help
You did not know that, but the situation in Java SIG is well known to
ance do you expect?
There is no "Java maintainers team" in Fedora. Java packages are
maintained by individual packagers. Theoretically there exists a Java
SIG, but its activity is limited to a couple of emails per year, with
significant part of them talking about orphaning or retiring pa
stead I encourage people to talk about the problem. I hope FESCo
will finally realize how important it is to allow building any package
against modules and change the policy, allowing modules to be used as
build dependencies for non-modular packages.
--
Mikolaj Izdebski
__
ly builds non-modular
contents against modules. It's Fedora developers (represented by
elected body of FESCo) that don't want to use modules in Fedoras' Koji
installation.
--
Mikolaj Izdebski
___
devel mailing list -- devel@lists.fedoraproject.org
To un
On Tue, Mar 12, 2019 at 12:17 PM Dominik 'Rathann' Mierzejewski
wrote:
>
> On Tuesday, 12 March 2019 at 12:02, Mikolaj Izdebski wrote:
> > On Tue, Mar 12, 2019 at 11:49 AM Jakub Jelen wrote:
> > >
> > > Is there already a way to package the java application as a
g the sparse
> modularity documentation.
The approach I used to build my modules should be described in "MBI
(playground 2.0)" on this list. I don't want to spend too much time on
describing the process in very detail - I am actively working on
ckages. Notably,
OpenJDK, Tomcat, Eclipse, Wildfly, Jenkins packages are not modular.
Moreover, all modular Java packages also have non-modular versions.
Only 260 out of ~1.4 Java packages are orphaned. Other packages still
have owners.
--
Mikolaj Izdebski
>
> Tom
>
> --
> Tom Hu
On Mon, Feb 11, 2019 at 11:19 PM Fabio Valentini wrote:
> I'm curious: What happens to modules when a package's master branch
> gets retired?
Nothing. Modules will continue to exist and will continue to be
delivered to users.
--
Mikolaj Iz
orphan
user and announce it on devel list so that anyone interested
(including comaintainers) can adopt orphaned package. This is exactly
what I did.
--
Mikolaj Izdebski
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe s
On Fri, Feb 1, 2019 at 8:46 AM Nicolas Mailhot
wrote:
> If MBI is about hiding build packages I don't see the point and I'm not
> interested.
It's the opposite - it's about opening build process to others and
allowing for collaboration. Instead of doing development by yourself
in private, you
On Thu, Jan 31, 2019 at 11:16 PM Kevin Fenzi wrote:
> > https://pagure.io/fesco/issue/2068
> >
> > And, after all, those packages shouldn’t be shipped to users.
>
> This of course means however that users who want to build their own
> verions of the applications or whatever can't start from our
On Fri, Feb 1, 2019 at 2:28 AM Kevin Fenzi wrote:
>
> On 1/31/19 4:52 PM, Neal Gompa wrote:
>
> ...snip...
>
> > COPR was supposed to be that outlet, but no one gives a damn about it.
> > Everyone complains that the service is "bad" and that the design is
> > "bad" but no one wants to actually
On Fri, Feb 1, 2019 at 3:37 PM Miroslav Suchý wrote:
> Dne 01. 02. 19 v 13:21 Mikolaj Izdebski napsal(a):
> > - builds failing to import to COPR distgit (was not a problem before
> > dist-git was introduced)
>
> This is actually new to me. Can you point me to some report
On Fri, Feb 1, 2019 at 4:48 PM Kevin Fenzi wrote:
> >>>It is not official build system of Fedora which is not helping with
> >>> Problem
> >>>№2: Testing of new rpm/koji/mock features/configuration
> >>>
> >>>
On Thu, Jan 31, 2019 at 1:36 PM Josh Boyer wrote:
> Why does this need to be deployed in the fedora infrastructure cloud?
> Seems like you could stand it up in AWS or somewhere else.
Because we (Fedora contributors) don't have budget to pay AWS bills.
If someone is willing to sponsor this then
xstream
xz-java
zinc
zopfli
--
Mikolaj Izdebski
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https
Hi Tomas,
On Mon, Jan 28, 2019 at 2:19 PM Tomas Radej wrote:
> I am orphaning xsel as I don't have time to maintain it. The recent gcc
> update means xsel no longer compiles.
>
> I am not sure if it is worth maintaining xsel when xclip is packaged as well,
> so if someone think so, please take
On Sat, Apr 13, 2019 at 12:17 PM Fabio Valentini wrote:
>
> On Fri, Apr 12, 2019 at 5:03 PM Mikolaj Izdebski wrote:
> >
> > On Mon, Mar 18, 2019 at 3:20 PM Mat Booth wrote:
> > > Eclipse in Fedora has dropped support for 32 bit architectures. The
> > > n
On Sat, Apr 13, 2019 at 12:42 PM Mikolaj Izdebski wrote:
> But EclipseLink is not the only available implementation of JPA. We
> also have other implementations packaged. The ones I am aware of:
> Hibernate 5, Hibernate 4, Hibernate 3, Apache OpenJPA.
Searching in Java Deptools [1]
modules (maven, ant, javapackages-tools) are not affected by this
issue and they continue to work and build on 32-bit arches.
--
Mikolaj Izdebski
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedorapr
On Tue, Apr 16, 2019 at 3:26 PM Jun Aruga wrote:
>
> Hi,
>
> I like to see "package branch name" of each modules to be aligned more.
>
> Here is a list of the current module, the module stream name, the
> package branch name, another package name. There are some patterns on
> the list.
>
> #
foo:
> > buildafter:
> > - bar
> >
>
> How does foo.spec get to know that it should enable bootstrapping in
> foo-bootstrap component, but disable it in foo component?
You can use different refs (and therefore different spec files) for
foo and foo-bootstrap.
/fedora-rawhide-armhfp.cfg.rpmnew. Can somebody
> with admin privileges fix that up, please?
Thanks for the report. I've fixed the problem.
Issues with maintainer test machines should be reported to the
respective contact listed on the wiki page [1], in this case
ad...@fedoraproject.org
--
Mi
On Sun, Aug 25, 2019 at 2:33 PM Igor Gnatenko
wrote:
> I see that there is no Fedora 31. Is anybody working on creating that
> and moving rawhide forward to 32?
Koschei branching is now complete. Sorry for the delay - it was caused
by scheduled vacation of mine [1,2] as well as other unexpected
: CDDL-1.0 or GPLv2 with exceptions
--
Mikolaj Izdebski
___
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
On Tue, Jul 23, 2019 at 5:24 PM Miro Hrončok wrote:
>
> On 23. 07. 19 16:08, Mikolaj Izdebski wrote:
> > On Tue, Jul 23, 2019 at 1:50 PM Miro Hrončok wrote:
> >> I acknowledge that it is your right to orphan essentially anything you
> >> want,
> >>
kager and added as co-maintainer.
[1] https://fedora-java.github.io/howto
[2] https://fedoraproject.org/wiki/SIGs/Java
--
Mikolaj Izdebski
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.
packages. If there are any issues with javapackages-tools then
please open bugs and I will respond to them.
--
Mikolaj Izdebski
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedo
On Mon, Aug 5, 2019 at 1:50 PM Hans de Goede wrote:
>
> Hi Fabio,
>
> On 05-08-19 13:37, Fabio Valentini wrote:
> > On Mon, Aug 5, 2019 at 1:15 PM Mikolaj Izdebski wrote:
> >>
> >> On Mon, Aug 5, 2019 at 12:07 PM Hans de Goede wrote:
> &g
ackages as others depend on them. But after
the recent mass-retirement of packages Eclipse packages are FTBFS [1]
in rawhide and will be retired by releng, unless someone fixes them
before Fedora 32 branching.
[1] https://apps.fedoraproject.org/koschei/groups/eclipse?collection=f31
--
Mikolaj Izdeb
ing new Java packagers, other than lack of people to be
onboarded.
--
Mikolaj Izdebski
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedorapr
, but starting from Fedora 32 I will maintain modular
versions only.
--
Mikolaj Izdebski
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https
On Tue, Jul 23, 2019 at 1:50 PM Miro Hrončok wrote:
> On 23. 07. 19 13:27, Mikolaj Izdebski wrote:
> > Soon after Fedora 31 branching I intend to retire java-packaging-howto
> > package and orphan byaccj and javapackages-tools packages. The reason
> > is that I intend to ma
packages which are used for building Java RPM
> packages in fedora) will need to be maintained as non-modular packages
> indefinitely.
That is not true. It is entirely possible and feasible to build a distribution
without ursine Maven/XMvn etc. For example look at RHEL 8 - it includes
Maven and An
edora contributors - maintainers who can more easily build packages have
more time to spend on important bugs and features affecting users, can get more
involved in other Fedora activities etc.
--
Mikolaj Izdebski
___
devel mailing list -- devel@lists.f
On Mon, Nov 18, 2019 at 12:17 PM John M. Harris Jr wrote:
>
> On Monday, November 18, 2019 3:42:20 AM MST Mikolaj Izdebski wrote:
> > IMHO effort spent on maintenance of most of these ursine Java packages
> > is mostly wasted effort. As I said before, many times, these p
the benefits they might provide.
What do you mean by "disallowing" default streams? Do you mean
removing them from Fedora?
--
Mikolaj Izdebski
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@l
n and ant packages with JDK 11 (and not building all libraries
> in the module with JDK 11)?
These libraries will still be built with JDK <= 8 bytecode, so they
should continue to work with JDK 8.
--
Mikolaj Izdebski
___
devel mailing list -- devel@lists.f
On Fri, Oct 25, 2019 at 8:47 PM Miro Hrončok wrote:
>
> On 25. 10. 19 19:30, Mikolaj Izdebski wrote:
> > Hello,
> >
> > Currently default Java runtime in Fedora is OpenJDK 8. This is not the
> > latest OpenJDK packaged, but still remains system-default version.
&g
be
built with javapackages-tools module, maintained by me.
[1] https://koji.kjnet.xyz/kojifiles/repos/m36/latest/x86_64/
[2] https://pagure.io/fm-orchestrator/issue/1321
--
Mikolaj Izdebski
___
devel mailing list -- devel@lists.fedoraproject.org
To
order, meaning that any builds submitted after module
component builds will be picked up after modular builds.
> I hope that's some sign that something is not working as intended?
This is expected behaviour of MBS.
--
Mikolaj Izdebski
__
g it is possible as long as its dependencies are packaged
and included in Fedora. To enable it, first make sure that its
dependencies (i.e. "gradle" and "xmvn-connector-gradle") are in
Fedora, then open a bug against "javapackages-tools"
On Mon, Jan 27, 2020 at 1:08 PM Miro Hrončok wrote:
>
> On 27. 01. 20 10:34, Mikolaj Izdebski wrote:
> > On Mon, Jan 27, 2020 at 6:04 AM Bill Chatfield via devel
> > wrote:
> >>
> >> I have chosen a delinquent Java package to work fix. But I need some h
or open issue at
https://github.com/fedora-java/javapackages/issues
--
Mikolaj Izdebski
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.
mbs.fedoraproject.org is maintained by Infrastructure Team [1]. You
can report issues at [2].
[1] https://fedoraproject.org/wiki/Infrastructure
[2] https://pagure.io/fedora-infrastructure/issues
--
Mikolaj Izdebski
On Mon, Feb 17, 2020 at 12:20 PM Stephan Bergmann wrote:
>
> I am trying
eeing such problems until they are reported by users.
I've just scaled scheduler up and it seems to be running again.
Thanks for the report.
--
Mikolaj Izdebski
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe
s, but in
general you'd need to obtain Maven POMs for particular project (eg.
from Maven Central), add missing build instructions ( section
of POM files) and model composition/inheritance ( and
elements of POM). There are several cases of packages that
are built this way in Fedora, which you can use as example
may change in the future - as
more projects start to use Gradle I may decide to take up its
maintenance in upcoming years.
--
Mikolaj Izdebski
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedor
201 - 300 of 382 matches
Mail list logo
