rawhide report: 20151106 changes

Compose started at Fri Nov 6 05:15:03 UTC 2015 Broken deps for i386 -- [IQmol] IQmol-2.3.0-9.fc24.i686 requires libboost_serialization.so.1.58.0 IQmol-2.3.0-9.fc24.i686 requires libboost_iostreams.so.1.58.0 IQmol-2.3.0

git commits&branches mess up

I have done some mistakes in [1] 1) I edited the file once to remove 32 bit CPU support, then I have done the push to master 2) I saw that I have forgotten to add changelog, so I edited the file again, I made a new push to master 3) I started merging the F21 branch to the master and I got the conf

Re: git commits&branches mess up

Hi, On Fri, 2015-11-06 at 14:01 +0100, Germano Massullo wrote: > I have done some mistakes in [1] > > 1) I edited the file once to remove 32 bit CPU support, then I have > done the push to master > 2) I saw that I have forgotten to add changelog, so I edited the file > again, I made a new push to

Re: git commits&branches mess up

Thank you, I was trying to solve with [1] but your > $ git checkout master -- darktable.spec # solve the conflict by taking the > file as it is in master is the key of success :-) [1]: https://help.github.com/articles/resolving-a-merge-conflict-from-the-command-line/ -- devel mailing list deve

What license is this?

I'm trying to package python-cycler for matplotlib. It has the attached LICENSE file. What should I put for license: tag?Copyright (c) 2015, matplotlib project All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the f

Re: What license is this?

3-clause BSD. https://opensource.org/licenses/BSD-3-Clause On Fri, Nov 6, 2015 at 8:58 AM, Neal Becker wrote: > I'm trying to package python-cycler for matplotlib. It has the attached > LICENSE file. What should I put for license: tag? > -- > devel mailing list > devel@lists.fedoraproject.org

Re: What license is this?

Err, to answer your question, the License tag should read "BSD". On Fri, Nov 6, 2015 at 8:59 AM, Neal Gompa wrote: > 3-clause BSD. https://opensource.org/licenses/BSD-3-Clause > > On Fri, Nov 6, 2015 at 8:58 AM, Neal Becker wrote: > >> I'm trying to package python-cycler for matplotlib. It has

Re: What license is this?

It's 3 clause BSD (as you can see with licensecheck), In license tag: BSD On 11/06/2015 02:58 PM, Neal Becker wrote: > I'm trying to package python-cycler for matplotlib. It has the attached > LICENSE file. What should I put for license: tag? > > > -- devel mailing list devel@lists.fedorapr

Re: git commits&branches mess up

On 11/06/2015 02:01 PM, Germano Massullo wrote: 1) I edited the file once to remove 32 bit CPU support Why are you trying to remove 32 bit support in the first place? -- Kalev -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code

Retire a package from Fedora i686 (not x86_64)

I just removed 32bit CPU support from Darktable's spec file due technical reasons. Are there any other things I need to clean up in Fedora infrastructure? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedor

Re: Retire a package from Fedora i686 (not x86_64)

On 06/11/15 14:18, Germano Massullo wrote: I just removed 32bit CPU support from Darktable's spec file due technical reasons. Are there any other things I need to clean up in Fedora infrastructure? Well you should start by reading the relevant guidelines: https://fedoraproject.org/wiki/Packag

Re: packaging golang guidelines (like etcd, consul)

On Mon, Nov 02, 2015 at 09:05:09AM -0500, Matthew Miller wrote: > On Sun, Nov 01, 2015 at 05:44:42PM +0100, Jan Chaloupka wrote: > > >are there some fedora guidelines for golang apps? > > >are there macros and helpers for rpm? > > https://fedoraproject.org/wiki/PackagingDrafts/Go > > This needs he

F24: no rsyslog forwarding

who is responsible that nothing is forwarded to the traditional syslog? systemd or rsyslog? /var/lib/rsyslog/imjournal.state exists and get re-created when it is deleted __ imjournal is configured $ModLoad imjournal $MainMsgQueueSize 10 $WorkDir

What is Source0 tag for this?

