Error in the packaging of fftw-devel-3.3.10-3.fc37.x86_64

2023-04-28 Thread Theodore Papadopoulo 

    Hi,

There seem to be some missing files in this package related to the cmake 
configuration.

Trying to detect fftw3 with cmake induces an error:

CMake Error at /usr/lib64/cmake/fftw3/FFTW3Config.cmake:13 (include):
   include could not find requested file:

 /usr/lib64/cmake/fftw3/FFTW3LibraryDepends.cmake
 Call Stack (most recent call first):
   CMakeLists.txt:113 (find_package)

 CMake Error at 
/usr/lib64/cmake/xtensor-fftw/xtensor-fftwConfig.cmake:66 (message):

   Please, select at least one of the available FFTW type libraries
 Call Stack (most recent call first):
   CMakeLists.txt:114 (find_package)

And indeed, there is no such file as:

/usr/lib64/cmake/fftw3/FFTW3LibraryDepends.cmake

in the package.

Seems to be a small packaging error

        Thank you in advance for correcting it... Tell me if I can help.

            Theo Papadopoulo.



___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

2022-07-08 Thread Theodore Papadopoulo 

On 7/6/22 08:30, Vitaly Zaitsev via devel wrote:

On 05/07/2022 21:15, Matthias Clasen wrote:
And I doubt that you'd be able to notice a 'smaller than 1% slowdown' 
on your system.


4% slowdown is unacceptable.


At least for Fedora Workstation, being
a useful system for developers with working debugging and profiling 
tools should have some weight too.


Debugging works well on Fedora without this flag.

I agree that it works well  (at least better than with most competing 
OSes), but that does not mean it works perfectly and that it's not 
improvable.
I must say that global debugging capabilities have decreased with time 
since 20 years. More and more, one needs to rely on "debugging by 
printf" because
gdb and similar tools are confused, notably because local variables are 
"optimsed out" (which I suspect is related to frame pointer). This is a 
price to
pay to better optimisation and performance, but leads to more time spent 
to find the place of a bug.


So yes it works well, but it could be better Now at which cost for 
the overall community, this is another story.


  Theo.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 33 System-Wide Change proposal: Make nano the default editor

2020-06-26 Thread Theodore Papadopoulo 
On 6/26/20 1:30 PM, Qiyu Yan wrote:
> 
> 
> Adam Williamson  > 于 2020年6月26日周五 上午9:32写道：
> 
> On Fri, 2020-06-26 at 08:44 +0800, Qiyu Yan wrote:
> > What about to provide a prompt to the user telling them the difference
> > between editors?
> > For example, when a new user to fedora first invokes git commit
> > without $EDITOR set, a program named fedora-default-editor comes up
> > and asks: Which editor do you like?
> > User can do his or hers choice and the choice will be remembered by
> > setting $EDITOR in his or hers ~/.bashrc
> >
> > The fedora-default-editor can be a small script that shows user all
> > the difference and set $EDITOR for the user.
> 
> It's a nice idea, but the problem with things like this is they
> *always* introduce bugs, and often wind up being unmaintained, because
> keeping them working is kind of a thankless task.
> 
> IMHO it's better to keep things simple and just pick a default. And the
> default should definitely be nano. :D
> 
> Then I will +1 for this proposal. Yes, this certainly will make Fedora
> easier use for beginners. And for those who would like to use vi as
> default, we should make this as easy as possible.

This seems the best approach in my opinion.
I totally agree that having something simple is important for new users.
My only fear (and it applies to any default editor choice) is that the
default will be changed only by a minority of new-users, or after many
months.

Thus having an educational approach which tells the user how to
configure his environment properly (and eventually doing it for him from
a list of choices) seems the most friendly approach.

I must add that nano feels like an old VT100 editor. Not very appealing
to new users (but indeed very clear on how to operate). My guess is that
an average user will hope to see an editor application with icons and
everything to popup (call it notepad and you will fill all his/her
expectations ;-) )... Of course, this will not work in a linux terminal,
but most new users don't even know the concept of a terminal...


0x12BF16AD4F273D5D.asc
Description: application/pgp-keys
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Self Introduction: Theo Papadopoulo

2019-12-05 Thread Theodore Papadopoulo 
On 12/5/19 2:50 PM, Theodore Papadopoulo wrote:
>   Hello,
> 
> My name is Theo Papadopoulo. I use linux based systems since 1996 and
> redhat/fedora ones since so long I do not quite remember (2005-2007?).
> Fedora is used within the research group (and actually with the research
> institute where I am) I belong to as the main computing platform. I'm
> participating in some specialized open source project you may not even
> know (OpenMEEG, OpenViBE or medInria) and occasionally helped in some
> more widespread - to somne extent - ones (blitz, matio, xtensor). I even
> have a very minor contribution to gcc years ago
> 
> Given this context, I often maintain a set of rpms for the group I
> belong. Very often those are packages that we need internally. But
> sometimes, this is just to cope with some orphaned fedora packages I'd
> like to give back to the community if possible
> 
>   All the best,
> 

And to reply to myself, here are (just the specs) of two packages I'd
like to un-retire. The first one is liblsl which is updated just a few
days ago and which was orpaned very recently). The second one itpp was
orphaned quite some time ago, and maybe about 1 year ago I had some
review on a new itpp spec file that probably needs to be updated now.

Those are the two packages I'd like to see back in fedora. I'd prefer to
co-maintain them if possible (for itpp I suspect they is no longer a
packager, for liblsl the packager seems to have been unresponsive to all
messages prior to the retiring of the package). If not, if someone could
sponsor me, I will try to do my best to regularly update those two
which should not belong to any critical path as they are retired (so I
guess there is little risk for me to harm the whole distribution).

Regards,

Theo.

%global version_major 1
%global version_minor 13
%global version_patch 0
%global version_release b13

Name:		liblsl
Version:	%{version_major}.%{version_minor}.%{version_patch}.%{version_release}
Release:	1%{?dist}
Summary:	Lab streaming layer API

License:	MIT
URL:		https://github.com/sccn/labstreaminglayer

# Source archived from git repo, excluding external libraries like boost:
# git clone https://github.com/sccn/labstreaminglayer.git
# cd labstreaminglayer/LSL/liblsl
# git archive --prefix=%%{name}-%%{version}/ %%{version} . | xz > %%{SOURCE0}
Source0:	%{name}-%{version}.tar.xz
Patch0:		liblsl-1.13.0-use_system_pugixml.patch
Patch1:		liblsl-1.13.0-install.patch

BuildRequires:  gcc-c++
BuildRequires:	boost-devel
BuildRequires:	cmake
BuildRequires:	dos2unix
BuildRequires:	pugixml-devel

Provides:	bundled(boost-endian)
Provides:	bundled(portable-archive)

%description
The lab streaming layer is a simple all-in-one approach to streaming experiment
data between applications in a lab, e.g. instrument time series, event markers,
audio, and so on.


%package devel
Summary:	Lab streaming layer API development files
Requires:	%{name}%{?_isa} = %{version}-%{release}

%description devel
Development files for liblsl.


%prep
%autosetup -p1
dos2unix CHANGELOG README.md LICENSE
find examples -type f \( -name '*.c' -o -name '*.cpp' \) -exec \
dos2unix {} \;
find examples -type f \( -name '*.c' -o -name '*.cpp' \) -exec \
sed -i '/^#include/s|\.\./\.\./\.\./include/||' {} \;
find examples -type f -name '*.vcproj' -delete
find examples -type f -name '*.vcxproj' -delete
find examples -type d -name '*.xcodeproj' -exec rm -rf {} +


%build
mkdir build
pushd build
%cmake \
-DLSL_NO_FANCY_LIBNAME=ON\
-DUSE_SYSTEM_BOOST=ON \
..
%make_build
popd


%install
pushd build
%make_install
popd


%ldconfig_scriptlets


