Fedora-Atomic 27-20180413.0 compose check report

[Fedora compose checker]

No missing expected images.

Passed openQA tests: 2/2 (x86_64)
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: How should I coordinate the package updates with you guys?

[Fabio Valentini]

I suggest you look at the wiki page describing the package update process,
specifically the section for rawhide:

https://fedoraproject.org/wiki/Updates_Policy#Rawhide_.2F_devel_.2F_master

It outlines the actions recommended / needed for updates with and without
implications for dependent packages.

Jason already posted a link to a script which you can use to determine
affected packages and their maintainers.

Fabio

On Fri, Apr 13, 2018, 00:07  wrote:

> On Thu, 12 Apr 2018 15:43:28 -0500
> Jason L Tibbitts III  wrote:
>
> > >   writes:
> >
> > > Brotli apparently just got a new update, and I was told I have to
> > > coordinate package updates with you guys in Rawhide instead of just
> > > uploading the updates unannounced. How should I proceed?
> > ]
> >
> > Well, there's only really a need to coordinate if the versioning of the
> > library changes, or if there's an ABI change and (boo) upstream doesn't
> > bother to bump the soversion when they break the ABI, or if there's
> > something else that people need to know about like an API change which
> > is going to break users of the library when they next rebuild.
> >
> > If you're just releasing a compatible update, then there's no real need
> > to say much of anything.  Otherwise this list would be flooded with
> > update notices.
> >
> > If you do need to make an announcement, you should say what is changing,
> > what needs to be done to accommodate it, and provide a list of packages
> > which will need rebuilding.  You can use the find-package-maintainers
> > script from
> >
> https://pagure.io/fedora-misc-package-utilities/blob/master/f/find-package-maintainers
> > to give a nice list of packages and their owners so that people can
> > easily see if they'll need to do anything.
> >
> > (This really needs to be put into the wiki if it isn't already there.)
> >
> >  - J<
> > ___
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
> How do I find out what packages depends on it? Would
> `dnf repoquery --whatrequires brotli`
> provide that? or is there a different command that I should run? Do I just
> make an announcement after uploading with the list of packages that need to
> rebuild or is there something else that I need to do first?
>
> --
> GPG Keys: https://keybase.io/pouar
> Tox ID:
>
> 2EA7A6D5494C10B2E0F32004A1E9CBD971777E551A902059E5EA7E73E5A299272F29D9FF5F6A
> Matrix ID: @Pouar:matrix.org Social Links:
> https://www.pouar.net/social.php
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

libupnp ABI change notice

[Nicolas Chauvet]

Hi,

I plan to update libupnp to 1.8.3 which comes with an ABI bump.
The libthreadutil library is also dropped in this new release.

I will rebuild the dependent applications

f29 scratch build
https://koji.fedoraproject.org/koji/taskinfo?taskID=26339066

On a side note, I've also updated the current branches to the latest
1.6.25 bugfix release.
Please report any issue in the related bodhi tickets

-- 
-

Nicolas (kwizart)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Packages optimized for very specific x86_64 "x" generation (OpenSUSE OBS / Fedora Koji)

[Germano Massullo]

As darktable co-maintainer, today I was speaking with darix from
OpenSUSE community, which maintains such package on that distro.
On their OBS build system, they are able to build various packages each
one optimized for a single x86_64 CPU generation using @BUILD_FLAVOR@ +
_multibuild file.[1] So for example they have packages
darktable-broadwell
darktable-ivybridge
darktable-sandybridge
darktable-skylake
darktable-skylake-avx512

 darix also said "that is an OBS feature, nothing that you can just copy
to koji[...]"
"there is no generic solution to this for a normal distro package".

I would like to study a way to make darktable (sub)packages very
optimized for each CPU generation, so I am asking you if that is
possible on Fedora, and what I should study to achieve it.

Best regards

[1]:
https://build.opensuse.org/package/show/home:darix:darktable:master/darktable
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Delay in upcoming Two Week Atomic Release

[Sinny Kumari]

Hi all,

This email is to inform that there will be some delay in next Atomic Two
Week
Release. This is due to some issues with uploading Atomic AMIs. We are
working
on getting it fixed as soon as possible. Once we have AMIs back, we will do
next
Two week release.

Thanks,
Sinny
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Fwd: Renaming "docker" references to generic ones like "container" or "OCI']

[Dennis Gilmore]

I am forwarding to devel list as Sushma was not subscribed and it was
rejected.

Dennis

- Mensaje reenviado 
De: Sushma Gajanur Shivakumar 
Para: devel-annou...@lists.fedoraproject.org
Cc: Ben Breard , den...@ausil.us, Mohan Boddu , Greg Sterling 
Asunto: Renaming "docker" references to generic ones like "container"
or "OCI'
Fecha: Fri, 13 Apr 2018 16:15:32 +0200

Hi All,

As the container landscape has changed over the last few years, Docker
Inc. has changed what the term "docker" means. Along with changes in
the container namespace with tools like buildah, cri-o, rkt and other
ways to run containers, it makes sense to refer to containers in a more
generic sense, using terms like "container" or "OCI(Open Container
Initiative)" instead of "docker".

