[Bug 1582801] New: perl-List-SomeUtils-XS-0.57 is available

[bugzilla]

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

Bug ID: 1582801
   Summary: perl-List-SomeUtils-XS-0.57 is available
   Product: Fedora
   Version: rawhide
 Component: perl-List-SomeUtils-XS
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com,
perl-devel@lists.fedoraproject.org



Latest upstream release: 0.57
Current version/release in rawhide: 0.56-2.fc28
URL: http://search.cpan.org/dist/List-SomeUtils-XS/

Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/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/10251/

-- 
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/OJ2GYQ2DH57PQ7DS4KKW4ULHZV7PSDAI/

Re: [fesco] Updated FTBFS package policy

[Till Maas]

Hi,

On Sat, May 26, 2018 at 04:27:15PM +0100, Sérgio Basto wrote:
> On Fri, 2018-05-25 at 15:46 +, Zbigniew Jędrzejewski-Szmek wrote:
> > Fedora package maintainers,
> > 
> > FESCo approved an updated policy for packages which fail to build
> > from
> > source during mass rebuilds (FTBFS) [1].
> 
> Please list all candidates packages to be retired , last time Till
> check was about 2000 IIRC 

There is no final list yet. I am currently rebuilding several packages
to ensure that there is a bug report for each package. The most accurate
list can be found here:
https://bugzilla.redhat.com/showdependencytree.cgi?id=1555378_resolved=1

During the F28 rebuild, the process failed to trigger a rebuild for a
lot of packages. I rebuilt a lot of them a while ago but I missed some,
too (I guess all packages that were rebuilt after the F26 mass rebuild
but not for F28). I am rebuilding them now, too. Also I will rebuild
packages for which a bug report is missing or lacks the log files.

Kind regards
Till
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/EBFTYI5HVHB56B3TLUUYIJROHN32JM53/

Re: scratch build of python-kivy fails on rawhide

[Sergio]

+ Exit 1, 
Child return code was: 1

Sent from my AndroidEm 26/05/2018 5:24 da tarde, Martin Gansser 
 escreveu:
>
> when trying to build python-kivy on rawhide it fails: 
>
> koji build --scratch rawhide ../SRPMS/python-kivy-1.10.0-1.fc28.src.rpm 
>
> https://koji.fedoraproject.org/koji/getfile?taskID=27203394=DEFAULT=build.log=-4000
>  
>
> have somebody a idea ?
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/FR546VFXFYXCXNTD3C2RVCXAIMJ7PQS2/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/LVJ3YP5J7O5W6T4OK5KBGQE4P6UD5DVB/

scratch build of python-kivy fails on rawhide

[Martin Gansser]

when trying to build python-kivy on rawhide it fails:

koji build --scratch rawhide ../SRPMS/python-kivy-1.10.0-1.fc28.src.rpm

https://koji.fedoraproject.org/koji/getfile?taskID=27203394=DEFAULT=build.log=-4000

have somebody a idea ?
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/FR546VFXFYXCXNTD3C2RVCXAIMJ7PQS2/

scratch build of python-kivy fails on rawhide

[Martin Gansser]

when trying to build python-kivy on rawhide it fails:

koji build --scratch rawhide ../SRPMS/python-kivy-1.10.0-1.fc28.src.rpm

https://koji.fedoraproject.org/koji/getfile?taskID=27203394=DEFAULT=build.log=-4000

have somebody a idea ?
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/BHSPFZALNYGCRKQ522VVZ3DK2TGRIKNS/

Re: [fesco] Updated FTBFS package policy

[Sérgio Basto]

On Fri, 2018-05-25 at 15:46 +, Zbigniew Jędrzejewski-Szmek wrote:
> Fedora package maintainers,
> 
> FESCo approved an updated policy for packages which fail to build
> from
> source during mass rebuilds (FTBFS) [1].

Please list all candidates packages to be retired , last time Till
check was about 2000 IIRC 