What is syntax for Source0 tag for git tag v0.9.0 tarball for this? https://github.com/matplotlib/cycler/tree/v0.9.0 And how can I verify it works? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedorapro

Re: What is Source0 tag for this?

https://github.com/matplotlib/cycler/archive/v%{version}/%{name}-%{version}.tar.gz On Fri, Nov 6, 2015, 4:09 PM Neal Becker wrote: > What is syntax for Source0 tag for git tag v0.9.0 tarball for this? > > https://github.com/matplotlib/cycler/tree/v0.9.0 > > And how can I verify it works? > > --

Re: packaging golang guidelines (like etcd, consul)

- Original Message - > From: "Adam Goode" > To: devel@lists.fedoraproject.org > Cc: "Matthew Miller" > Sent: Friday, November 6, 2015 3:47:42 PM > Subject: Re: packaging golang guidelines (like etcd, consul) > > On Mon, Nov 02, 2015 at 09:05:09AM -0500, Matthew Miller wrote: > > On Sun,

Re: [EPEL-devel] mod_passenger missing from EPEL 6

On 11/05/2015 11:30 PM, Rob Nelson wrote: Hello, I have previously installed mod_passenger from EPEL 6: server1$ yum list mod_passenger Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: centos.den.host-engine.com * epel: mir

Re: What is Source0 tag for this?

On Sex, 2015-11-06 at 10:08 -0500, Neal Becker wrote: > What is syntax for Source0 tag for git tag v0.9.0 tarball for this? > > https://github.com/matplotlib/cycler/tree/v0.9.0 > > And how can I verify it works? https://fedoraproject.org/wiki/Packaging:SourceURL#Git_Tags and spectool -g cycle

systemd package bloat

it's one thing that there is a common tarball containing everything, but 26 MB, 821 files including /usr/bin/machinectl and /usr/lib/systemd/systemd-machined useless on tiny virtual machines is too much and the beast is growing slightly F21: 22 MB F22: 24 MB F23: 26 MB there should be *really

bodhi should strip subjects

don't get me wrong, but subjects above 1 KB are a joke and typically spammers which try to bypass contentfilters by put the payload in the subject header Nov 4 16:27:42 mail-gw postfix/cleanup[27083]: 3nrX0s6JB2z28: reject: header Subject: [Fedora Update] [comment] extra-cmake-modules-5.15.0

Re: systemd package bloat

2015-11-06 16:35 GMT+01:00 Reindl Harald : > it's one thing that there is a common tarball containing everything, but 26 > MB, 821 files including /usr/bin/machinectl and > /usr/lib/systemd/systemd-machined useless on tiny virtual machines is too > much and the beast is growing slightly > > F21: 22

Re: systemd package bloat

On Fri, Nov 06, 2015 at 04:48:34PM +0100, Haïkel wrote: > Excellent idea, please file a ticket and it'd be appreciated if you > could send patches. Well, see However, it probably _is_ the case that a specfile showing how this would actually wo

Re: [HEADS UP] Ongoing rebuild of Python3.5 in Rawhide

On 11/04/2015 12:23 PM, Robert Kuska wrote: > There is ongoing rebuild of Python3.5 in rawhide's side-tag f24-python3. > > I would like to ask all maintainers to rebuild their packages (which > depend on python3) within the f24-python3 side-tag. > > To rebuild your package simply run: > `fedpkg b

Re: systemd package bloat

Am 06.11.2015 um 17:19 schrieb Matthew Miller: On Fri, Nov 06, 2015 at 04:48:34PM +0100, Haïkel wrote: Excellent idea, please file a ticket and it'd be appreciated if you could send patches. Well, see However, it probably _is_ the case th

Fedora Release Tools team - some house keeping and process changes

For anyone who isn't already aware, I've partnered with the Fedora release tooling folks to help organize work and communication into and out of the team. The team is focused on tooling & process in support of the release engineering functions of Fedora. The core team consists of Adam Miller, Ku

Re: F24: no rsyslog forwarding

