Re: What to I have to do....

Dne 8.12.2017 v 18:33 Adam Williamson napsal(a): > How long will it be before you can get the modernization/cleanup > finished? You're going to be sitting there waiting for 50 people to > respond to pull requests, A week? And only then do the change directly? Sometimes the maintainers have a

Fedora Rawhide-20171210.n.2 compose check report

Missing expected images: Server boot x86_64 Server dvd i386 Workstation live i386 Server dvd x86_64 Server boot i386 Kde live i386 Failed openQA tests: 49/106 (x86_64), 1/2 (arm) New failures (same test did not fail in Rawhide-20171204.n.0): ID: 179815 Test: x86_64 KDE-live-iso

[Test-Announce] Fedora 28 Rawhide 20171210.n.2 nightly compose nominated for testing

Announcing the creation of a new nightly release validation test event for Fedora 28 Rawhide 20171210.n.2. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki

Current state of Rawhide

I'm trying to get an install of Rawhide going, but not having too much luck. I tried installing from Fedora-Rawhide-20171127.n.0 which appears to be the "Last known good" from [1]. The install succeeds, but it boots to a blank screen. The OpenQA tests results seem to indicate the same

licensing change: col changed from GPLv2 to MIT with version 0.13.0.5

It appears with version 0.13.0.5 colm switch from a GPLv2 to MIT license. https://src.fedoraproject.org/rpms/colm/c/ec0ba86370fa20f30369656beab3b b04af97e7bd?branch=master JT ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send

[Bug 1524078] perl-App-cpm-0.955 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1524078 Upstream Release Monitoring changed: What|Removed |Added

[SO-NAME BUMP] libjson-c.so.3 comes to Rawhide

Hello folks, I'll update json-c to v0.13 for Rawhide. This will bump libjson-c so- name from 2 to 3 and will remove some deprecated stuff from its API. I'll bump and rebuild all affected packages in the same run and add patches for the new API, if needed. As soon as the first set of builds is

[Bug 1485919] Do not provide "perl(setup)"

https://bugzilla.redhat.com/show_bug.cgi?id=1485919 Fedora Update System changed: What|Removed |Added Status|ON_QA

Re: Retiring openerp7 and openerp-client

On Sunday, 10 December 2017 at 21:11, Alec Leamas wrote: > As heading says, I'm retiring these openerp packages. They need > more love than I'm able to give them since I nowadays don't use > them anymore. If it's just that you don't have time to take care of them, you should simply orphan them.

[EPEL-devel] Re: missing orphaned packages reports?

On 12/05/2017 10:57 AM, Mátyás Selmeci wrote: > Hi, > > I haven't seen new 'orphaned packages' emails since July. Is that on > purpose? Tyll has done those in the past, and they are somewhat tied to the Fedora release cycle. They should fire up again in the f28 cycle hopefully. kevin

[EPEL-devel] Re: Python 3.6 in EPEL

On 12/05/2017 01:36 AM, Aurelien Bompard wrote: > Hey folks! > > I have a need for Python 3.5+ in EPEL (newest versions of Mailman 3 need > it), so I tried rebuilding it by taking advantage of our %python3_other_* > macros. There's a lot of packages that need to be built in the right order > to

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

The following Fedora EPEL 7 Security updates need testing: Age URL 1007 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-1087 dokuwiki-0-0.24.20140929c.el7 770 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-dac7ed832f mcollective-2.8.4-1.el7 352

Retiring openerp7 and openerp-client

Hi all, As heading says, I'm retiring these openerp packages. They need more love than I'm able to give them since I nowadays don't use them anymore. The difference between being employed and running a one person company that is... Cheers! --alec ___

Re: Self introduction

On Sun, Dec 10, 2017 at 11:50:14AM +0100, Jan De Luyck wrote:> Hello people, > I've recently submitted a package to be included with Fedora, and since > I'm new on the packager block, I'm throwing in this intro ;) (als also > recommended/required by the guidelines) Hello and welcome! --

Re: Wiki search?

> is it just me or there is no way to search the new wiki? Could we pretty > please have easily accessible search bar, or have a search button under the > obvious "Navigation" drop down? Anything would do the trick really... Not ideal, but you can browse to

Re: Wiki search?

On 12/10/2017 02:21 PM, Radka Janekova wrote: > Hi, > > is it just me or there is no way to search the new wiki? Could we pretty > please have easily accessible search bar, or have a search button under > the obvious "Navigation" drop down? Anything would do the trick really... > Should be

Re: gdb: No symbol table info available

On Sun, 2017-12-10 at 14:10 +0100, Jan Kratochvil wrote: > the debuginfo-install command installs only *-debuginfo and not the > *-debugsource counterpart which is then missing for GDB.  That is now > a DNF bug I guess. It is indeed: https://bugzilla.redhat.com/show_bug.cgi?id=1494628 There is a

Wiki search?

Hi, is it just me or there is no way to search the new wiki? Could we pretty please have easily accessible search bar, or have a search button under the obvious "Navigation" drop down? Anything would do the trick really... Radka -- *Radka Janeková* .NET & OpenShift

Re: gdb: No symbol table info available

On Sun, 10 Dec 2017 13:43:25 +0100, Richard Shaw wrote: > I pretty much did the same thing with valgrind but the output of your > script is much more concise and easier to read. Fedora GDB should print the dnf debuginfo-install command. When it does not? It uses a similar script logic

Re: gdb: No symbol table info available

On Sat, Dec 9, 2017 at 5:49 PM, Ian Kent wrote: > eu-unstrip -n --core coredump |\ > gawk '{TMP=$2; $1=$2=""; print "/usr/lib/debug/.build-id/" > substr(TMP,0,2) "/" substr(TMP,3,38) $0}' > > Using the output from above dnf can be used to work out what's missing > with

Re: gdb: No symbol table info available

On Sat, Dec 9, 2017 at 5:49 PM, Ian Kent wrote: > On 10/12/17 02:13, Richard Shaw wrote: > > I'm working on a segfault in the latest version of hedgewars and I can > reproduce the crash easy enough and I have installed both the debuginfo for > hedgewars and all the packages gdb

Re: gdb: No symbol table info available

On Sat, Dec 9, 2017 at 2:11 PM, John Reiser wrote: > I'm working on a segfault in the latest version of hedgewars and I can >> reproduce the crash easy enough ... >> > > Filing a bugzilla report and including a reproducible test case > enables others to help you.

[Bug 1524159] New: perl-Test2-Suite-0.000096 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1524159 Bug ID: 1524159 Summary: perl-Test2-Suite-0.96 is available Product: Fedora Version: rawhide Component: perl-Test2-Suite Keywords: FutureFeature, Triaged Assignee:

[Bug 1524152] New: perl-Dist-Zilla-Plugin-Git-2.043 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1524152 Bug ID: 1524152 Summary: perl-Dist-Zilla-Plugin-Git-2.043 is available Product: Fedora Version: rawhide Component: perl-Dist-Zilla-Plugin-Git Keywords: FutureFeature, Triaged

Re: Removing old cruft, e.g. Provides: systemd-units (was Re: What to I have to do....)

On Sun, Dec 10, 2017 at 4:28 AM, Igor Gnatenko < ignatenkobr...@fedoraproject.org> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > After reading all responses in thread which is mentioned in subject I > think we > need to develop some policies / procedures how to deal with old

Re: What to I have to do....

On 07 Dec 2017, at 5:31 PM, Steve Dickson wrote: > Where committed to the master branch and not to any other > branch make the maintenance of those branches a pain > because I can no longer cherry-pick between branches. > I have to make multiple commits to multiple branches >

Self introduction

Hello people, I've recently submitted a package to be included with Fedora, and since I'm new on the packager block, I'm throwing in this intro ;) (als also recommended/required by the guidelines) The package I've sent up is NotepadQQ, a 'clone' of a well-known editor for Windows. I'm working

Removing old cruft, e.g. Provides: systemd-units (was Re: What to I have to do....)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 After reading all responses in thread which is mentioned in subject I think we need to develop some policies / procedures how to deal with old cruft, for example: - - Requires: systemd-units - - Requires: /bin/mktemp Former has changed to systemd

Re: What to I have to do....

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 2017-12-08 at 08:40 -0500, Steve Dickson wrote: > Hey, > > On 12/07/2017 02:31 PM, Florian Weimer wrote: > > On 12/07/2017 04:31 PM, Steve Dickson wrote: > > > Where committed to the master branch and not to any other > > > branch make the

Re: What to I have to do....

On Sat, Dec 09, 2017 at 09:10:13PM +, Philip Kovacs wrote: > It's just simple human courtesy. A good analogy is saying "Hello" when you meet somebody on the street. You live in a village and it's unthinkable not do it. Then you move to a small town and everybody still does, except when it's

Re: What to I have to do....

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, 2017-12-07 at 10:31 -0500, Steve Dickson wrote: > Hello, > > What do I have to do to stop random people > from making random changes to packages I maintain? > > How do people get this type of permission? > > Case in point; > > commit