> The updated policy is still at https://fedoraproject.org/wiki/Fails_t
> o_build_from_source.
> 
> Highlights:
> 
> - packages which FTBFS are subject to orphaning if there is no
>   maintainer acknowledgement within 8 weeks
> 
> - packages which FTBFS in two consecutive mass rebuilds will be
>   retired soon after the second mass rebuild
> 
> The implementation of this policy hinges on improving the releng
> scripts used to create and manage FTBFS bugs. There is approximately
> two months until the next use of those scripts, so I'm hopeful we'll
> get them working.
> 
> If your package wasn't successfully built for F28, please fix that!
> 
> [1] https://pagure.io/fesco/issue/1890
> [2] https://pagure.io/fesco/issue/1877#comment-509161
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelin
> es
> List Archives: https://lists.fedoraproject.org/archives/list/devel@li
> sts.fedoraproject.org/message/P3KFTJMDNO42POS5N3Z4UXDNPFGAQH73/
-- 
Sérgio M. B.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/XGSZ4DCFB7E5DPZUQUJU5WSXKI432CL3/

Re: Valid use case for modularity or not?

[Fabio Valentini]

On Sat, May 26, 2018 at 3:44 PM Neal Gompa  wrote:

> On Sat, May 26, 2018 at 9:35 AM Fabio Valentini 
> wrote:

> > Hi all,

