Re: Datacenter move days 3 and 4

[John M. Harris Jr]

On Thursday, June 11, 2020 9:09:53 PM MST Kevin Fenzi wrote:
> We are working on getting this install moved over to recent
> fedora or rhel, but for now it's rhel7 and python34.

RHEL7 is better than RHEL8 anyway. ;)

I'm planning to skip RHEL8 entirely, it's totally b0rked.

-- 
John M. Harris, Jr.

___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Datacenter move day 2

[John M. Harris Jr]

On Thursday, June 11, 2020 9:25:41 AM MST Ben Cotton wrote:
> On Thu, Jun 11, 2020 at 12:08 PM Kevin Kofler 
> wrote:
> >
> >
> > FYI, claiming the badge for the elections does not work,
> > badges.fedoraproject.org spews an error 500 Internal Server Error.
> >
> >
> 
> The badge claim URL should be valid for a few days beyond the end of
> the voting period. If anyone is unable to claim the badge, they can
> open an issue at https://pagure.io/fedora-project-schedule/new_issue
> and I will manually award badges when the system is back online.
> 
> -- 
> Ben Cotton
> He / Him / His
> Senior Program Manager, Fedora & CentOS Stream
> Red Hat
> TZ=America/Indiana/Indianapolis

Ben,

This has actually happened before the move started. It may be an issue with 
the Badges app. I mentioned this in #fedora-admin when I voted on the 28th of 
last month. (I later got the badge with the URL generated by voting for a 
different position)

-- 
John M. Harris, Jr.

___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Datacenter move days 3 and 4

[Kevin Fenzi]

Greetings all. 

This email will cover days 3 and 4, as by the time I was going to send
yesterdays it was late and mailman was still down anyhow. :) 

So, yesterday started out seeming like a pretty simple day, but didn't
turn out that way. We planned to move only two things and work on fixing
issues from the buildsystem and other moves in the first two days. 

* datagrepper / datanommer. This took until this morning as the database
is really gigantic. Again, we wanted to load it into a more modern
postgres. Now that it's moved and on postgres 12.2, we will be looking
into partitioning the data (perhaps by month? quarter?) so queries for
anything recent are much faster.

* mailman / lists: This turned out to be our biggest problem of the
move. :( We are working on getting this install moved over to recent
fedora or rhel, but for now it's rhel7 and python34. Because of that we
decided to just copy the instance over entire and adjust it over a fresh
install. The copy ran most of the day, and was nearing completion but
then we acidentally resized the orig instance. :( We resized it back,
but the filesystem was messed up and the instance would no longer boot.
It was at this point we decided that lack of sleep could leed to poor
decisions and mistakes and we started a copy off of the data on the copy
to another freshly installed instance and went and got some sleep.

The next day, in a stroke of luck, the copy we were doing had already copied
all the disk that had data on it, so we were able to fsck it and resize
it and we were back in business. mailman/lists was back up this morning
and happily processing away. 

Today, in addition to finishing the above two migrations from yesterday,
we moved: 

* openqa. Right now it doesn't have any arm or power workers, but we
have some almost ready to go there that we should have in place next
week.

* Various openshift apps (docsbuilding, websites building, cron jobs,
etc). We even have release-monitoring and the new hotness up and
running. I am trying to bring koschei up as well, but it needs some more
work. 

* Some small misc apps: blockerbugs, kerneltest, etc. 

* We also fixed tons and tons of issues all over the map. Mostly around
things reaching other things or something not running for some
configuration reason.

At this point everything we planned to be in the minimal fedora should
be up and working. We do have a more capacity than we need, so if things
go smoothly without too many more things to fix, I'd like to see about
bringing up badges as it's a popular app and if we have capacity and can
easily do it we can bring it up. 

Tomorrow and this weekend we are going to work on taking things down in
the old datacenter and get them ready for shipping next week. They will
be in transit next week, then we hopefully can get them racked and built
and start adding capacity back the week after. 

So, if you notice something not working now, please do look to see if
there's already a ticket on it, and if not please file one. 
( https://pagure.io/fedora-infrastructure/issues ).

Overall things went pretty good from my view, and I would really like to
thank the awesome fedora community for being patient with us. I was
pretty surprised how few people asked why things were down and when they
did other community memebers were quick to tell them.

kevin


signature.asc
Description: PGP signature
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[389-devel] 389 DS nightly 2020-06-12 - 95% PASS

[vashirov]

https://fedorapeople.org/groups/389ds/ci/nightly/2020/06/12/report-389-ds-base-1.4.4.3-20200611git3ddcc62.fc32.x86_64.html
___
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://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org

[Regression] Blender build failure on armv7 architecture

[Luya Tshimbalanga]

Hello team,

Blender 2.83.0 successfuly built on all but one architecture: armv7h.

https://koji.fedoraproject.org/koji/buildinfo?buildID=1522859

Could these maintainers investigate the cause ? I intend to temporarly 
exclude it until the fix is publishe.


Thanks

--
Luya Tshimbalanga
Fedora Design Team
Fedora Design Suite maintainer
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

FESCo election results

[Ben Cotton]

Greetings, all!

The elections for FESCo election for Fedora 32 have concluded, and the results
are shown below.

FESCo is electing 4 seats this time.
A total of 273 ballots were cast, meaning a candidate
could accumulate up to 2730 votes (273 * 10).

The results for the elections are as follows:

  # votes |  name
- +--
1507  | Neal Gompa (ngompa)
1450  | Stephen Gallagher (sgallagh)
1372  | Igor Raits (ignatenkobrain)
1148  | Clément Verna (cverna)
- +--
1124  | Justin Forbes (jforbes)
 997  | Chris Murphy (chrismurphy)
 937  | Petr Šabata (psabata)
 904  | Frantisek Zatloukal (frantisekz)
 755  | James Cassell (cyberpear)
 730  | Michal Novotný (clime)


Congratulations to the winning candidates, and thank you all
candidates for running this elections!

For a full election rundown, see the Community Blog post:
https://communityblog.fedoraproject.org/fedora-32-elections-results/

-- 
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

FESCo election results

[Ben Cotton]

Greetings, all!

The elections for FESCo election for Fedora 32 have concluded, and the results
are shown below.

FESCo is electing 4 seats this time.
A total of 273 ballots were cast, meaning a candidate
could accumulate up to 2730 votes (273 * 10).

The results for the elections are as follows:

  # votes |  name
- +--
1507  | Neal Gompa (ngompa)
1450  | Stephen Gallagher (sgallagh)
1372  | Igor Raits (ignatenkobrain)
1148  | Clément Verna (cverna)
- +--
1124  | Justin Forbes (jforbes)
 997  | Chris Murphy (chrismurphy)
 937  | Petr Šabata (psabata)
 904  | Frantisek Zatloukal (frantisekz)
 755  | James Cassell (cyberpear)
 730  | Michal Novotný (clime)


Congratulations to the winning candidates, and thank you all
candidates for running this elections!

For a full election rundown, see the Community Blog post:
https://communityblog.fedoraproject.org/fedora-32-elections-results/

-- 
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org

[Test-Announce] 2020-06-15 @ 15:00 UTC - Fedora QA Meeting

[Adam Williamson]

# Fedora Quality Assurance Meeting
# Date: 2020-06-15
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

We didn't meet for a few weeks, so let's check in and see where
things are.

If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.

== Proposed Agenda Topics ==

1. Previous meeting follow-up
2. Fedora 33 status
3. Data center move updates
4. Test Day / community event status
5. Open floor
-- 
adamw
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[389-devel] Roadmap for rust as a requirement in the project

[William Brown]

Hi all,

Background: https://pagure.io/389-ds-base/issue/51140


Ludwig and Mark both raised some good points here. First is that features today 
(EntryUUID, LDAPSsoToken) are both locked behind another language. Rightly so, 
they shouldn't be hidden here forever. As well, Mark wants to ask what it would 
take to enable by default.

** Why did I use the fedse.c to load a plugin entry?

Because we don't (fully) support startup migrations yet. Mark has privately 
reminded me that he has reviewed 
https://pagure.io/389-ds-base/pull-request/49579 and that I should revive it. 
This v4 plugin adds a stateful assertion of entries allowing better migrations 
beyond what fedse.c's bootstrap can achieve. IE we can create an entry if it 
does not exist, and modify it partially if an admin has changed it (ie we can 
tweak defaults but without affecing say pluginEnabled). There was an issue 
viktor raised about pbkdf2 where it could not be disabled, and this would 
resolve it. Most likely, I will break the on startup migrations out from the v4 
plugin patch set, and make it it's own change, and move some of the content 
from fedse.c and friends into this.

** TODO list to get rust enabled by default.

I think there is still a bit of work to do to enable by default, but I think we 
are pretty close. Roughly ordered, this is the list of things that has to 
happen to let us enable rust by default.

- everyone -> test that you can build and run tests with --enable-rust 
--disable-asan in your development environment so that we can work out and 
issues that may exist for us as developers.
- william -> fix the intentional name leak in the rust slapi plugin interface 
to use lazy_static. Today this triggers LSAN which breaks basic test suites.
- william -> clean up libsds linking and some of the related elements
- william -> revive and make on upgrade configs better (see above), potentially 
break it out from the v4 plugin patch.
- william + mark -> check that our respective major distros/releases can build 
with --enable-rust in release rpms
- william + viktor -> check that we can pass with --enable-rust and 
--enable-asan, especially in CI
- anyone interested -> update wiki contributing guide to include rust as a 
requirement
- (optional) anyone interested (but not william) -> add a section to the wiki 
on using rust in development
- team -> agree we are happy, and make configure.ac have --enable-rust by 
default
- team -> after a few weeks / months, remove the ifdefs, duplicate C versions 
of Rust features, and enable/disable features from configure.ac


Does this seem reasonable to everyone? I really want to make sure we do this 
right as a team, and we are all happy with it (I don't want a repeat of 
nunc-stans ;) ). If we agree on this, I will open some tickets up, add the 
relevant blocks/ordering and assign out the work.

Thank you all!

—
Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs
___
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://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org

[Bug 1842173] perl-Test2-Suite-0.000130 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1842173

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version|perl-Test2-Suite-0.000130-1 |perl-Test2-Suite-0.000130-1
   |.fc33   |.fc33
   ||perl-Test2-Suite-0.000130-1
   ||.fc32
 Resolution|--- |ERRATA
Last Closed||2020-06-11 22:56:19



--- Comment #4 from Fedora Update System  ---
perl-Test2-Suite-0.000130-1.fc32 has been pushed to the Fedora 32 stable
repository. If problems still persist, please make note of it in this bug
report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

Re: A few questions about a package update / policy questions / GCC 9 error

[Nathanael D. Noblet]

On Thu, 2020-06-11 at 16:13 -0400, Simo Sorce wrote:
> I wish this was easier done than said :)

Yeah, this isn't *my* project, I just packaged it. 

Thank you to everyone who added suggestions to dealing with the C code.
I'll take a look and see what upstream thinks about it.

I am wondering if anyone has thoughts about changing the sysconfig
file.

Sincerely,
-- 
Nathanael
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Fedora Jam switch to GNOME

[Yann Collette]

Thanks for the Link.

I use the RT Kernel just for music. For standard desktop tasks, I switch 
to the official Fedora Kernel.


With the standard Fedora Kernel, I've got too many xruns, that's why I 
decided to test RT Kernel.


Le 11/06/2020 à 22:47, Erich Eickmeyer a écrit :

Hi Yann,

On 6/11/20 10:50 AM, Yann COLLETTE wrote:

Hello,

I have a repository with a real time kernel I use for music.
https://copr.fedorainfracloud.org/coprs/ycollet/linuxmao/

With this kernel, I can 128 samples buffer at 48kHz and 5 ms latency
without Xruns.
I use "a lot" of applications to perform guitar (guitarix + tuxguitar).
I also can record video "live".

Here's an example:
https://www.youtube.com/watch?v=HPL-iNg42Ag

Best regards,

YC


Sounds great, but you might think about making it a lowlatency kernel
instead. Real-time kernels have a plethora of security implications when
used on desktop systems. Real Time kernels are meant for embedded
systems, and using one in your desktop system to reduce latency isn't
worth the security risk. See
https://help.ubuntu.com/community/UbuntuStudio/RealTimeKernel

Other than that, I wouldn't mind having you on the Fedora Jam team. :)

-Erich



___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Fedora Jam switch to GNOME

[Erich Eickmeyer]

Hi Yann,

On 6/11/20 10:50 AM, Yann COLLETTE wrote:
> Hello,
>
> I have a repository with a real time kernel I use for music.
> https://copr.fedorainfracloud.org/coprs/ycollet/linuxmao/
>
> With this kernel, I can 128 samples buffer at 48kHz and 5 ms latency
> without Xruns.
> I use "a lot" of applications to perform guitar (guitarix + tuxguitar).
> I also can record video "live".
>
> Here's an example:
> https://www.youtube.com/watch?v=HPL-iNg42Ag
>
> Best regards,
>
> YC
>
Sounds great, but you might think about making it a lowlatency kernel
instead. Real-time kernels have a plethora of security implications when
used on desktop systems. Real Time kernels are meant for embedded
systems, and using one in your desktop system to reduce latency isn't
worth the security risk. See
https://help.ubuntu.com/community/UbuntuStudio/RealTimeKernel

Other than that, I wouldn't mind having you on the Fedora Jam team. :)

-Erich

___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[389-devel] please review: PR 51151 - Set the default minimum worker threads

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/51151

--

389 Directory Server Development Team
___
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://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org

Re: Announcement: Aim to remove libdb-java from Fedora-rawhide

[Florian Weimer]

* Ondrej Dubaj:

> we are aiming to remove libdb-java package from Fedora-rawhide, as we
> are currently preparing for jdk update from jdk-1.8 to jdk-11 in
> Fedora rawhide. The problem is that we are unable to rebuild this
> package with jdk-11. It is still possible to "hack" it and rebuild it
> with jdk-1.8, but that can cause unexpected runtime behaviour
> according to JVM-11, which will soon be default in Fedora-rawhide.

Out of curiosity, what is the exact problem?

Thanks,
Florian
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: A few questions about a package update / policy questions / GCC 9 error

[Simo Sorce]

On Thu, 2020-06-11 at 20:21 +0200, Björn Persson wrote:
> Simo Sorce wrote:
> > If you really want to avoid the warning instead of ignoring it, you
> > should change the code this way:
> > 
> > strncpy(t->name, name, MAX_TUBE_NAME_LEN-1);
> > if (t->name[MAX_TUBE_NAME_LEN - 2] != '\0') {
> > t->name[MAX_TUBE_NAME_LEN - 1] = '\0';
> > twarnx("truncating tube name");
> > }
> 
> That code will warn wrongly about truncation when the name is exactly 
> MAX_TUBE_NAME_LEN - 1 bytes long.

Yes but that is unavoidable unless you ant to add a check on the source
length, which is entirely doable of course.

> Nathanael, you could link to libbsd and use strlcpy if that's available
> on all target platforms. Or, if you happen to be using Glib, use
> g_strlcpy. Otherwise use Peter's snprintf solution, but DO NOT make the
> mistake of passing the input as the format string!
> 
> And choose a better language than C for your next project.

I wish this was easier done than said :)

