Re: Splitting AppStream data into Workstation/Server

On Fri, Sep 1, 2017 at 8:37 AM, Alexander Bokovoy wrote: > On pe, 01 syys 2017, Neal Gompa wrote: >> >> On Fri, Sep 1, 2017 at 7:52 AM, Marius Vollmer >> wrote: >>> >>> Neal Gompa writes: >>> > So, what about creating a

Re: Splitting AppStream data into Workstation/Server

Neal Gompa writes: > Implement your AppStream filter at the application level, rather than > messing with appstream-data package. Yes, of course. Cockpit will do the right thing even with the full appstream-data package. This is only about not having 15 MiB of useless data

Re: Splitting AppStream data into Workstation/Server

Neal Gompa writes: >> So, what about creating a dedicated appstream-data-server package that >> carries only those components that we want to see on a Server? >> >> Initially, it would contain only components of type "addon" that extend >> "cockpit.desktop", and components of

Re: CI projects in Copr

On Fri, Sep 1, 2017 at 1:41 PM, Gerd Hoffmann wrote: > Hi, > > > Right, this is cool. The problem is that the upstream repo would need > > to be configured to provide a public message that something has been > > changed > > in it (i.e. new release) so the question is how to

Re: Splitting AppStream data into Workstation/Server

On pe, 01 syys 2017, Neal Gompa wrote: On Fri, Sep 1, 2017 at 7:52 AM, Marius Vollmer wrote: Neal Gompa writes: So, what about creating a dedicated appstream-data-server package that carries only those components that we want to see on a

Re: Splitting AppStream data into Workstation/Server

On Fri, Sep 1, 2017 at 8:57 AM, Alexander Bokovoy wrote: > On pe, 01 syys 2017, Neal Gompa wrote: >> >> On Fri, Sep 1, 2017 at 8:37 AM, Alexander Bokovoy >> wrote: >>> >>> On pe, 01 syys 2017, Neal Gompa wrote: On Fri, Sep 1, 2017 at 7:52

Re: AppStream and COPR

Dne 1.9.2017 v 15:31 Neal Gompa napsal(a): > On Fri, Sep 1, 2017 at 9:12 AM, Marius Vollmer > wrote: >> Neal Gompa writes: >> >>> [...] It's already kind of second-class in Fedora because it's not >>> properly integrated into our repodata (like it's

Re: CI projects in Copr

Hi, > Right, this is cool. The problem is that the upstream repo would need > to be configured to provide a public message that something has been > changed > in it (i.e. new release) so the question is how to do this part. Ah, right, setting up a webhook needs access to the upstream repo too.

Re: are the armv7hl builders healthy?

On Fri, Sep 01, 2017 at 08:17:11AM -0400, Kaleb Keithley wrote: > > I'm trying to build ceph-12.2.0 for f28, So far the build has failed twice > on armv7hl during %install trying to install a file that was seeminlyly > successfully built. > > That's two different files. The first time it was

Re: Splitting AppStream data into Workstation/Server

On Fri, Sep 1, 2017 at 9:03 AM, Richard Hughes wrote: > On Fri, Sep 1, 2017 at 2:00 PM, Neal Gompa wrote: >> It's not just about your vision of usage, it's about how everyone else >> uses it too! :) > > Well, we could do the opposite, we could just include

Re: are the armv7hl builders healthy?

Is there any way to fix cmake or the ceph cmake rules so that they report the real useful error message, instead of throwing it away & providing a generic "cannot copy file" message with no details ? Quick and dirty: prefix all commands with something like strace -o "| grep '= -1'"

Re: AppStream and COPR (was: Splitting AppStream data into Workstation/Server)

Neal Gompa writes: > All PackageKit based software managers automatically download the > data, as the Dnf PK backend does this: > https://github.com/hughsie/PackageKit/blob/master/backends/dnf/pk-backend-dnf.c#L553 Ahh, thanks! "pkcon refresh force" indeed downloads it for

Re: Splitting AppStream data into Workstation/Server

On pe, 01 syys 2017, Neal Gompa wrote: On Fri, Sep 1, 2017 at 8:37 AM, Alexander Bokovoy wrote: On pe, 01 syys 2017, Neal Gompa wrote: On Fri, Sep 1, 2017 at 7:52 AM, Marius Vollmer wrote: Neal Gompa writes: So, what

Re: Splitting AppStream data into Workstation/Server

Marius Vollmer wrote: > Neal Gompa writes: > >>> So, what about creating a dedicated appstream-data-server package that >>> carries only those components that we want to see on a Server? >>> >>> Initially, it would contain only components of type "addon" that extend >>>

AppStream and COPR (was: Splitting AppStream data into Workstation/Server)

Neal Gompa writes: > [...] It's already kind of second-class in Fedora because it's not > properly integrated into our repodata (like it's supposed to be, and > how it is in openSUSE, Mageia, and even in COPR). > > We should be making AppStream data support first-class, not >

Re: Splitting AppStream data into Workstation/Server

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 2017-09-01 at 16:01 +0300, Marius Vollmer wrote: > Neal Gompa writes: > > > Implement your AppStream filter at the application level, rather > > than > > messing with appstream-data package. > > Yes, of course.

Re: AppStream and COPR (was: Splitting AppStream data into Workstation/Server)

On Fri, Sep 1, 2017 at 9:12 AM, Marius Vollmer wrote: > Neal Gompa writes: > >> [...] It's already kind of second-class in Fedora because it's not >> properly integrated into our repodata (like it's supposed to be, and >> how it is in openSUSE,

Re: Module Stream "Expansion"

On 31 August 2017 at 22:09, Matthew Miller wrote: > On Thu, Aug 31, 2017 at 08:11:56PM +1000, Nick Coghlan wrote: >> > I'd think the solution is simply to mark your module with "Service >> > Level: alpha" (and then we'd want some tooling where SL-alpha and >> > SL-beta

Re: Splitting AppStream data into Workstation/Server

On Fri, Sep 1, 2017 at 7:52 AM, Marius Vollmer wrote: > Neal Gompa writes: > >>> So, what about creating a dedicated appstream-data-server package that >>> carries only those components that we want to see on a Server? >>> >>> Initially, it would

are the armv7hl builders healthy?

I'm trying to build ceph-12.2.0 for f28, So far the build has failed twice on armv7hl during %install trying to install a file that was seeminlyly successfully built. That's two different files. The first time it was cephfs-journal-tool, the second time it was the one immediately after:

Re: FAILED: BuildError: package ... not in list for tag f28-pending

On Thu, 31 Aug 2017 22:14:11 +0200, Björn 'besser82' Esser wrote: > > It's been several hours since this entirely new package repo has been > > created, > > but the koji build still fails. How long does it take for koji to learn > > about this new package? > it takes as long someone from releng

Re: FAILED: BuildError: package ... not in list for tag f28-pending

On 01/09/17 17:26, Michael Schwendt wrote: On Thu, 31 Aug 2017 22:14:11 +0200, Björn 'besser82' Esser wrote: It's been several hours since this entirely new package repo has been created, but the koji build still fails. How long does it take for koji to learn about this new package? it

RFC: retiring yum

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 So I think F28/F29 would be best time for retiring YUM. Right now DNF should be already stable and provide same capabilities (or documented that something will not be supported). Hopefully infrastructure / rel-eng folks will finally add support for

Summary/Minutes from today's FESCo Meeting (2017-09-01)

https://meetbot.fedoraproject.org/fedora-meeting/2017-09-01/fesco.2017-09-01-16.02.log.html . Meeting summary --- * init process (jforbes, 16:02:16) * #1761 Update of "Fedora Release Live Cycle" and "Changes / Policy" (jforbes, 16:06:01) * LINK:

Re: Module Stream "Expansion"

On Fri, Sep 01, 2017 at 09:25:22PM +1000, Nick Coghlan wrote: > So the request is for there to be a way to indicate that a stream is > available for explicit dependencies, but *shouldn't* be taken into > account for implicit stream expansion yet. Then, once the low level > stream is stable, *then*

Re: Providing ABI/API assurances for the base runtime in Fedora.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 2017-09-01 at 09:28 -0500, Carlos O'Donell wrote: > Fedora Developers, > > I am working on a way to provide concrete ABI/API assurances for > parts of the base runtime. Note that Base Runtime is F26-only thing and in F27 it is called Host

Schedule for today's FESCo Meeting (2017-09-01)

Following is the list of topics that will be discussed in the FESCo meeting Friday at 16:00UTC in #fedora-meeting on irc.freenode.net. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowto or run: date -d '2017-09-01 16:00 UTC' Links to all issues below

Re: Schedule for today's FESCo Meeting (2017-09-01)

Also new business: #topic #1766 Is ImageMagick 7 appropriate for Fedora 27 (and even 28)? .fesco 1766 https://pagure.io/fesco/issue/1766 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to

Providing ABI/API assurances for the base runtime in Fedora.

Fedora Developers, I am working on a way to provide concrete ABI/API assurances for parts of the base runtime. I've written up some of the key ideas here: https://fedoraproject.org/wiki/BaseRuntimeInterface Any feedback would be appreciated, including bikeshed on component name prefix for

Re: RFC: retiring yum

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 2017-09-01 at 13:56 -0400, Neal Gompa wrote: > On Fri, Sep 1, 2017 at 1:01 PM, Igor Gnatenko > wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > So I think F28/F29 would be best time

Re: Splitting AppStream data into Workstation/Server

/*Igor Gnatenko*/ wrote on Fri, 01 Sep 2017 15:19:34 +0200: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 2017-09-01 at 16:01 +0300, Marius Vollmer wrote: Neal Gompa writes: Implement your AppStream filter at the application level, rather than messing with

Re: Build weirdness

On Fri, Sep 01, 2017 at 10:56:39PM +0200, Sandro Mani wrote: > Hi > > I've got another weird situation: I wanted to get pjproject building > again, rebased and added necessary patches, did the scratch build, > and all looked good [1]. So I went ahead and committed the result, > fired off the

Raising requirement for application icons in GNOME Software

Hi all, At the moment the appstream-builder requires a 48x48px application icon[1] to be included in the AppStream metadata. I'm sure it's no surprise that 48x48 padded to 64x64 and then interpolated up to 128x128 (for HiDPI screens) looks pretty bad. For F28 and higher I'm going to raise the

Build weirdness

Hi I've got another weird situation: I wanted to get pjproject building again, rebased and added necessary patches, did the scratch build, and all looked good [1]. So I went ahead and committed the result, fired off the build, but to my surprise that build failed while applying the patches

Re: RFC: retiring yum

On 2017-09-01 2:52 PM, Matthew Miller wrote: On Fri, Sep 01, 2017 at 02:38:59PM -0400, Fernando Nasser wrote: 1) Can we use existing repositories created with yum createrepo with dnf? Yes. 2) Are "groups" supported?  (E.g.: yum instalgroup xxx) Yes. Thanks Matthew.  I guess it will be just

Re: RFC: retiring yum

On Fri, 2017-09-01 at 15:00 -0500, Ian Pilcher wrote: > On 09/01/2017 02:21 PM, Igor Gnatenko wrote: > > This is true and we have plans to implement this, but problem is > > that > > we don't know how to represent data. When it is about installing > > some > > packages -- it's more or less easy to

Re: RFC: retiring yum

On Friday, 1 September 2017 21:30:44 CEST Matthew Miller wrote: > RPM specfile changelogs are often of interest to systems > administrators. Agreed. Before I update a huge number of hosts I'd like to check the changelogs for any possible trouble. This is the the main thing I miss in dnf right

Re: RFC: retiring yum

On 09/01/2017 12:01 PM, Igor Gnatenko wrote: Do you still have some critical missing functionality in DNF? And let us know reasons why would you like to keep YUM available (hopefully there are no)! AFAIK there is still no way to get dependency information out of DNF. (There may be a way to do

[Test-Announce] Fedora 27 Branched 20170901.n.1 nightly compose nominated for testing

Announcing the creation of a new nightly release validation test event for Fedora 27 Branched 20170901.n.1. 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

Re: RFC: retiring yum

On 2017-09-01 1:01 PM, Igor Gnatenko wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 So I think F28/F29 would be best time for retiring YUM. Right now DNF should be already stable and provide same capabilities (or documented that something will not be supported). Hopefully

Re: RFC: retiring yum

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 2017-09-01 at 13:30 -0500, Ian Pilcher wrote: > On 09/01/2017 12:01 PM, Igor Gnatenko wrote: > > Do you still have some critical missing functionality in DNF? And > > let > > us know reasons why would you like to keep YUM available

Re: RFC: retiring yum

Hi, /*Igor Gnatenko*/ wrote on Fri, 01 Sep 2017 19:01:49 +0200: <..> Do you still have some critical missing functionality in DNF? And let us know reasons why would you like to keep YUM available (hopefully there are no)! I've not tried 'dnf remove --duplicates' yet, but if it behaves similar

Re: [SO-NAME BUMP] Updating jsoncpp on Rawhide and fc27

Am 28.08.2017 um 22:28 schrieb Björn 'besser82' Esser: Hello folks, I'm planning to update jsoncpp on Rawhide and fc27 during the next days.  After the builds have landed, I'll take care of rebuilding all consumers against the new so name.  Since the API / ABI has no publicly consumed

Re: Urgent attention required; ImageMagick update breakage

On Mon, 2017-08-28 at 20:39 -0500, Michael Cronenworth wrote: > Rebuild status: > * All F25/F26 packages have been rebuilt against ImageMagick 6.9.9.9 > * Most of the F27+ packages have been rebuilt with the following exceptions: > - cuneiform > FTBFS since Fedora 23, last upstream release

Re: RFC: retiring yum

On Fri, Sep 01, 2017 at 02:38:59PM -0400, Fernando Nasser wrote: > 1) Can we use existing repositories created with yum createrepo with dnf? Yes. > 2) Are "groups" supported?  (E.g.: yum instalgroup xxx) Yes. -- Matthew Miller Fedora Project Leader

Re: Build weirdness

I think you've basically analyzed it correctly. The patches have been added to the ‘sources’ file (and so are pulled from the lookaside cache). This is of course wrong. The new patches are in git, but these are overwritten by the lookaside cache. The easiest thing is to simply edit the

Re: RFC: retiring yum

On Fri, 2017-09-01 at 13:30 -0500, Ian Pilcher wrote: > On 09/01/2017 12:01 PM, Igor Gnatenko wrote: > > Do you still have some critical missing functionality in DNF? And > > let > > us know reasons why would you like to keep YUM available (hopefully > > there are no)! > > AFAIK there is still no

Re: RFC: retiring yum

On Sep 1, 2017 3:31 PM, "Matthew Miller" wrote: On Fri, Sep 01, 2017 at 09:19:24PM +0200, Igor Gnatenko wrote: > > There is still one thing I've noticed we're missing: API and CLI for > > getting package changelogs[1]. This exists in yum but doesn't in dnf. > While I

Re: Urgent attention required; ImageMagick update breakage

On 09/01/2017 01:13 PM, Adam Williamson wrote: FESCo decided at today's meeting that 7 should not go to F27 (unless it can be made parallel installable and not used by anything release- blocking by default), and to go into F28 there must be a system-wide Change: The libs are definitely

Re: FAILED: BuildError: package ... not in list for tag f28-pending

On 09/01/2017 12:46 PM, Tom Hughes wrote: > On 01/09/17 17:26, Michael Schwendt wrote: >> On Thu, 31 Aug 2017 22:14:11 +0200, Björn 'besser82' Esser wrote: >> It's been several hours since this entirely new package repo has been created, but the koji build still fails. How long does

Re: RFC: retiring yum

On Fri, Sep 01, 2017 at 09:19:24PM +0200, Igor Gnatenko wrote: > > There is still one thing I've noticed we're missing: API and CLI for > > getting package changelogs[1]. This exists in yum but doesn't in dnf. > While I agree that this is missing functionality, being honest I think > we should

Re: Raising requirement for application icons in GNOME Software

At the moment the appstream-builder requires a 48x48px application icon[1] to be included in the AppStream metadata. I'm sure it's no surprise that 48x48 padded to 64x64 and then interpolated up to 128x128 (for HiDPI screens) looks pretty bad. Instead: magnify by 3x linear pixel replication (48

Re: RFC: retiring yum

On 09/01/2017 02:21 PM, Igor Gnatenko wrote: This is true and we have plans to implement this, but problem is that we don't know how to represent data. When it is about installing some packages -- it's more or less easy to show, but when upgrades / downgrades are involved it becomes way more

Re: RFC: retiring yum

On Fri, Sep 1, 2017 at 1:01 PM, Igor Gnatenko wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > So I think F28/F29 would be best time for retiring YUM. Right now DNF > should be already stable and provide same capabilities (or documented > that

Re: CI projects in Copr

Quack, On 09/01/2017 01:28 AM, Michal Novotny wrote: > But I think an off-line talk might be the best. Depends on you. I can understand you don't want this thread to end-up in flames, and yes sometimes it helps to have a live direct talk, but this also means the rest of this list is kept out. I

Re: CI projects in Copr

Hello Gerd, On Fri, Sep 1, 2017 at 11:20 AM, Gerd Hoffmann wrote: > Hi, > > > It's easier on implementation. That's the main reason. I generally > > believe that > > what's easier on implementation is better. > > It's maybe easier on the copr side, but not for the copr

Re: CI projects in Copr

Hi, > It's easier on implementation. That's the main reason. I generally > believe that  > what's easier on implementation is better. It's maybe easier on the copr side, but not for the copr users ... If you can modify the upstream project (either because you are upstream, or in case upstream

Re: CI projects in Copr

2017-09-01 11:20 GMT+02:00 Gerd Hoffmann : > So, what would be really helpful, especially for CI with the option to > build and test every upstream commit, would be support for *two* git > repos. One git repo where the spec-file and other build-related stuff > lives (distgit

Re: CI projects in Copr

Hey Marc, On Fri, Sep 1, 2017 at 8:55 AM, Marc Dequènes (Duck) wrote: > Quack, > > On 09/01/2017 01:28 AM, Michal Novotny wrote: > > > But I think an off-line talk might be the best. Depends on you. > > I can understand you don't want this thread to end-up in flames, and yes >

Splitting AppStream data into Workstation/Server

Hi, I hope that soon the first Cockpit add-on appears in the Fedora repositories. Cockpit can find such add-ons via their AppStream metainfo data, similar to how GNOME Software finds applications to install for a desktop environment. Thus, we would need to install the appstream-data package

Re: Splitting AppStream data into Workstation/Server

On Fri, Sep 1, 2017 at 6:37 AM, Marius Vollmer wrote: > Hi, > > I hope that soon the first Cockpit add-on appears in the Fedora > repositories. Cockpit can find such add-ons via their AppStream > metainfo data, similar to how GNOME Software finds applications to >

[Bug 1487449] perl-Email-Stuffer-0.016 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1487449 Petr Pisar changed: What|Removed |Added Status|ASSIGNED|CLOSED

[Bug 1487536] New: Upgrade perl-Config-Model to 2.108

https://bugzilla.redhat.com/show_bug.cgi?id=1487536 Bug ID: 1487536 Summary: Upgrade perl-Config-Model to 2.108 Product: Fedora Version: rawhide Component: perl-Config-Model Keywords: FutureFeature Assignee:

ppisar pushed to perl-CPAN-Common-Index (master). "Rebuild to overcome race with F27 mass rebuild side tag"

From ab235aa1de9d5d614e77828c43f3eeb6acbe93f6 Mon Sep 17 00:00:00 2001 From: Petr Písař Date: Sep 01 2017 08:26:25 + Subject: Rebuild to overcome race with F27 mass rebuild side tag --- diff --git a/perl-CPAN-Common-Index.spec b/perl-CPAN-Common-Index.spec index

ppisar pushed to perl-CPAN-Common-Index (f27). "Rebuild to overcome race with F27 mass rebuild side tag"

From ab235aa1de9d5d614e77828c43f3eeb6acbe93f6 Mon Sep 17 00:00:00 2001 From: Petr Písař Date: Sep 01 2017 08:26:25 + Subject: Rebuild to overcome race with F27 mass rebuild side tag --- diff --git a/perl-CPAN-Common-Index.spec b/perl-CPAN-Common-Index.spec index

[Bug 1475581] perl-CPAN-Common-Index-0.010 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1475581 Petr Pisar changed: What|Removed |Added Status|CLOSED |MODIFIED Fixed In

[Bug 1475581] perl-CPAN-Common-Index-0.010 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1475581 --- Comment #2 from Fedora Update System --- perl-CPAN-Common-Index-0.010-2.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-12081b7db9 -- You are receiving

[Bug 1455726] perl-HTML-TableExtract-2.15 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1455726 Petr Pisar changed: What|Removed |Added Status|NEW |ASSIGNED

ppisar uploaded HTML-TableExtract-2.15.tar.gz for perl-HTML-TableExtract

54fe445bd4bfc55d244ba6ba9888ea556b1a93b384be1f935ae3e93dc6d9e07167fa0fa07365d7fbc89e0a4924a40ea10fdc63d2ebf55f8d5f0d2ed90848a607 HTML-TableExtract-2.15.tar.gz

[Bug 1455726] perl-HTML-TableExtract-2.15 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1455726 Petr Pisar changed: What|Removed |Added Status|ASSIGNED|NEW External Bug

[Bug 1487628] perl-Verilog-Perl-3.440 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1487628 Petr Pisar changed: What|Removed |Added Status|ASSIGNED|MODIFIED Fixed In

ppisar pushed to perl-Verilog-Perl (f27). "3.440 bump"

From 255b49962c13b65e2b1a1e6999afa8b25435205c Mon Sep 17 00:00:00 2001 From: Petr Písař Date: Sep 01 2017 13:12:04 + Subject: 3.440 bump --- diff --git a/.gitignore b/.gitignore index 836e8d4..b278065 100644 --- a/.gitignore +++ b/.gitignore @@ -15,3 +15,4 @@

[Bug 1462514] Requires for bugzilla package missing perl(ExtUtils:: MakeMaker)

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

[Bug 1485626] perl-Imager-1.006 is available

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

[Bug 1487628] New: perl-Verilog-Perl-3.440 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1487628 Bug ID: 1487628 Summary: perl-Verilog-Perl-3.440 is available Product: Fedora Version: rawhide Component: perl-Verilog-Perl Keywords: FutureFeature, Triaged Assignee:

ppisar pushed to perl-Verilog-Perl (master). "3.440 bump"

From 255b49962c13b65e2b1a1e6999afa8b25435205c Mon Sep 17 00:00:00 2001 From: Petr Písař Date: Sep 01 2017 13:12:04 + Subject: 3.440 bump --- diff --git a/.gitignore b/.gitignore index 836e8d4..b278065 100644 --- a/.gitignore +++ b/.gitignore @@ -15,3 +15,4 @@

[Bug 1462514] Requires for bugzilla package missing perl(ExtUtils:: MakeMaker)

https://bugzilla.redhat.com/show_bug.cgi?id=1462514 --- Comment #3 from Fedora Update System --- bugzilla-5.0.3-5.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See

ppisar uploaded Verilog-Perl-3.440.tar.gz for perl-Verilog-Perl

04ff1ed5fffe428864de063025be355b2dda082c67e8f64af31ce5d7c513f1f73c41047e1a172d3171c38624362583e01020782f61fb2e13304dd0520ed9e7ce Verilog-Perl-3.440.tar.gz

[Bug 1487628] perl-Verilog-Perl-3.440 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1487628 --- Comment #2 from Fedora Update System --- perl-Verilog-Perl-3.440-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-b681e3a2fd -- You are receiving this

spot uploaded HTML-Tree-5.07.tar.gz for perl-HTML-Tree

a1faaf547d7db323388d5f6b289ab96887de5a80add55aefd380e4b540948514550a86785bdccf0776dfff38085b6bd3e98228f96231264217adcfc2f132c5de HTML-Tree-5.07.tar.gz

[Bug 1487192] perl-HTML-Tree-5.07 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1487192 --- Comment #4 from Fedora Update System --- perl-HTML-Tree-5.07-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-5174b10318 -- You are receiving this mail

spot pushed to perl-Log-Dispatch (f27). "2.66"

From b698a8c6797c1a6543b1661b3c7b58d126fbe938 Mon Sep 17 00:00:00 2001 From: Tom Callaway Date: Aug 29 2017 14:08:17 + Subject: 2.66 --- diff --git a/.gitignore b/.gitignore index 642363c..ae14a4e 100644 --- a/.gitignore +++ b/.gitignore @@ -4,3 +4,4 @@

spot pushed to perl-HTML-Tree (master). "5.07"

From 8264a5fe92c6ee3d84c18d8cf961de53ee590b14 Mon Sep 17 00:00:00 2001 From: Tom Callaway Date: Sep 01 2017 14:21:54 + Subject: 5.07 --- diff --git a/.gitignore b/.gitignore index a776f44..4fa7b0b 100644 --- a/.gitignore +++ b/.gitignore @@ -5,3 +5,4 @@

spot pushed to perl-HTML-Tree (f27). "5.07"

From 8264a5fe92c6ee3d84c18d8cf961de53ee590b14 Mon Sep 17 00:00:00 2001 From: Tom Callaway Date: Sep 01 2017 14:21:54 + Subject: 5.07 --- diff --git a/.gitignore b/.gitignore index a776f44..4fa7b0b 100644 --- a/.gitignore +++ b/.gitignore @@ -5,3 +5,4 @@

[Bug 1487192] perl-HTML-Tree-5.07 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1487192 --- Comment #3 from Upstream Release Monitoring --- spot's perl-HTML-Tree-5.07-1.fc27 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=965061 -- You are receiving this mail

RE: Need help ?

Thanks Matthew, I had not seen that. Perfect Labor day weekend reading ! From: Matthew Miller Sent: Friday, September 1, 2017 5:07 PM To: Fedora QA Development Subject: Re: Need help ? On Fri, Sep 01, 2017 at 08:57:54PM -, Ellen OSullivan wrote: > I'm a newbie, would like to help out with

RE: Need help ?

>> It is worth noting that to obtain a @fedoraproject.org email alias, you need >> to be what is called “CLA+1”. I need to become a “CLA+1” - I am not in a group. Should I ask in the Fedora-QA list? thanks From: Matthew Miller Sent: Friday, September 1, 2017 5:07 PM To: Fedora QA

Need help ?

I'm a newbie, would like to help out with something. I'm dev/qa automation at work but fairly new to Linux. Willing to clean the floors, make the coffee :-) ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to

Re: Need help ?

On Fri, Sep 01, 2017 at 05:23:42PM -0400, Ellen OSullivan wrote: > >> It is worth noting that to obtain a @fedoraproject.org email alias, you > >> need to be what is called “CLA+1”. > I need to become a “CLA+1” - I am not in a group. Should I ask in > the Fedora-QA list? Yeah, I think someone

Re: Need help ?

On Fri, Sep 01, 2017 at 08:57:54PM -, Ellen OSullivan wrote: > I'm a newbie, would like to help out with something. I'm dev/qa > automation at work but fairly new to Linux. Willing to clean the > floors, make the coffee :-) Hi Ellen, and welcome! I think we need qa automation expertise even

Question about working with upstream vs patches

Howdy, I'd like to help work toward the Fedora move toward Python 3. There is lots of good information out there about much of the process, but I did have a few questions about how you like to do things, and the proper work-flow. If I start working on a particular package, should I mention as

[Bug 1487801] New: perl-Date-Manip-6.60 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1487801 Bug ID: 1487801 Summary: perl-Date-Manip-6.60 is available Product: Fedora Version: rawhide Component: perl-Date-Manip Keywords: FutureFeature, Triaged Assignee:

[Bug 1487803] New: perl-Locale-Codes-3.54 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1487803 Bug ID: 1487803 Summary: perl-Locale-Codes-3.54 is available Product: Fedora Version: rawhide Component: perl-Locale-Codes Keywords: FutureFeature, Triaged Assignee:

[Bug 1486717] abi-compliance-checker-2.2 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1486717 --- Comment #6 from Fedora Update System --- abi-dumper-1.1-1.el6 abi-tracker-1.11-1.el6 has been submitted as an update to Fedora EPEL 6. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-eb0a63456d -- You

[Bug 1486717] abi-compliance-checker-2.2 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1486717 --- Comment #4 from Fedora Update System --- abi-compliance-checker-2.2-1.fc27 abi-dumper-1.1-1.fc27 abi-tracker-1.11-1.fc27 has been submitted as an update to Fedora 27.

[Bug 1486717] abi-compliance-checker-2.2 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1486717 --- Comment #7 from Fedora Update System --- abi-compliance-checker-2.2-1.fc26 abi-dumper-1.1-1.fc26 abi-tracker-1.11-1.fc26 has been submitted as an update to Fedora 26.

[Bug 1486717] abi-compliance-checker-2.2 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1486717 --- Comment #5 from Fedora Update System --- abi-compliance-checker-2.2-1.el7 abi-dumper-1.1-1.el7 abi-tracker-1.11-1.el7 has been submitted as an update to Fedora EPEL 7.

[Bug 1486717] abi-compliance-checker-2.2 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1486717 --- Comment #8 from Fedora Update System --- abi-compliance-checker-2.2-1.fc25 abi-dumper-1.1-1.fc25 abi-tracker-1.11-1.fc25 has been submitted as an update to Fedora 25.

[Bug 1487808] New: perl-Net-HTTP-6.17 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1487808 Bug ID: 1487808 Summary: perl-Net-HTTP-6.17 is available Product: Fedora Version: rawhide Component: perl-Net-HTTP Keywords: FutureFeature, Triaged Assignee:

[Bug 1487810] New: perl-Shell-Config-Generate-0.29 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1487810 Bug ID: 1487810 Summary: perl-Shell-Config-Generate-0.29 is available Product: Fedora Version: rawhide Component: perl-Shell-Config-Generate Keywords: FutureFeature, Triaged

  1   2   >