> > I think I finally found a scenario where building some of my (and
> others') packages as modules would be beneficial.

> > The situation is:

> > - The syncthing package has a lot of golang dependencies.
> > - Some of them are too old in fedora, even in fedora rawhide, and some
of
> them have not been touched in years.
> > - However, some other packages may depend on those older versions, or
the
> packagers don't have time to check for compatibility.

> > The idea for a solution I came up with:

> > - Build syncthing as a module.
> > - Add "syncthing" branches to all incompatible dependencies (I guess I
> have to request commit/admin access to do that for packages I don't own
> yet?).
> > - Update those branches to use the exact same commit as the vendored
> sources in upstream syncthing.
> > - Use those modules as dependencies for the syncthing module.

> > Is that a valid, feasible use case of modularity?


> You can kind of pigeonhole it into that, but I think you might be better
> served by vendoring things you can't use from Fedora packages and going
> from there.

> The problem is that you're touching other people's packages and hoping
they
> don't make those branches go away. And at the end of it, the output would
> be a single package that lives outside of the normal repo metadata and
only
> modularity-enabled clients would be able to install it.

> The excludes most of the package managers that people can use in Fedora
> right now.

> It might make sense if you could describe which dist-git commit to use in
> the module definition, regardless of what's actually released in the main
> repos, and it would just build from those until you upgrade it. That would
> avoid the need for branches in all the golang packages you need for
> syncthing.

I don't think that would be the case.
An upstream commit that's newer than anything that has ever been packaged
before for a fedora branch is never available, not even if I could target
other dist-git commits. That's why I thought of modularity.



> --
> 真実はいつも一つ！/ Always, there's only one truth!
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/DABQYU6UORCGF7TO5EQFKX5KGS457QZX/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/HHZPNOCZNZVEY4WFFCUG76662XJWU73O/

Re: herbstluftwm

[Silvia Sánchez]

Hi,

Right now, no because I'm in the process of moving to a new laptop.
Usually yes, I use it.
Thanks Till for offering to sponsor me.  I'll do my homework for this now
:3  Thank you!
About my FAS, it's lailah just because Fedora didn't allow me to have a
normal name with uppercase in the beginning.  Otherwise, it would be
"Lailah".  That was my intention and that's why I write it that way in my
emails. Maybe I should just put a link instead.

Kind regards,
Silvia
FAS: Lailah




On 26 May 2018 at 13:29, Till Maas  wrote:

> Hi Silvia,
>
> just a short follow up, are you using herbstluftwm? Usually it makes sense
> to package what you use to be familiar with the package. Also it would be
> great if you create pull requests with your proposed changes to
> herbstluftwm.
>
> Kind regards
> Till
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.
> fedoraproject.org/message/T6BGY3O4CFH355KUVDW44MJFJCVNE22D/
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/B6ZMD2IYAEQIBTPWRQGWXJ7ZDAKTKUDB/

Re: Updates to mathematical software

[Rex Dieter]

Jerry James wrote:

> Hello everyone.  Months ago, I started working on updates to a couple of
> our mathematical packages. 
...
> I believe that I have finally reached
> a point of closure, where I can update the whole pile and have everything
> still work afterwards.

Thanks for your heroic efforts, much appreciated!

-- Rex
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/Y3R5PKQU63DIDNC3HVN757RZLD4TU6YZ/

Re: Valid use case for modularity or not?

[Neal Gompa]

On Sat, May 26, 2018 at 9:35 AM Fabio Valentini 
wrote:

> Hi all,

> I think I finally found a scenario where building some of my (and
others') packages as modules would be beneficial.

> The situation is:

> - The syncthing package has a lot of golang dependencies.
> - Some of them are too old in fedora, even in fedora rawhide, and some of
them have not been touched in years.
> - However, some other packages may depend on those older versions, or the
packagers don't have time to check for compatibility.

> The idea for a solution I came up with:

> - Build syncthing as a module.
> - Add "syncthing" branches to all incompatible dependencies (I guess I
have to request commit/admin access to do that for packages I don't own
yet?).
> - Update those branches to use the exact same commit as the vendored
sources in upstream syncthing.
> - Use those modules as dependencies for the syncthing module.

> Is that a valid, feasible use case of modularity?


You can kind of pigeonhole it into that, but I think you might be better
served by vendoring things you can't use from Fedora packages and going
from there.

The problem is that you're touching other people's packages and hoping they
don't make those branches go away. And at the end of it, the output would
be a single package that lives outside of the normal repo metadata and only
modularity-enabled clients would be able to install it.

The excludes most of the package managers that people can use in Fedora
right now.

It might make sense if you could describe which dist-git commit to use in
the module definition, regardless of what's actually released in the main
repos, and it would just build from those until you upgrade it. That would
avoid the need for branches in all the golang packages you need for
syncthing.



--
真実はいつも一つ！/ Always, there's only one truth!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/DABQYU6UORCGF7TO5EQFKX5KGS457QZX/

Valid use case for modularity or not?

[Fabio Valentini]

Hi all,

I think I finally found a scenario where building some of my (and others')
packages as modules would be beneficial.

The situation is:

- The syncthing package has a lot of golang dependencies.
- Some of them are too old in fedora, even in fedora rawhide, and some of
them have not been touched in years.
- However, some other packages may depend on those older versions, or the
packagers don't have time to check for compatibility.

The idea for a solution I came up with:

- Build syncthing as a module.
- Add "syncthing" branches to all incompatible dependencies (I guess I have
to request commit/admin access to do that for packages I don't own yet?).
- Update those branches to use the exact same commit as the vendored
sources in upstream syncthing.
- Use those modules as dependencies for the syncthing module.

Is that a valid, feasible use case of modularity?

Fabio
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/64XTRYMFLBSMHDXE4FW7ANEYYQFQGIY6/

Re: herbstluftwm

[Till Maas]

Hi Silvia,

just a short follow up, are you using herbstluftwm? Usually it makes sense to 
package what you use to be familiar with the package. Also it would be great if 
you create pull requests with your proposed changes to herbstluftwm.

Kind regards
Till
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/T6BGY3O4CFH355KUVDW44MJFJCVNE22D/

Re: Cfitsio soname bump

[Christian Dersch]

OK, most Rawhide rebuilds are done, so far we have two FTBFS:

On 05/25/2018 12:41 PM, Sergio Pascual wrote:
>
> bes-0:3.17.4-7.fc29.src
FTBFS, seems to be unrelated to the cfitsio update. Filed bug
https://bugzilla.redhat.com/show_bug.cgi?id=1582724

> siril-0:0.9.8.3-3.fc29.src
FTBFS, my package, currently investigating. Seems to be unrelated to
cfitsio too.

Result still unknown for package root, that build will take some while.

Greetings,
Christian
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/PW5YOO4JGY7NSTEARGPG7JAFY6H3O3DI/

[Bug 1582164] perl-Data-Types-0.13 is available

[bugzilla]

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

Upstream Release Monitoring  
changed:

   What|Removed |Added

Summary|perl-Data-Types-0.12 is |perl-Data-Types-0.13 is
   |available   |available



--- Comment #2 from Upstream Release Monitoring 
 ---
Latest upstream release: 0.13
Current version/release in rawhide: 0.09-19.fc28
URL: http://search.cpan.org/dist/Data-Types/

Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/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/2778/

-- 
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/2YAVJIYDHTJ5NEE4F6N7OENG4B73GNHM/

Re: herbstluftwm

[Till Maas]

Am 26. Mai 2018 10:54:37 MESZ schrieb Alexander Ploumistos 
:
>Hi Silvia,
>
>On Sat, May 26, 2018 at 10:07 AM Silvia Sánchez 
>wrote:
>> Hi,
>
>> Mastaiza, would you be so kind to sponsor me?  I'll be glad to
>maintain
>your package, I like it and it's a shame it's going to be orphaned.
>
>herbstluftwm used to be maintained by Christopher Meng (cicku).
>Mastaiza is not one of our sponsors, nor is he a member of the packager
>group, so he can not sponsor you.
>The wiki page that Michael Cronenworth mentioned contains everything
>you
>need to know, as well as an overwhelming number of links to other wiki
>pages, with even more information relevant to becoming a packager, e.g.
>http://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group
>
>While you're looking for a sponsor it would be a good idea to update
>herbstluftwm to v0.7 (in COPR, or whatever works for you), bring its
>spec
>file up to speed with the latest guidelines and conduct a few informal
>package reviews.
>
>> Kind regards,
>> Silvia
>> FAS:  Lailah
>
>One last little thing, your FAS name is spelled "lailah", with a
>lowercase
>l. Not that people won't be able to find you, just saying.

Hi Silvia,
 
I will sponsor you if you do what Alexander suggested and do a few preliminary 
reviews.

Kind regards
Till
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/GBOD7P53KHBC5YHB2EW5AGLTVWWNMFDU/

Re: Cfitsio soname bump

[Sergio Pascual]

Hi

2018-05-26 10:12 GMT+02:00 Christian Dersch :

>
> @Sergio: For F28 we have to coordinate somehow.


Yes, when I saw how many packages depend on cfitsio, I thought, "this is
going to be difficult in F28, but in rawhide it will be easier"



> I'm unhappy with the
> soname bump (and the way upstream handles security fixes), they bump for
> almost every new release nowadays…
>
>
In the past, I have exchanged some lengthy mails with upstream explaining
when they should change the soname. They didn't have a soname then.
In seems that I didn't explain myself very well.



> Greetings,
> Christian
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.
> fedoraproject.org/message/YDAYVECLC33VIE4VABS57EA6UMOSYD35/
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/YDDXQWDEVD5IKF5CVLSNTX46MVB5AOUW/

Re: Cfitsio soname bump

[Sergio Pascual]

Sorry, I tried to follow the policy as I remembered it. As a packager with
limited time
to work in Fedora, I tend to update packages. It's difficut for me to be up
to date with
the all the policy changes, the guidelines changes and the packaging
changes.

If Fedora wants this kind of policy to be effective, it should automate the
checks. Like, I don't know,
people is doing this days in github, with pull requests, automated sanity
checks of the RPMS, bots checking the
dependecies of your packages and sending emails to the packger owners, etc




2018-05-25 17:55 GMT+02:00 Adam Williamson :

> On Fri, 2018-05-25 at 12:41 +0200, Sergio Pascual wrote:
> > Hello, I'm going to build new cfitsio 3.450 in Rawhide.  This involves a
> > soname bump. Notice that I plan to do the same in F28 (with a buildroot
> > override, etc) as cfitsio has security issues
> > https://bugzilla.redhat.com/show_bug.cgi?id=1570484
>
> Thanks for the heads-up, but this is still not in line with the policy:
>
> "When a proposed update contains an ABI or API change: notify a week in
> advance both fedora-devel and maintainers directly (using the
> packagename-owner@ alias) whose packages depend on yours to rebuild or
> offer to do these rebuilds for them."
>
> Note, in the original "a week in advance" is bolded. AFAICS you did not
> send this notice to the package owners, nor did you send it "a week in
> advance" - you have done the build already.
>
> https://fedoraproject.org/wiki/Updates_Policy#Rawhide_.2F_devel_.2F_master
>
> >
> > The list of dependencies I get are:
> >
> > $ dnf --releasever rawhide repoquery --whatrequires cfitsio --alldeps
> --srpm
> >
> > CCfits-0:2.5-7.fc29.src
> > astrometry-0:0.73-4.fc29.src
> > bes-0:3.17.4-7.fc29.src
> > cfitsio-0:3.430-1.fc29.src
> > cpl-0:7.0-8.fc29.src
> > gdal-0:2.2.4-2.fc29.src
> > healpix-0:3.31-10.fc29.src
> > indi-apogee-0:1.6.2-3.fc29.src
> > indi-gphoto-0:1.6.2-4.fc29.src
> > kst-0:2.0.8-20.fc29.src
> > kstars-1:2.9.3-2.fc29.src
> > libindi-0:1.6.2-3.fc29.src
> > luminance-hdr-0:2.5.1-11.fc29.src
> > nightview-0:0.3.3-27.fc29.src
> > perl-Astro-FITS-CFITSIO-0:1.11-7.fc29.src
> > phd2-0:2.6.5-1.fc29.src
> > pyfits-0:3.5-3.fc29.src
> > python-astropy-0:3.0.1-1.fc29.src
> > python-fitsio-0:0.9.11-5.fc29.src
> > python-healpy-0:1.11.0-4.fc29.src
> > python2-astropy-0:2.0.5-2.fc29.src
> > root-0:6.12.06-2.fc29.src
> > siril-0:0.9.8.3-3.fc29.src
> > skyviewer-0:1.0.1-14.fc29.src
> > ufraw-0:0.22-12.fc29.src
> > vips-0:8.6.2-4.fc29.src
> > wcslib-0:5.18-1.fc29.src
>
> Now the build's been done I'll try and help with rebuilding at least
> the most important of these. :/
> --
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
> http://www.happyassassin.net
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.
> fedoraproject.org/message/2R7LYBSDDTTU5KOIARZUVEWOUV64Z7FM/
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/RBFODV6MOVWIMBWEQLHESQDHLKRE2UU6/

Re: herbstluftwm

[Alexander Ploumistos]

Hi Silvia,

On Sat, May 26, 2018 at 10:07 AM Silvia Sánchez  wrote:
> Hi,

> Mastaiza, would you be so kind to sponsor me?  I'll be glad to maintain
your package, I like it and it's a shame it's going to be orphaned.

herbstluftwm used to be maintained by Christopher Meng (cicku).
Mastaiza is not one of our sponsors, nor is he a member of the packager
group, so he can not sponsor you.
The wiki page that Michael Cronenworth mentioned contains everything you
need to know, as well as an overwhelming number of links to other wiki
pages, with even more information relevant to becoming a packager, e.g.
http://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group

While you're looking for a sponsor it would be a good idea to update
herbstluftwm to v0.7 (in COPR, or whatever works for you), bring its spec
file up to speed with the latest guidelines and conduct a few informal
package reviews.

> Kind regards,
> Silvia
> FAS:  Lailah

One last little thing, your FAS name is spelled "lailah", with a lowercase
l. Not that people won't be able to find you, just saying.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/QLSIPGWIWKFI6K3OKHXCYTQPLQWTV3CR/

Re: Cfitsio soname bump

[Christian Dersch]

Hi,

On 05/25/2018 05:55 PM, Adam Williamson wrote:
>> The list of dependencies I get are:
>>
>> $ dnf --releasever rawhide repoquery --whatrequires cfitsio --alldeps --srpm
>>
>> CCfits-0:2.5-7.fc29.src
>> astrometry-0:0.73-4.fc29.src
>> bes-0:3.17.4-7.fc29.src
>> cfitsio-0:3.430-1.fc29.src
>> cpl-0:7.0-8.fc29.src
>> gdal-0:2.2.4-2.fc29.src
>> healpix-0:3.31-10.fc29.src
>> indi-apogee-0:1.6.2-3.fc29.src
>> indi-gphoto-0:1.6.2-4.fc29.src
>> kst-0:2.0.8-20.fc29.src
>> kstars-1:2.9.3-2.fc29.src
>> libindi-0:1.6.2-3.fc29.src
>> luminance-hdr-0:2.5.1-11.fc29.src
>> nightview-0:0.3.3-27.fc29.src
>> perl-Astro-FITS-CFITSIO-0:1.11-7.fc29.src
>> phd2-0:2.6.5-1.fc29.src
>> pyfits-0:3.5-3.fc29.src
>> python-astropy-0:3.0.1-1.fc29.src
>> python-fitsio-0:0.9.11-5.fc29.src
>> python-healpy-0:1.11.0-4.fc29.src
>> python2-astropy-0:2.0.5-2.fc29.src
>> root-0:6.12.06-2.fc29.src
>> siril-0:0.9.8.3-3.fc29.src
>> skyviewer-0:1.0.1-14.fc29.src
>> ufraw-0:0.22-12.fc29.src
>> vips-0:8.6.2-4.fc29.src
>> wcslib-0:5.18-1.fc29.src
> Now the build's been done I'll try and help with rebuilding at least
> the most important of these. :/

As the build was not yet done yesterday (but now), I'll take care of the
rebuilds now. I own some of the packages requiring a rebuild anyway.

@Sergio: For F28 we have to coordinate somehow. I'm unhappy with the
soname bump (and the way upstream handles security fixes), they bump for
almost every new release nowadays…

Greetings,
Christian
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/YDAYVECLC33VIE4VABS57EA6UMOSYD35/

Re: herbstluftwm

[Silvia Sánchez]

Hi,

Mastaiza, would you be so kind to sponsor me?  I'll be glad to maintain
your package, I like it and it's a shame it's going to be orphaned.

Kind regards,
Silvia
FAS:  Lailah



On 25 May 2018 at 20:59, Michael Cronenworth  wrote:

> On 05/25/2018 02:27 PM, Silvia Sánchez wrote:
>
>>
>> Thanks for the link.  So according to the guidelines I should install
>> developer client tools and...?  It says nothing about how to maintain
>> someone else's package.  I might be missing something.
>>
>
> You will need to become part of the "packager" group, which requires you
> become sponsored.
>
> https://fedoraproject.org/wiki/How_to_get_sponsored_into_
> the_packager_group#Become_a_co-maintainer
>
> Once you are part of that group you can become the maintainer of someone
> else's package.
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.or
> g/archives/list/devel@lists.fedoraproject.org/message/CT5VTP
> KWNJ54MYWVF4FGGF4ZPW77U7NY/
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/WMTLF7UWWOTXONNRGE6CCXMPSLJ5I2JY/