Simo.

-- 
Simo Sorce
RHEL Crypto Team
Red Hat, Inc



___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Open Seats on the Fedora Packaging Committee

[James Antill]

 Just a reminder that the deadline for this is just less two weeks away
now, so here's the information again if you want to apply:


 The Fedora Packaging Committee has some open seats and is accepting
submissions from interested candidates to serve on the FPC.

 This position involves not only reviewing Packaging Guideline drafts
submitted to the FPC for consideration, but also helping rewrite drafts
to resolve issues in a more acceptable fashion. Additionally, the FPC
reviews UID/GID soft static assignment.

 Currently the FPC meets on IRC weekly, on Thursdays based around 12:00
east coast US time, for approximately an hour.
 That can change slightly, but any new time would need to be good for
all the members (East Coast US and German TZs, at least).

 FPC members serve for as long as they are willing, there are currently
no term limits. All decisions are voted on using a +1 (for), 0
(abstain), and -1 (against) mechanism, and all decisions must be
approved by a majority (+5). FPC Meetings do not happen if a quorum (5
members) is not present. Candidates who are interested should provide
the following details to the FPC for consideration, by emailing it
directly to me (james(a)fedoraproject.org).

 The FPC will consider all candidates, but strongly prefers candidates
who have extensive experience packaging in Fedora. Due to the current
environment we will be accepting applications for the next _two_ weeks
(deadline Wednesday, 2020-06-24).

 Name:
 FAS Account:
 Provenpackager? (Yes/No):
 Main area of packaging interest/expertise:
 Reason(s) for wanting to join the FPC:

 Thanks in advance,
  ~James

___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org

[389-devel] please review: PR 51150 - healthcheck tests for "notes=A" and "notes=F" in the access log

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/51150

--

389 Directory Server Development Team
___
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://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org

Open Seats on the Fedora Packaging Committee

[James Antill]

 Just a reminder that the deadline for this is just less two weeks away
now, so here's the information again if you want to apply:


 The Fedora Packaging Committee has some open seats and is accepting
submissions from interested candidates to serve on the FPC.

 This position involves not only reviewing Packaging Guideline drafts
submitted to the FPC for consideration, but also helping rewrite drafts
to resolve issues in a more acceptable fashion. Additionally, the FPC
reviews UID/GID soft static assignment.

 Currently the FPC meets on IRC weekly, on Thursdays based around 12:00
east coast US time, for approximately an hour.
 That can change slightly, but any new time would need to be good for
all the members (East Coast US and German TZs, at least).

 FPC members serve for as long as they are willing, there are currently
no term limits. All decisions are voted on using a +1 (for), 0
(abstain), and -1 (against) mechanism, and all decisions must be
approved by a majority (+5). FPC Meetings do not happen if a quorum (5
members) is not present. Candidates who are interested should provide
the following details to the FPC for consideration, by emailing it
directly to me (james(a)fedoraproject.org).

 The FPC will consider all candidates, but strongly prefers candidates
who have extensive experience packaging in Fedora. Due to the current
environment we will be accepting applications for the next _two_ weeks
(deadline Wednesday, 2020-06-24).

 Name:
 FAS Account:
 Provenpackager? (Yes/No):
 Main area of packaging interest/expertise:
 Reason(s) for wanting to join the FPC:

 Thanks in advance,
  ~James

___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[Bug 1841308] remove hardcoded requirement for Crypt::Random

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1841308

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #6 from Fedora Update System  ---
perl-Crypt-PWSafe3-1.22-14.el8 has been pushed to the Fedora EPEL 8 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-6f9f9d0c47


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1845194] perl-libwww-perl-6.45 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1845194



--- Comment #3 from Fedora Update System  ---
perl-libwww-perl-6.45-1.fc31 has been pushed to the Fedora 31 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-5ed193d5b3


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1839515] perl-CPAN-Perl-Releases-5.20200524 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1839515



--- Comment #11 from Fedora Update System  ---
perl-CPAN-Perl-Releases-5.20200607-1.fc31 has been pushed to the Fedora 31
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-c582c88002


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1842709] perl-Module-CoreList-5.20200602 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1842709



--- Comment #13 from Fedora Update System  ---
perl-Module-CoreList-5.20200603-1.fc31 has been pushed to the Fedora 31 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-1af547e348


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1844899] perl-CPAN-Perl-Releases-5.20200607 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1844899



--- Comment #4 from Fedora Update System  ---
perl-CPAN-Perl-Releases-5.20200607-1.fc31 has been pushed to the Fedora 31
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-c582c88002


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1842176] perl-CPAN-Perl-Releases-5.20200530 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1842176



--- Comment #8 from Fedora Update System  ---
perl-CPAN-Perl-Releases-5.20200607-1.fc31 has been pushed to the Fedora 31
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-c582c88002


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1842698] perl-CPAN-Perl-Releases-5.20200601 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1842698



--- Comment #6 from Fedora Update System  ---
perl-CPAN-Perl-Releases-5.20200607-1.fc31 has been pushed to the Fedora 31
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-c582c88002


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1842709] perl-Module-CoreList-5.20200602 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1842709



--- Comment #12 from Fedora Update System  ---
perl-Module-CoreList-5.20200603-1.fc32 has been pushed to the Fedora 32 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-b339710d87


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1845194] perl-libwww-perl-6.45 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1845194

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #2 from Fedora Update System  ---
perl-libwww-perl-6.45-1.fc32 has been pushed to the Fedora 32 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-c642e979b0


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1842524] perl-Date-Manip-6.82 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1842524

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
perl-Date-Manip-6.82-1.fc32 has been pushed to the Fedora 32 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-3c190874ee


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1842176] perl-CPAN-Perl-Releases-5.20200530 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1842176



--- Comment #7 from Fedora Update System  ---
perl-CPAN-Perl-Releases-5.20200607-1.fc32 has been pushed to the Fedora 32
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-2ec305b097


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1842698] perl-CPAN-Perl-Releases-5.20200601 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1842698



--- Comment #5 from Fedora Update System  ---
perl-CPAN-Perl-Releases-5.20200607-1.fc32 has been pushed to the Fedora 32
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-2ec305b097


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1839515] perl-CPAN-Perl-Releases-5.20200524 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1839515



--- Comment #10 from Fedora Update System  ---
perl-CPAN-Perl-Releases-5.20200607-1.fc32 has been pushed to the Fedora 32
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-2ec305b097


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1844899] perl-CPAN-Perl-Releases-5.20200607 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1844899

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
perl-CPAN-Perl-Releases-5.20200607-1.fc32 has been pushed to the Fedora 32
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-2ec305b097


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[EPEL-devel] Fedora EPEL 6 updates-testing report

[updates]

The following builds have been pushed to Fedora EPEL 6 updates-testing

php-horde-Horde-Core-2.31.14-1.el6
tomcat-7.0.104-1.el6

Details about builds:



 php-horde-Horde-Core-2.31.14-1.el6 (FEDORA-EPEL-2020-51264d8702)
 Horde Core Framework libraries

Update Information:

**Horde_Core 2.31.14**  * [jan] Avoid concurrent access to DNS cache from
multiple hosts (cheese PR#9). * [jan] Support Redis Sentinel configuration
(Michael Menge, Request #14998). * [jan] Use file hashing for detecting outdated
configuration files. * [mjr] Fix regression in Autodiscover v1 (Bug #14992).

ChangeLog:

* Tue Jun  9 2020 Remi Collet  - 2.31.14-1
- update to 2.31.14




 tomcat-7.0.104-1.el6 (FEDORA-EPEL-2020-6fe406a051)
 Apache Servlet/JSP Engine, RI for Servlet 3.0/JSP 2.2 API

Update Information:

This update includes a rebase from 7.0.103 up to 7.0.104 which resolves one CVE
along with various other bugs/features:  * rhbz#1838964  CVE-2020-9484 tomcat:
Apache Tomcat Remote Code Execution via session persistence [fedora-all]

ChangeLog:

* Thu Jun  4 2020 Hui Wang  - 1:7.0.104-1
- Update to 7.0.104


___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org

[Bug 1838904] perl-perlfaq-5.20200523 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1838904



--- Comment #16 from Fedora Update System  ---
perl-5.30-3120200602094358.a9ea5770 has been pushed to the Fedora 31 Modular
stable repository. If problems still persist, please make note of it in this
bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1840363] perl-Compress-Bzip2-2.27 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1840363



--- Comment #12 from Fedora Update System  ---
perl-5.30-3120200602094358.a9ea5770 has been pushed to the Fedora 31 Modular
stable repository. If problems still persist, please make note of it in this
bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1829089] perl-Module-CoreList-5.20200428 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1829089



--- Comment #16 from Fedora Update System  ---
perl-5.30-3120200602094358.a9ea5770 has been pushed to the Fedora 31 Modular
stable repository. If problems still persist, please make note of it in this
bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1830464] perl-Encode-3.06 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1830464



--- Comment #16 from Fedora Update System  ---
perl-5.30-3120200602094358.a9ea5770 has been pushed to the Fedora 31 Modular
stable repository. If problems still persist, please make note of it in this
bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1842709] perl-Module-CoreList-5.20200602 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1842709



--- Comment #11 from Fedora Update System  ---
perl-5.30-3120200602094358.a9ea5770 has been pushed to the Fedora 31 Modular
stable repository. If problems still persist, please make note of it in this
bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1846509] New: perl-Devel-Gladiator-0.08 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1846509

Bug ID: 1846509
   Summary: perl-Devel-Gladiator-0.08 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Devel-Gladiator
  Keywords: FutureFeature, Triaged
  Assignee: ppi...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org, ppi...@redhat.com
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 0.08
Current version/release in rawhide: 0.07-12.fc32
URL: http://search.cpan.org/dist/Devel-Gladiator/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from anitya:
https://release-monitoring.org/project/12313/


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1835355] perl-Email-MIME-ContentType: rubygem-mail: Out of memory issue through nested MIME parts [epel-all]

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1835355



--- Comment #5 from Fedora Update System  ---
perl-Email-MIME-1.949-1.el8, perl-Email-MIME-ContentType-1.024-1.el8 has been
pushed to the Fedora EPEL 8 stable repository. If problems still persist,
please make note of it in this bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1835353] rubygem-mail: Out of memory issue through nested MIME parts

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1835353



--- Comment #7 from Fedora Update System  ---
perl-Email-MIME-1.949-1.el8, perl-Email-MIME-ContentType-1.024-1.el8 has been
pushed to the Fedora EPEL 8 stable repository. If problems still persist,
please make note of it in this bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1835360] perl-Email-MIME: rubygem-mail: Out of memory issue through nested MIME parts [epel-all]

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1835360



--- Comment #5 from Fedora Update System  ---
perl-Email-MIME-1.949-1.el8, perl-Email-MIME-ContentType-1.024-1.el8 has been
pushed to the Fedora EPEL 8 stable repository. If problems still persist,
please make note of it in this bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1842709] perl-Module-CoreList-5.20200602 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1842709

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
 Resolution|--- |ERRATA
Last Closed||2020-06-11 18:32:41



--- Comment #10 from Fedora Update System  ---
perl-5.30-3220200602094358.35f641a4 has been pushed to the Fedora 32 Modular
stable repository. If problems still persist, please make note of it in this
bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1838904] perl-perlfaq-5.20200523 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1838904



--- Comment #15 from Fedora Update System  ---
perl-5.30-3220200602094358.35f641a4 has been pushed to the Fedora 32 Modular
stable repository. If problems still persist, please make note of it in this
bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1829089] perl-Module-CoreList-5.20200428 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1829089



--- Comment #15 from Fedora Update System  ---
perl-5.30-3220200602094358.35f641a4 has been pushed to the Fedora 32 Modular
stable repository. If problems still persist, please make note of it in this
bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1830464] perl-Encode-3.06 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1830464



--- Comment #15 from Fedora Update System  ---
perl-5.30-3220200602094358.35f641a4 has been pushed to the Fedora 32 Modular
stable repository. If problems still persist, please make note of it in this
bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1840363] perl-Compress-Bzip2-2.27 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1840363



--- Comment #11 from Fedora Update System  ---
perl-5.30-3220200602094358.35f641a4 has been pushed to the Fedora 32 Modular
stable repository. If problems still persist, please make note of it in this
bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

Re: A few questions about a package update / policy questions / GCC 9 error

[Björn Persson]

Simo Sorce wrote:
> If you really want to avoid the warning instead of ignoring it, you
> should change the code this way:
> 
> strncpy(t->name, name, MAX_TUBE_NAME_LEN-1);
> if (t->name[MAX_TUBE_NAME_LEN - 2] != '\0') {
> t->name[MAX_TUBE_NAME_LEN - 1] = '\0';
> twarnx("truncating tube name");
> }

That code will warn wrongly about truncation when the name is exactly 
MAX_TUBE_NAME_LEN - 1 bytes long.

Nathanael, you could link to libbsd and use strlcpy if that's available
on all target platforms. Or, if you happen to be using Glib, use
g_strlcpy. Otherwise use Peter's snprintf solution, but DO NOT make the
mistake of passing the input as the format string!

And choose a better language than C for your next project.

Björn Persson


pgpUai9i5B_si.pgp
Description: OpenPGP digital signatur
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Fedora Jam switch to GNOME

[Yann COLLETTE]

Hello,

I have a repository with a real time kernel I use for music.
https://copr.fedorainfracloud.org/coprs/ycollet/linuxmao/

With this kernel, I can 128 samples buffer at 48kHz and 5 ms latency 
without Xruns.

I use "a lot" of applications to perform guitar (guitarix + tuxguitar).
I also can record video "live".

Here's an example:
https://www.youtube.com/watch?v=HPL-iNg42Ag

Best regards,

YC

Le 11/06/2020 à 11:14, Lukas Ruzicka a écrit :

Hi Erich,

so today I spent some time in the recording session with the following 
settings and configurations:


  * The machine is 2x 12core Intel Xeon with an SSD drive and 32GB RAM
- I know that this is a recording overkill and I am not sure how
much the machine itself can influence the recording process.
  * Soundcard is Focusrite Scarlett 2i4 over USB
  * My system is an updated Fedora Workstation 32 with stock kernel (I
only lifted up the ulimits)
  * The recording session was set to 48KHz, 32bit float audio
  * The session had about 15 tracks, out of which there were 5
sound+midi tracks and the rest were sound tracks

and I have made the following observations:

  * the session could perform playback normally on 512 samples and
10ms latency
  * when I recorded on 512 samples and 10ms latency, I could work
flawlessly for about 10 or 15 minutes and then, all of a sudden,
Ardour spat a bunch of xruns. I started to delete the xrun markers
one after another and Ardour crashed.
  * then I restarted it on 1024 samples and 21ms latency which was
fine for the rest of the work -> did not have any more xruns.

So, I can confirm, that with the above settings I can use stock Fedora 
Workstation with Gnome desktop for my recording at 1024 samples with 
21ms latency.
I could not test higher freqencies, because I do not have any such a 
project ready, but when I experimented with 192KHz, I was fine with 
2048 sampes and 42ms latency, which I remember very well (from that 
experience my settings of 2048 samples do originate from).


I hope you can use this info, if you needed something else, please let 
me know.



On Wed, Jun 10, 2020 at 8:13 PM Harsh Jain > wrote:


Hi Erich ,
Sorry , I thought the primary focus was to find a new de to shift to .
Improving Gnome in terms of reducing resource usage (and in
general ) seems pretty nice . I'd be happy to have another de I
can work smoothly with :)
This might not be relevant but if you install pantheon de , you
can switch to gnome on the logout screen (even if you didn't
install it ) and it basically brings gnome shell with pantheon apps .
I felt it was a bit smoother than normal gnome ( I didn't test
this extensively but everything seemed to work fine ) .Maybe this
can help in some way ?
Thanks ,
Harsh

On Wed, 10 Jun, 2020, 22:10 , mailto:er...@ericheickmeyer.com>> wrote:

On Wed, 2020-06-10 at 22:01 +0530, Harsh Jain wrote:
> Hi ,
> I'm not too familiar with Fedora Jam but if you want to minimize
> resource usage , shouldn't XFCE be a better choice since
it's less
> intensive with resources . Although Gnome has also reduced
resource
> usage since initial 3.x releases as well I think . It's just
really
> hard to decide between evrything (l'm de hopping currently
as well) .
> Again ,I'm sorry if none of this was useful .
> Thanks ,
> Harsh
>

Hi Harsh,

I also lead Ubuntu Studio and we just moved away from Xfce to KDE
Plasma because we wanted a more-functional desktop for creative
professionals. The resource usage between Xfce and Plasma is
neglegable
(about 50MB difference) and KDE is a better choice for
graphics artists
(which Ubuntu Studio also covers.

I think you missed the point though: the goal is to help GNOME
improve.
I've had conversations with people who want to see GNOME
improve in
this regard and want to work with me in improving it. So, this
isn't
about simply switching desktops, this is about helping another
desktop
improve its situation. If Jam is to switch, it's going to
GNOME, that
decision is already made. The "If" is what I'm working on,
whether or
not to actually go through with it.  If it does happen, the
goal is to
improve GNOME. One can always install whatever desktop they
want and do
"dnf groupinstall 'Audio Production'".

I hoep that clears things up, as I think you missed the point. :)

Erich
___
devel mailing list -- devel@lists.fedoraproject.org

To unsubscribe send an email to
devel-le...@lists.fedoraproject.org

Re: Fedora Jam switch to GNOME

[Erich Eickmeyer]

On 6/11/20 10:33 AM, Jonathan Wakely wrote:
>
> "The beatings will continue until morale improves" ?
>
No. The only way to provide feedback to improve something is to actually
*use* the product. Yelling and screaming if you're not actually using it
does nothing to improve it.





signature.asc
Description: OpenPGP digital signature
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Fedora Jam switch to GNOME

[Jonathan Wakely]

On 10/06/20 09:09 -0700, er...@ericheickmeyer.com wrote:

Hi all,

I'm considering moving Fedora Jam from KDE Plasma to GNOME. There are
multiple reasons for this, and I think part of it would be beneficial
to the overall GNOME and Fedora communities as it would be a way to be
helping improve the situation in GNOME that exist as the biggest
objections from the community of musicians and Linux audio enthusiasts
in the overall community.

The biggest objections are resource usage, since the more resources
that are in use, the more it tends to interfere with real-time audio
processes, causing buffer overruns and/or underruns. These overruns and
underruns are known as Xruns. The fewer Xruns, the better, as Xruns
cause pops during recording. When doing real-time audio work, you want
to have as low of latency as possible which requires as small of a
buffer as possible. The goal is to have a small buffer to get minimal
latency while avoiding Xruns.

Unfortunately, GNOME has, since 3.0, traditionally interfered with
these processes and caused Xruns. My goal, by moving Fedora Jam from
Plasma to GNOME, is to help GNOME improve this situation.


"The beatings will continue until morale improves" ?
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: A few questions about a package update / policy questions / GCC 9 error

[Jonathan Wakely]

On 10/06/20 21:43 +0300, Peter Pentchev wrote:

On Wed, Jun 10, 2020 at 02:22:53PM -0400, Simo Sorce wrote:

On Wed, 2020-06-10 at 14:16 -0400, Simo Sorce wrote:
> On Wed, 2020-06-10 at 20:01 +0200, Dan Čermák wrote:
> > "Nathanael D. Noblet"  writes:
> >
> > > Hello,
> > >
> > >   I maintain beanstalkd which is a message server of sorts. It recently
> > > released a new version however some changes I'm not 100% sure about.
> > >
> > >   When compiling I got the following GCC error.
> > >
> > > usr/include/bits/string_fortified.h:106:10: error: '__builtin_strncpy'
> > > specified bound 201 equals destination size [-Werror=stringop-
> > > truncation]
> > >   106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos
> > > (__dest));
> > >   |  ^~
> > > 
> > >
> > > Results via google says that strncpy needs to have the third argument
> > > less than the 2nd, so I've got this patch, similar to others:
> > >
> > > --- beanstalkd-1.12/tube.c.org  2020-06-10 09:37:35.129224346 -0600
> > > +++ beanstalkd-1.12/tube.c  2020-06-10 09:37:42.761138035 -0600
> > > @@ -12,7 +12,7 @@
> > >  if (!t)
> > >  return NULL;
> > >
> > > -strncpy(t->name, name, MAX_TUBE_NAME_LEN);
> > > +strncpy(t->name, name, MAX_TUBE_NAME_LEN-1);
> > >  if (t->name[MAX_TUBE_NAME_LEN - 1] != '\0') {
> > >  t->name[MAX_TUBE_NAME_LEN - 1] = '\0';
> > >  twarnx("truncating tube name");
> > >
> > > You'll notice it was already checking the len-1 for null. Can anyone
> > > verify that my change won't cause some un-intended bug I don't
> > > understand?
> >
> > If I understand it correctly, then you are now invoking undefined
> > behavior: you copy at most MAX_TUBE_NAME_LEN-1 bytes to t->name and then
> > check whether the following byte (that was never written to) is not
> > equal to 0. I have not checked the code of beanstalkd, but the contents
> > of t->name[MAX_TUBE_NAME_LEN - 1] will be zero if it was allocated via
> > calloc() at best or random at worst. Irrespectively of that, the check
> > now no longer does what it *should*: null terminate the string if it is
> > not null terminated. It will now randomly null terminate it or not at
> > all.
>
> strncpy() is a truly awful API unfortunately, the change is
> meaningless, but it is not random as Dan says.
>
> The original form is more correct though, because now you can get
> spurious warnings that the string have been truncated when that is not
> true. (If t->name is not zeroized you will get the spurious warning for
> any string shorter than MAX_TUBE_NAME_LEN, which is the opposite of
> what the warning says.
>
> The third argument to strncpy can be as long as the size of the buffer
> you are writing into, the additional check you have there insures that
> the string is terminated (even if that requires truncation).
>
> So I would say you should drop your change and stop believing in random
> google results :)

Sorry, hit send prematurely.

If you really want to avoid the warning instead of ignoring it, you
should change the code this way:

strncpy(t->name, name, MAX_TUBE_NAME_LEN-1);
if (t->name[MAX_TUBE_NAME_LEN - 2] != '\0') {
t->name[MAX_TUBE_NAME_LEN - 1] = '\0';
twarnx("truncating tube name");
}

NOTE: the -2 in the condition, this is needed because memory locations
start counting from 0, so if you write N-1 bytes the Nth-1 byte is at
the N-2 position when you start counting from 0.
And that is the last position your strncpy wrote to, and if that is not
0 then potentially string truncation occurred.

You still want to zero the last available byte in that case and not the
N-1 available byte, so you set N-1 to 0, not N-2.

N-1 is the Nth byte when you start counting from 0 and N is the size of
the array.


...or use snprintf() and check! its! return! value! (sorry, I've had to
explain that to too many people over too many years).


^ This.


Something like (completely, totally untested, but should give you an
idea):

 const int res = snprintf(t->name, MAX_TUBE_NAME_LEN, "%s", name);
 if (res < 0 || (size_t)res >= MAX_TUBE_NAME_LEN)
twarnx("truncating tube name");

...although, in all fairness, the two conditions should be checked
separately, since the first one (res < 0) indicates a serious error and
no meaningful characters at all written to t->name.

___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: git merge issue

[Jonathan Wakely]

On 11/06/20 06:41 -0500, Richard Shaw wrote:

I'm working on updating fldigi to build better in the Fedora MinGW
environment and I have commit access to the git repo (at least access to
create my own branches).

I have a branch called "tmp/mingw" and I've made several commits. I know
other commits had been made to master and I've done this in many other
instances but in this case it's causing a "bad merge":

(commit current working state)
$ git commit -am "Initial commit for MinGW 64bit build fixes."
$ git push tmp/mingw

(master is a few commits head of my branch)
$ git merge master
(Merge commit is added to my branch)

$ git push
$ git push
Password:
Enumerating objects: 31, done.
Counting objects: 100% (31/31), done.
Delta compression using up to 12 threads
Compressing objects: 100% (11/11), done.
Writing objects: 100% (11/11), 1.40 KiB | 1.40 MiB/s, done.
Total 11 (delta 10), reused 0 (delta 0), pack-reused 0
remote: -Info- Update is fast-forward
remote: -Info- The user is: 'hobbes1069'
remote: -Info- Found matching head pattern: 'refs/heads/tmp/.*'
remote: -Info- Checking user: 'hobbes1069' against pattern: '.*'
remote: -Grant- Allowing user: 'hobbes1069' with pattern: '.*'
remote: -Grant- Granting access based on ./info/allowed-users
remote:
remote: *** Your commits contain a bad merge:
remote: ***   47456e93  2020-06-10  Merge branch 'master' into tmp/mingw***
Please rebase on top of this commit in tmp/mingw:
remote: ***   a596a086  2020-06-10  Initial commit for MinGW 64bit builds.
remote: error: hook declined to update refs/heads/tmp/mingw
To ssh://git.code.sf.net/p/fldigi/fldigi
! [remote rejected]   tmp/mingw -> tmp/mingw (hook declined)
error: failed to push some refs to 'ssh://
hobbes1...@git.code.sf.net/p/fldigi/fldigi'

Every time I think I "get" git, I find out I really don't...


This isn't git. The error says "hook declined" which means it's a
custom hook on the remote end that has refused the push.


Interestingly when I first tried to push my branch I had to use:

$ git push origin HEAD:tmp/mingw

just using:

$ git push origin tmp/mingw

Didn't work. Is this a sourceforge git quirk?


No.

The value of 'git config push.default' determines the behaviour of
that command. For most of the possible values for push.default
that's the expected behaviour.

For push.default=simple or push.default=upstream that command will try
to push to a branch on the remote end using the name of the branch
that tmp/mingw tracks, which is probably 'master'.

To create a new branch on the remote with that name, HEAD:tmp/mingw is
the right refspec to use.

___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[Bug 1846493] New: perl-Sereal-Decoder-4.014 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1846493

Bug ID: 1846493
   Summary: perl-Sereal-Decoder-4.014 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Sereal-Decoder
  Keywords: FutureFeature, Triaged
  Assignee: ppi...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: de...@fateyev.com, jples...@redhat.com,
perl-devel@lists.fedoraproject.org, ppi...@redhat.com
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 4.014
Current version/release in rawhide: 4.011-1.fc32
URL: http://search.cpan.org/dist/Sereal-Decoder/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from anitya:
https://release-monitoring.org/project/8066/


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1846491] New: perl-Sereal-Encoder-4.014 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1846491

Bug ID: 1846491
   Summary: perl-Sereal-Encoder-4.014 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Sereal-Encoder
  Keywords: FutureFeature, Triaged
  Assignee: ppi...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: de...@fateyev.com, jples...@redhat.com,
perl-devel@lists.fedoraproject.org, ppi...@redhat.com
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 4.014
Current version/release in rawhide: 4.011-1.fc32
URL: http://search.cpan.org/dist/Sereal-Encoder/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from anitya:
https://release-monitoring.org/project/8065/


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1846490] New: perl-Sereal-4.014 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1846490

Bug ID: 1846490
   Summary: perl-Sereal-4.014 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Sereal
  Keywords: FutureFeature, Triaged
  Assignee: ppi...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: de...@fateyev.com, perl-devel@lists.fedoraproject.org,
ppi...@redhat.com
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 4.014
Current version/release in rawhide: 4.011-1.fc32
URL: http://search.cpan.org/dist/Sereal/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from anitya:
https://release-monitoring.org/project/7605/


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

Re: git merge issue

[Richard Shaw]

On Thu, Jun 11, 2020 at 11:46 AM Miro Hrončok  wrote:

> On 11. 06. 20 13:41, Richard Shaw wrote:
> > remote: *** Your commits contain a bad merge:
> > remote: ***   47456e93  2020-06-10  Merge branch 'master' into
> tmp/mingw***
> > Please rebase on top of this commit in tmp/mingw:
> > remote: ***   a596a086  2020-06-10  Initial commit for MinGW 64bit
> builds.
>
> This sounds like some hook of their own. They are asking you to rebase
> your
> changes instead of merging.
>

Yeah, that's what I ended up doing...

Thanks,
Richard
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Highlights from the latest Copr release 2020-06-10

[Pavel Raiskup]

On Wednesday, June 10, 2020 10:31:32 PM CEST Iñaki Ucar wrote:
> > - Copr-cli supports batch build delete feature:
> >
> > $ copr-cli delete build_id [build_id ...]
>
> Hooray! Just delete or delete-build?

Yes, typo, I meant "delete-build" command.

Pavel


___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: git merge issue

[Miro Hrončok]

On 11. 06. 20 13:41, Richard Shaw wrote:

remote: *** Your commits contain a bad merge:
remote: ***   47456e93  2020-06-10  Merge branch 'master' into tmp/mingw*** 
Please rebase on top of this commit in tmp/mingw:

remote: ***   a596a086  2020-06-10  Initial commit for MinGW 64bit builds.


This sounds like some hook of their own. They are asking you to rebase your 
changes instead of merging.


--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[Bug 1846147] New: perl-Sereal-4.012 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1846147

Bug ID: 1846147
   Summary: perl-Sereal-4.012 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Sereal
  Keywords: FutureFeature, Triaged
  Assignee: ppi...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: de...@fateyev.com, perl-devel@lists.fedoraproject.org,
ppi...@redhat.com
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 4.012
Current version/release in rawhide: 4.011-1.fc32
URL: http://search.cpan.org/dist/Sereal/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from anitya:
https://release-monitoring.org/project/7605/


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

Re: swap-on-ZRAM by default

[Konstantin Kharlamov]

On Mon, 2020-06-08 at 09:37 +0300, Konstantin Kharlamov wrote:
> On Sun, 2020-06-07 at 18:19 -0600, Chris Murphy wrote:
> > On Sun, Jun 7, 2020 at 12:56 PM Konstantin Kharlamov <
> > > hi-an...@yandex.ru> wrote:
> > > enough! The moral of this story is that you can't get away with
> > > only
> > > ZRAM without any disk SWAP. You need disk SWAP. And if you have
> > > disk
> > > SWAP, ZSWAP fits more nicely there as a compressing buffer before
> > > the
> > > data finally spills over to disk.
> > 
> > Your use case is intentionally overcommitting available memory and
> > it
> > sounds like you don't have much choice in that you (a) the workload
> > you have is the workload you need to run, and (b) memory isn't
> > upgradeable.
> > 
> > You should consider testing whether swap-on-zram sized to 100% RAM
> > fits your use case better. And in fact if your workload gets very
> > good
> > compression ratios, it can be quite reasonable to go higher than
> > 100%.
> 
> Thanks! I'll give it a try, will report back.

So far everything was fine with ZRAM configured to use 100%. That said,
as per discussion in another thread I have migrated today back to ZSRAM
as it is more suitable when there is a on-disk SWAP as well (can't
provide a link as mail archive returns 503 right now, but the
discussion is called "Fedora 33 System-Wide Change proposal: swap on
zram". Turns out, the discussion of proposal is being held there, not
in this thread. It is easy to mistake because the original proposal
page does not have a link to discussion right now. I could as well have
started a new discussion ¯\_(ツ)_/¯).
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Schedule for Thursday's FPC Meeting (2020-06-11 16:00 UTC)

[James Antill]

 Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2020-06-11 16:00 UTC in #fedora-meeting-1 on 
irc.freenode.net.

 Local time information (via. uitime):

= Day: Thursday ==
2020-06-11 09:00 PDT  US/Pacific
2020-06-11 12:00 EDT  --> US/Eastern <--
2020-06-11 16:00 UTC  UTC   
2020-06-11 17:00 BST  Europe/London 
2020-06-11 18:00 CEST Europe/Berlin 
2020-06-11 18:00 CEST Europe/Paris  
2020-06-11 21:30 IST  Asia/Calcutta 
 New Day: Friday -
2020-06-12 00:00 HKT  Asia/Hong_Kong
2020-06-12 00:00 +08  Asia/Singapore
2020-06-12 01:00 JST  Asia/Tokyo
2020-06-12 02:00 AEST Australia/Brisbane


 Links to all tickets below can be found at: 

https://pagure.io/packaging-committee/issues?status=Open=meeting

= Followup Issues =

#topic #907 Which %__foo macros for executables are acceptable? 
.fpc 907
https://pagure.io/packaging-committee/issue/907

#topic #909 Suggest that linting/measuring-coverage is not for %check
.fpc 909
https://pagure.io/packaging-committee/issue/909

#topic #963 Blanket Bootstrap Exception for building Mono 
.fpc 963
https://pagure.io/packaging-committee/issue/963

#topic #977 Get new members? 
.fpc 977
https://pagure.io/packaging-committee/issue/977

= Followup Pull Requests =

#topic #pr-814 Add SELinux Independent Policy Guidelines 
https://pagure.io/packaging-committee/pull-request/814

#topic #pr-938 Add Package Review Process page 
https://pagure.io/packaging-committee/pull-request/938

#topic #pr-#947 Deprecate Old Style Dependency Generators 
https://pagure.io/packaging-committee/pull-request/947

#topic #pr-#954 Prohibit use of `rpm` command from specfile. 
https://pagure.io/packaging-committee/pull-request/954

= New Pull Requests =

#topic #pr-#942 Recommend storing changelog entries in separate file. 
https://pagure.io/packaging-committee/pull-request/942

= Open Floor = 

 For more complete details, please visit each individual ticket.  The
report of the agenda items can be found at:

https://pagure.io/packaging-committee/issues?status=Open=meeting

 If you would like to add something to this agenda, you can:
  * Reply to this e-mail
  * File a new ticket at: https://pagure.io/packaging-committee
  * E-mail me directly
  * Bring it up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting.
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: A few questions about a package update / policy questions / GCC 9 error

[Tony Nelson]

On 20-06-10 14:22:53, Simo Sorce wrote:

On Wed, 2020-06-10 at 14:16 -0400, Simo Sorce wrote:
> On Wed, 2020-06-10 at 20:01 +0200, Dan Čermák wrote:
> > "Nathanael D. Noblet"  writes:
> >
> > > Hello,
> > >
> > >   I maintain beanstalkd which is a message server of sorts. It  
recently
> > > released a new version however some changes I'm not 100% sure  
about.

> > >
> > >   When compiling I got the following GCC error.
> > >
> > > usr/include/bits/string_fortified.h:106:10: error:  
'__builtin_strncpy'

> > > specified bound 201 equals destination size [-Werror=stringop-
> > > truncation]
> > >   106 |   return __builtin___strncpy_chk (__dest, __src, __len,  
__bos

> > > (__dest));
> > >   |   
^~

> > > 
> > >
> > > Results via google says that strncpy needs to have the third  
argument

> > > less than the 2nd, so I've got this patch, similar to others:
> > >
> > > --- beanstalkd-1.12/tube.c.org  2020-06-10 09:37:35.129224346  
-0600
> > > +++ beanstalkd-1.12/tube.c  2020-06-10 09:37:42.761138035  
-0600