We have already renamed the Docker namespace to "containers" in dist-
git. The Bugzilla project for containers is under container as well.
Wherever possible to be consistent with using more generic terms,
"docker" should be renamed to an appropriate generic term. This will
allow us to more seamlessly adapt and change with the continuing
evolution of the container based world. A side effect is that the
changes will more closely align us with ongoing work within Red Hat.

There are several areas that can be evaluated for changes from "docker"
to "container" (or OCI).  These include:
Changing a package description to be more generic
Working with upstream to rename the project and bringing that back to
Fedora
Changing labels and descriptions used within Dockerfiles
The non-exhaustive* full list of current containers[1] and packages[2]
to be considered is not a very large list and your consideration and
efforts to help are greatly appreciated.

* The bellow URLs will not show a package that is using docker only in
the package description which shows up in bugzilla along with other
locations
[1] https://src.fedoraproject.org/projects/container/%2A
[2] https://src.fedoraproject.org/projects/*docker*


Best Regards,
Sushma Shivakumar
RCM Project Manager
Red Hat, Brno

signature.asc
Description: This is a digitally signed message part
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Release rpkg-1.53

[Chenxiong Qi]

On Fri, Apr 13, 2018 at 12:56 PM, Tomasz Kłoczko
 wrote:
> On 11 April 2018 at 03:34, Chenxiong Qi  wrote:
>> Hi all,
>>
>> A new version rpkg-1.53  is released.
>>
>> This is the first version delivering Python 3 package, which is
>> python3-rpkg. Thanks Miro Hrončok for making the patch.
> [..]
>
> It would be good to port fedpkg to python 3.
> Someone is working on this? And/or what still is missing do make such
> transition?

It's in progress. Please following https://pagure.io/fedpkg/issue/180

>
> kloczek
> --
> Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org



-- 
Regards,
Chenxiong Qi
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Packages optimized for very specific x86_64 "x" generation (OpenSUSE OBS / Fedora Koji)

[Dominik 'Rathann' Mierzejewski]

On Friday, 13 April 2018 at 15:47, Germano Massullo wrote:
> As darktable co-maintainer, today I was speaking with darix from
> OpenSUSE community, which maintains such package on that distro.
> On their OBS build system, they are able to build various packages each
> one optimized for a single x86_64 CPU generation using @BUILD_FLAVOR@ +
> _multibuild file.[1] So for example they have packages
> darktable-broadwell
> darktable-ivybridge
> darktable-sandybridge
> darktable-skylake
> darktable-skylake-avx512
> 
>  darix also said "that is an OBS feature, nothing that you can just copy
> to koji[...]"
> "there is no generic solution to this for a normal distro package".
> 
> I would like to study a way to make darktable (sub)packages very
> optimized for each CPU generation, so I am asking you if that is
> possible on Fedora, and what I should study to achieve it.

On Fedora 27+ (glibc 2.26+), you can use the standard way of building
optimized libraries and putting them in platform and capability-specific
directories, e.g.:
/usr/lib64/haswell
/usr/lib64/haswell/avx512_1
/usr/lib64/xeon_phi

It's not the same as OBS does, but it's better than nothing.

See this article for more information
https://clearlinux.org/blogs/transparent-use-library-packages-optimized-intel-architecture

Regards,
Dominik
-- 
Fedora   https://getfedora.org  |  RPMFusion   http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
-- from "Collected Sayings of Muad'Dib" by the Princess Irulan
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: How should I coordinate the package updates with you guys?

[Adam Williamson]