%files
%license LICENSE src/portable_archive/license.txt
%doc CHANGELOG README.md
%{_libdir}/*.so.*
%{_bindir}/*

%files devel
%doc examples
%{_includedir}/%{name}
%{_libdir}/*.so
%{_datadir}/*


%changelog
* Tue Dec 3 2019 Theodore Papadopoulo  - 1.13.0.b13-1
- New upstream release (tag 1.13.0-b13)

* Thu Jul 25 2019 Fedora Release Engineering  - 1.12.0-6
- Rebuilt for https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild

* Fri Feb 01 2019 Fedora Release Engineering  - 1.12.0-5
- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild

* Fri Jul 13 2018 Fedora Release Engineering  - 1.12.0-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild

* Thu Jun 14 2018 Dmitry Mikhirev  - 1.12.0-3
- Fix build with boost 1.66+ (#1556596)

* Wed Feb 07 2018 Fedora Release Engineering  - 1.12.0-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild

* Sun Nov 26 2017 Dmitry Mikhirev  - 1.12.0-1
- New upstream release (#1504351)
- Convert line endings in examples to unix format

* Thu Aug 03 2017 Fedora Release Engineering  - 1.11.0-10
- Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Binutils_Mass_Rebuild

* Wed Jul 26 2017 Fedora Release Engineering  - 1.11.0-9
- Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild

Self Introduction: Theo Papadopoulo

2019-12-05 Thread Theodore Papadopoulo 
Hello,

My name is Theo Papadopoulo. I use linux based systems since 1996 and
redhat/fedora ones since so long I do not quite remember (2005-2007?).
Fedora is used within the research group (and actually with the research
institute where I am) I belong to as the main computing platform. I'm
participating in some specialized open source project you may not even
know (OpenMEEG, OpenViBE or medInria) and occasionally helped in some
more widespread - to somne extent - ones (blitz, matio, xtensor). I even
have a very minor contribution to gcc years ago

Given this context, I often maintain a set of rpms for the group I
belong. Very often those are packages that we need internally. But
sometimes, this is just to cope with some orphaned fedora packages I'd
like to give back to the community if possible

All the best,

Theo.


0x12BF16AD4F273D5D.asc
Description: application/pgp-keys
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Unorphan instructions

2019-12-04 Thread Theodore Papadopoulo 
On 12/4/19 12:11 PM, Miro Hrončok wrote:
> On 04. 12. 19 11:28, Fabio Valentini wrote:
>> Doesn't the new "Take" button at
>> https://src.fedoraproject.org/rpms/eclipse-avr work, so we don't have
>> to bother releng anymore?
>> It's at the bottom of the left navigation area.
> 
> I have updated the instructions:
> 
> https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#Claiming_Ownership_of_an_Orphaned_Package

Well, I need a little bit more on this page. This page is for
maintainers only... What would be the procedure for a non-maintainer to
ask/help for unretirement of a package. It would be nice if the page
could have some links for that...

I'm mostly interested in two packages at this time:
- the first one is liblsl which has been retired fairly recently
(november 2019). It seems that the maintainer has been unresponsive. As
I need this package,  and as it seems that the project is still active,
I refreshed the spec to build the new 1.13 release (the beta 13
actually). This release seems much  more simpler to do than the former
one (less patch).
- the second one is itpp which has been retired quite some time ago.

I need the two and have update the specs I obtained from fedpkg. Is
there a way (not too complicated) for me to give back that work to the
community and to help in the "un-retiration" of these two packages ???

Theo.


0x12BF16AD4F273D5D.asc
Description: application/pgp-keys
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Destop environment and gl performance...

2019-05-29 Thread Theodore Papadopoulo 
Can someone explain why the destop environment (here Cinnamon) can have
such an impact on the graphic card performance ?

Using glmark, we see a 2x to 20x factor in glmark performance between
various destops (mate,xlfce,cinnamon). What can justify such a huge gap
in perfs ?

Even better is there a way to investigate the GPU usage (a la ps or top)
to understand such issues ?

Thank's in advance..

Theo.


0x12BF16AD4F273D5D.asc
Description: application/pgp-keys
___
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

Packaging problem in pybind11-devel ?

2019-04-30 Thread Theodore Papadopoulo 
Before submitting a bugzilla, I wonder whether this is a choice made on
purpose or not.

The pybind11-devel package defines a set of CMake Module files. But (at
least for fedora 29) these files do not end up in
/usr/share/cmake/Modules as usually but in /usr/share/cmake/pybind11
where cmake does not find them by default... This seems non standard...
Is this on purpose ?

rpm -ql pybind11-devel-2.2.4-1.fc29.x86_64

[...]
/usr/share/cmake/pybind11
/usr/share/cmake/pybind11/FindPythonLibsNew.cmake
/usr/share/cmake/pybind11/pybind11Config.cmake
/usr/share/cmake/pybind11/pybind11ConfigVersion.cmake
/usr/share/cmake/pybind11/pybind11Targets.cmake
/usr/share/cmake/pybind11/pybind11Tools.cmake
[...]

Thank's

Theo.


0x12BF16AD4F273D5D.asc
Description: application/pgp-keys
___
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

Re: /etc/yum.repos.d -> /etc/distro.repos.d

2019-03-13 Thread Theodore Papadopoulo 
On 3/13/19 4:03 PM, mcatanz...@gnome.org wrote:
> On Wed, Mar 13, 2019 at 7:50 AM, Kalev Lember 
> wrote:
>> Please don't, it's just pointless renaming that invalidates all end user
>> documentation and makes it harder for other programs such as packagekit
>> and gnome-software that all need to adopt for the new paths.
> 
> Handling a rename is not exactly rocket science. Why would this be at
> all problematic? The change is proposed for F31, not F30. That's plenty
> of time. If this is the last remaining usage of "yum" in the distro then
> let's get rid of it and move on. Since both locations should be read, it
> should be fully backwards-compatible anyway.

It is reasonable to introduce a better name for the repo and
/etc/distro.repos.d seems to be a nice and clearer one. It furthermore
somewhat stresses that it is not related to a specific tool (yum) which
is indeed the case since packagekit and others also use it.

So creating the new directory (1) -- provided everyone agrees on the
name -- and putting the repo files in it is nice and not complicated or
dangerous.

A different question is migration of all tools/documentation to this new
directory. Fortubately, there is a simple solution. Make a symbolic link
from the old directory to the new. Adding this symbolic link (2) ensures
that everything works smoothly immediately (and conveys the message that
the "true" directory changed).

A third question (3) is when to suppress the symbolic link. Nothing
requires that this is immediate (except eventually some aesthetics). It
can last as long as needed to ensure that all tools are migrated and
that the name change is sufficiently documented (there will be always
old web ressources that will remain with the old name, but if the new
name appears often enough on web searches, that's OK).

I believe that (1) and (2) can be done immediately and could be consensual.

(3) can be dealt much later

Theo.


0x12BF16AD4F273D5D.asc
Description: application/pgp-keys
___
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

JSharing some poor experience

2018-07-19 Thread Theodore Papadopoulo 
Hello,

I recently upgraded my computer to Fedora 28 and experienced some
strange behaviour with the cinnamon deskop when having two screens.
On the second screen there was a black "border" around windows (eg
terminals) that was flickering and expanding eg when the mouse was
moving

This was somewhat unpleasant but manageable... Today, it started
bothering me a little, so I did a little search and found (rather easily
once I had the right keywords):

https://fedoraproject.org/wiki/Changes/VA-API_1.0.0

which clearly states that for intel graphic cards, it is necessary to
install libva-intel-driver which is only available from rpmfusion-free.
In my case, it was not installed, so I guess the troubles were coming
from the software rendering...

What I find strange is that fedora 28 depends (in my configuration with
the two external screen configuration, which is probably not that
common) on something which is outside it repositories to properly
function. And the information on this new dependency is not very
explicit (eg in the release notes as far as I can tell).

I just wanted to share this small glitch for others that might have
encountered the same problem and in the hope that this situation can
improve so that it become invisible to the end-user. For example, can
the rpm migrate to fedora repos since it's free and the proper
dependency is added, so that it is installed by default with desktops
(or the desktops that need it) ? Or otherwise, fix the software
rendering (which is probably more difficult and more work).

Otherwise Fedora 28 is so far a great vintage... Tahnk you for all the
great work.

Theo.


0x12BF16AD4F273D5D.asc
Description: application/pgp-keys
___
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/ESPOSV4DX76FYZEA4PZQR35FTX6UUMDP/

Re: Unretiring itpp

2017-01-23 Thread Theodore Papadopoulo 
On 01/23/2017 04:51 PM, Alexander Ploumistos wrote:
> It might feel like I'm splitting hairs, but please bear with me.

No, no it's me that have not understood your previous request. I had not
realized how much the guidelines might have changed these last years,
and I learnt a lot (even though I might not remember all of it).

I really appreciated all the comments I got. Thanks again to all.

So here are the last versions.

Then if there is a agreement, I'll need some advice on how to proceed
next...

Again thank's lot

Theo.
Name:   itpp
Version:4.3.1
Release:1%{?dist}
Summary:C++ library for math, signal/speech processing, and communications

License:GPLv3
URL:http://itpp.sourceforge.net/
Source: http://downloads.sourceforge.net/itpp/%{name}-%{version}.tar.bz2
# Taken from upstream at:
# https://sourceforge.net/p/itpp/git/ci/8ff787c218c31ad90c51c2da54085e79bb7fd1b3/
Patch1: itpp-lib64.patch

BuildRequires:  gcc-gfortran, atlas-devel, fftw-devel
BuildRequires:  tetex-latex
BuildRequires:  cmake, doxygen, ghostscript

%description
IT++ is a C++ library of mathematical, signal processing, speech
processing, and communications classes and functions.  The kernel of
the IT++ library is built upon templated vector and matrix classes
with many functions for their manipulation.  Such a kernel makes IT++
similar to Octave.  IT++ makes extensive use of existing open-source
libraries (but not only) for increased functionality, speed, and
accuracy.


%package devel
Summary:Development files for itpp
Requires:   %{name}%{?_isa} = %{version}-%{release}
Requires:   fftw-devel%{?_isa}, atlas-devel%{?_isa}, gcc-gfortran%{?_isa}

%description devel
This package contains the itpp header files, libs, and man pages.


%package doc
Summary:Documentation for itpp
BuildArch:  noarch

%description doc
This package contains the documentation for itpp.


%prep
%setup -q
%patch1 -p1 -b .lib64

%build
mkdir -p %{_target_platform}
pushd %{_target_platform}
%cmake -DBLA_VENDOR=ATLAS -DCMAKE_BUILD_TYPE=Release ..
popd
make -C %{_target_platform} %{?_smp_mflags}

%install
make -C %{_target_platform} install DESTDIR=$RPM_BUILD_ROOT


%post -p /sbin/ldconfig

%postun -p /sbin/ldconfig


%files
%{!?_licensedir:%global license %doc}
%doc AUTHORS ChangeLog NEWS README
%license COPYING
%{_libdir}/*.so.*
%{_datadir}/%{name}

%files devel
%{_includedir}/%{name}
%{_libdir}/*.so
%{_libdir}/pkgconfig/%{name}.pc
%{_bindir}/%{name}-config
%{_mandir}/man1/*

%files doc
%dir %{_docdir}/%{name}
%{_docdir}/%{name}/html/

%changelog
* Sun Jan 22 2017 Theodore Papadopoulo <theodore.papadopo...@inria.fr> - 4.3.1-1
- Switch to version 4.3.1
- Adapt to cmake build.

* Wed Jan 18 2017 BogusDateBot
- Eliminated rpmbuild "bogus date" warnings due to inconsistent weekday,
  by assuming the date is correct and changing the weekday.
  Tue Sep 13 2006 --> Tue Sep 12 2006 or Wed Sep 13 2006 or Tue Sep 19 2006 or 
  Sun Oct 28 2006 --> Sun Oct 22 2006 or Sat Oct 28 2006 or Sun Oct 29 2006 or 

* Wed Feb 09 2011 Fedora Release Engineering <rel-...@lists.fedoraproject.org> - 4.0.6-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_15_Mass_Rebuild

* Fri Jul 24 2009 Fedora Release Engineering <rel-...@lists.fedoraproject.org> - 4.0.6-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_12_Mass_Rebuild

* Fri Apr 24 2009 Milos Jakubicek <xja...@fi.muni.cz> - 4.0.6-1
- Fix FTBFS:
- Update to 4.0.6 bugfix release
- Dropped itpp-gcc43.patch (merged upstream).
- Added itpp-gcc44.patch

* Wed Feb 25 2009 Fedora Release Engineering <rel-...@lists.fedoraproject.org> - 4.0.0-7
- Rebuilt for https://fedoraproject.org/wiki/Fedora_11_Mass_Rebuild

* Mon Dec 15 2008 Deji Akingunola <dakin...@gmail.com> - 4.0.0-6
- Rebuild for atlas-3.8.2

* Sun Sep 14 2008 Manuel "lonely wolf" Wolfshant <wo...@fedoraproject.org> - 4.0.0-5
- Fix building with gcc4.3

* Fri May 23 2008 Jon Stanley <jonstan...@gmail.com> - 4.0.0-4
- Fix license tag

* Mon Feb 18 2008 Fedora Release Engineering <rel-...@fedoraproject.org> - 4.0.0-3
- Autorebuild for GCC 4.3

* Sun Dec  9 2007  Ed Hill <e...@eh3.com> - 4.0.0-2
- fix hard-coded libdir error

* Sun Dec  9 2007  Ed Hill <e...@eh3.com> - 4.0.0-1
- new upstream 4.0.0

* Sat Aug 25 2007  Ed Hill <e...@eh3.com> - 3.10.12-1
- new upstream 3.10.12

* Tue Apr 17 2007  Ed Hill <e...@eh3.com> - 3.10.10-1
- new upstream 3.10.10

* Tue Apr 17 2007  Ed Hill <e...@eh3.com> - 3.10.9-2
- fix dir ownership per bz #233842

* Sun Mar 18 2007  Ed Hill <e...@eh3.com> - 3.10.9-1
- new upstream 3.10.9

* Sat Feb 10 2007  Ed Hill <e...@eh3.com> - 3.10.8-1
- new upstream 3.10.8

* Wed Dec  6 2006  Ed Hill <e...@eh3.com> - 3.10.7-1
- new upstream 3.10.7

* Sat Oct 28 2006  Ed Hill <e...@eh3.com> - 3.10.6-1
- new upstream 3.10.6

*

Re: Unretiring itpp

2017-01-23 Thread Theodore Papadopoulo 
On 01/22/2017 08:11 PM, Alexander Ploumistos wrote:
> Almost there, still some light reading ahead:
> http://fedoraproject.org/wiki/Packaging:Guidelines#Changelogs
> 
> You need to amend your changelog entry heading to match one of the
> styles mentioned there, the most common being
> 
> * Sun Jan 22 2017 Theodore.Papadopoulo  - 
> 4.3.1-1
> 
> As Michael Schwendt pointed out earlier, your release tags should
> start at 1, not 0.
> https://fedoraproject.org/wiki/Packaging:Versioning#Release_Tag

Oups. That was a remainder of the previous version which I mistakenly
forgot to change.

> There is a school of thought that adheres to git-style, imperative,
> present tense log entries, e.g. "- Switch to version 4.3.1" instead of
> "- Switched to version 4.3.1", though I've seen compelling arguments
> for using the past tense. This is mostly a matter of personal
> preference, but do try to be consistent.
.
Personally, I do not care. I find that the use of the past tense is more
consistent with the remainder of the ChangeLog (Dropped, Added, ...).
But again, I really do not care, so will do what is aviced as best practise.


Theo.
Name:   itpp
Version:4.3.1
Release:1%{?dist}
Summary:C++ library for math, signal/speech processing, and communications

License:GPLv3
URL:http://itpp.sourceforge.net/
Source: http://downloads.sourceforge.net/itpp/%{name}-%{version}.tar.bz2
# Taken from upstream at:
# https://sourceforge.net/p/itpp/git/ci/8ff787c218c31ad90c51c2da54085e79bb7fd1b3/
Patch1: itpp-lib64.patch

BuildRequires:  gcc-gfortran, atlas-devel, fftw-devel
BuildRequires:  tetex-latex
BuildRequires:  cmake, doxygen, ghostscript

%description
IT++ is a C++ library of mathematical, signal processing, speech
processing, and communications classes and functions.  The kernel of
the IT++ library is built upon templated vector and matrix classes
with many functions for their manipulation.  Such a kernel makes IT++
similar to Octave.  IT++ makes extensive use of existing open-source
libraries (but not only) for increased functionality, speed, and
accuracy.


%package devel
Summary:Development files for itpp
Requires:   %{name}%{?_isa} = %{version}-%{release}
Requires:   fftw-devel%{?_isa}, atlas-devel%{?_isa}, gcc-gfortran%{?_isa}

%description devel
This package contains the itpp header files, libs, and man pages.


%package doc
Summary:Documentation for itpp
BuildArch:  noarch

%description doc
This package contains the documentation for itpp.


%prep
%setup -q
%patch1 -p1 -b .lib64

%build
mkdir -p %{_target_platform}
pushd %{_target_platform}
%cmake -DBLA_VENDOR=ATLAS -DCMAKE_BUILD_TYPE=Release ..
popd
make -C %{_target_platform} %{?_smp_mflags}

%install
make -C %{_target_platform} install DESTDIR=$RPM_BUILD_ROOT


%post -p /sbin/ldconfig

%postun -p /sbin/ldconfig


%files
%{!?_licensedir:%global license %doc}
%doc AUTHORS ChangeLog NEWS README
%license COPYING
%{_libdir}/*.so.*
%{_datadir}/%{name}

%files devel
%{_includedir}/%{name}
%{_libdir}/*.so
%{_libdir}/pkgconfig/%{name}.pc
%{_bindir}/%{name}-config
%{_mandir}/man1/*

%files doc
%dir %{_docdir}/%{name}
%{_docdir}/%{name}/html/

%changelog
* Sun Jan 22 2017 theodore.papadopo...@inria.fr - 4.3.1-1
- Switch to version 4.3.1
- Adapt to cmake build.

* Wed Jan 18 2017 BogusDateBot
- Eliminated rpmbuild "bogus date" warnings due to inconsistent weekday,
  by assuming the date is correct and changing the weekday.
  Tue Sep 13 2006 --> Tue Sep 12 2006 or Wed Sep 13 2006 or Tue Sep 19 2006 or 
  Sun Oct 28 2006 --> Sun Oct 22 2006 or Sat Oct 28 2006 or Sun Oct 29 2006 or 

* Wed Feb 09 2011 Fedora Release Engineering  - 4.0.6-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_15_Mass_Rebuild

* Fri Jul 24 2009 Fedora Release Engineering  - 4.0.6-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_12_Mass_Rebuild

* Fri Apr 24 2009 Milos Jakubicek  - 4.0.6-1
- Fix FTBFS:
- Update to 4.0.6 bugfix release
- Dropped itpp-gcc43.patch (merged upstream).
- Added itpp-gcc44.patch

* Wed Feb 25 2009 Fedora Release Engineering  - 4.0.0-7
- Rebuilt for https://fedoraproject.org/wiki/Fedora_11_Mass_Rebuild

* Mon Dec 15 2008 Deji Akingunola  - 4.0.0-6
- Rebuild for atlas-3.8.2

* Sun Sep 14 2008 Manuel "lonely wolf" Wolfshant  - 4.0.0-5
- Fix building with gcc4.3

* Fri May 23 2008 Jon Stanley  - 4.0.0-4
- Fix license tag

* Mon Feb 18 2008 Fedora Release Engineering  - 4.0.0-3
- Autorebuild for GCC 4.3

* Sun Dec  9 2007  Ed Hill  - 4.0.0-2
- fix hard-coded libdir error

* Sun Dec  9 2007  Ed Hill  - 4.0.0-1
- new upstream 4.0.0

* Sat Aug 25 2007  Ed Hill  - 3.10.12-1
- new upstream

Re: Unretiring itpp

2017-01-22 Thread Theodore Papadopoulo 
OK. Thank's for the quick reply. Here is the updated spec.


On 01/22/2017 04:01 PM, Alexander Ploumistos wrote:
> On Sun, Jan 22, 2017 at 4:31 PM, Theodore Papadopoulo
> <theodore.papadopo...@inria.fr> wrote:
>> OK, I hope I have taken into acount of all suggestions except one (I
>> found nothing on %licence in %files).
> 
> "If the source package includes the text of the license(s) in its own
> file, then that file, containing the text of the license(s) for the
> package must be included in %license."
> (taken from https://fedoraproject.org/wiki/Packaging:LicensingGuidelines )
> 
> You should change
> 
> %files
> %doc COPYING AUTHORS ChangeLog NEWS README
> 
> to
> 
> %files
> %license COPYING
> %doc AUTHORS ChangeLog NEWS README
> 
> I think that if you're packaging for EPEL you may also need
> 
> %{!?_licensedir:%global license %doc}
> 
> right after %files, but I'm not sure if it's needed any more.
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> 

Name:   itpp
Version:4.3.1
Release:1%{?dist}
Summary:C++ library for math, signal/speech processing, and communications

License:GPLv3
URL:http://itpp.sourceforge.net/
Source: http://downloads.sourceforge.net/itpp/%{name}-%{version}.tar.bz2
# Taken from upstream at:
# https://sourceforge.net/p/itpp/git/ci/8ff787c218c31ad90c51c2da54085e79bb7fd1b3/
Patch1: itpp-lib64.patch

BuildRequires:  gcc-gfortran, atlas-devel, fftw-devel
BuildRequires:  tetex-latex
BuildRequires:  cmake, doxygen, ghostscript

%description
IT++ is a C++ library of mathematical, signal processing, speech
processing, and communications classes and functions.  The kernel of
the IT++ library is built upon templated vector and matrix classes
with many functions for their manipulation.  Such a kernel makes IT++
similar to Octave.  IT++ makes extensive use of existing open-source
libraries (but not only) for increased functionality, speed, and
accuracy.


%package devel
Summary:Development files for itpp
Requires:   %{name}%{?_isa} = %{version}-%{release}
Requires:   fftw-devel%{?_isa}, atlas-devel%{?_isa}, gcc-gfortran%{?_isa}

%description devel
This package contains the itpp header files, libs, and man pages.


%package doc
Summary:Documentation for itpp
BuildArch:  noarch

%description doc
This package contains the documentation for itpp.


%prep
%setup -q
%patch1 -p1 -b .lib64

%build
mkdir -p %{_target_platform}
pushd %{_target_platform}
%cmake -DBLA_VENDOR=ATLAS -DCMAKE_BUILD_TYPE=Release ..
popd
make -C %{_target_platform} %{?_smp_mflags}

%install
make -C %{_target_platform} install DESTDIR=$RPM_BUILD_ROOT


%post -p /sbin/ldconfig

%postun -p /sbin/ldconfig


%files
%{!?_licensedir:%global license %doc}
%doc AUTHORS ChangeLog NEWS README
%license COPYING
%{_libdir}/*.so.*
%{_datadir}/%{name}

%files devel
%{_includedir}/%{name}
%{_libdir}/*.so
%{_libdir}/pkgconfig/%{name}.pc
%{_bindir}/%{name}-config
%{_mandir}/man1/*

%files doc
%dir %{_docdir}/%{name}
%{_docdir}/%{name}/html/

%changelog
* Sun Jan 22 2017 theodore.papadopo...@inria.fr = 4.3.1-0
- Switched to version 4.3.1
- Adapted to cmake build.

* Wed Jan 18 2017 BogusDateBot
- Eliminated rpmbuild "bogus date" warnings due to inconsistent weekday,
  by assuming the date is correct and changing the weekday.
  Tue Sep 13 2006 --> Tue Sep 12 2006 or Wed Sep 13 2006 or Tue Sep 19 2006 or 
  Sun Oct 28 2006 --> Sun Oct 22 2006 or Sat Oct 28 2006 or Sun Oct 29 2006 or 

* Wed Feb 09 2011 Fedora Release Engineering <rel-...@lists.fedoraproject.org> - 4.0.6-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_15_Mass_Rebuild

* Fri Jul 24 2009 Fedora Release Engineering <rel-...@lists.fedoraproject.org> - 4.0.6-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_12_Mass_Rebuild

* Fri Apr 24 2009 Milos Jakubicek <xja...@fi.muni.cz> - 4.0.6-1
- Fix FTBFS:
- Update to 4.0.6 bugfix release
- Dropped itpp-gcc43.patch (merged upstream).
- Added itpp-gcc44.patch

* Wed Feb 25 2009 Fedora Release Engineering <rel-...@lists.fedoraproject.org> - 4.0.0-7
- Rebuilt for https://fedoraproject.org/wiki/Fedora_11_Mass_Rebuild

* Mon Dec 15 2008 Deji Akingunola <dakin...@gmail.com> - 4.0.0-6
- Rebuild for atlas-3.8.2

* Sun Sep 14 2008 Manuel "lonely wolf" Wolfshant <wo...@fedoraproject.org> - 4.0.0-5
- Fix building with gcc4.3

* Fri May 23 2008 Jon Stanley <jonstan...@gmail.com> - 4.0.0-4
- Fix license tag

* Mon Feb 18 2008 Fedora Release Engineering <rel-...@fedoraproject.org> - 4.0.0-3
- Autorebuild for GCC 4.3

* Sun Dec  9 2007  Ed Hill <e...@eh3.com> - 4.0.0-2
- fix hard-coded libdir error

* Sun Dec  9 2007  Ed Hill <e...@

Re: Unretiring itpp

2017-01-22 Thread Theodore Papadopoulo 
OK, I hope I have taken into acount of all suggestions except one (I
found nothing on %licence in %files). For now I have made the
4.3.1+patch version as the git repo, while it indeed solves the place
where are installed libraries, does not put correct values in
itpp-config and itpp.pc. Beside the patch needed to correct this I have
a git version of the patch that I attach also here. I will submit the
necessary change to itpp with the hope it will be integrated rapidly so
as to avoid having to patch the git version.

Again thank's for all the comments I gathered so far.

Theo.
Name:   itpp
Version:4.3.1
Release:1%{?dist}
Summary:C++ library for math, signal/speech processing, and communications

License:GPLv3
URL:http://itpp.sourceforge.net/
Source: http://downloads.sourceforge.net/itpp/%{name}-%{version}.tar.bz2
# Taken from upstream at:
# https://sourceforge.net/p/itpp/git/ci/8ff787c218c31ad90c51c2da54085e79bb7fd1b3/
Patch1: itpp-lib64.patch

BuildRequires:  gcc-gfortran, atlas-devel, fftw-devel
BuildRequires:  tetex-latex
BuildRequires:  cmake, doxygen, ghostscript

%description
IT++ is a C++ library of mathematical, signal processing, speech
processing, and communications classes and functions.  The kernel of
the IT++ library is built upon templated vector and matrix classes
with many functions for their manipulation.  Such a kernel makes IT++
similar to Octave.  IT++ makes extensive use of existing open-source
libraries (but not only) for increased functionality, speed, and
accuracy.


%package devel
Summary:Development files for itpp
Requires:   %{name}%{?_isa} = %{version}-%{release}
Requires:   fftw-devel%{?_isa}, atlas-devel%{?_isa}, gcc-gfortran%{?_isa}

%description devel
This package contains the itpp header files, libs, and man pages.


%package doc
Summary:Documentation for itpp
BuildArch:  noarch

%description doc
This package contains the documentation for itpp.


%prep
%setup -q
%patch1 -p1 -b .lib64

%build
mkdir -p %{_target_platform}
pushd %{_target_platform}
%cmake -DBLA_VENDOR=ATLAS -DCMAKE_BUILD_TYPE=Release ..
popd
make -C %{_target_platform} %{?_smp_mflags}

%install
make -C %{_target_platform} install DESTDIR=$RPM_BUILD_ROOT


%post -p /sbin/ldconfig

%postun -p /sbin/ldconfig


%files
%doc COPYING AUTHORS ChangeLog NEWS README
%{_libdir}/*.so.*
%{_datadir}/%{name}

%files devel
%{_includedir}/%{name}
%{_libdir}/*.so
%{_libdir}/pkgconfig/%{name}.pc
%{_bindir}/%{name}-config
%{_mandir}/man1/*

%files doc
%dir %{_docdir}/%{name}
%{_docdir}/%{name}/html/

%changelog
* Sun Jan 22 2017 theodore.papadopo...@inria.fr = 4.3.1-0
- Switched to version 4.3.1
- Adapted to cmake build.

* Wed Jan 18 2017 BogusDateBot
- Eliminated rpmbuild "bogus date" warnings due to inconsistent weekday,
  by assuming the date is correct and changing the weekday.
  Tue Sep 13 2006 --> Tue Sep 12 2006 or Wed Sep 13 2006 or Tue Sep 19 2006 or 
  Sun Oct 28 2006 --> Sun Oct 22 2006 or Sat Oct 28 2006 or Sun Oct 29 2006 or 

* Wed Feb 09 2011 Fedora Release Engineering  - 4.0.6-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_15_Mass_Rebuild

* Fri Jul 24 2009 Fedora Release Engineering  - 4.0.6-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_12_Mass_Rebuild

* Fri Apr 24 2009 Milos Jakubicek  - 4.0.6-1
- Fix FTBFS:
- Update to 4.0.6 bugfix release
- Dropped itpp-gcc43.patch (merged upstream).
- Added itpp-gcc44.patch

* Wed Feb 25 2009 Fedora Release Engineering  - 4.0.0-7
- Rebuilt for https://fedoraproject.org/wiki/Fedora_11_Mass_Rebuild

* Mon Dec 15 2008 Deji Akingunola  - 4.0.0-6
- Rebuild for atlas-3.8.2

* Sun Sep 14 2008 Manuel "lonely wolf" Wolfshant  - 4.0.0-5
- Fix building with gcc4.3

* Fri May 23 2008 Jon Stanley  - 4.0.0-4
- Fix license tag

* Mon Feb 18 2008 Fedora Release Engineering  - 4.0.0-3
- Autorebuild for GCC 4.3

* Sun Dec  9 2007  Ed Hill  - 4.0.0-2
- fix hard-coded libdir error

* Sun Dec  9 2007  Ed Hill  - 4.0.0-1
- new upstream 4.0.0

* Sat Aug 25 2007  Ed Hill  - 3.10.12-1
- new upstream 3.10.12

* Tue Apr 17 2007  Ed Hill  - 3.10.10-1
- new upstream 3.10.10

* Tue Apr 17 2007  Ed Hill  - 3.10.9-2
- fix dir ownership per bz #233842

* Sun Mar 18 2007  Ed Hill  - 3.10.9-1
- new upstream 3.10.9

* Sat Feb 10 2007  Ed Hill  - 3.10.8-1
- new upstream 3.10.8

* Wed Dec  6 2006  Ed Hill  - 3.10.7-1
- new upstream 3.10.7

* Sat Oct 28 2006  Ed Hill  - 3.10.6-1
- new upstream 3.10.6

* Wed Oct 11 2006  Ed Hill  - 3.10.5-7
- explicitly link with -lstdc++

* Tue Oct 10 2006  Ed Hill  - 3.10.5-6
- fix unowned

Re: Unretiring itpp

2017-01-20 Thread Theodore Papadopoulo 
On 01/20/2017 07:50 AM, Zbigniew Jędrzejewski-Szmek wrote:
> On Fri, Jan 20, 2017 at 02:32:22AM +0100, Kevin Kofler wrote:
>> Theodore Papadopoulo wrote:
>>> The only problem is that libraries got installed (as usual with cmake) in
>>> /usr/lib and not in /usr/lib64,
>>
>> Only if the CMakeLists.txt is broken. It should use LIB_INSTALL_DIR and/or 
>> LIB_SUFFIX. In this case, it was fixed back in 2014 (!):
>> https://sourceforge.net/p/itpp/git/ci/8ff787c218c31ad90c51c2da54085e79bb7fd1b3/
>> (The last release is from 2013!)
>>
>>> which I worked around with a mv (not sure this is teh best solution, but
>>> it works).
>>
>> Please fix CMakeLists.txt (just backport the upstream fix) instead.
> 
> Without looking at the repo, it sounds like packaging a git snapshot would
> be easier and better.

Is this allowed ??? I know that in many cases this is discouraged.
That would be even simpler for me. Of course, Correcting the build with
a patch is also easy. I just tried to be the less invasive.

Anyway, thank's for all the feedbacks, I'll make another version of the
spec incorporating all the comments.

Theo.




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

Re: Unretiring itpp

2017-01-19 Thread Theodore Papadopoulo 
On 01/19/2017 01:38 AM, Michael Schwendt wrote:
>> Provided I get some guidance (or readings, account settings, ...), I
>> ciuld maintain or co-maintain the package if necessary.
> [...]
> https://fedoraproject.org/wiki/Packaging:LicensingGuidelines#License_Text
> 
> 
>> %{_bindir}/%{name}-config
> 
> Needs to be checked whether it refers to /usr/lib and /usr/lib64.


Is this version better ? I think I incorporated all your suggestions +
some more that are in the same vein to what you suggested.

Theo.
Name:   itpp
Version:4.3.1
Release:1%{?dist}
Summary:C++ library for math, signal/speech processing, and communications

Group:  System Environment/Libraries
License:GPLv2+
URL:http://itpp.sourceforge.net/
Source0:http://downloads.sourceforge.net/itpp/itpp-%{version}.tar.bz2
BuildRoot:  %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
# Filed into upstream bugtracker at:
# https://sourceforge.net/tracker/?func=detail=2780001_id=37044=418758

BuildRequires:  gcc-gfortran, atlas-devel, fftw-devel
BuildRequires:  tetex-latex
BuildRequires:  cmake, doxygen, ghostscript

%description
IT++ is a C++ library of mathematical, signal processing, speech
processing, and communications classes and functions.  The kernel of
the IT++ library is built upon templated vector and matrix classes
with many functions for their manipulation.  Such a kernel makes IT++
similar to Octave.  IT++ makes extensive use of existing open-source
libraries (but not only) for increased functionality, speed, and
accuracy.


%package devel
Summary:Development files for itpp
Group:  Development/Libraries
Requires:   %{name}%{?_isa} = %{version}-%{release}
Requires:   fftw-devel%{?_isa}, atlas-devel%{?_isa}, gcc-gfortran%{?_isa}

%description devel
This package contains the itpp header files, libs, and man pages.


%package doc
Summary:Documentation for itpp
BuildArch:  noarch

%description doc
This package contains the documentation for itpp.


%prep
%setup -q

%build
%cmake -DBLA_VENDOR=ATLAS -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr
make %{?_smp_mflags}

%install
make install DESTDIR=$RPM_BUILD_ROOT
mv $RPM_BUILD_ROOT/usr/lib $RPM_BUILD_ROOT/%{_libdir}
perl -pi -e's:^libdir=\$\{exec_prefix}/lib$:libdir=\${exec_prefix}/lib64:' $RPM_BUILD_ROOT/%{_bindir}/%{name}-config 
perl -pi -e's:^libdir=/usr/lib$:libdir=/usr/lib64:' $RPM_BUILD_ROOT/%{_libdir}/pkgconfig/%{name}.pc
mkdir -p $RPM_BUILD_ROOT/%{_docdir}/%{name}
cp -p COPYING AUTHORS ChangeLog NEWS README \
  $RPM_BUILD_ROOT/%{_docdir}/%{name}


%post -p /sbin/ldconfig

%postun -p /sbin/ldconfig


%files
%dir %{_docdir}/%{name}
%{_docdir}/%{name}/[A-Z]*
%{_libdir}/*.so.*
%{_datadir}/%{name}

%files devel
%{_includedir}/%{name}
%{_libdir}/*.so
%{_libdir}/pkgconfig/%{name}.pc
%{_bindir}/%{name}-config
%{_mandir}/man1/*

%files doc
%{_docdir}/%{name}/html


%changelog
* Wed Jan 18 2017 theodore.papadopo...@inria.fr = 4.3.1-0
- Switched to version 4.3.1
- Adapted to cmake build.

* Wed Jan 18 2017 BogusDateBot
- Eliminated rpmbuild "bogus date" warnings due to inconsistent weekday,
  by assuming the date is correct and changing the weekday.
  Tue Sep 13 2006 --> Tue Sep 12 2006 or Wed Sep 13 2006 or Tue Sep 19 2006 or 
  Sun Oct 28 2006 --> Sun Oct 22 2006 or Sat Oct 28 2006 or Sun Oct 29 2006 or 

* Wed Feb 09 2011 Fedora Release Engineering  - 4.0.6-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_15_Mass_Rebuild

* Fri Jul 24 2009 Fedora Release Engineering  - 4.0.6-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_12_Mass_Rebuild

* Fri Apr 24 2009 Milos Jakubicek  - 4.0.6-1
- Fix FTBFS:
- Update to 4.0.6 bugfix release
- Dropped itpp-gcc43.patch (merged upstream).
- Added itpp-gcc44.patch

* Wed Feb 25 2009 Fedora Release Engineering  - 4.0.0-7
- Rebuilt for https://fedoraproject.org/wiki/Fedora_11_Mass_Rebuild

* Mon Dec 15 2008 Deji Akingunola  - 4.0.0-6
- Rebuild for atlas-3.8.2

* Sun Sep 14 2008 Manuel "lonely wolf" Wolfshant  - 4.0.0-5
- Fix building with gcc4.3

* Fri May 23 2008 Jon Stanley  - 4.0.0-4
- Fix license tag

* Mon Feb 18 2008 Fedora Release Engineering  - 4.0.0-3
- Autorebuild for GCC 4.3

* Sun Dec  9 2007  Ed Hill  - 4.0.0-2
- fix hard-coded libdir error

* Sun Dec  9 2007  Ed Hill  - 4.0.0-1
- new upstream 4.0.0

* Sat Aug 25 2007  Ed Hill  - 3.10.12-1
- new upstream 3.10.12

* Tue Apr 17 2007  Ed Hill  - 3.10.10-1
- new upstream 3.10.10

* Tue Apr 17 2007  Ed Hill  - 3.10.9-2
- fix dir ownership per bz #233842

* Sun Mar 18 2007  Ed Hill  - 3.10.9-1
- new upstream 3.10.9

* Sat Feb 10 2007  Ed Hill  - 3.10.8-1

Re: Unretiring itpp

2017-01-19 Thread Theodore Papadopoulo 
Thank's a lot for the review.
I will analyze all your comments and produce an updated spec file.
I need some time to understand the references you sent.

Thank's again.

Theo.

On 01/19/2017 01:38 AM, Michael Schwendt wrote:
>> Provided I get some guidance (or readings, account settings, ...), I
>> ciuld maintain or co-maintain the package if necessary.
> 
>> Release:0%{?dist}
> 
> First release of a package usually starts with 1 not 0:
> https://fedoraproject.org/wiki/Packaging:Versioning#Release_Tag
> 
>> %package devel
>> Requires:   %{name} = %{version}-%{release}
> 
> https://fedoraproject.org/wiki/Packaging:Guidelines#Requiring_Base_Package
> 
>> Requires:   pkgconfig
> 
> If there are pkgconfig .pc files included in that package, there will
> be automatic Provides/Requires for pkgconfig and the inter-dependencies
> as specified within the .pc files.
> 
>> Requires:   fftw-devel, atlas-devel, gcc-gfortran
> 
> You may want to make them arch-specific, too.
> 
>> %package doc
>> Summary:Documentation for itpp
>> Group:  Development/Libraries
> 
> Wrong group tag for Documentation packages, and the Group tag is not
> necessary for a long time:
> https://fedoraproject.org/wiki/Packaging:Guidelines#Tags_and_Sections
> 
> Most likely, you also want to make this subpackage "BuildArch: noarch".
> 
>> Requires:   %{name} = %{version}-%{release}
> 
> Doubtful. Keep documentation packages free of dependencies when the
> included HTML documentation can be displayed and doesn't need the base
> package.
> 
>> %install
>> rm -rf $RPM_BUILD_ROOT
> 
> Clean up of buildroot is automatic for a long time:
> https://fedoraproject.org/wiki/Packaging:Guidelines#Tags_and_Sections
> 
>> make install DESTDIR=$RPM_BUILD_ROOT LIBDIR=$RPM_BUILD_ROOT/usr/lib64
> 
> What does the LIBDIR definition achieve when you still need to move
> the libs from /usr/lib later?
> 
>> mv $RPM_BUILD_ROOT/usr/lib $RPM_BUILD_ROOT/%{_libdir}
> 
> 
>> %clean
>> rm -rf $RPM_BUILD_ROOT/
> 
> https://fedoraproject.org/wiki/Packaging:Guidelines#Tags_and_Sections
> 
>> %files
>> %defattr(-,root,root,-)
> 
> https://fedoraproject.org/wiki/Packaging:Guidelines#File_Permissions
> 
> 
>> %dir %{_docdir}/%{name}
>> %{_docdir}/%{name}/[A-Z]*
> 
> https://fedoraproject.org/wiki/Packaging:LicensingGuidelines#License_Text
> 
> 
>> %{_bindir}/%{name}-config
> 
> Needs to be checked whether it refers to /usr/lib and /usr/lib64.
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> 




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

Re: Unretiring itpp

2017-01-18 Thread Theodore Papadopoulo 
On 01/18/2017 07:01 PM, Jon Ciesla wrote:
> 
> It will need to be re-reviewed, since it's been retired more than two weeks.

Of course...

Theo.




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

Unretiring itpp

2017-01-18 Thread Theodore Papadopoulo 
Hi,

I'd like to unretire itpp(which was retired on 2011-07-25 due to
constant C++ build problems). It seems that those problems have been
solved and that as of (at least) itpp-4.3.1, it now correctly builds.

Basically I recovered the last spec from fedpkgs and adapted it to cmake
(which is now supported by itpp). As far as I can tell, it builds with
almost no troubles. The only problem is that libraries got installed (as
usual with cmake) in /usr/lib and not in /usr/lib64, which I worked
around with a mv (not sure this is teh best solution, but it works).

itpp is a veru general library for signal processing and is also used in
a brain computer interface suite called OpenVibe, which without itpp is
crippled on fedora (which is not the case on Unbutu or windows for example).

Provided I get some guidance (or readings, account settings, ...), I
ciuld maintain or co-maintain the package if necessary.

Thank you very much,

Theo Papadopoulo.
Name:   itpp
Version:4.3.1
Release:0%{?dist}
Summary:C++ library for math, signal/speech processing, and communications

Group:  System Environment/Libraries
License:GPLv2+
URL:http://itpp.sourceforge.net/
Source0:http://downloads.sourceforge.net/itpp/itpp-%{version}.tar.bz2
BuildRoot:  %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
# Filed into upstream bugtracker at:
# https://sourceforge.net/tracker/?func=detail=2780001_id=37044=418758

BuildRequires:  gcc-gfortran, atlas-devel, fftw-devel
BuildRequires:  tetex-latex
BuildRequires:  doxygen, ghostscript

%description
IT++ is a C++ library of mathematical, signal processing, speech
processing, and communications classes and functions.  The kernel of
the IT++ library is built upon templated vector and matrix classes
with many functions for their manipulation.  Such a kernel makes IT++
similar to Octave.  IT++ makes extensive use of existing open-source
libraries (but not only) for increased functionality, speed, and
accuracy.


%package devel
Summary:Development files for itpp
Group:  Development/Libraries
Requires:   %{name} = %{version}-%{release}
Requires:   pkgconfig
Requires:   fftw-devel, atlas-devel, gcc-gfortran

%description devel
This package contains the itpp header files, libs, and man pages.


%package doc
Summary:Documentation for itpp
Group:  Development/Libraries
Requires:   %{name} = %{version}-%{release}

%description doc
This package contains the documentation for itpp.


%prep
%setup -q

%build
%cmake -DBLA_VENDOR=ATLAS -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr
make %{?_smp_mflags}

%install
rm -rf $RPM_BUILD_ROOT
make install DESTDIR=$RPM_BUILD_ROOT LIBDIR=$RPM_BUILD_ROOT/usr/lib64
mv $RPM_BUILD_ROOT/usr/lib $RPM_BUILD_ROOT/%{_libdir}
mkdir -p $RPM_BUILD_ROOT/%{_docdir}/%{name}
cp -p COPYING AUTHORS ChangeLog NEWS README \
  $RPM_BUILD_ROOT/%{_docdir}/%{name}


%clean
rm -rf $RPM_BUILD_ROOT/


%post -p /sbin/ldconfig

%postun -p /sbin/ldconfig


%files
%defattr(-,root,root,-)
%dir %{_docdir}/%{name}
%{_docdir}/%{name}/[A-Z]*
%{_libdir}/*.so.*
%{_datadir}/%{name}

%files devel
%defattr(-,root,root,-)
%{_includedir}/%{name}
%{_libdir}/*.so
%{_libdir}/pkgconfig/%{name}.pc
%{_bindir}/%{name}-config
%{_mandir}/man1/*

%files doc
%defattr(-,root,root,-)
%{_docdir}/%{name}/html


%changelog
* Wed Jan 18 2017 theodore.papadopo...@inria.fr = 4.3.1-0
- Switched to version 4.3.1
- Adapted to cmake build.

* Wed Jan 18 2017 BogusDateBot
- Eliminated rpmbuild "bogus date" warnings due to inconsistent weekday,
  by assuming the date is correct and changing the weekday.
  Tue Sep 13 2006 --> Tue Sep 12 2006 or Wed Sep 13 2006 or Tue Sep 19 2006 or 
  Sun Oct 28 2006 --> Sun Oct 22 2006 or Sat Oct 28 2006 or Sun Oct 29 2006 or 

* Wed Feb 09 2011 Fedora Release Engineering  - 4.0.6-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_15_Mass_Rebuild

* Fri Jul 24 2009 Fedora Release Engineering  - 4.0.6-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_12_Mass_Rebuild

* Fri Apr 24 2009 Milos Jakubicek  - 4.0.6-1
- Fix FTBFS:
- Update to 4.0.6 bugfix release
- Dropped itpp-gcc43.patch (merged upstream).
- Added itpp-gcc44.patch

* Wed Feb 25 2009 Fedora Release Engineering  - 4.0.0-7
- Rebuilt for https://fedoraproject.org/wiki/Fedora_11_Mass_Rebuild

* Mon Dec 15 2008 Deji Akingunola  - 4.0.0-6
- Rebuild for atlas-3.8.2

* Sun Sep 14 2008 Manuel "lonely wolf" Wolfshant  - 4.0.0-5
- Fix building with gcc4.3

* Fri May 23 2008 Jon Stanley  - 4.0.0-4
- Fix license tag

* Mon Feb 18 2008 Fedora Release Engineering  - 4.0.0-3
- Autorebuild for GCC 4.3

* Sun Dec  9 2007  Ed Hill  - 4.0.0-2
- fix hard-coded libdir

Re: RFC: Change the default hostname for Fedora 26+

2016-11-10 Thread Theodore Papadopoulo 
On 11/09/2016 02:32 PM, Matthew Miller wrote:
> On Tue, Nov 08, 2016 at 03:25:58PM -0800, Andrew Lutomirski wrote:
>> If the hostname is non-constant, can we also arrange that, by default,
>> this hostname is never sent over the network?  In particular, I think
>> that DHCP requests should *not* include this hostname.  We're already
>> starting to randomize MAC addresses -- there's no reason to give a
>> persistent per-installation identifier to every network.
> 
> There's two different cases that I'm not sure how to resolve elegantly.
> On a home network or on a business network, having the name available
> is highly desirable. On a public network, just the opposite.


Add a checkbox in nm so that users can state whether they are on a
trusted network or not ??

Theo.




smime.p7s
Description: S/MIME Cryptographic Signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: DNF and PackageKit background data usage

2016-11-07 Thread Theodore Papadopoulo 
On 11/05/2016 05:01 AM, Kevin Kofler wrote:
> Theodore Papadopoulo wrote:
>> Add to this that these caches seem to be never cleaned, so that they
>> grow up very large  up to the point they prevent updating the system. I
>> just found that the packagekit cache on my machine is about 7Gb !!!
>> Probably because I do use packageit at all (dnf cache is much smaller at
>> ~700 Mb).
> 
> IMHO, this is a feature, and the DNF default behavior is the bug, a critical 
> data loss bug even! Given that Fedora does NOT keep old updates on its 
> mirrors, the only convenient way to revert a broken update is to keep ALL 
> old updates cached locally. Otherwise, you have to hunt down the old builds 
> directly in Koji. The version from the GA release is more often than not TOO 
> old, you really want the previous update.
> 
> I consider it very broken to delete files that I might still need without 
> even asking me. Setting keepcache=1 is the one of the very first things I do 
> to any new Fedora installation.

Well, if I understand well. You tell us that because fedora repos do not
keep versions of old packages, all fedora machine have to keep them
locally ?? And that just in case they want to revert a package.
Honestly, why on earth would one ask every fedora machine to have copies
of something that is not even kept in the original repo ?

To me, if the other solutions that were proposed are not OK for some
reason, it is the fedora repo policy of not keeping old updates that is
wrong

Given the usual thoughtfull posts you usually make in this list, I fear
I have not well understood what you say or I'm missing some point
Otherwise, let's not correct a bug by creating other bugs


Theo.



smime.p7s
Description: S/MIME Cryptographic Signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: DNF and PackageKit background data usage

2016-11-02 Thread Theodore Papadopoulo 
On 10/31/2016 05:10 PM, Adam Williamson wrote:
> On Mon, 2016-10-31 at 15:09 +, Richard Hughes wrote:
>>
>> I think this kind of issue is really fixed the hard way, i.e. fixing
>> bugs and adding unimplemented features rather than just adding complex
>> UI workarounds.
> 
> I think making it work as best as possible without interaction is
> great, but I'd argue that fundamentally this needs interaction. At a
> bare minimum the UI for users to mark connections as metered or
> unmetered needs to be there. Is there actually UI for this already? I
> could not find it.
> 
> The question of what the default state should be is an interesting one,
> and I bet your take on it differs substantially depending on your level
> of 'internet connection privilege'. ;)

While all of this is true, let's not forget that having two completely
different mechanisms downloading the same information in cache is the
really bad thing...





smime.p7s
Description: S/MIME Cryptographic Signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: DNF and PackageKit background data usage

2016-10-30 Thread Theodore Papadopoulo 
On 10/30/2016 02:26 AM, Adam Williamson wrote:
> There's two things I think are somewhat unfortunate here:
> 
> 1) Both dnf and GNOME Software / PackageKit default to performing
> fairly data-hungry transactions in the background, out of the box,
> without telling you about it. GNOME's is particularly bad, as it will
> happily download available updates in the background, which can be
> gigabytes worth of data. DNF only updates its metadata caches (on a
> systemd timer), but even that could be behaviour that users in certain
> circumstances really really do not want.
> 
> 2) There is no particularly obvious or visible mechanism for a 'typical
> user' (or, if you prefer, many of the target 'personas' for our
> flavors) to configure this behaviour...and you have to figure out two
> completely *different* configuration mechanisms in order to shut off
> both.

Add to this that these caches seem to be never cleaned, so that they
grow up very large  up to the point they prevent updating the system. I
just found that the packagekit cache on my machine is about 7Gb !!!
Probably because I do use packageit at all (dnf cache is much smaller at
~700 Mb).

A common cache, would be very welcome if possible. Less time, less
download volume, less used space.

Theo.



smime.p7s
Description: S/MIME Cryptographic Signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: DNF and PackageKit background data usage

2016-10-30 Thread Theodore Papadopoulo 
On 10/30/2016 02:26 AM, Adam Williamson wrote:

> * We could have some kind of configuration interface appear on install
> / first boot. This would require integration with anaconda and/or
> initial-setup and gnome-initial-setup.
> 
> * We could invert the defaults and have the apps ask the user if they
> want to enable data-hungry background operations on first interaction:
> the first time you use dnf (without -y) it could say 'hey, do you want
> to turn on background cache refreshes?' Similarly, the first time you
> run GNOME Software or click on an update notification, it could say
> 'hey, do you want to turn on background update downloads'?
> 
> * We could at least make both of them respect one single config setting
> for 'do data hungry background operations' (this is kinda one small
> part of the bigger issue that is 'dnf and PK-based stuff don't share
> any configuration aside from repo definitions').

The first two points are necessary but not sufficient at least for
people with varying internet connexions (laptops). Ideally, you'd want
to configure it per internet interface. Specifically, this is typically
the thng I do not want while being connected thought a smartphone (even
more when abroad).

So not only a first time configuration, but also an easy way to disable
it Your third point seems crucial.

Theo.




smime.p7s
Description: S/MIME Cryptographic Signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Specifying arch in comps/yumgroups.xml

2011-11-12 Thread Theodore Papadopoulo 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11/11/2011 04:31 AM, Kevin Kofler wrote:
 Theodore Papadopoulo wrote:
 I'm playing with comps to install software. I'm mostly in an
 x86-64 environment, but for compatibility I need some i386
 packages... but those seem to be invisible and I find no syntax
 that make them visible... And there seems to be no error messages
 either at createrepo time or at use time.
 
 You can do what wine does and create an x86_64 metapackage which
 Requires the i386 package you want.

Great workaround. I'll try to do that...

Thank's for the answer...

Theo.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk6+Op4ACgkQEr8WrU8nPV0GuQCfSDspHXyhsNhchTJlg8arh7gJ
u5QAoJq80Ymay8RAMOdvgtU/UDBRMQb+
=A+b8
-END PGP SIGNATURE-
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Specifying arch in comps/yumgroups.xml

2011-11-09 Thread Theodore Papadopoulo 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

I'm playing with comps to install software. I'm mostly in an x86-64
environment, but for compatibility I need some i386 packages...
but those seem to be invisible and I find no syntax that make them
visible... And there seems to be no error messages either at
createrepo time or at use time.

On the internet, I found the following message:

: sv == seth vidal skvidal at phy.duke.edu writes:
:
:sv No. It doesn't support arch syntax b/c comps doesn't support it
:sv either.
:
:Any hope of extending it in the future?  It seems reasonable to be
:able to do this, either by just listing what you would give to yum
:install or by adding a tag:
:
:packagereq type=default arch=i386ncurses/packagereq
:
:sv I can add a string to the output but there isn't one there now.
:
:It would be appreciated.  If you're short on time, feel free to point
:me at a general place in the code where I should look and I'll have a
:go.  I don't really speak Python but I'm willing to try.

Is it possible that nothing changed since 2004 ??
Is there any workaround to my problem...

Excerpt of my yumgroups.xml (the last package:

group
idImmersiveBCI/id
uservisibletrue/uservisible
nameImmersiveBCI/name
packagelist
  packagereq type=mandatoryflex/packagereq
  packagereq type=mandatorybison/packagereq
  packagereq type=mandatoryopenmpi/packagereq
  packagereq type=mandatoryopenmpi-devel/packagereq
  packagereq type=mandatoryOpenSceneGraph/packagereq
  packagereq type=mandatoryOpenSceneGraph-devel/packagereq
  packagereq type=mandatoryxxx-1.10.00-2.i386/packagereq
/packagelist
/group

Thank's in advance

Theo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk67J5EACgkQEr8WrU8nPV1LAwCffIclkpy70FNmWWxOKg2PUCT/
RZMAnR1lqm0h6OxL/w4bBok5kV35wIYf
=Isg3
-END PGP SIGNATURE-
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel