On Thu, 28 Mar 2019 at 12:47, M A Young wrote:
[..]
> > python3-rpm is required by dnf so it is really hard to have manageable
> > system without that part (however in extreme cases it is still possible
> to
> > drop completely dnf).
>
> You could always use microdnf instead.
>
If it is really
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 them was already announced on
On Thu, Mar 28, 2019 at 11:57 AM Miro Hrončok wrote:
>
> On 27. 03. 19 20:53, Fabio Valentini wrote:> On the other side, I don't think
> that the problem of orphaned
> > "important" packages will go away, and this group can offer
> > maintenance until a "proper" new maintainer for those packages
Hi,
Just found that on some minimal system it is not possible to remove some
rpm subpackages.
* Current state
# rpm -qa | grep rpm
rpm-libs-4.14.2.1-4.fc30.1.x86_64
rpm-4.14.2.1-4.fc30.1.x86_64
python3-rpm-4.14.2.1-4.fc30.1.x86_64
rpm-build-libs-4.14.2.1-4.fc30.1.x86_64
On 28. 03. 19 14:49, Mikolaj Izdebski wrote:
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
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 Izdebski
On 27. 03. 19 20:53, Fabio Valentini wrote:> On the other side, I don't think
that the problem of orphaned
"important" packages will go away, and this group can offer
maintenance until a "proper" new maintainer for those packages is
found.
You realize that once it is maintained by the group,
On Thu, 28 Mar 2019, Tomasz Kłoczko wrote:
> Hi,
>
> Just found that on some minimal system it is not possible to remove some rpm
> subpackages.
>
> * Current state
>
> # rpm -qa | grep rpm
> rpm-libs-4.14.2.1-4.fc30.1.x86_64
> rpm-4.14.2.1-4.fc30.1.x86_64
>
On Thu, Mar 28, 2019 at 08:52:18AM +, Zbigniew Jędrzejewski-Szmek wrote:
> On Wed, Mar 27, 2019 at 01:55:44PM +, Zbigniew Jędrzejewski-Szmek wrote:
> > I'm trying to compile systemd in koji and mock, and I'm getting suspicious
> > crashes...
> >
> > $ valgrind
Hi Ingvar,
On Thursday, March 28, 2019 11:58:21 AM CET Ingvar Hagelund wrote:
> Fedora prohibits the use of rpath, ref
> https://docs.fedoraproject.org/en-US/packaging-guidelines/#_beware_of_rpath
>
> When compiling varnish with litbool, I ensure this by the usual
>
> sed -i
On Thursday, March 28, 2019 1:27:34 PM CET Pavel Raiskup wrote:
> Hi Ingvar,
>
> On Thursday, March 28, 2019 11:58:21 AM CET Ingvar Hagelund wrote:
> > Fedora prohibits the use of rpath, ref
> > https://docs.fedoraproject.org/en-US/packaging-guidelines/#_beware_of_rpath
> >
> > When compiling
On Thu, Mar 28, 2019 at 02:14:31PM +0100, Jakub Jelinek wrote:
> On Thu, Mar 28, 2019 at 08:52:18AM +, Zbigniew Jędrzejewski-Szmek wrote:
> > On Wed, Mar 27, 2019 at 01:55:44PM +, Zbigniew Jędrzejewski-Szmek wrote:
> > > I'm trying to compile systemd in koji and mock, and I'm getting
Hi,
On Thu, 2019-03-28 at 14:28 +, Zbigniew Jędrzejewski-Szmek wrote:
> On Thu, Mar 28, 2019 at 02:14:31PM +0100, Jakub Jelinek wrote:
> > On Thu, Mar 28, 2019 at 08:52:18AM +, Zbigniew Jędrzejewski-Szmek wrote:
> > > On Wed, Mar 27, 2019 at 01:55:44PM +, Zbigniew Jędrzejewski-Szmek
Dne 28. 03. 19 v 0:48 Miro Hrončok napsal(a):
> 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 them was already announced on java-devel
On Wed, 27 Mar 2019 at 21:27, Jonathan Wakely
wrote:
> On 26/03/19 11:40 +, Tomasz Kłoczko wrote:
> >On Tue, 26 Mar 2019 at 08:57, Jonathan Wakely
> >wrote:
> >[..]
> >
> >> >What does this 42 means in this case? It means that during whole gcc
> build
> >> >are repeated 42 times some subset
On Wed, Mar 27, 2019 at 01:55:44PM +, Zbigniew Jędrzejewski-Szmek wrote:
> Hi,
>
> I'm trying to compile systemd in koji and mock, and I'm getting suspicious
> crashes...
>
> $ valgrind x86_64-redhat-linux-gnu/test-terminal-util
> /* test_default_term_for_tty */
> ...
> /* test_read_one_char
Hi,
Just to say I won't be able to attend, sorry.
Regards,
Silvia
FAS: Lailah
On Wed, 27 Mar 2019 at 15:55, Ben Cotton wrote:
> Reminder: the Go/No-Go meeting for the Fedora 30 Beta release will be
> held TOMORROW, 2019-03-28 at 17:00 UTC in #fedora-meeting-1. For more
> information, see:
On Thu, Mar 28, 2019 at 12:08 AM Luya Tshimbalanga
wrote:
>
> On 2019-03-26 10:07 a.m., Georg Sauthoff wrote:
> > Hello,
> >
> > when packaging a C/C++ program, the rpm automatic dependency feature
> > usually works well for shared libraries.
> >
> > That mean when program 'bar' needs
On 28/03/19 19:17, Jason L Tibbitts III wrote:
"RM" == Robert-André Mauchin writes:
RM> Since our float of Golang packages is severely out of date, I was
RM> expecting a load of new messages from Bugzilla.
I don't believe it notifies when the project is first added. It should
notify when
On Thu, Mar 28, 2019 at 1:43 PM Tomasz Kłoczko wrote:
>
> On Thu, 28 Mar 2019 at 16:37, Miroslav Suchý wrote:
>>
>> Dne 28. 03. 19 v 13:57 Tomasz Kłoczko napsal(a):
>> > dnf does not provide any signing functions and I was not even aware that
>> > someone implemented in base dnf building
>> >
On Mon, Mar 25, 2019 at 4:12 PM Ben Cotton wrote:
>
> https://fedoraproject.org/wiki/Changes/Include_security_modules_in_efi_Grub2
>
This Change proposal is on hold.
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
Pronouns: he/him
On Thu, 28 Mar 2019 at 16:37, Miroslav Suchý wrote:
> Dne 28. 03. 19 v 13:57 Tomasz Kłoczko napsal(a):
> > dnf does not provide any signing functions and I was not even aware that
> someone implemented in base dnf building
> > functionalities (someone is using that?)
>
> No, DNF likely does not
> "RM" == Robert-André Mauchin writes:
RM> Since our float of Golang packages is severely out of date, I was
RM> expecting a load of new messages from Bugzilla.
I don't believe it notifies when the project is first added. It should
notify when the project is next updated.
- J<
I found out what is wrong, you created the project without Fedora
mapping, so the first version was retrieved without knowing how this is
packaged in Fedora. But I see, that the mapping was added later, but the
message about the mapping wasn't send by Anitya. Did you added the
mapping using
On Thursday, 28 March 2019 16:17:33 CET Luya Tshimbalanga wrote:
> Hello team,
>
> I encountered an issue related to luxcorerender unable to use the new
> boost dependency. See
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=33804165
>
> Could someone resolve that problem?
>
>
>
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? It would be very helpful
for local builds/testing, but is not available in:
sudo dnf
Hi,
this is really suspicious, I didn't saw any issue related to
the-new-hotness or Anitya in recent days.
I will check what is going on.
mkonecny
On 28/03/19 19:09, Robert-André Mauchin wrote:
Hello,
Earlier this week, I wrote a script to check and add all Golang packages to
Anitya.
On Thursday, 28 March 2019 19:38:30 CET Michal Konecny wrote:
> I found out what is wrong, you created the project without Fedora
> mapping, so the first version was retrieved without knowing how this is
> packaged in Fedora. But I see, that the mapping was added later, but the
> message about
On 3/28/19 4:17 AM, Tomasz Kłoczko wrote:
>Really?
>Really do you want me to answer on the question "why there is no
any sense
>repeat 42 times some tests on the source code configuration
stage?" ??
Yes, because you repeatedly make the mistake of assuming that one
Hello,
Earlier this week, I wrote a script to check and add all Golang packages to
Anitya. Everything went smoothly, and dozens of packages were registered and
got their version retrieved.
Since our float of Golang packages is severely out of date, I was expecting a
load of new messages from
On Wed, Mar 27, 2019 20:12:32 +0530, Hemant Kumar Singh wrote:
> Greetings,
> I am Hemant Kumar Singh,
Hi Hemant,
Welcome to Fedora!
> a computer science undergrad studying in NIT Warangal,
> India. I am interested to work on the project "CentOS CI User Front End" with
> Fedora Project under
Fedora prohibits the use of rpath, ref
https://docs.fedoraproject.org/en-US/packaging-guidelines/#_beware_of_rpath
When compiling varnish with litbool, I ensure this by the usual
sed -i 's|^hardcode_libdir_flag_spec=.*|hardcode_libdir_flag_spec=""|g;
On Thu, Mar 28, 2019 at 11:46 AM Aleksandra Fedorova wrote:
>
> I propose to change the scope of the SIG a bit.
>
> Maintaining packages could be one of the activities of the SIG, but its
> primary purpose should be to deal with this topic in general.
>
> Watch for orphans, develop orphaning and
On Thu, Mar 28, 2019 at 7:32 AM Tomasz Kłoczko wrote:
>
> Hi,
>
> Just found that on some minimal system it is not possible to remove some rpm
> subpackages.
>
> * Current state
>
> # rpm -qa | grep rpm
> rpm-libs-4.14.2.1-4.fc30.1.x86_64
> rpm-4.14.2.1-4.fc30.1.x86_64
>
On 3/28/19 1:31 PM, Tomasz Kłoczko wrote:
Hi,
Just found that on some minimal system it is not possible to remove some
rpm subpackages.
* Current state
# rpm -qa | grep rpm
rpm-libs-4.14.2.1-4.fc30.1.x86_64
rpm-4.14.2.1-4.fc30.1.x86_64
python3-rpm-4.14.2.1-4.fc30.1.x86_64
Hello team,
I encountered an issue related to luxcorerender unable to use the new
boost dependency. See
https://koji.fedoraproject.org/koji/taskinfo?taskID=33804165
Could someone resolve that problem?
Thanks
Luya
___
devel mailing list --
> "MH" == Miro Hrončok writes:
MH> You realize that once it is maintained by the group, nobody else is
MH> going to take it?
When the stewardship SIG maintains a package, it should be for the sole
purpose of keeping it around just long enough to avoid serious
disruption that would be caused
Hi,When publishing, does Fedora: a) rebuild a maintainer's package from source and gpg sign it with their own fedora gpg key
(ex. /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-11-primary)
OR:
b) publish the package that the maintainer personally compiled and gpg signed with their
Hello developers,
I have created a `mythes` and `hyphen` package for the Esperanto language.
Unfortunately, I am not a sponsored Fedora developer, and the package
doesn't seem like it'll be accepted unless I become sponsored.
Between all manner of tasks, I do not have the time to pursue becoming
Thanks for the response.
Michael Zhang
Software Developer Test (WAS Install Team)
Phone: 1-9054133415
E-mail: michael.zh...@ibm.com
- Original message -From: Tom Hughes To: Development discussions related to Fedora , Michael Zhang Cc:Subject: Re:
Dne 28. 03. 19 v 13:57 Tomasz Kłoczko napsal(a):
> dnf does not provide any signing functions and I was not even aware that
> someone implemented in base dnf building
> functionalities (someone is using that?)
No, DNF likely does not user rpmb and rpms.
Both libraries has 21K + 15K. It is really
Hey, We read in the guidelines that all jars and class files should go under %{_javadir} (/usr/share/java by default). We were initially thinking of symlinking all the jars and class files but recently, we thought "could we put the whole OpenLiberty install under /usr/share/java/openliberty?" I
On 28/03/2019 16:24, Michael Zhang wrote:
When publishing, does Fedora:
a) rebuild a maintainer's package from source and gpg sign it with
their own fedora gpg key
(ex. /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-11-primary)
OR:
b) publish the package that the maintainer
Le 2019-03-28 17:26, Michael Zhang a écrit :
Hi
We read in the guidelines that all jars and class files should go
under %{_javadir} (/usr/share/java by default). We were initially
thinking of symlinking all the jars and class files but recently, we
thought "could we put the whole OpenLiberty
I propose to change the scope of the SIG a bit.
Maintaining packages could be one of the activities of the SIG, but its
primary purpose should be to deal with this topic in general.
Watch for orphans, develop orphaning and retirement workflows, develop a
strategy how to manage those cases, how
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 not part of any modules I am currently
On 20. 03. 19 9:57, Fabio Valentini wrote:
I've gone ahead with my proposal and created the Stewardship SIG.
This includes the SIGs/Stewardship wiki page [0], the @stewardship-sig
FAS group [1], to which high-priority orphaned packages can be
assigned, and the stewardship-sig mailing list [2].
On Thu, 28 Mar 2019 at 20:57, Neal Gompa wrote:
[..]
> > Other things related to the rpm.
> > Why in main rpm package is possible to find whole /usr/lib/rpm/platform?
> That directory contains ONLY resources used during build!!! Why main rpm
> package includes documentation about building
On Thu, 28 Mar 2019 at 11:47, Neal Gompa wrote:
[..]
> No. The rpm plugins are runtime activated things, that's why they are
> split out.
>
Exactly. Just checked and in python code those modules initialisation looks
like below:
--
# try to import build bits but dont require it
try:
from
On Fri, Mar 29, 2019 at 12:33 AM Miro Hrončok wrote:
>
> On 20. 03. 19 9:57, Fabio Valentini wrote:
> > I've gone ahead with my proposal and created the Stewardship SIG.
> >
> > This includes the SIGs/Stewardship wiki page [0], the @stewardship-sig
> > FAS group [1], to which high-priority
On Wed, 2019-03-27 at 11:38 -0400, Charalampos Stratakis wrote:
> Not interested anymore in this package, feel free to reach me out if
> you'd like to take it, I'll orphan it this week.
I'm actively using Lektor so I'll take it off your shoulders gladly.
Thank you for your work on it.
Br,
Saša
On Thu, Mar 28, 2019 at 8:22 AM Miro Hrončok wrote:
>
> On 26. 03. 19 1:51, Miro Hrončok wrote:
> > On 25. 03. 19 18:56, Kevin Fenzi wrote:
> >> Just make python36 obsolete the old version of python34 that had
> >> /usr/bin/python3. This causes yum to install the new python34 and pull
> >> in
On 3/28/19 5:22 AM, Miro Hrončok wrote:
>
> A PR is at https://src.fedoraproject.org/rpms/python36/pull-request/27
>
> I'm still not sure about how it will behave. We should probably test it.
I just did a bunch of testing and the Obsoletes works great.
It does mean if someone has only packages
https://bugzilla.redhat.com/show_bug.cgi?id=1690939
Fedora Update System changed:
What|Removed |Added
Fixed In Version|perl-LWP-MediaTypes-6.04-1. |perl-LWP-MediaTypes-6.04-1.
The following Fedora EPEL 6 Security updates need testing:
Age URL
104 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-b7556983e8
tomcat-7.0.92-1.el6
28 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-06b243cced
guacamole-server-1.0.0-1.el6
8
https://bugzilla.redhat.com/show_bug.cgi?id=1690939
Fedora Update System changed:
What|Removed |Added
Status|ON_QA |CLOSED
Fixed In
https://bugzilla.redhat.com/show_bug.cgi?id=1690193
--- Comment #6 from Fedora Update System ---
perl-CPAN-2.26-1.fc29 has been pushed to the Fedora 29 stable repository. If
problems still persist, please make note of it in this bug report.
--
You are receiving this mail because:
You are on
https://pagure.io/389-ds-base/issue/50310
https://pagure.io/389-ds-base/pull-request/50311
--
Sincerely,
William
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
On Thu, 28 Mar 2019 13:22:26 +0100
Miro Hrončok wrote:
>
> A PR is at https://src.fedoraproject.org/rpms/python36/pull-request/27
> I'm still not sure about how it will behave. We should probably test
> it.
https://bugzilla.redhat.com/show_bug.cgi?id=1687196
Check my bug report first. You
https://pagure.io/389-ds-base/pull-request/50307
___
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 28. 03. 19 21:54, Tuomo Soini wrote:
On Thu, 28 Mar 2019 13:22:26 +0100
Miro Hrončok wrote:
A PR is at https://src.fedoraproject.org/rpms/python36/pull-request/27
I'm still not sure about how it will behave. We should probably test
it.
On 3/28/19 4:39 PM, Miro Hrončok wrote:
> On 28. 03. 19 21:54, Tuomo Soini wrote:
>> On Thu, 28 Mar 2019 13:22:26 +0100
>> Miro Hrončok wrote:
>>
>>>
>>> A PR is at https://src.fedoraproject.org/rpms/python36/pull-request/27
>>
>>> I'm still not sure about how it will behave. We should probably
https://pagure.io/389-ds-base/pull-request/50309
___
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
https://bugzilla.redhat.com/show_bug.cgi?id=1693934
Bug ID: 1693934
Summary: perl-DateTime-Locale-1.24 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: perl-DateTime-Locale
Keywords: FutureFeature,
64 matches
Mail list logo