> > > @@ -12,7 +12,7 @@
> > >  if (!t)
> > >  return NULL;
> > >
> > > -strncpy(t->name, name, MAX_TUBE_NAME_LEN);
> > > +strncpy(t->name, name, MAX_TUBE_NAME_LEN-1);
> > >  if (t->name[MAX_TUBE_NAME_LEN - 1] != '\0') {
> > >  t->name[MAX_TUBE_NAME_LEN - 1] = '\0';
> > >  twarnx("truncating tube name");
> > >
> > > You'll notice it was already checking the len-1 for null. Can  
anyone

> > > verify that my change won't cause some un-intended bug I don't
> > > understand?
> >
> > If I understand it correctly, then you are now invoking undefined
> > behavior: you copy at most MAX_TUBE_NAME_LEN-1 bytes to t->name  
and then
> > check whether the following byte (that was never written to) is  
not
> > equal to 0. I have not checked the code of beanstalkd, but the  
contents
> > of t->name[MAX_TUBE_NAME_LEN - 1] will be zero if it was  
allocated via
> > calloc() at best or random at worst. Irrespectively of that, the  
check
> > now no longer does what it *should*: null terminate the string if  
it is
> > not null terminated. It will now randomly null terminate it or  
not at

> > all.
>
> strncpy() is a truly awful API unfortunately, the change is
> meaningless, but it is not random as Dan says.
>
> The original form is more correct though, because now you can get
> spurious warnings that the string have been truncated when that is  
not
> true. (If t->name is not zeroized you will get the spurious warning  
for

> any string shorter than MAX_TUBE_NAME_LEN, which is the opposite of
> what the warning says.
>
> The third argument to strncpy can be as long as the size of the  
buffer
> you are writing into, the additional check you have there insures  
that

> the string is terminated (even if that requires truncation).
>
> So I would say you should drop your change and stop believing in  
random

> google results :)

Sorry, hit send prematurely.

If you really want to avoid the warning instead of ignoring it, you
should change the code this way:

strncpy(t->name, name, MAX_TUBE_NAME_LEN-1);
if (t->name[MAX_TUBE_NAME_LEN - 2] != '\0') {
t->name[MAX_TUBE_NAME_LEN - 1] = '\0';
twarnx("truncating tube name");
}

NOTE: the -2 in the condition, this is needed because memory locations
start counting from 0, so if you write N-1 bytes the Nth-1 byte is at
the N-2 position when you start counting from 0.
And that is the last position your strncpy wrote to, and if that is  
not

0 then potentially string truncation occurred.

You still want to zero the last available byte in that case and not  
the

N-1 available byte, so you set N-1 to 0, not N-2.

N-1 is the Nth byte when you start counting from 0 and N is the size  
of

the array.

HTH,
Simo.


I prefer to not look outside of the string's data into apparently
uninitialized memory.  Was t->name initialized elsewhere?  I would
write:

t->name[0] = 0;
strncat(t->name, name, MAX_TUBE_NAME_LEN-1);
if (strcmp(t->name, name)) {
...

strncat always writes a terminating NUL.

strcmp only looks at the string data, not past its end.

BTW, a better name for MAX_TUBE_NAME_LEN would be MAX_TUBE_NAME_SIZ.

C, bah.

--

TonyN.:'   
  '  
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[Bug 1846149] New: perl-Sereal-Encoder-4.012 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1846149

Bug ID: 1846149
   Summary: perl-Sereal-Encoder-4.012 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Sereal-Encoder
  Keywords: FutureFeature, Triaged
  Assignee: ppi...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: de...@fateyev.com, jples...@redhat.com,
perl-devel@lists.fedoraproject.org, ppi...@redhat.com
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 4.012
Current version/release in rawhide: 4.011-1.fc32
URL: http://search.cpan.org/dist/Sereal-Encoder/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from anitya:
https://release-monitoring.org/project/8065/


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

git merge issue

[Richard Shaw]

I'm working on updating fldigi to build better in the Fedora MinGW
environment and I have commit access to the git repo (at least access to
create my own branches).

I have a branch called "tmp/mingw" and I've made several commits. I know
other commits had been made to master and I've done this in many other
instances but in this case it's causing a "bad merge":

(commit current working state)
$ git commit -am "Initial commit for MinGW 64bit build fixes."
$ git push tmp/mingw

(master is a few commits head of my branch)
$ git merge master
(Merge commit is added to my branch)

$ git push
$ git push
Password:
Enumerating objects: 31, done.
Counting objects: 100% (31/31), done.
Delta compression using up to 12 threads
Compressing objects: 100% (11/11), done.
Writing objects: 100% (11/11), 1.40 KiB | 1.40 MiB/s, done.
Total 11 (delta 10), reused 0 (delta 0), pack-reused 0
remote: -Info- Update is fast-forward
remote: -Info- The user is: 'hobbes1069'
remote: -Info- Found matching head pattern: 'refs/heads/tmp/.*'
remote: -Info- Checking user: 'hobbes1069' against pattern: '.*'
remote: -Grant- Allowing user: 'hobbes1069' with pattern: '.*'
remote: -Grant- Granting access based on ./info/allowed-users
remote:
remote: *** Your commits contain a bad merge:
remote: ***   47456e93  2020-06-10  Merge branch 'master' into tmp/mingw***
Please rebase on top of this commit in tmp/mingw:
remote: ***   a596a086  2020-06-10  Initial commit for MinGW 64bit builds.
remote: error: hook declined to update refs/heads/tmp/mingw
To ssh://git.code.sf.net/p/fldigi/fldigi
 ! [remote rejected]   tmp/mingw -> tmp/mingw (hook declined)
error: failed to push some refs to 'ssh://
hobbes1...@git.code.sf.net/p/fldigi/fldigi'

Every time I think I "get" git, I find out I really don't...

Interestingly when I first tried to push my branch I had to use:

$ git push origin HEAD:tmp/mingw

just using:

$ git push origin tmp/mingw

Didn't work. Is this a sourceforge git quirk?

Help!

Thanks,
Richard
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Datacenter move day 2

[Ben Cotton]

On Thu, Jun 11, 2020 at 12:08 PM Kevin Kofler  wrote:
>
> FYI, claiming the badge for the elections does not work,
> badges.fedoraproject.org spews an error 500 Internal Server Error.
>
The badge claim URL should be valid for a few days beyond the end of
the voting period. If anyone is unable to claim the badge, they can
open an issue at https://pagure.io/fedora-project-schedule/new_issue
and I will manually award badges when the system is back online.

-- 
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Announcement: Aim to remove libdb-java from Fedora-rawhide

[Ondrej Dubaj]

Hello everyone,

we are aiming to remove libdb-java package from Fedora-rawhide, as we are
currently preparing for jdk update from jdk-1.8 to jdk-11 in Fedora
rawhide. The problem is that we are unable to rebuild this package with
jdk-11. It is still possible to "hack" it and rebuild it with jdk-1.8, but
that can cause unexpected runtime behaviour according to JVM-11, which will
soon be default in Fedora-rawhide.

There seems to be no packages, which depend directly to libdb-java and
upstream does not support version 5.3.28 anymore.

If anyone has any reasons why this should not be made, or someone is
currently active user of this JDBC connector, please leave a comment with
your opinion in the tracker [1] mentioned below.

There is also an existing tracker for deprecating libdb in Fedora [2], so
this can be understand as a first step.

Additional info about jdk-11 here [3].

Best regards,

Ondrej Dubaj
Associate Software Engineer
Red Hat

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1846398
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1834842
[3]
https://fedoraproject.org/wiki/Changes/Java11#Intermediate_step_build_with_java-1.8.0-openjdk-devel_and_run_with_java_.28that_means_any_sytem_java.2C_eg_java-11-openjdk.29
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org

Re: [ELN] Opt out python2.7 from ELN

[Miro Hrončok]

On 11. 06. 20 13:09, Miro Hrončok wrote:

On 08. 06. 20 16:49, Miro Hrončok wrote:

Hello,

as a maintainer of the python2.7 package I was surprised to see it being built 
for ELN and I like to start a discussion on whether and how can I opt out this 
deprecated package from ELN.
I also see the python3.6 package being rebuilt for ELN and would also like for 
that one to be removed. It is packaged for developers so they can test their 
software, not as something to put to a next version of a enterprise distribution.

Both packages are added via:

https://github.com/minimization/content-resolver-input/pull/25


But I am not sure if this is enough to block them from ELN.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Datacenter move day 2

[Kevin Fenzi]

On Wed, Jun 10, 2020 at 01:33:17PM +0200, Dan Horák wrote:
> On Wed, 10 Jun 2020 12:55:08 +0200
> Dan Horák  wrote:
> 
> > On Wed, 10 Jun 2020 12:46:15 +0200
> > Dan Horák  wrote:
> > 
> > > On Wed, 10 Jun 2020 12:17:42 +0200
> > > Dan Horák  wrote:
> > > 
> > > > On Tue, 9 Jun 2020 23:24:57 -0700
> > > > Kevin Fenzi  wrote:
> > > > 
> > > > > Greetings everyone. 
> > > > > 
> > > > > Just a quick recap of our day 2 datacenter move. 
> > > > > 
> > > > > Today was the buildsystem and all it's assocated things. 
> > > > > 
> > > > > As for builders in the new datacenter, we have 32 buildvm's, 40
> > > > > buildvm-ppc64's, the same number of s390x (15) and 15 each of
> > > > > buildvm-a64 (aarch6) and buildvm-a32 (armv7/armhfp). So, likely
> > > > > arm builds are going to be the last to finish for many. Luckily
> > > > > this only needs to last us a few weeks until we can get the rest
> > > > > of our arm builders shipped and re-added. 
> > > > 
> > > > I see only the 2nd group (KVM) of s390x builders being enabled, is
> > > > that right?
> > > 
> > > and they are experiencing the "incomplete srpm" issue frequently :-(
> > 
> > might be a problem with their cache
> 
> and Smooge fixed the cache config, so the s390x builders work again

I disabled them as it seemed that they were failing all builds. 

I'll go ahead and re-enable the z/vm ones again now that the cache is
sorted out. 

kevin



signature.asc
Description: PGP signature
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Datacenter move day 2

[Kevin Kofler]

Kevin Fenzi wrote:
> Greetings everyone.
> 
> Just a quick recap of our day 2 datacenter move.

FYI, claiming the badge for the elections does not work, 
badges.fedoraproject.org spews an error 500 Internal Server Error.

Kevin Kofler
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[Bug 1846148] New: perl-Sereal-Decoder-4.012 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1846148

Bug ID: 1846148
   Summary: perl-Sereal-Decoder-4.012 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Sereal-Decoder
  Keywords: FutureFeature, Triaged
  Assignee: ppi...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: de...@fateyev.com, jples...@redhat.com,
perl-devel@lists.fedoraproject.org, ppi...@redhat.com
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 4.012
Current version/release in rawhide: 4.011-1.fc32
URL: http://search.cpan.org/dist/Sereal-Decoder/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from anitya:
https://release-monitoring.org/project/8066/


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

Re: Datacenter move day 2

[Kevin Fenzi]

On Wed, Jun 10, 2020 at 04:31:39PM +0200, Dominik 'Rathann' Mierzejewski wrote:
> On Wednesday, 10 June 2020 at 08:24, Kevin Fenzi wrote:
> > Greetings everyone. 
> > 
> > Just a quick recap of our day 2 datacenter move. 
> 
> Thanks for all your hard work and for providing these (not so little)
> updates!

You're welcome. 
> 
> I hope you get some well-deserved rest after all is done.

Me too. ;) I look forward to getting back to helping people get cool
things done in our community. 

kevin


signature.asc
Description: PGP signature
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Fedora Jam switch to GNOME

[Zbigniew Jędrzejewski-Szmek]

On Wed, Jun 10, 2020 at 09:09:28AM -0700, er...@ericheickmeyer.com wrote:
> Hi all,
> 
> I'm considering moving Fedora Jam from KDE Plasma to GNOME. There are
> multiple reasons for this, and I think part of it would be beneficial
> to the overall GNOME and Fedora communities as it would be a way to be
> helping improve the situation in GNOME that exist as the biggest
> objections from the community of musicians and Linux audio enthusiasts
> in the overall community.
> 
> The biggest objections are resource usage, since the more resources
> that are in use, the more it tends to interfere with real-time audio
> processes, causing buffer overruns and/or underruns. These overruns and
> underruns are known as Xruns. The fewer Xruns, the better, as Xruns
> cause pops during recording. When doing real-time audio work, you want
> to have as low of latency as possible which requires as small of a
> buffer as possible. The goal is to have a small buffer to get minimal
> latency while avoiding Xruns.
> 
> Unfortunately, GNOME has, since 3.0, traditionally interfered with
> these processes and caused Xruns. My goal, by moving Fedora Jam from
> Plasma to GNOME, is to help GNOME improve this situation.

I'll be blunt here. I don't think this is a good _motivation_ for the
change. If you want to improve Gnome, you can do switch your own
desktop and do tests, and you can write patches, or you can review
other's patches, or you can talk on gnome mailing lists to make the
issue more prominent. But a spin for users should use whatever is best
for the purpose of that spin, period. Users != guinea pigs.

> The other reason for switching away from Plasma is the overall negative
> attitude I see from Fedora KDE users and former Fedora KDE
> contributors. It seems to be an attitude against the progress of
> improving the Linux desktop for the better, and simply complaining. I
> know some of this attitude comes from Red Hat dropping KDE from being a
> desktop in REHL, among other changes. That attitude is regressive, and
> does nothing to help the community if all you do is complain. I could
> name names, but for the sake of the "Friends" foundation, I will not.

I'd prefer to talk about which DE is better (now, or in the
foreseeable future). While too many complaints are indeed tiring,
those human-related reasons don't seem like enough to switch the
desktop either.

(I have no knowledge whether KDE or Gnome is better for music. If the
pipewire stuff works out then the situation might be quite different
than in the past... The switch might be well motivated by this and
other reasons, I just think that the two listed above are not good.)

Zbyszek
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[Bug 1846147] perl-Sereal-4.012 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1846147

Petr Pisar  changed:

   What|Removed |Added

 Depends On||1846148, 1846149





Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1846148
[Bug 1846148] perl-Sereal-Decoder-4.012 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1846149
[Bug 1846149] perl-Sereal-Encoder-4.012 is available
-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1846148] perl-Sereal-Decoder-4.012 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1846148