On Thu, 2018-04-12 at 17:06 -0500, po...@pouar.net wrote:
> On Thu, 12 Apr 2018 15:43:28 -0500
> Jason L Tibbitts III  wrote:
> 
> > > > > > >   writes:
> > 
> >   
> > > Brotli apparently just got a new update, and I was told I have to
> > > coordinate package updates with you guys in Rawhide instead of just
> > > uploading the updates unannounced. How should I proceed?
> > 
> > ]  
> > 
> > Well, there's only really a need to coordinate if the versioning of the
> > library changes, or if there's an ABI change and (boo) upstream doesn't
> > bother to bump the soversion when they break the ABI, or if there's
> > something else that people need to know about like an API change which
> > is going to break users of the library when they next rebuild.
> > 
> > If you're just releasing a compatible update, then there's no real need
> > to say much of anything.  Otherwise this list would be flooded with
> > update notices.
> > 
> > If you do need to make an announcement, you should say what is changing,
> > what needs to be done to accommodate it, and provide a list of packages
> > which will need rebuilding.  You can use the find-package-maintainers
> > script from
> > https://pagure.io/fedora-misc-package-utilities/blob/master/f/find-package-maintainers
> > to give a nice list of packages and their owners so that people can
> > easily see if they'll need to do anything.
> > 
> > (This really needs to be put into the wiki if it isn't already there.)
> > 
> >  - J<
> > ___
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> 
> How do I find out what packages depends on it? Would
> `dnf repoquery --whatrequires brotli`
> provide that?

No, not quite.

>  or is there a different command that I should run?

Well, the script above. But you can also do:

dnf repoquery --releasever=rawhide --refresh --whatrequires 
"libbrotlicommon.so.1()(64bit)"
dnf repoquery --releasever=rawhide --refresh --whatrequires 
"libbrotlidec.so.1()(64bit)"
dnf repoquery --releasever=rawhide --refresh --whatrequires 
"libbrotlienc.so.1()(64bit)"

to find *binary* packages with an auto-generated dependency on
the current sonames provided by the library, and:

dnf repoquery --releasever=rawhide --disablerepo=* --enablerepo=fedora-source 
--whatrequires brotli-devel

to find all source packages that BuildRequire brotli-devel.

>  Do I just
> make an announcement after uploading with the list of packages that need to
> rebuild or is there something else that I need to do first?

Read the URL Fabio linked to, but the important thing is, you need to
do the announcement *well in advance* of doing the actual build, and
ideally come up with a plan for making sure the builds of the
dependencies happen on the same day as the build of brotli.

Note this is all assuming the new version will actually change the
soname - if it doesn't, there's no problem. The current soname in
Rawhide is 'libbrotli(whatever).so.1', if that's the same with the new
version, all existing packages should continue to work with it without
needing to be rebuilt.

Thanks!
-- 
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

Re: Schedule for Friday's FESCo Meeting (2018-04-13)

[Zbigniew Jędrzejewski-Szmek]

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting/2018-04-13/fesco.2018-04-13-15.00.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting/2018-04-13/fesco.2018-04-13-15.00.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting/2018-04-13/fesco.2018-04-13-15.00.log.html

Meeting summary
---
* init process  (zbyszek, 15:00:41)

* #1877 large number of packages FTBFS in F28  (zbyszek, 15:04:28)
  * LINK: https://pagure.io/fesco/issue/1877   (zbyszek, 15:04:28)
  * AGREED: till will create a list of FTBFS packages, post it to devel
and announce that they will be retired in 6 weeks if not being
worked on (+6, 0, -0)  (tyll, 15:31:57)
  * ACTION: till will send a list of FTBFS packages to devel and retire
them in 6 weeks  (tyll, 15:32:13)

* #1874 Package Anki has a Non-responsive Maintainer  (zbyszek,
  15:32:26)
  * LINK: https://pagure.io/fesco/issue/1874   (zbyszek, 15:32:26)
  * anki maintainer is responsive again  (tyll, 15:35:27)
  * AGREED: No additional action is required from FESCo (+5, 0, 0)
(zbyszek, 15:36:15)

* #1872 Disable Test Gating requirements until more UI is enabled
  (zbyszek, 15:36:29)
  * LINK: https://pagure.io/fesco/issue/1872   (zbyszek, 15:36:29)
  * AGREED: Wait another week to see how the Bohdi changes shake out
before deciding whether to disable gating (+5, 0, 0)  (zbyszek,
15:43:58)

* #1868 Change the Changes template  (zbyszek, 15:44:09)
  * LINK: https://pagure.io/fesco/issue/1868   (zbyszek, 15:44:09)
  * ACTION: zbyszek to generate a counter-proposal to spur discussion
(zbyszek, 15:55:28)

* #1878 Please change "Everything" directory to something less
  inaccurately comprehensive  (zbyszek, 15:55:34)
  * LINK: https://pagure.io/fesco/issue/1878   (zbyszek, 15:55:40)
  * We'll return to this after F28 is released  (zbyszek, 16:04:06)

* #1876 Please orphan all LXQt packages / nonresponsive maintainer
  heliocastro  (zbyszek, 16:05:05)
  * LINK: https://pagure.io/fesco/issue/1876   (zbyszek, 16:05:11)
  * AGREED: Wait another week for the heliocastro to respond and orphan
packages if there's no reponse (+6, 0, 0)  (zbyszek, 16:10:09)

* Next week's chair  (zbyszek, 16:10:18)
  * ACTION: maxamillion will chair next meeting  (zbyszek, 16:12:37)

* Open Floor  (zbyszek, 16:17:54)
  * LINK:
https://koji.fedoraproject.org/koji/packageinfo?packageID=19167 for
example does not have a build for f28  (tyll, 16:21:17)

Meeting ended at 16:30:59 UTC.


Action Items

* till will send a list of FTBFS packages to devel and retire them in 6
  weeks
* zbyszek to generate a counter-proposal to spur discussion
* maxamillion will chair next meeting


Action Items, by person
---
* maxamillion
  * maxamillion will chair next meeting
* zbyszek
  * zbyszek to generate a counter-proposal to spur discussion
* **UNASSIGNED**
  * till will send a list of FTBFS packages to devel and retire them in
6 weeks


People Present (lines said)
---
* zbyszek (111)
* tyll (41)
* jsmith (38)
* nirik (24)
* zodbot (16)
* x3mboy (15)
* maxamillion (13)
* jwb (5)
* pjones (2)
* dgilmore (2)
* pingou (1)
* sgallagh (0)
* bowlofeggs (0)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

FreeCAD: undefined reference to `Py::ifPyErrorThrowCxxException()'

[Richard Shaw]

I've posted to upstreams mailing list but have not as of yet gotten a
response.

I've run into the following error trying to build the latest version of
FreeCAD which requires python-pycxx but Rawhide now has 7.0.3 and the
bundled version appears to be 6.2.8.

I'm used to undefined references indicating that a library is missing at
the linker stage, but in the case of python-pycxx, it's a copylib. There is
no library to link to and it seems to be picking up the source and headers
at the correct location so I'm at a loss...

[ 24%] Linking CXX shared library ../../lib/libFreeCADBase.so
cd /builddir/build/BUILD/FreeCAD-0.17/build/src/Base && /usr/bin/cmake -E
cmake_link_script CMakeFiles/FreeCADBase.dir/link.txt --verbose=1
/usr/bin/c++ -fPIC -Wall -Wextra -Wno-write-strings -O2 -g -pipe -Wall
-Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS
-fexceptions -fstack-protector-strong -grecord-gcc-switches
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic
-fasynchronous-unwind-tables -fstack-clash-protection -mcet -fcf-protection
-std=c++11 -D_OCC64 -Wl,--no-undefined -shared
-Wl,-soname,libFreeCADBase.so -o ../../lib/libFreeCADBase.so
CMakeFiles/FreeCADBase.dir/usr/src/CXX/cxxextensions.c.o
CMakeFiles/FreeCADBase.dir/usr/src/CXX/cxx_extensions.cxx.o
CMakeFiles/FreeCADBase.dir/usr/src/CXX/cxxsupport.cxx.o
CMakeFiles/FreeCADBase.dir/usr/src/CXX/IndirectPythonInterface.cxx.o
CMakeFiles/FreeCADBase.dir/Axis.cpp.o
CMakeFiles/FreeCADBase.dir/AxisPyImp.cpp.o
CMakeFiles/FreeCADBase.dir/Base64.cpp.o
CMakeFiles/FreeCADBase.dir/BaseClass.cpp.o
CMakeFiles/FreeCADBase.dir/BaseClassPyImp.cpp.o
CMakeFiles/FreeCADBase.dir/BoundBoxPyImp.cpp.o
CMakeFiles/FreeCADBase.dir/Builder3D.cpp.o
CMakeFiles/FreeCADBase.dir/Console.cpp.o
CMakeFiles/FreeCADBase.dir/CoordinateSystem.cpp.o
CMakeFiles/FreeCADBase.dir/CoordinateSystemPyImp.cpp.o
CMakeFiles/FreeCADBase.dir/Debugger.cpp.o
CMakeFiles/FreeCADBase.dir/Exception.cpp.o
CMakeFiles/FreeCADBase.dir/ExceptionFactory.cpp.o
CMakeFiles/FreeCADBase.dir/Factory.cpp.o
CMakeFiles/FreeCADBase.dir/FileInfo.cpp.o
CMakeFiles/FreeCADBase.dir/FileTemplate.cpp.o
CMakeFiles/FreeCADBase.dir/FutureWatcherProgress.cpp.o
CMakeFiles/FreeCADBase.dir/gzstream.cpp.o
CMakeFiles/FreeCADBase.dir/GeometryPyCXX.cpp.o
CMakeFiles/FreeCADBase.dir/Handle.cpp.o
CMakeFiles/FreeCADBase.dir/InputSource.cpp.o
CMakeFiles/FreeCADBase.dir/Interpreter.cpp.o
CMakeFiles/FreeCADBase.dir/Matrix.cpp.o
CMakeFiles/FreeCADBase.dir/MatrixPyImp.cpp.o
CMakeFiles/FreeCADBase.dir/MemDebug.cpp.o
CMakeFiles/FreeCADBase.dir/Parameter.cpp.o
CMakeFiles/FreeCADBase.dir/ParameterPy.cpp.o
CMakeFiles/FreeCADBase.dir/Persistence.cpp.o
CMakeFiles/FreeCADBase.dir/PersistencePyImp.cpp.o
CMakeFiles/FreeCADBase.dir/Placement.cpp.o
CMakeFiles/FreeCADBase.dir/PlacementPyImp.cpp.o
CMakeFiles/FreeCADBase.dir/PyExport.cpp.o
CMakeFiles/FreeCADBase.dir/PyObjectBase.cpp.o
CMakeFiles/FreeCADBase.dir/Reader.cpp.o
CMakeFiles/FreeCADBase.dir/Rotation.cpp.o
CMakeFiles/FreeCADBase.dir/RotationPyImp.cpp.o
CMakeFiles/FreeCADBase.dir/Sequencer.cpp.o
CMakeFiles/FreeCADBase.dir/Stream.cpp.o
CMakeFiles/FreeCADBase.dir/Swap.cpp.o
CMakeFiles/FreeCADBase.dir/swigpyrun_1.3.25.cpp.o
CMakeFiles/FreeCADBase.dir/swigpyrun_1.3.33.cpp.o
CMakeFiles/FreeCADBase.dir/swigpyrun_1.3.36.cpp.o
CMakeFiles/FreeCADBase.dir/swigpyrun_1.3.38.cpp.o
CMakeFiles/FreeCADBase.dir/swigpyrun_1.3.40.cpp.o
CMakeFiles/FreeCADBase.dir/swigpyrun.cpp.o
CMakeFiles/FreeCADBase.dir/TimeInfo.cpp.o
CMakeFiles/FreeCADBase.dir/Tools.cpp.o
CMakeFiles/FreeCADBase.dir/Tools2D.cpp.o
CMakeFiles/FreeCADBase.dir/Type.cpp.o CMakeFiles/FreeCADBase.dir/Uuid.cpp.o
CMakeFiles/FreeCADBase.dir/Vector3D.cpp.o
CMakeFiles/FreeCADBase.dir/VectorPyImp.cpp.o
CMakeFiles/FreeCADBase.dir/Writer.cpp.o
CMakeFiles/FreeCADBase.dir/XMLTools.cpp.o
CMakeFiles/FreeCADBase.dir/UnitsApi.cpp.o
CMakeFiles/FreeCADBase.dir/UnitsApiPy.cpp.o
CMakeFiles/FreeCADBase.dir/UnitsSchema.cpp.o
CMakeFiles/FreeCADBase.dir/UnitsSchemaInternal.cpp.o
CMakeFiles/FreeCADBase.dir/UnitsSchemaMKS.cpp.o
CMakeFiles/FreeCADBase.dir/UnitsSchemaImperial1.cpp.o
CMakeFiles/FreeCADBase.dir/UnitsSchemaCentimeters.cpp.o
CMakeFiles/FreeCADBase.dir/UnitsSchemaMmMin.cpp.o
CMakeFiles/FreeCADBase.dir/Quantity.cpp.o
CMakeFiles/FreeCADBase.dir/QuantityPyImp.cpp.o
CMakeFiles/FreeCADBase.dir/Unit.cpp.o
CMakeFiles/FreeCADBase.dir/UnitPyImp.cpp.o
CMakeFiles/FreeCADBase.dir/PyTools.c.o
CMakeFiles/FreeCADBase.dir/PreCompiled.cpp.o -lpython2.7 -lxerces-c
-lboost_filesystem -lboost_program_options -lboost_regex -lboost_signals
-lboost_system -lboost_thread -lboost_chrono -lboost_date_time
-lboost_atomic -lz -lQtCore -lutil -ldl -lzipios
BUILDSTDERR: CMakeFiles/FreeCADBase.dir/usr/src/CXX/cxx_extensions.cxx.o:
In function `Py::Object::validate()':
BUILDSTDERR: /usr/src/CXX/Python2/cxx_extensions.cxx:122: undefined
reference to `Py::ifPyErrorThrowCxxException()'
BUILDSTDERR: CMakeFiles/FreeCADBase.dir/usr/src/CXX/cxx_

Re: How should I coordinate the package updates with you guys?

[pouar]

On Fri, 13 Apr 2018 09:29:56 -0700
Adam Williamson  wrote:

> On Thu, 2018-04-12 at 17:06 -0500, po...@pouar.net wrote:
> > On Thu, 12 Apr 2018 15:43:28 -0500
> > Jason L Tibbitts III  wrote:
> > 
>   > > > > > > >   writes:
> ] > > 
> > >   
> .]> > > Brotli apparently just got a new update, and I was told I have to
> > > > coordinate package updates with you guys in Rawhide instead of just
> > > > uploading the updates unannounced. How should I proceed?
> ..> > 
> > > ]  
> > > 
> > > Well, there's only really a need to coordinate if the versioning of the
> > > library changes, or if there's an ABI change and (boo) upstream doesn't
> > > bother to bump the soversion when they break the ABI, or if there's
> > > something else that people need to know about like an API change which
> > > is going to break users of the library when they next rebuild.
> > > 
> > > If you're just releasing a compatible update, then there's no real need
> > > to say much of anything.  Otherwise this list would be flooded with
> > > update notices.
> > > 
> > > If you do need to make an announcement, you should say what is changing,
> > > what needs to be done to accommodate it, and provide a list of packages
> > > which will need rebuilding.  You can use the find-package-maintainers
> > > script from
> > > https://pagure.io/fedora-misc-package-utilities/blob/master/f/find-package-maintainers
> > > to give a nice list of packages and their owners so that people can
> > > easily see if they'll need to do anything.
> > > 
> > > (This really needs to be put into the wiki if it isn't already there.)
> > > 
> > >  - J<
> > > ___
> > > devel mailing list -- devel@lists.fedoraproject.org
> > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> ..> 
> > How do I find out what packages depends on it? Would
> > `dnf repoquery --whatrequires brotli`
> > provide that?
> [...]  
> 
> No, not qu>  or is there a different command that I should run?
>  [...]  
> 
> Well, the script above. But you can also do:
> 
> dnf repoquery --releasever=rawhide --refresh --whatrequires 
> "libbrotlicommon.so.1()(64bit)"
> dnf repoquery --releasever=rawhide --refresh --whatrequires 
> "libbrotlidec.so.1()(64bit)"
> dnf repoquery --releasever=rawhide --refresh --whatrequires 
> "libbrotlienc.so.1()(64bit)"
> 
> to find *binary* packages with an auto-generated dependency on
> the current sonames provided by the library, and:
> 
> dnf repoquery --releasever=rawhide --disablerepo=* --enablerepo=fedora-source 
> --whatrequires brotli-devel
> 
> to find all source packages that BuildRequire brotli-d>  Do I just
> > make an announcement after uploading with the list of packages that need to
> > rebuild or is there something else that I need to do first?
> 
>  [...]  
> 
> Read the URL Fabio linked to, but the important thing is, you need to
> do the announcement *well in advance* of doing the actual build, and
> ideally come up with a plan for making sure the builds of the
> dependencies happen on the same day as the build of brotli.
> 
> Note this is all assuming the new version will actually change the
> soname - if it doesn't, there's no problem. The current soname in
> Rawhide is 'libbrotli(whatever).so.1', if that's the same with the new
> version, all existing packages should continue to work with it without
> needing to be rebuilt.
> 
> Thanks!

Not sure how to interpret the example email `packagename-owner@alias`. Would
that be like `brotli-po...@fedoraproject.org` or `po...@fedoraproject.org`
or something else? Is `fedoraproject.org` the right domain for `alias`?

-- 
GPG Keys: https://keybase.io/pouar
Tox ID:
2EA7A6D5494C10B2E0F32004A1E9CBD971777E551A902059E5EA7E73E5A299272F29D9FF5F6A
Matrix ID: @Pouar:matrix.org Social Links: https://www.pouar.net/social.php


pgpnOdKReUxmg.pgp
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: How should I coordinate the package updates with you guys?

[Mathieu Bridon]

On Fri, 2018-04-13 at 15:41 -0500, po...@pouar.net wrote:
> Not sure how to interpret the example email `packagename-owner@alias`
> . Would that be like `brotli-po...@fedoraproject.org` or
> `po...@fedoraproject.org` or something else? Is `fedoraproject.org`
> the right domain for `alias`?

It's ${srpmname}-ow...@fedoraproject.org, so in your case:

brotli-ow...@fedoraproject.org


-- 
Mathieu
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: How should I coordinate the package updates with you guys?

[pouar]

On Fri, 13 Apr 2018 22:58:58 +0200
Mathieu Bridon  wrote:

> On Fri, 2018-04-13 at 15:41 -0500, po...@pouar.net wrote:
> > Not sure how to interpret the example email `packagename-owner@alias`
> > . Would that be like `brotli-po...@fedoraproject.org` or
> > `po...@fedoraproject.org` or something else? Is `fedoraproject.org`
> > the right domain for `alias`?
>   
> 
> It's ${srpmname}-ow...@fedoraproject.org, so in your case:
> 
> brotli-ow...@fedoraproject.org
> 
> 

One last question, do I need to list the whatrequires recursively and email
those maintainers as well or just list the immediate whatrequires and
just email those guys?

-- 
GPG Keys: https://keybase.io/pouar
Tox ID:
2EA7A6D5494C10B2E0F32004A1E9CBD971777E551A902059E5EA7E73E5A299272F29D9FF5F6A
Matrix ID: @Pouar:matrix.org Social Links: https://www.pouar.net/social.php


pgpkYCqmv5Qms.pgp
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Anyone interested in Testing the wireframes of the Fedora Community App?

[Abhishek Sharma]

Hello!

So I have been working on the wireframes for the revamped Fedora Community
App

(as a part of my GSoC proposal) and I am ready to share the V1.

I need some people to volunteer for the wireframe testing. In the process,
you will be asked to do very simple tasks (which will hardly take 2
minutes) on a clickable prototype. I can learn from the insights of testing
to iterate on the design of the application. Basically what's working and
what's not. I believe to design the best UX, we need to pay attention to
what users do.

Please reply to this email if you're interested so that I can invite you
for the testing.

Thanks :-)

Best,
Abhishek
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Anyone interested in Testing the wireframes of the Fedora Community App?

[Umar Parooq]

I am in.

On Fri, Apr 13, 2018, 10:52 PM Abhishek Sharma 
wrote:

> Hello!
>
> So I have been working on the wireframes for the revamped Fedora
> Community App
> 
> (as a part of my GSoC proposal) and I am ready to share the V1.
>
> I need some people to volunteer for the wireframe testing. In the process,
> you will be asked to do very simple tasks (which will hardly take 2
> minutes) on a clickable prototype. I can learn from the insights of testing
> to iterate on the design of the application. Basically what's working and
> what's not. I believe to design the best UX, we need to pay attention to
> what users do.
>
> Please reply to this email if you're interested so that I can invite you
> for the testing.
>
> Thanks :-)
>
> Best,
> Abhishek
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Anyone interested in Testing the wireframes of the Fedora Community App?

[Abhishek Sharma]

Sent you the invite, Umar. Thanks!

Will love to see more participation from the community :-)

On Sat, Apr 14, 2018 at 3:29 AM, Umar Parooq 
wrote:

> I am in.
>
> On Fri, Apr 13, 2018, 10:52 PM Abhishek Sharma 
> wrote:
>
>> Hello!
>>
>> So I have been working on the wireframes for the revamped Fedora
>> Community App
>> 
>> (as a part of my GSoC proposal) and I am ready to share the V1.
>>
>> I need some people to volunteer for the wireframe testing. In the
>> process, you will be asked to do very simple tasks (which will hardly take
>> 2 minutes) on a clickable prototype. I can learn from the insights of
>> testing to iterate on the design of the application. Basically what's
>> working and what's not. I believe to design the best UX, we need to pay
>> attention to what users do.
>>
>> Please reply to this email if you're interested so that I can invite you
>> for the testing.
>>
>> Thanks :-)
>>
>> Best,
>> Abhishek
>> ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>>
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: How should I coordinate the package updates with you guys?

[Adam Williamson]

On Fri, 2018-04-13 at 16:42 -0500, po...@pouar.net wrote:
> On Fri, 13 Apr 2018 22:58:58 +0200
> Mathieu Bridon  wrote:
> 
> > On Fri, 2018-04-13 at 15:41 -0500, po...@pouar.net wrote:
> > > Not sure how to interpret the example email `packagename-owner@alias`
> > > . Would that be like `brotli-po...@fedoraproject.org` or
> > > `po...@fedoraproject.org` or something else? Is `fedoraproject.org`
> > > the right domain for `alias`?
> > 
> >   
> > 
> > It's ${srpmname}-ow...@fedoraproject.org, so in your case:
> > 
> > brotli-ow...@fedoraproject.org
> > 
> > 
> 
> One last question, do I need to list the whatrequires recursively and email
> those maintainers as well or just list the immediate whatrequires and
> just email those guys?

Just the immediate ones.
-- 
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

Re: FreeCAD: undefined reference to `Py::ifPyErrorThrowCxxException()'

