Hi Vit,
On 3/12/19 5:40 PM, Vít Ondruch wrote:
> Will it help to mitigate issues such as:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1284684
>
This is related to the following change which was made in Fedora 23:
https://fedoraproject.org/wiki/Changes/Harden_All_Packages.
My proposal does
https://bugzilla.redhat.com/show_bug.cgi?id=1688060
Bug ID: 1688060
Summary: perl-Log-Dispatchouli-2.017 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: perl-Log-Dispatchouli
Keywords: FutureFeature,
https://bugzilla.redhat.com/show_bug.cgi?id=1688059
Bug ID: 1688059
Summary: perl-Encode-3.01 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: perl-Encode
Keywords: FutureFeature, Triaged
Missing expected images:
Atomichost qcow2 x86_64
Atomichost raw-xz x86_64
Compose FAILS proposed Rawhide gating check!
9 of 47 required tests failed, 8 results missing
openQA tests matching unsatisfied gating requirements shown with **GATING**
below
Unsatisfied gating requirements that could
On Tue, Mar 12, 2019 at 6:03 PM Randy Barlow
wrote:
> As Miro said in another post, it's not that FESCo doesn't want to use
> modules in Koji, it's that we want to make sure that the packager
> experience is as good as it was pre-modularity, and in particular that
> packagers can build locally as
On Tue, Mar 12, 2019 at 2:53 AM Zdenek Dohnal wrote:
>
> IMHO Stephen meant it as driverless 'driver' or IPP everywhere enabled
> printer, since 'generic IPP driver' does not exist.
OK.
> >
> > What supports IPP Everywhere out of the box?
> >
> > Any computer running CUPS 1.5 or later
> I beg
https://bugzilla.redhat.com/show_bug.cgi?id=1684255
Fedora Update System changed:
What|Removed |Added
Fixed In Version|perl-Locale-Codes-3.60-1.fc |perl-Locale-Codes-3.60-1.fc
https://bugzilla.redhat.com/show_bug.cgi?id=1680158
Fedora Update System changed:
What|Removed |Added
Status|ON_QA |CLOSED
Fixed In Version|
https://bugzilla.redhat.com/show_bug.cgi?id=1679806
Fedora Update System changed:
What|Removed |Added
Fixed In Version|perl-Socket-2.029-1.fc30|perl-Socket-2.029-1.fc30
On Tue, 2019-03-12 at 22:18 +0100, Mikolaj Izdebski wrote:
> It's Fedora developers (represented by
> elected body of FESCo) that don't want to use modules in Fedoras'
> Koji
> installation.
As Miro said in another post, it's not that FESCo doesn't want to use
modules in Koji, it's that we want
On 12. 03. 19 22:11, Mikolaj Izdebski wrote:
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.
Oh we do realize. Especially since everything will
https://bugzilla.redhat.com/show_bug.cgi?id=1684255
Fedora Update System changed:
What|Removed |Added
Status|ON_QA |CLOSED
Fixed In
https://bugzilla.redhat.com/show_bug.cgi?id=1679806
Fedora Update System changed:
What|Removed |Added
Status|ON_QA |CLOSED
Fixed In
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 module or
> > > we will really
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
> modular repos.
Incorrect. Koji (the software) *can* use modular repos. I know of more
than one installation of Koji that successfully builds
On Tue, Mar 12, 2019 at 6:20 PM Christopher wrote:
> Addendum: some of us part-time packagers, which depended on these
> packages to build our own Java packages don't know how to convert to
> modular packaging. I'm still trying to learn in my spare time, but I
> don't know where to look and have
https://bugzilla.redhat.com/show_bug.cgi?id=1688004
Bug ID: 1688004
Summary: perl-Test-Inter-1.08 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: perl-Test-Inter
Keywords: FutureFeature, Triaged
On Tue, Mar 12, 2019 at 3:11 PM Jakub Jelen wrote:
>
> On Tue, 2019-03-12 at 13:43 +0200, Aleksandar Kurtakov wrote:
> > Hmm,
> > https://lists.fedoraproject.org/archives/list/java-de...@lists.fedoraproject.org/thread/MQMRQVENBLDRS67WLNQ7EOCMSDI5WIET/
> > seems that people had a lot of time to
https://pagure.io/389-ds-base/pull-request/50278
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
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: If
On 3/12/19 8:38 AM, Randy Barlow wrote:
> On Mon, 2019-03-11 at 21:55 +0100, Tomasz Torcz wrote:
>> Hmm, rebulding container on config change? Sounds fishy.
>> Have you tried putting production.ini into ConfigMap?
>
> It is in a configmap:
>
>
On 3/12/19 4:14 AM, Vít Ondruch wrote:
>
> Dne 11. 03. 19 v 19:29 Kevin Fenzi napsal(a):
>> On 3/11/19 4:31 AM, Vít Ondruch wrote:
>>> Hi,
>>>
>>> Can somebody please enlighten me, how to update Rawhide after branching
>>> and not using --nogpgcheck?
>> Can you expand on the case here?
>>
>> What
On 3/11/19 11:45 AM, Fabio Valentini wrote:
>
> I'm having a similar problem, but with Silverblue / rawhide.
>
> I installed the system when rawhide was still f30, but now I can't run
> "rpm-ostree upgrade" anymore, due to this error:
>
> Enabled rpm-md repositories: rawhide
> Updating
Dear all,
You are kindly invited to the meeting:
EPEL Steering Co on 2019-03-13 from 18:00:00 to 19:00:00 GMT
At freenode@fedora-meeting
The meeting will be about:
This is the weekly EPEL Steering Committee Meeting. Agenda is in the
On Tue, Mar 12, 2019 at 7:57 AM Christophe de Dinechin
wrote:
>
> I tried to compile your preprocessed fragment with both clang or gcc.
> Interestingly:
>
> 1) Without your command-line options, I don’t see the same error.
>
> 2) With your command-line options, I see the error with gcc, but not
https://pagure.io/389-ds-base/pull-request/50256
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
On Tue, Mar 12, 2019 at 11:43 AM Miroslav Suchý wrote:
>
> Dne 12. 03. 19 v 12:34 Neal Gompa napsal(a):
> > 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
> > * Now it's
The epel7 python rebuild has finished. All of the resulting packages
are now in Bohdi updates.
They will remain in updates until at least April 2.
They have not made it into epel-testing yet.
Due to a Bohdi bug [1], we had to break up the updates. So we now
have 6 updates, that we will treat as
Le 2019-03-12 17:34, Zbigniew Jędrzejewski-Szmek a écrit :
I think Fedora has managed to avoid many of the issues Michael list:
…
We do have other problems... but I think ours are quite a bit
different than Debian's.
Yes, we do have the same class of problems (old infra and processes that
On Tue, Mar 12, 2019 at 11:52:50AM -0400, Przemek Klosowski wrote:
> A longtime Debian developer Michael Stapelberg described his
> frustrations with their distribution development environment
>
> https://michael.stapelberg.ch/posts/2019-03-10-debian-winding-down/
>
> Many points are spookily
For your information:
perl-true's license has changed from "Same as Perl" (GPL+ or Artistic) to
"Artistic 2.0".
This happened when the version changed from 0.18 to 1.0.1 today. I've
built the newly-licensed version in f30 and rawhide.
Regards, Paul.
#fedora-meeting-3: Weekly Meeting of the Modularity Team
Meeting started by nils at 15:00:00 UTC.
Minutes:
A longtime Debian developer Michael Stapelberg described his
frustrations with their distribution development environment
https://michael.stapelberg.ch/posts/2019-03-10-debian-winding-down/
Many points are spookily similar to issues in Fedora, as discussed on
this list, for instance the
Hello,
I've just enabled F30 chroots in Copr.
The projects that have "Follow Fedora branching" enabled, have them
automatically activated as well builds from rawhide forked into them.
Jakub
___
devel mailing list -- devel@lists.fedoraproject.org
To
Dne 12. 03. 19 v 12:34 Neal Gompa napsal(a):
> 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
> * Now it's too late because he orphaned nearly 1700 packages to force
>
On Mon, 2019-03-11 at 21:55 +0100, Tomasz Torcz wrote:
> Hmm, rebulding container on config change? Sounds fishy.
> Have you tried putting production.ini into ConfigMap?
It is in a configmap:
On Tue, 2019-03-12 at 12:16 +0100, Dominik 'Rathann' Mierzejewski
wrote:
> Maybe, but it will cause the removal of other packages that depend on
> their regular (non-modular) builds. You are forcing the hands of
> their
> maintainers before the infrastructure to make modular packages
> available
>
On Tue, Mar 12, 2019 at 1:55 PM Colin Walters wrote:
>
>
> On Mon, Mar 11, 2019, at 2:46 PM, Fabio Valentini wrote:
> >
> > I'm having a similar problem, but with Silverblue / rawhide.
> >
> > I installed the system when rawhide was still f30, but now I can't run
> > "rpm-ostree upgrade"
On Tue, 2019-03-12 at 13:43 +0200, Aleksandar Kurtakov wrote:
> On Tue, Mar 12, 2019 at 1:36 PM Neal Gompa
> wrote:
>
> > On Tue, Mar 12, 2019 at 7:29 AM Aleksandar Kurtakov <
> > akurt...@redhat.com>
> > wrote:
> > > On Tue, Mar 12, 2019 at 1:17 PM Dominik 'Rathann' Mierzejewski <
> >
https://bugzilla.redhat.com/show_bug.cgi?id=1687604
Petr Pisar changed:
What|Removed |Added
Status|ASSIGNED|CLOSED
Fixed In Version|
On Mon, Mar 11, 2019, at 2:46 PM, Fabio Valentini wrote:
>
> I'm having a similar problem, but with Silverblue / rawhide.
>
> I installed the system when rawhide was still f30, but now I can't run
> "rpm-ostree upgrade" anymore, due to this error:
>
> Enabled rpm-md repositories: rawhide
>
On 12. 03. 19 13:44, Chris Lalancette wrote:
Sorry for not responding earlier.
I'm not really involved with imagefactory at all, though I am still the
maintainer of Oz. As Daniel pointed out, you'll want to start with Ian Mcleod
for that package (he can point you in the right direction).
On Tue, Mar 12, 2019 at 8:35 AM Mikolaj Izdebski wrote:
>
> 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
>
>
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
Find below a list of topics which are planned to be discussed in the
Fedora Modularity Team meeting on Tuesday at 15:00 UTC in
#fedora-meeting-3 on irc.freenode.net.
To find out when this is in your local time zone, check the Fedora
Calendar (if you've set it and are logged in):
Will it help to mitigate issues such as:
https://bugzilla.redhat.com/show_bug.cgi?id=1284684
and mitigate workarounds such as:
https://bugzilla.redhat.com/show_bug.cgi?id=1543394
That would be wonderful.
Also, while OT to this specific change, I would love to have ability to
have some
Dne 12. 03. 19 v 11:11 Miro Hrončok napsal(a):
> https://bugzilla.redhat.com/show_bug.cgi?id=1659737
>
> Anyone knows how to contact the maintainer?
>
Last time I was in contact with Chris was via his email:
clalance...@gmail.com
He is still active from time to time:
Dne 12. 03. 19 v 12:46 Vít Ondruch napsal(a):
>
>
> Dne 12. 03. 19 v 12:14 Vít Ondruch napsal(a):
>> Dne 11. 03. 19 v 19:29 Kevin Fenzi napsal(a):
>>> On 3/11/19 4:31 AM, Vít Ondruch wrote:
Hi,
Can somebody please enlighten me, how to update Rawhide after branching
and not
> On 11 Mar 2019, at 18:16, Tom Callaway wrote:
>
> Hi folks,
>
> I spent some time this weekend trying to get Chromium 72 building on Fedora,
> but I kept running into a C++ issue that I was not able to resolve. This
> happened with gcc-9.0.1-0.8.fc30.x86_64 and gcc-8.3.1-2.fc29.x86_64.
>
Dne 12. 03. 19 v 12:14 Vít Ondruch napsal(a):
> Dne 11. 03. 19 v 19:29 Kevin Fenzi napsal(a):
>> On 3/11/19 4:31 AM, Vít Ondruch wrote:
>>> Hi,
>>>
>>> Can somebody please enlighten me, how to update Rawhide after branching
>>> and not using --nogpgcheck?
>> Can you expand on the case here?
>>
>>
On Tue, Mar 12, 2019 at 1:36 PM Neal Gompa wrote:
> On Tue, Mar 12, 2019 at 7:29 AM Aleksandar Kurtakov
> wrote:
> >
> > On Tue, Mar 12, 2019 at 1:17 PM Dominik 'Rathann' Mierzejewski <
> domi...@greysector.net> wrote:
> >>
> >> On Tuesday, 12 March 2019 at 12:02, Mikolaj Izdebski wrote:
> >> >
On 10. 3. 2019 19:59, Tomasz Kłoczko wrote:
> On Thu, 28 Feb 2019 at 14:11, Neal Gompa wrote:
> [..]
>>> tl;dr dhcp 4.4.1 will not require bind-export-libs and will bring
>>> dhcp-libs-static with bundled version of libisc/libdns/etc
>>>
>>> As ISC dropped support of single thread build of BIND
On Tue, Mar 12, 2019 at 7:29 AM Aleksandar Kurtakov wrote:
>
> On Tue, Mar 12, 2019 at 1: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
Dne 09. 03. 19 v 12:41 Vít Ondruch napsal(a):
> Dne 09. 03. 19 v 4:03 Mamoru TASAKA napsal(a):
>> Vít Ondruch wrote on 2019/03/09 8:03:
>>> Hi,
>>>
>>> Running `dnf update`, it tries to install:
>>>
>>> Installing weak dependencies:
>>> mkpasswd x86_64 5.4.1-3.fc31
>>>
On Tue, Mar 12, 2019 at 1:17 PM Dominik 'Rathann' Mierzejewski <
domi...@greysector.net> 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 module or
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 module or
> > we will really remove all these package from Fedora?
>
> Most of Java packages listed in this thread
Dne 11. 03. 19 v 19:29 Kevin Fenzi napsal(a):
> On 3/11/19 4:31 AM, Vít Ondruch wrote:
>> Hi,
>>
>> Can somebody please enlighten me, how to update Rawhide after branching
>> and not using --nogpgcheck?
> Can you expand on the case here?
>
> What should happen is:
>
> * branching
> * f30 repos
On Tue, Mar 12, 2019 at 11:49 AM Jakub Jelen wrote:
>
> Is there already a way to package the java application as a module or
> we will really remove all these package from Fedora?
Most of Java packages listed in this thread are already packaged as
modules. Their retirement in rawhide won't
On 3/11/19 12:29 PM, Florian Weimer wrote:
* Panu Matilainen:
It's glibc's own %post own scripts that are somehow breaking it. I've
a minimal reproducer here with glibc 2.29 in /srv/root chroot. The
bash version is just to show whether bash is alive or not:
Yes, you are right, I had actually
On 12. 03. 19 11:48, Jakub Jelen wrote:
Is there already a way to package the java application as a module or
we will really remove all these package from Fedora?
You can build Java apps as modules, yes.
If we remove the mentioned packages from rawhide, it will be the only way to
build Java
Is there already a way to package the java application as a module or
we will really remove all these package from Fedora?
I am really not interested in maintaining a whole java frameworks
stack, but some guidance (not these weekly emails) from java
maintainers team that took this decision would
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: If
* Panu Matilainen:
> Because if you think about it from the point of something like glibc,
> the new version has to be installed before the old one can be
> removed. And now if you think about that, and what would happen if the
> directory in question was something like /bin instead of a rarely
>
On Tue, Mar 12, 2019 at 10:12 AM Miro Hrončok wrote:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1659737
>
> Anyone knows how to contact the maintainer?
He is occasionally active, he still has an active github account, you
can probably get hold of him via contact details there.
On Tue, Mar 12, 2019 at 11:11:01AM +0100, Miro Hrončok wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=1659737
>
> Anyone knows how to contact the maintainer?
According to git history Chris hasn't touched that package in dist-git
since the very first import in 2011, so is likely the wrong
https://bugzilla.redhat.com/show_bug.cgi?id=1659737
Anyone knows how to contact the maintainer?
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
On 12. 03. 19 11:05, Miro Hrončok wrote:
Hi,
I'm doing nonresponsive maintainer (Chris Lalancette) in
https://bugzilla.redhat.com/show_bug.cgi?id=1659737
Yet src.fp.o says the package belongs to Ian McLeod.
This is not the first time I've noticed that the bugzilla info is quite wrong,
most
Hi,
I'm doing nonresponsive maintainer (Chris Lalancette) in
https://bugzilla.redhat.com/show_bug.cgi?id=1659737
Yet src.fp.o says the package belongs to Ian McLeod.
This is not the first time I've noticed that the bugzilla info is quite wrong,
most likely very outdated.
Is this a know
On Mon, Mar 11, 2019 at 02:50:44PM -0500, Jason L Tibbitts III wrote:
> > "VO" == Vít Ondruch writes:
>
> VO> In this case, if DNF said something like "you have installed
> VO> foo-1:1.0, but there is available foo-0:2.0" it would give me
> VO> hint. From the start it would be annoying, but
Hi,
I suspect it's a chicken and egg issue:
* Look at /etc/yum.repos.d/fedora-rawhide.repo
* You can see the line:
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
* But "$releasever" is determined by the version of "fedora-release" package.
* So dnf, tries
OLD: Fedora-30-20190301.n.0
NEW: Fedora-30-20190312.n.0
= SUMMARY =
Added images:12
Dropped images: 4
Added packages: 22
Dropped packages:19
Upgraded packages: 241
Downgraded packages: 2
Size of added packages: 310.08 MiB
Size of dropped packages:228.89
Dne 11. 03. 19 v 20:50 Jason L Tibbitts III napsal(a):
>> "VO" == Vít Ondruch writes:
> VO> In this case, if DNF said something like "you have installed
> VO> foo-1:1.0, but there is available foo-0:2.0" it would give me
> VO> hint. From the start it would be annoying, but once we would
On 3/11/19 10:52 PM, Chris Murphy wrote:
> On Thu, Feb 28, 2019 at 2:56 PM Stephen Gallagher wrote:
>
>> * Printing must work on at least one printer available to Fedora QA.
>> "Work" is defined as the output from the device matching a preview
>> shown on the GNOME print preview display. (Note
Missing expected images:
Atomichost raw-xz x86_64
Atomichost qcow2 x86_64
Failed openQA tests: 10/141 (x86_64), 1/2 (arm)
ID: 362235 Test: x86_64 Workstation-live-iso desktop_update_graphical
URL: https://openqa.fedoraproject.org/tests/362235
ID: 362239 Test: x86_64
On 3/12/19 6:07 AM, Robert-André Mauchin wrote:
Hello,
I have an issue with the update of papirus-icon-theme: in the new version,
symlinks
have replaced what was previously folders and dnf errors out on this:
For example, on the current version:
$ ll /usr/share/icons/Papirus-Light/16x16
https://bugzilla.redhat.com/show_bug.cgi?id=1687686
Bug ID: 1687686
Summary: perl-Data-ObjectDriver-0.17 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: perl-Data-ObjectDriver
Keywords: FutureFeature,
Announcing the creation of a new nightly release validation test event
for Fedora 30 Branched 20190312.n.0. 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
77 matches
Mail list logo