Petr Pisar  changed:

   What|Removed |Added

 Blocks||1846147





Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1846147
[Bug 1846147] perl-Sereal-4.012 is available
-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

Re: [ELN] Opt out python2.7 from ELN

[Miro Hrončok]

On 08. 06. 20 16:49, Miro Hrončok wrote:

Hello,

as a maintainer of the python2.7 package I was surprised to see it being built 
for ELN and I like to start a discussion on whether and how can I opt out this 
deprecated package from ELN.
I also see the python3.6 package being rebuilt for ELN and would also like for 
that one to be removed. It is packaged for developers so they can test their 
software, not as something to put to a next version of a enterprise distribution.


Thanks,

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[Bug 1846149] perl-Sereal-Encoder-4.012 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1846149

Petr Pisar  changed:

   What|Removed |Added

 Blocks||1846147





Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1846147
[Bug 1846147] perl-Sereal-4.012 is available
-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

Re: dropping NSS DBM format support in F33+

[Robert Relyea]

On 6/11/20 8:37 AM, Robert Relyea wrote:

On 4/23/20 11:16 AM, Brian C. Lane wrote:

On Wed, Apr 22, 2020 at 10:11:25AM +0200, Daiki Ueno wrote:

Hello,

I am not sure if this deserves a Fedora Change proposal, so I'd like to
hear any opinions first before proceeding with the process.

NSS (the crypto library used by Firefox) historically supports 2
database formats: SQLite and DBM.  The latter is considered legacy and
we switched the default database format to SQLite in F28[1]. Since then
I presume most of the applications have switched to the new format.
Therefore we are planning to phase out the support of DBM, targetting
F33+.

How will that effect people who have been upgrading since before F28?
Will the DBM database be transitioned to SQLite (or has it already)?


It depends on how the database was used. NSS automatically updates to 
the new format if:


1) the database is opened R/W, and

2) the user has authenticated to the database (logged into to it). If 
the database has no password, then only (1) is required.


Most use cases will, most likely, have caused the above changes. 
Firefox would have triggered a login anytime the user first needs to 
access tha master password list.  Thunderbird and servers would have 
triggered those conditions when the certificate was renewed.


If you aren't sure, you can manually force an update on any fedora 
version before F33 with the following command:


certutil -K -X -d {directory_of_nss_database}
If you are running on a system pre-F28, you need to add sql: before the 
{directory_of_nss_database}. This should work on any system built since 
2005.


and supply the password when prompted.

bob
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[Bug 1846149] perl-Sereal-Encoder-4.012 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1846149

Petr Pisar  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
 CC|jples...@redhat.com,|
   |ppi...@redhat.com   |
   Doc Type|--- |If docs needed, set a value




-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1846147] perl-Sereal-4.012 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1846147

Petr Pisar  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
 Depends On||1252529



--- Comment #1 from Petr Pisar  ---
An enhancement release suitable for all Fedoras and EPEL ≥ 8.



Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1252529
[Bug 1252529] Review Request: perl-Test-MemoryGrowth - Assert that code does
not cause growth in memory usage
-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1846148] perl-Sereal-Decoder-4.012 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1846148

Petr Pisar  changed:

   What|Removed |Added

 Depends On||1252529





Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1252529
[Bug 1252529] Review Request: perl-Test-MemoryGrowth - Assert that code does
not cause growth in memory usage
-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

Re: dropping NSS DBM format support in F33+

[Robert Relyea]

On 4/23/20 11:16 AM, Brian C. Lane wrote:

On Wed, Apr 22, 2020 at 10:11:25AM +0200, Daiki Ueno wrote:

Hello,

I am not sure if this deserves a Fedora Change proposal, so I'd like to
hear any opinions first before proceeding with the process.

NSS (the crypto library used by Firefox) historically supports 2
database formats: SQLite and DBM.  The latter is considered legacy and
we switched the default database format to SQLite in F28[1].  Since then
I presume most of the applications have switched to the new format.
Therefore we are planning to phase out the support of DBM, targetting
F33+.

How will that effect people who have been upgrading since before F28?
Will the DBM database be transitioned to SQLite (or has it already)?


It depends on how the database was used. NSS automatically updates to 
the new format if:


1) the database is opened R/W, and

2) the user has authenticated to the database (logged into to it). If 
the database has no password, then only (1) is required.


Most use cases will, most likely, have caused the above changes. Firefox 
would have triggered a login anytime the user first needs to access tha 
master password list.  Thunderbird and servers would have triggered 
those conditions when the certificate was renewed.


If you aren't sure, you can manually force an update on any fedora 
version before F33 with the following command:


certutil -K -X -d {directory_of_nss_database}

and supply the password when prompted.

bob
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[Bug 1846148] perl-Sereal-Decoder-4.012 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1846148



--- Comment #3 from Fedora Update System  ---
FEDORA-2020-0236944568 has been submitted as an update to Fedora 31.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-0236944568


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1846149] perl-Sereal-Encoder-4.012 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1846149



--- Comment #3 from Fedora Update System  ---
FEDORA-2020-0236944568 has been submitted as an update to Fedora 31.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-0236944568


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1846149] perl-Sereal-Encoder-4.012 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1846149



--- Comment #2 from Fedora Update System  ---
FEDORA-2020-61103921dc has been submitted as an update to Fedora 32.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-61103921dc


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1846147] perl-Sereal-4.012 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1846147

Petr Pisar  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
 CC|ppi...@redhat.com   |
   Doc Type|--- |If docs needed, set a value




-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1846148] perl-Sereal-Decoder-4.012 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1846148



--- Comment #4 from Petr Pisar  ---
Good for EPEL8 either, but a new perl(Test::MemoryGrowth) dependency is missing
there.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1846149] perl-Sereal-Encoder-4.012 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1846149

Petr Pisar  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-Sereal-Encoder-4.012-1
   ||.fc33



--- Comment #1 from Petr Pisar  ---
An enhancement release suitable for all Fedoras.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1846148] perl-Sereal-Decoder-4.012 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1846148

Petr Pisar  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
 CC|jples...@redhat.com,|
   |ppi...@redhat.com   |
   Doc Type|--- |If docs needed, set a value




-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

Announcement: Aim to remove libdb-java from Fedora-rawhide

[Ondrej Dubaj]

Hello everyone,

we are aiming to remove libdb-java package from Fedora-rawhide, as we are
currently preparing for jdk update from jdk-1.8 to jdk-11 in Fedora
rawhide. The problem is that we are unable to rebuild this package with
jdk-11. It is still possible to "hack" it and rebuild it with jdk-1.8, but
that can cause unexpected runtime behaviour according to JVM-11, which will
soon be default in Fedora-rawhide.

There seems to be no packages, which depend directly to libdb-java and
upstream does not support version 5.3.28 anymore.

If anyone has any reasons why this should not be made, or someone is
currently active user of this JDBC connector, please leave a comment with
your opinion in the tracker [1] mentioned below.

There is also an existing tracker for deprecating libdb in Fedora [2], so
this can be understand as a first step.

Additional info about jdk-11 here [3].

Best regards,

Ondrej Dubaj
Associate Software Engineer
Red Hat

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1846398
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1834842
[3]
https://fedoraproject.org/wiki/Changes/Java11#Intermediate_step_build_with_java-1.8.0-openjdk-devel_and_run_with_java_.28that_means_any_sytem_java.2C_eg_java-11-openjdk.29
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[389-devel] Please review missing ifdef

[William Brown]

https://pagure.io/389-ds-base/pull-request/51146 
—
Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs
___
389-devel mailing list -- 389-de...@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-de...@lists.fedoraproject.org

Re: [ELN] Opt out python2.7 from ELN

[Miro Hrončok]

On 10. 06. 20 11:09, Vít Ondruch wrote:

You should probably open PR modifying this file:

https://github.com/minimization/content-resolver-input/blob/master/configs/view-eln.yaml


Thanks. I don't understand that file and hence I won't open PRs to it (not until 
I understand the relation between this file and ELN).


--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Fedora Jam switch to GNOME

[Sam Varshavchik]

er...@ericheickmeyer.com writes:


Anyhow, I'd love to see a discussion about this as well as any guidance
toward making this change. I know there would have to be a new
kickstart along with Koji pointing toward said kickstart. I could make
the kickstart, but I think I'd need Koji to look for it.


Have you considered XFCE? For me, XFCE is a breath of fresh air. It's a  
traditional desktop environment, that always feels like a comfortable, well  
worn pair of shoes.


And to your comment about attitudes, I can only say that I had one  
opportunity to report a bug, it was received well and addressed.




pgpaYaBDQ4PJ_.pgp
Description: PGP signature
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[389-devel] 389 DS nightly 2020-06-11 - 95% PASS

[vashirov]