[Mamoru TASAKA]

Richard Shaw wrote on 04/14/2018 04:38 AM:

I've posted to upstreams mailing list but have not as of yet gotten a
response.

I've run into the following error trying to build the latest version of
FreeCAD which requires python-pycxx but Rawhide now has 7.0.3 and the
bundled version appears to be 6.2.8.

I'm used to undefined references indicating that a library is missing at
the linker stage, but in the case of python-pycxx, it's a copylib. There is
no library to link to and it seems to be picking up the source and headers
at the correct location so I'm at a loss...

[ 24%] Linking CXX shared library ../../lib/libFreeCADBase.so
cd /builddir/build/BUILD/FreeCAD-0.17/build/src/Base && /usr/bin/cmake -E
cmake_link_script CMakeFiles/FreeCADBase.dir/link.txt --verbose=1
/usr/bin/c++ -fPIC -Wall -Wextra -Wno-write-strings -O2 -g -pipe -Wall
-Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS
-fexceptions -fstack-protector-strong -grecord-gcc-switches
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic
-fasynchronous-unwind-tables -fstack-clash-protection -mcet -fcf-protection
-std=c++11 -D_OCC64 -Wl,--no-undefined -shared
-Wl,-soname,libFreeCADBase.so -o ../../lib/libFreeCADBase.so
CMakeFiles/FreeCADBase.dir/usr/src/CXX/cxxextensions.c.o
CMakeFiles/FreeCADBase.dir/usr/src/CXX/cxx_extensions.cxx.o
CMakeFiles/FreeCADBase.dir/usr/src/CXX/cxxsupport.cxx.o
CMakeFiles/FreeCADBase.dir/usr/src/CXX/IndirectPythonInterface.cxx.o
CMakeFiles/FreeCADBase.dir/Axis.cpp.o
CMakeFiles/FreeCADBase.dir/AxisPyImp.cpp.o
CMakeFiles/FreeCADBase.dir/Base64.cpp.o




 CMakeFiles/FreeCADBase.dir/PyTools.c.o

CMakeFiles/FreeCADBase.dir/PreCompiled.cpp.o -lpython2.7 -lxerces-c
-lboost_filesystem -lboost_program_options -lboost_regex -lboost_signals
-lboost_system -lboost_thread -lboost_chrono -lboost_date_time
-lboost_atomic -lz -lQtCore -lutil -ldl -lzipios
BUILDSTDERR: CMakeFiles/FreeCADBase.dir/usr/src/CXX/cxx_extensions.cxx.o:
In function `Py::Object::validate()':
BUILDSTDERR: /usr/src/CXX/Python2/cxx_extensions.cxx:122: undefined
reference to `Py::ifPyErrorThrowCxxException()'
BUILDSTDERR: CMakeFiles/FreeCADBase.dir/usr/src/CXX/cxx_extensions.cxx.o:
In function
`Py::PythonExtensionBase::callOnSelf(std::__cxx11::basic_string, std::allocator > const&, Py::Object const&,
Py::Object const&, Py::Object const&, Py::Object const&, Py::Object const&,
Py::Object const&, Py::Object const&, Py::Object const&, Py::Object
const&)':
BUILDSTDERR: /usr/include/CXX/Python2/Objects.hxx:2450: undefined reference
to `Py::ifPyErrorThrowCxxException()'
BUILDSTDERR: /usr/include/CXX/Python2/Objects.hxx:2426: undefined reference
to `Py::ifPyErrorThrowCxxException()'
BUILDSTDERR: /usr/include/CXX/Python2/Objects.hxx:2426: undefined reference
to `Py::ifPyErrorThrowCxxException()'
BUILDSTDERR: /usr/include/CXX/Python2/Objects.hxx:2426: undefined reference
to `Py::ifPyErrorThrowCxxException()'
BUILDSTDERR:
CMakeFiles/FreeCADBase.dir/usr/src/CXX/cxx_extensions.cxx.o:/usr/include/CXX/Python2/Objects.hxx:2426:
more undefined references to `Py::ifPyErrorThrowCxxException()' follow
BUILDSTDERR: collect2: error: ld returned 1 exit status