On Nov 6, 2015 9:52 AM, "Reindl Harald" wrote: > > who is responsible that nothing is forwarded to the traditional syslog? > systemd or rsyslog? > Journald is probably hold the log socket and not forwarding to syslog > /var/lib/rsyslog/imjournal.state exists and get re-created when it is deleted

Re: F24: no rsyslog forwarding

Am 06.11.2015 um 18:15 schrieb Subhendu Ghosh: On Nov 6, 2015 9:52 AM, "Reindl Harald" mailto:h.rei...@thelounge.net>> wrote: > > who is responsible that nothing is forwarded to the traditional syslog? > systemd or rsyslog? > Journald is probably hold the log socket and not forwarding to

Re: Retire a package from Fedora i686 (not x86_64)

06.11.2015, 17:18, "Germano Massullo" : > I just removed 32bit CPU support from Darktable's spec file due > technical reasons. It is hard to help if you just say "due to technical reasons". What are they? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailma

Re: Browser choice in live images

Michael Catanzaro wrote: > I miss QtWebKit. :( > > For those not familiar with the history, QtWebKit was deleted from the > upstream WebKit project about three years ago after the maintainers > said they no longer had the resources to continue maintaining it > upstream. It now lives on KDE.org but

Re: Retire a package from Fedora i686 (not x86_64)

For example, SSE3 instructions set is one of the minimum requirements and 99% of 32 bit only CPUs do not support it. Only Pentium 4 >= Prescott architecture supports it. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduc

Re: Browser choice in live images

On Fri, 2015-11-06 at 20:07 +0100, Kevin Kofler wrote: > QtWebEngine is definitely the plan for F24. The most likely browser > candidate (if Konqueror and/or Rekonq don't get a sudden revival of > upstream > activity) is probably Qupzilla, which already has experimental > QtWebEngine > support,

Re: Retire a package from Fedora i686 (not x86_64)

06.11.2015, 22:11, "Germano Massullo" :For example, SSE3 instructions set is one of the minimum requirements and 99% of 32 bit only CPUs do not support it. Only Pentium 4 >= Prescott architecture supports it. Prescott is 11 years old. I would expect vast majority of people who are currently running

Re: Retire a package from Fedora i686 (not x86_64)

On 11/06/2015 02:11 PM, Germano Massullo wrote: For example, SSE3 instructions set is one of the minimum requirements and 99% of 32 bit only CPUs do not support it. Only Pentium 4 >= Prescott architecture supports it. For that kind of thing, add a runtime test for required CPU features at s

Re: Retire a package from Fedora i686 (not x86_64)

Germano Massullo wrote: > For example, SSE3 instructions set is one of the minimum requirements and > 99% of 32 bit only CPUs do not support it. Only Pentium 4 >= Prescott > architecture supports it. I think building it with SSE3 is better than excluding the architecture entirely. And FYI, requir

Re: Browser choice in live images

Michael Catanzaro wrote: > On Fri, 2015-11-06 at 20:07 +0100, Kevin Kofler wrote: >> QtWebEngine is definitely the plan for F24. The most likely browser >> candidate (if Konqueror and/or Rekonq don't get a sudden revival of >> upstream >> activity) is probably Qupzilla, which already has experimen

Re: Browser choice in live images

Two small corrections about Qupzilla: I wrote: > QtWebEngine is definitely the plan for F24. The most likely browser > candidate (if Konqueror and/or Rekonq don't get a sudden revival of > upstream activity) is probably Qupzilla, which already has experimental > QtWebEngine support, and which has

Re: systemd package bloat

Hi On Fri, Nov 6, 2015 at 11:23 AM, Reindl Harald wrote: > > the same way as other packages to it? > > * see php > * see httpd > More useful if you could submit a spec file patch Rahul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fe

Re: bodhi should strip subjects

Again, what you're saying makes sense but if you don't file tickets, it won't get fixed. Here's bodhi bug tracker. https://github.com/fedora-infra/bodhi/issues Regards, H. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Co

Re: F24: no rsyslog forwarding

Hi On Fri, Nov 6, 2015 at 12:20 PM, Reindl Harald wrote: > to say it in other words: i did not ask for "probably", just pointed out > that Rawhide is currently broken, that probably systemd or probably rsyslog > is broken in the one or other direction is clear Can you file a bug report? Rahul

Fedora Rawhide 20151106 compose check report

Missing expected images: Cloud disk raw i386 Cloud disk raw x86_64 Cloud_atomic disk raw x86_64 Generic boot i386 Generic boot x86_64 No images in this compose but not Rawhide 20151105 No images in Rawhide 20151105 but not this. -- Mail generated by check-compose: https://git.fedorahosted.org/c

Re: Retire a package from Fedora i686 (not x86_64)

On 11/06/2015 09:50 PM, Stuart Gathman wrote: On 11/06/2015 02:11 PM, Germano Massullo wrote: For example, SSE3 instructions set is one of the minimum requirements and 99% of 32 bit only CPUs do not support it. Only Pentium 4 >= Prescott architecture supports it. For that kind of thing, add a

Re: Retire a package from Fedora i686 (not x86_64)

On 11/06/2015 10:00 PM, Kevin Kofler wrote: Germano Massullo wrote: For example, SSE3 instructions set is one of the minimum requirements and 99% of 32 bit only CPUs do not support it. Only Pentium 4 >= Prescott architecture supports it. I think building it with SSE3 is better than excluding t

Re: Retire a package from Fedora i686 (not x86_64)

Am 06.11.2015 um 20:11 schrieb Germano Massullo: For example, SSE3 instructions set is one of the minimum requirements and 99% of 32 bit only CPUs do not support it. Only Pentium 4 >= Prescott architecture supports it seriously? with that argumentation Fedora would drop i686 at all well, i d

Re: Retire a package from Fedora i686 (not x86_64)

On 06/11/15 07:29 PM, Ralf Corsepius wrote: > On 11/06/2015 10:00 PM, Kevin Kofler wrote: >> Germano Massullo wrote: >>> For example, SSE3 instructions set is one of the minimum >>> requirements and >>> 99% of 32 bit only CPUs do not support it. Only Pentium 4 >= Prescott >>> architecture supports

Re: Retire a package from Fedora i686 (not x86_64)

Am 07.11.2015 um 05:00 schrieb Luya Tshimbalanga: On 06/11/15 07:29 PM, Ralf Corsepius wrote: But if upstream doesn't care, it's going to be a problem. :-( Exactly - That's the actual problem. Upstream does not care and Fedora seems unable to address this issue. Ralf According to my system

Re: Retire a package from Fedora i686 (not x86_64)

On 11/07/2015 04:55 AM, Reindl Harald wrote: Am 06.11.2015 um 20:11 schrieb Germano Massullo: For example, SSE3 instructions set is one of the minimum requirements and 99% of 32 bit only CPUs do not support it. Only Pentium 4 >= Prescott architecture supports it seriously? Probably. with

Re: Retire a package from Fedora i686 (not x86_64)

On 11/07/2015 05:03 AM, Reindl Harald wrote: Am 07.11.2015 um 05:00 schrieb Luya Tshimbalanga: On 06/11/15 07:29 PM, Ralf Corsepius wrote: But if upstream doesn't care, it's going to be a problem. :-( Exactly - That's the actual problem. Upstream does not care and Fedora seems unable to addr

Re: Retire a package from Fedora i686 (not x86_64)

On Sat, 7 Nov 2015 04:29:48 +0100 Ralf Corsepius wrote: > On 11/06/2015 10:00 PM, Kevin Kofler wrote: > > Germano Massullo wrote: > >> For example, SSE3 instructions set is one of the minimum > >> requirements and 99% of 32 bit only CPUs do not support it. Only > >> Pentium 4 >= Prescott archit

Re: Retire a package from Fedora i686 (not x86_64)

Il 07/11/2015 04:29, Ralf Corsepius ha scritto: > I don't see sse3 in /proc/cpuinfo of any machine I have, but I also > don't see any runtime error/warning from darktable. Because SSE3 is shown as "pni", Prescott New Instructions [1] [2] [1]: https://en.wikipedia.org/wiki/SSE3 [2]: http://unix.sta