https://fedorapeople.org/groups/389ds/ci/nightly/2020/06/11/report-389-ds-base-1.4.3.9-1.fc32.x86_64.html
___
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://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org

Re: Highlights from the latest Copr release 2020-06-10

[Iñaki Ucar]

On Wed, 10 Jun 2020 at 21:42, Pavel Raiskup  wrote:
>
> - Copr project "runtime" dependencies were implemented.

Great!

> - Copr-cli supports batch build delete feature:
>
> $ copr-cli delete build_id [build_id ...]

Hooray! Just delete or delete-build?

-- 
Iñaki Úcar
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Self Introduction: Qiyu Yan

[西木野羰基]

Thanks!
My first review request: https://bugzilla.redhat.com/show_bug.cgi?id=1846175
Any one willing to review that? A very simple package. And I am also
looking for a sponsorship after this can be approved.

Robin Lee  于2020年6月11日周四 上午12:47写道：
>
>
>
> On Thursday, June 11, 2020, Qiyu Yan  wrote:
> > I am Qiyu Yan, mail: yanqiy...@gmail.com, a 5-yesr Fedora user and a 
> > undergraduate student in Physics.
> >
> > I started doing packaging because I want to setup development environment 
> > for my lab's computers, the software I first packaged is geant4 on copr 
> > http://copr.fedorainfracloud.org/coprs/yanqiyu/geant4/
> >
> > By improving the package forked from someone else, I started to know how to 
> > do packaging. (geant4 is a complexed software, I need more time to package 
> > it well)
> >
> > But I am not trying to join devel to bring geant4 to official repository 
> > here:
> >
> > I want to make an open-source anti-censorship proxy software 
> > [Trojan](https://github.com/trojan-gfw/trojan) [GPL-3.0 license] available 
> > to Fedora's official repositories. Will that be  possible? (Its named as 
> > trojan but it is a proxy, which pretends to be a TLS server which makes it 
> > possible to bypass China, or any other government's censorship)
> >
> > Fedora's official repositories already have a python3-shadowsocks with 
> > similar functions, but that project is likely to be out of maintenance. I 
> > think having a new one will be great.
> >
> > I have made it to be able to build on 
> > [koji](https://koji.fedoraproject.org/koji/taskinfo?taskID=45580956) what 
> > to do next to carry on?
> >
> > And I want to add more proxy software, such as 
> > [V2ray](https://github.com/v2ray/v2ray-core) and 
> > [Shadowsocks-libev](https://github.com/shadowsocks/shadowsocks-libev) later.
> >
> > Why I want to build those proxies into fedora's official repository? That 
> > is because downloading those software from GitHub or COPR will be extremely 
> > slow, but if them can enter official repository, they will be mirrored into 
> > China, which will make it easier to install for Chinese users.
> >
> > And they are not a Chinese only software, they are also useful when you 
> > don't want someone else to know if you are using a proxy, wireguard or 
> > IPSec just do encryption but not confuse possible attackers.
> >
>
> Welcome!
> You can follow this guide[0] and submit your first review request.
>
> [0] https://fedoraproject.org/wiki/Join_the_package_collection_maintainers
>
> ___
> > 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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: 
> > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> > ___
> 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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Draft of New Python Packaging Guidelines

[Tomas Orsava]

On 6/9/20 12:15 PM, Petr Viktorin wrote:

On 2020-06-08 12:15, Tomas Orsava wrote:

On 6/8/20 11:58 AM, Petr Viktorin wrote:



On 2020-06-05 16:12, Tomas Orsava wrote:

On 6/5/20 2:26 PM, Petr Viktorin wrote:



On 2020-06-05 11:51, Tomas Orsava wrote:

On 6/5/20 11:26 AM, Petr Viktorin wrote:

On 2020-06-03 21:49, Tomas Orsava wrote:

Hi,
I have left a few notes about the text itself as comments in 
the document.


Comments about the subject matter are inlined below:

On 4/30/20 3:41 PM, Petr Viktorin wrote:



### Dist-info metadata

Each Python package **MUST** include *Package Distribution 
Metadata* conforming to [PyPA 
specifications](https://packaging.python.org/specifications/) 
(specifically, [Recording installed 
distributons](https://packaging.python.org/specifications/recording-installed-packages/)). 



This applies to libraries (e.g. `python-requests`) as well as 
tools (e.g. `ansible`).



> XXX what with splitting into subpackages? 1) dist-info 
always installed, 2) dist-info installed trough a metapackage?

> * Ideally, do the split upstream
> * Consider package split between library & tool (see poetry, 
fedpkg)

>
> e.g.
> When software is split into several subpackages, it is OK to 
only ship metadata in one built RPM.



dist-info usually corresponds to an importable module, so let's 
say that it SHOULD be in the same subpackage as the importable 
module?


But if you split that module, which submodule does the dist-info 
go to?

I'd leave it to the packager; all these cases are different.


That's why I suggested the SHOULD, because there will be 
exceptions. But I think these guidelines might be read by people 
who will not be actively aware of the relationship between 
dist-info and a Python importable module, so I would add guidance 
that these should be together if possible.


Please suggest the wording you'd like to see.
The one you have has the problem that there can be more importable 
modules in one project. It doesn't give any guidance for what to 
do if you split the project.


Of course, if you put importable module(s) in one subpackage and 
documentation in another, the dist-info should be with the module(s).



I'm trying to read this guide through the eyes of someone starting 
out with Fedora and/or Python, so I'd rather not assume people know 
these details.


How about:

    When software is split into several subpackages, it is OK to only
    ship metadata in one built RPM. If the project contains an
    importable module(s), the metadata SHOULD be included in the same
    subpackage as the (main) importable module.

(First sentence already was in the text, I included it for context.)


I added it. I put the **SHOULD** sentence near the top of the 
section to align to the organization of the document: rules first, 
explanations/examples under them.


Looks good, thank you.

All in all, really nice document. Let me know if you could use more 
help with it!


Tomas


Well, any of the XXX could use help :)
Except maybe the links; those can be dded when we convert from Markdown.



Is there some way to do reviews? If someone just replaces XXX with text, 
it's hard to notice.


Tomas



___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to 
python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/

List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org

___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org

[Bug 1846148] perl-Sereal-Decoder-4.012 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1846148



--- Comment #2 from Fedora Update System  ---
FEDORA-2020-61103921dc has been submitted as an update to Fedora 32.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-61103921dc


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

Monthly highlights from the Red Hat's Python-maint team, May 2020

[Tomas Orsava]

Hi,
we're the Python-maint team from Red Hat, and we'd like to experiment 
with sharing with you what we are working on from month to month. There 
are some things we should not disclose (such as embargoed CVEs), but the 
majority of what we do is out in public. Please let us know if you find 
this useful and whether you'd like us to continue.


So here are the highlights of what we've been working on this May, 2020:

*Fedora:*

 * Python updated to Python 3.9 in rawhide (Fedora 33)

 * ~3000 source packages rebuilt

 * ~100 reamain problematic (fail to build)

 * python3X packages renamed to python3.X in rawhide

 * Python RPM depndency generators:

 * Backported proposed upstream changes, added new test suite to Fedora CI

 * Working on handling of proposed Python extras subpackages

 * pipenv continually being rebased to new versions, currently 2020.5.28

 * Test in copr:https://copr.fedorainfracloud.org/coprs/g/python/pipenv/

 * Provided feedback and fixes upstream

 * pytest updated to 5 on rawhide (compat package with pytest 4 introduced)

 * pip updated to version 20.1, changes in Python RPM macros were
   needed to workaround problems with new PEP 610

 * https://www.python.org/dev/peps/pep-0610/

 * New RPM macros for easier packaging: %py_provides, %pytest and
   %python3_shebang_fix

 * 
%py_provides:https://src.fedoraproject.org/rpms/python-rpm-macros/pull-request/52

 * 
%python3_shebang_fixhttps://src.fedoraproject.org/rpms/python-rpm-macros/pull-request/58

 * %pytesthttps://src.fedoraproject.org/rpms/python-rpm-macros/pull-request/55

 * Improved %pypi_source macro

 * Removes tildes (`~`) from %version so that it works with
   alpha/beta/dev releases out of the box

 * https://src.fedoraproject.org/rpms/python-rpm-macros/pull-request/57

 * Python 3.8.3 updated across Fedora releases

 * pypy and pypy 3 updated to versions 7.3.1

 * provided feedback upstream for new Cython alpha release


*CPython:*

 * CPython 3.9b1 was released:
   seehttps://docs.python.org/dev/whatsnew/3.9.html

 * Fixing a CPython type reference count issue found by PySide

 * Python 3.9 is now FIPS compatible upstream.

 * Proof-of-concept of subinterpreters running in parellel with one GIL
   per interpreter: "Subinterpreters 4x faster than sequential
   execution or threads on CPU-bound
   
workload"https://mail.python.org/archives/list/python-...@python.org/thread/S5GZZCEREZLA2PEMTVFBCDM52H4JSENR/

 * Progress on subinterpreter isolation work: most free lists are now
   per-interpreter.https://bugs.python.org/issue40521

 * Progress on hiding implementation details from the C API: Py_TYPE(),
   Py_REFCNT() and Py_SIZE() can no longer be used as l-value. Use
   Py_SET_TYPE(), Py_SET_REFCNT() and Py_SET_SIZE()
   
instead.https://mail.python.org/archives/list/capi-...@python.org/thread/HYFQHLGNCRFBOMOOV2WUT46CQPXV5VQ7/

 * New --hardlink-dupes option in compileall: "If two .pyc files with
   different optimization level have the same content, use hard links
   to consolidate duplicate
   
files."https://docs.python.org/dev/library/compileall.html#cmdoption-compileall-hardlink-dupes

 * Helped to get features merged before the 3.9 feature freeze:
   removeprefix/removesuffix (PEP 616), new zoneinfo module (PEP 615).
   Fixed buildbot failures and a few reference leaks.

 * Python Steering Council Community Address with our team member
   Victor Stinner:https://www.youtube.com/watch?v=xX8fGuh4T_o

*
*
*Red Hat Enterprise Linux:*

 * Overhauling the FIPS patch for python3 in RHEL 7

 * Created an Insights rule candidate that verifies Python alternatives

 * Backporting fix for Python's CVE-2019-16056 to older RHEL 7 versions

 * For RHEL9 preparations -- see the Fedora section


*Red Hat Software Collections:*

 * Python 3.8 from RHSCL 3.5 added for s2i-python-container upstream


*Misc:*

 * Releasing a GitHub action to run Tox on
   Fedora:https://github.com/marketplace/actions/python-tox-on-fedora


All the best,
Python-maint

___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org