Thanks,
Richard



Py::ifPyErrorThrowCxxException() is defined in
/usr/src/CXX/Python2/cxx_exceptions.cxx , so you have to also compile and
link this file.

Regards,
Mamoru

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

plan to update brotli to 1.0.4 in Rawhide

[pouar]

I'm supposed to notify you a week in advanced, which for me puts it
at 2018-04-21. the following packages will need to be rebuilt once that
happens.

golang-github-dsnet-compress
httpd
php-pecl-http
python-httpbin
webkit2gtk3
woff2


So I just announce that I'm updating the package on the day I update it
right?
-- 
GPG Keys: https://keybase.io/pouar
Tox ID:
2EA7A6D5494C10B2E0F32004A1E9CBD971777E551A902059E5EA7E73E5A299272F29D9FF5F6A
Matrix ID: @Pouar:matrix.org Social Links: https://www.pouar.net/social.php
BEGIN:VCARD
VERSION:4.0
CLASS:public
N:Dragon;Pouar;;;
X-EVOLUTION-FILE-AS:Pouar Dragon
FN:Pouar Dragon
EMAIL:po...@pouar.net
NICKNAME:Pouar
GENDER:M
URL:https://www.pouar.net
X-TWITTER:https://twitter.com/the_pouar
X-MOZILLA-HTML:FALSE
X-EVOLUTION-BLOG-URL:https://drupal.pouar.net
X-KADDRESSBOOK-BlogFeed:https://drupal.pouar.net
X-KADDRESSBOOK-OPENPGPFP:E107AB5293597577A88AB4AF725BA94668AECE69
X-KADDRESSBOOK-CRYPTOPROTOPREF:openpgp/mime
X-KADDRESSBOOK-CRYPTOSIGNPREF:alwaysIfPossible
NOTE:PGP Keys: https://keybase.io/pouar
REV:2017-04-17T14:58:50Z(8)
END:VCARD


pgps2zt3UQqbk.pgp
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Test-Announce] Proposal to CANCEL: 2018-04-16 Fedora QA Meeting

[Adam Williamson]

Hi folks! I'm proposing we cancel the QA meeting on Monday. We've met
the last two weeks, and I don't think there's anything urgent on the
agenda.

If you're aware of anything important we have to discuss this week,
please do reply to this mail and we can go ahead and run the meeting.
Thanks!

There *will* be a blocker review meeting, of course.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Test-Announce] 2018-04-16 @ 16:00 UTC - Fedora 28 Blocker Review Meeting

[Adam Williamson]

# F28 Blocker Review meeting
# Date: 2018-04-16
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Hi folks! We have 6 proposed blockers and 5 proposed freeze exception
issues for Final to review, so let's have a review meeting on Monday.

If you have time this weekend, you can take a look at the proposed or
accepted blockers before the meeting -  the full lists can be found
here: https://qa.fedoraproject.org/blockerbugs/ .

We'll be evaluating these bugs to see if they violate any of the 
Release Criteria and warrant the blocking of a release if they're not 
fixed. Information on the release criteria for F28 can be found on the 
wiki [0].

For more information about the Blocker and Freeze exception process, 
check out these links:
 - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
 - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process

And for those of you who are curious how a Blocker Review Meeting 
works - or how it's supposed to go and you want to run one - check out 
the SOP on the wiki:
 - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting

Have a good weekend and see you on Monday!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org