Re: Fedora 29 Beta status: RC4 incoming

2018-09-23 Thread Amit Saha 
On Thu, Sep 20, 2018 at 1:27 AM Adam Williamson
 wrote:
>
> On Wed, 2018-09-19 at 21:31 +1000, Amit Saha wrote:
> > Hi Adam,
> >
> > How do I propose
> > https://pagure.io/releng/issue/7814 as a blocker for the F29 release?
>
> It cannot be one, as that is not a release-blocking image - none of the
> vagrant boxes are.
>
> But in process terms, Zbigniew is correct. All blockers must be tracked
> through Bugzilla, so if the 'correct' issue tracker is somewhere else,
> you have to create a shadow bug in Bugzilla. Just note that the
> Bugzilla bug is for blocker/FE purposes, and point to the external
> issue. We do this quite commonly for issues where the fix will be in
> fedora-comps or fedora-kickstarts, for e.g.

Thanks Adam and Zbigniew. I proposed
https://bugzilla.redhat.com/show_bug.cgi?id=1632012 as a FE.


> --
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
> http://www.happyassassin.net
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org



-- 
http://echorand.me
___
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: Fedora 29 Beta status: RC4 incoming

2018-09-19 Thread Amit Saha 
Hi Adam,

How do I propose
https://pagure.io/releng/issue/7814 as a blocker for the F29 release?

Thanks,
Amit


On Wed, 19 Sep 2018 at 4:03 pm, Adam Williamson 
wrote:

> Hi, folks! Just a quick mail to let everyone know where we are with F29
> Beta.
>
> We managed to throw together fixes for all the currently-accepted
> blockers (thanks to the dnf team for help there), so an RC4 (aka Beta-
> 1.4) is currently composing. Compared to RC3 it contains a newer libdnf
> with a fix for https://bugzilla.redhat.com/show_bug.cgi?id=1629340 . It
> also includes a newer gnome-shell with fixes for FE bug
> https://bugzilla.redhat.com/show_bug.cgi?id=1628263 and also
> https://gitlab.gnome.org/GNOME/gnome-shell/issues/140 (which kinda
> snuck in there), new builds of dnfdragora and dnfdaemon that fix two
> significant bugs for users of those -
> https://bugzilla.redhat.com/show_bug.cgi?id=1624652 and
> https://bugzilla.redhat.com/show_bug.cgi?id=1629378 - and an
> updatedgnome-documents which actually works (that was
> https://bugzilla.redhat.com/show_bug.cgi?id=1628244 ).
>
> The second Go/No-Go meeting will be on Thursday, so it would be awesome
> if folks could pitch in and help get as much testing done as possible
> on Beta-1.4 when it arrives. There will be an announcement mail sent to
> test-announce@, so look out for that. It will have links to the
> validation pages, which have the download links at the top. General
> exploratory testing would also be great to find any significant issues
> not specifically covered in the validation tests. It should arrive in
> around 8-9 hours, assuming the compose takes about as long as the
> previous one. Some of the media will actually be available from Koji a
> little sooner than that, for anyone who wants to get a head start on
> testing; to find the live images, for instance, go to this URL:
>
>
> https://koji.fedoraproject.org/koji/tasks?state=closed=flat=createLiveMedia=-id
>
> and look for tasks with the string 'Fedora-29-20180919.0' in them (*not*
> 'Fedora-29-20180919.n.0', those would be nightlies, which don't have
> the extra fixed packages).
>
> Thanks a lot, everyone!
> --
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
> http://www.happyassassin.net
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>
-- 
http://echorand.me
___
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: poppler soname bump in rawhide

2018-08-20 Thread Amit Saha 
On Sat, Aug 18, 2018 at 8:19 PM Christian Dersch 
wrote:

> Am Di., 14. Aug. 2018 um 15:41 Uhr schrieb Marek Kasik  >:
>
>>
>>
>> On 08/14/2018 01:29 PM, Stephen Gallagher wrote:
>> > On Mon, Aug 13, 2018 at 8:32 PM Marek Kasik  wrote:
>> >
>> >> Hi,
>> >>
>> >> I'm going to rebase poppler in rawhide to poppler-0.67.0 now.
>> >>
>> >> There are several API changes and soname bump of the base library
>> >> libpoppler.so.*.
>> >>
>> >> I've checked all packages which depend on the libpoppler.so.* and have
>> >> backported/prepared fixes to reflect poppler's API changes.
>> >>
>> >> Unfortunately, libreoffice does not build currently (#1615616). But
>> I've
>> >> decided to push the rebase though because branching will happen today
>> >> and I could not do chain build after that for F29.
>> >>
>> >> Btw, if your package use the unstable API (headers from poppler-devel),
>> >> could you consider to change it to use a stable API (glib, qt, C++)?
>> >>
>> >>
>> >>
>> > Please do not push this change today. We are going to branch F29 and I'd
>> > really like to not see a whole lot of breakage at the same time.
>> >
>> > It would be best to work out the kinks in Rawhide and then merge them
>> all
>> > at once to F29 between Branching and Beta Freeze.
>>
>> Hi,
>>
>> I've already pushed the change to rawhide at night. The only problems
>> are LibreOffice and GDAL now. They don't build from source even without
>> the rebase of poppler.
>> I'm looking at the GDAL now and I see that Caolan has pushed new
>> LibreOffice to rawhide.
>>
>>
> Any news on gdal? This breaks three of the Fedora Spins: Astronomy,
> Robotic and Scientific. So please fix this asap! And please coordinate that
> better next time, poppler is known to break things… Pushing that before
> branching (and mostly without announcement, because there was no time to
> test) was not a good idea :(
>

Thanks for raising.  Asking for Fedora Scientific - should I comment out
packages which needs gdal?


> Greetings
> Christian
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/L66GQVQMIQVEHNAVN6PO6UZBMY4MZGBT/
>
___
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/TPRO753DD36IY45NBPUIRR7YTQUWPG54/

Re: [HEADS UP] Update libgit2 to 0.27

2018-08-16 Thread Amit Saha 
On Thu, Aug 16, 2018 at 7:25 PM Zbigniew Jędrzejewski-Szmek <
zbys...@in.waw.pl> wrote:

> On Thu, Aug 16, 2018 at 02:14:41PM +1000, Amit Saha wrote:
> > Hi Igor,
> >
> > On Fri, Aug 10, 2018 at 4:33 PM Igor Gnatenko <
> > ignatenkobr...@fedoraproject.org> wrote:
> >
> > > Hello everyone,
> > >
> > > 0.27.x is released long time ago, but I never got time for updating
> it. It
> > > obviously involves SONAME change.
> > >
> > > The good thing about this release is that it breaks only things in
> runtime
> > > and only one function changed signature (for building) which nobody
> uses
> > > anyway.
> > >
> > > I'm going to update library as soon as I get time (possibly on this
> > > weekend if no all dependent packages build fine). I will handle all
> > > rebuilds myself, just sending a notice.
> > >
> > > List of affected packages is below.
> > > Maintainers by package:
> > > R-git2r  qulogic
> > > geany-pluginsdmaphy ohaessler pingou
> > > ghc-bdcs-api clumens
> > > ghc-gi-ggit  dshea
> > > git-evtagignatenkobrain walters
> > > gitg ankursinha ignatenkobrain nacho pwalter
> > > julianalimilan
> > > kf5-ktexteditor  dvratil jgrulich rdieter than
> > > libgit2-glib ignatenkobrain kalev nacho pwalter
> > > python-pygit2pwalter
> > > rubygem-rugged   ignatenkobrain ktdreyer tdawson
> > > rust-exa ignatenkobrain
> > > rust-pretty-git-prompt ignatenkobrain ttomecek
> > > subsurface   pingou
> > >
> > > Packages by maintainer:
> > > ankursinha gitg
> > > clumensghc-bdcs-api
> > > dmaphy geany-plugins
> > > dshea  ghc-gi-ggit
> > > dvratilkf5-ktexteditor
> > > ignatenkobrain git-evtag gitg libgit2-glib rubygem-rugged rust-exa
> > > rust-pretty-git-prompt
> > > jgrulich   kf5-ktexteditor
> > > kalev  libgit2-glib
> > > ktdreyer   rubygem-rugged
> > > nacho  gitg libgit2-glib
> > > nalimilan  julia
> > > ohaessler  geany-plugins
> > > pingou geany-plugins subsurface
> > > pwaltergitg libgit2-glib python-pygit2
> > > qulogicR-git2r
> > > rdieterkf5-ktexteditor
> > > tdawsonrubygem-rugged
> > > than   kf5-ktexteditor
> > > ttomecek   rust-pretty-git-prompt
> > > waltersgit-evtag
> > >
> >
> > Thanks for your work. Just noticed that julia  hasn't been built
> > succesfully (
> https://koji.fedoraproject.org/koji/packageinfo?packageID=19172)
> > .  Seems to have failed with: "cc1plus: error: unrecognized command line
> > option '-mcet'"
> >
> > This is currently an issue in Fedora Scientific building. What would be
> the
> > path forward here?
>
> Drop '-mcet'? It's a bit hard to find docs for it, but [1] says:
> """-mcet -fcf-protection enables support for the Control-Flow
> -Enforcement > Technology (CET) feature in future Intel CPUs. This
> -involves the
>  generation of additional NOPs, which are ignored by the current
>  CPUs. It is recommended that you enable this flag now, to detect any
>  issues caused by them (e.g., interactions with dynamic
>  instrumentation frameworks, or performance issues)."""
>
> It sounds like it's not something that is particularly needed at this
> time.
>

https://fedoraproject.org/wiki/Changes/HardeningFlags28 seems to suggest
that this was implemented explicitly?

I am way out of touch, but a quick search for `mcet` in the package SRPM
and the source tarball from (https://src.fedoraproject.org/rpms/julia),
didn't show up `mcet` being explicitly added either.




>
> The build log also has a lot of:
> /usr/include/features.h:381:4: warning: #warning _FORTIFY_SOURCE requires
> compiling with optimization (-O) [-Wcpp]
>  #  warning _FORTIFY_SOURCE requires compiling with optimization (-O)
> ^~~
> This sounds like the package is not being built with the distro flags.
>
> Zbyszek
> ___
> 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/EK6CO5NUDCTU7JC65EFD5BI5GXOTKJKJ/
>
___
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/2PNV6Z3G6LL4IRWGS4NEMBGDQ4JHCJQT/

Re: [HEADS UP] Update libgit2 to 0.27

2018-08-15 Thread Amit Saha 
Hi Igor,

On Fri, Aug 10, 2018 at 4:33 PM Igor Gnatenko <
ignatenkobr...@fedoraproject.org> wrote:

> Hello everyone,
>
> 0.27.x is released long time ago, but I never got time for updating it. It
> obviously involves SONAME change.
>
> The good thing about this release is that it breaks only things in runtime
> and only one function changed signature (for building) which nobody uses
> anyway.
>
> I'm going to update library as soon as I get time (possibly on this
> weekend if no all dependent packages build fine). I will handle all
> rebuilds myself, just sending a notice.
>
> List of affected packages is below.
> Maintainers by package:
> R-git2r  qulogic
> geany-pluginsdmaphy ohaessler pingou
> ghc-bdcs-api clumens
> ghc-gi-ggit  dshea
> git-evtagignatenkobrain walters
> gitg ankursinha ignatenkobrain nacho pwalter
> julianalimilan
> kf5-ktexteditor  dvratil jgrulich rdieter than
> libgit2-glib ignatenkobrain kalev nacho pwalter
> python-pygit2pwalter
> rubygem-rugged   ignatenkobrain ktdreyer tdawson
> rust-exa ignatenkobrain
> rust-pretty-git-prompt ignatenkobrain ttomecek
> subsurface   pingou
>
> Packages by maintainer:
> ankursinha gitg
> clumensghc-bdcs-api
> dmaphy geany-plugins
> dshea  ghc-gi-ggit
> dvratilkf5-ktexteditor
> ignatenkobrain git-evtag gitg libgit2-glib rubygem-rugged rust-exa
> rust-pretty-git-prompt
> jgrulich   kf5-ktexteditor
> kalev  libgit2-glib
> ktdreyer   rubygem-rugged
> nacho  gitg libgit2-glib
> nalimilan  julia
> ohaessler  geany-plugins
> pingou geany-plugins subsurface
> pwaltergitg libgit2-glib python-pygit2
> qulogicR-git2r
> rdieterkf5-ktexteditor
> tdawsonrubygem-rugged
> than   kf5-ktexteditor
> ttomecek   rust-pretty-git-prompt
> waltersgit-evtag
>

Thanks for your work. Just noticed that julia  hasn't been built
succesfully (https://koji.fedoraproject.org/koji/packageinfo?packageID=19172)
.  Seems to have failed with: "cc1plus: error: unrecognized command line
option '-mcet'"

This is currently an issue in Fedora Scientific building. What would be the
path forward here?

Thanks,
Amit.





> --
>
> -Igor Gnatenko
> ___
> 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/B6YVXJV3IRIVQPHEQFPIMWDBPADR6IJ7/
>
___
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/S7ZYJYOOEDC336DB4B26YF3FAF4D7F2G/

Re: F29 Self Contained Change: FedoraScientific VagrantBox

2018-02-26 Thread Amit Saha 
> On 02/17/2018 01:38 AM, Jan Kurik wrote:
> 
> Where is this ISO?  There have been questions at ask.fpo for two 
> releases looking for this and I couldn't find them anywhere.

There hasn't been one for the last two releases due to build failures. However, 
here's a nightly: https://koji.fedoraproject.org/koji/buildinfo?buildID=1049864
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: F29 Self Contained Change: FedoraScientific VagrantBox

2018-02-26 Thread Amit Saha 
> On 02/17/2018 04:38 AM, Jan Kurik wrote:
> 
> Since a VagrantBox is a deliverable, should this be a system wide change?

Sure, I guess I can do that. I am not sure. 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Scilab, rkward install in Rawhide: nothing provides libgfortran.so.4()

2018-02-18 Thread Amit Saha 
> On Sat, Feb 17, 2018 at 11:05:39AM -0000, Amit Saha wrote:
> 
> Rebuild whatever fortran packages have failed during mass rebuild which
> should have fixed this.

Sorry - can you please clarify?

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

Scilab, rkward install in Rawhide: nothing provides libgfortran.so.4()

2018-02-17 Thread Amit Saha 
Hi all,

`scilab` and `rkward` installation in Rawhide (in the Fedora Scientific build) 
is currently failing with: nothing provides libgfortran.so.4(). I can see that 
nothing provides libgfortran.so.4 on rawhide. The reason seems to be a new 
release of libgfortran. The last libgfortran release with which these packages 
both successfully installed was: libgfortran-7.2.1-7.fc28. The current version 
is 8.0.1-0.9.fc28. 

What's the path forward here?

rkward koji: https://koji.fedoraproject.org/koji/packageinfo?packageID=4881
scilab koji: https://koji.fedoraproject.org/koji/packageinfo?packageID=12847

Thanks for your help.

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

Re: F26 System Wide Change: Python Classroom Lab

2017-02-01 Thread Amit Saha 
On Thu, 2 Feb 2017 at 5:20 am, Brian (bex) Exelbierd <b...@pobox.com> wrote:

>
>
> > On Jan 31, 2017, at 1:16 PM, Miro Hrončok <mhron...@redhat.com> wrote:
> >
> >> On 31.1.2017 09:13, Amit Saha wrote:
> >> Hello Jan,
> >>
> >> The Fedora Scientific spin already includes most  of the Python 3
> >> packages you are looking at. Is it worth looking at that instead of a
> >> new spin? I am happy to change it to use GNOME instead of KDE.
> >
> > Hi. It's not about GNOME/KDE, it's about main purpose of such lab and
> also marketing. Compare:
> >
> > > Use Fedora for teaching Python, it has a Python Clasroom Lab available
> just for that!
> >
> > With:
> >
> > > Use Fedora for teaching Python, it has a Scientific Spin that happens
> to have all the Python 3 tools needed!
>
> Phrased this way I agree with you. However, I think your wording is pretty
> harsh. I'm on a plane right now so I don't have the Scientific Spin
> marketing message in hand, but I think you could say:
>
> Teaching or learning python, the Fedora Scientific Spin is a great way to
> easily have all the tools you need. It also supports additional educational
> options with the included science components.
>
> Before pushing on this I'd like to see the Scientific Spin's build size.



As the maintainer of this spin, I would be to discuss any changes to be
suitable for meeting the needs of both target audiences.



>
> Regards,
>
> bex
>
>
>
> >
> >>
> >>
> >>
> >> Have you though
> >> On Tue, 31 Jan 2017 at 6:31 pm, Jan Kurik <jku...@redhat.com
> >> <mailto:jku...@redhat.com>> wrote:
> >>
> >>= System Wide Change: Python Classroom Lab =
> >>https://fedoraproject.org/wiki/Changes/PythonClassroomLab
> >>
> >>Change owner(s):
> >>* Miro Hrončok 
> >>* SIGs/Python <python-de...@lists.fedoraproject.org
> >><mailto:python-de...@lists.fedoraproject.org>>
> >>
> >>
> >>A new Python Classroom Lab will be created in 3 variants: Workstation
> >>based, Docker based and Vagrant based. It's an important step for our
> >>Fedora Loves Python initiative. The main audience are Python teachers
> >>and workshop instructors.
> >>
> >>
> >>== Detailed Description ==
> >>A new comps packages group with Python development tools will be
> >>created and a new Lab (or Spin) for teaching Python or Python related
> >>topics will be available from labs.fedoraproject.org
> >><http://labs.fedoraproject.org> as well as from
> >>the Docker Hub and Vagrant Atlas.
> >>
> >>A work in progress for the lab is available on GitHub.
> >>
> >>The Lab will contain:
> >>* Python 3.6 including the python3-devel package
> >>* Python 2.7 including the python2-devel package
> >>* PyPy 3
> >>* tox
> >>* virtualenv
> >>* IPython console for both Python 2 and 3
> >>* Jupyter Notebook with Python 2 and 3 kernels (if this gets into
> >>Fedora in time)
> >>* offline documentation for Python 2 and 3
> >>* basic toolchain for building C and C++ extensions and valgrind
> >>* git
> >>* nano, vim, ssh client, curl, wget
> >>* devel packages for commonly used dependencies of packages on the
> >>Python Package Index
> >>* * libxml2-devel
> >>* * libyaml-devel
> >>...
> >>
> >>The Workstation based lab will also contain:
> >>* Basic GNOME
> >>* Terminal emulator
> >>* Text editor
> >>* PDF reader
> >>* Web browser
> >>* Image viewer
> >>* ...and possibly other utilities
> >>
> >>But it will not include multimedia and virtualization support, office
> >>suite, e-mail client.
> >>
> >>
> >>== Scope ==
> >>Proposal owners:
> >>* create the comps group
> >>* create kickstarts for live and vagrant variants
> >>* create a layer for docker
> >>
> >>Other developers:
> >>* Design team: Create an image for labs.fedoraproject.org
> >><http://labs.fedoraproject.org>
> >>* Websites team: Add the new Lab to labs.fedoraproject.org
> >><http://labs.fedoraproject.org>
> >>
> >>Release enginee

Re: F26 System Wide Change: Python Classroom Lab

2017-01-31 Thread Amit Saha 
Hello Jan,

The Fedora Scientific spin already includes most  of the Python 3 packages
you are looking at. Is it worth looking at that instead of a new spin? I am
happy to change it to use GNOME instead of KDE.



Have you though
On Tue, 31 Jan 2017 at 6:31 pm, Jan Kurik  wrote:

> = System Wide Change: Python Classroom Lab =
> https://fedoraproject.org/wiki/Changes/PythonClassroomLab
>
> Change owner(s):
> * Miro Hrončok 
> * SIGs/Python 
>
>
> A new Python Classroom Lab will be created in 3 variants: Workstation
> based, Docker based and Vagrant based. It's an important step for our
> Fedora Loves Python initiative. The main audience are Python teachers
> and workshop instructors.
>
>
> == Detailed Description ==
> A new comps packages group with Python development tools will be
> created and a new Lab (or Spin) for teaching Python or Python related
> topics will be available from labs.fedoraproject.org as well as from
> the Docker Hub and Vagrant Atlas.
>
> A work in progress for the lab is available on GitHub.
>
> The Lab will contain:
> * Python 3.6 including the python3-devel package
> * Python 2.7 including the python2-devel package
> * PyPy 3
> * tox
> * virtualenv
> * IPython console for both Python 2 and 3
> * Jupyter Notebook with Python 2 and 3 kernels (if this gets into
> Fedora in time)
> * offline documentation for Python 2 and 3
> * basic toolchain for building C and C++ extensions and valgrind
> * git
> * nano, vim, ssh client, curl, wget
> * devel packages for commonly used dependencies of packages on the
> Python Package Index
> * * libxml2-devel
> * * libyaml-devel
> ...
>
> The Workstation based lab will also contain:
> * Basic GNOME
> * Terminal emulator
> * Text editor
> * PDF reader
> * Web browser
> * Image viewer
> * ...and possibly other utilities
>
> But it will not include multimedia and virtualization support, office
> suite, e-mail client.
>
>
> == Scope ==
> Proposal owners:
> * create the comps group
> * create kickstarts for live and vagrant variants
> * create a layer for docker
>
> Other developers:
> * Design team: Create an image for labs.fedoraproject.org
> * Websites team: Add the new Lab to labs.fedoraproject.org
>
> Release engineering:
> List of deliverables:
> * Labs/i386/iso/Fedora-Python-Classroom-Live-i386-_RELEASE_MILESTONE_.iso
> *
> Labs/x86_64/iso/Fedora-Python-Classroom-Live-x86_64-_RELEASE_MILESTONE_.iso
> *
> Labs/armhfp/images/Fedora-Python-Classroom-armhfp-_RELEASE_MILESTONE_-sda.raw.xz
> *
> Labs/i386/images/Fedora-Python-Classroom-Vagrant-_RELEASE_MILESTONE_.i386.vagrant-libvirt.box
> *
> Labs/i386/images/Fedora-Python-Classroom-Vagrant-_RELEASE_MILESTONE_.i386.vagrant-virtualbox.box
> *
> Labs/x86_64/images/Fedora-Python-Classroom-Vagrant-_RELEASE_MILESTONE_.x86_64.vagrant-libvirt.box
> *
> Labs/x86_64/images/Fedora-Python-Classroom-Vagrant-_RELEASE_MILESTONE_.x86_64.vagrant-virtualbox.box
> * docker images via Fedora Docker Layered image build service
>
> Policies and guidelines: nothing
>
> Trademark approval: waiting
> --
> Jan Kuřík
> Platform & Fedora Program Manager
> Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
-- 
http://echorand.me
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Rstudio

2016-02-29 Thread Amit Saha 
> SG> Hello, I like to have everything on my system in a package. So, I
> SG> looked around and found no recipe or rpm for Rstudio.
> 
> I actually just use the upstream RPMs, but I unpack and repack them to
> remove some bundled crap and some extraneous Provides:.  Might not even
> need to do that these days; I haven't checked lately.
> 
> But having it in Fedora proper would be really great.  At least I think
> it's sufficiently free.


And I would gladly include it in Fedora Scientific, right now you get
rkward and could also use Jupyter notebook for it:
http://fedora-scientific.readthedocs.org/en/latest/R_programming.html

> 
>  - J<
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Updating engineering and scientific group in comps

2015-03-09 Thread Amit Saha 
Hi,

I would like to make the following change to the engineering and scientific 
group:

diff --git a/comps-f22.xml.in b/comps-f22.xml.in
index 7b03241..af70ac6 100644
--- a/comps-f22.xml.in
+++ b/comps-f22.xml.in
@@ -1449,6 +1449,10 @@
   packagereq type=mandatorymaxima/packagereq
   packagereq type=mandatoryoctave/packagereq
   packagereq type=mandatorypython-matplotlib/packagereq
+  packagereq type=mandatorypython-matplotlib-tk/packagereq
+  packagereq type=mandatorypython-ipython/packagereq
+  packagereq type=mandatorypython-ipython-console/packagereq
+  packagereq type=mandatorypython-ipython-notebook/packagereq
   packagereq type=mandatoryR/packagereq
   packagereq type=mandatoryscipy/packagereq
   packagereq type=mandatoryspeedcrunch/packagereq
@@ -1570,6 +1574,7 @@
   packagereq type=optionalpython-biopython/packagereq
   packagereq type=optionalpython-cvxopt/packagereq
   packagereq type=optionalpython-networkx/packagereq
+  packagereq type=optionalpython-pandas/packagereq
   packagereq type=optionalpython-theano/packagereq
   packagereq type=optionalqalculate-gtk/packagereq
   packagereq type=optionalqalculate-kde/packagereq

and similar change for f23 as well.

Is there any objection? I am not sure if I have the right permissions to push 
this change as well..but that is
another problem to solve.

Best,
Amit.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Fedora scientific packaging

2014-11-23 Thread Amit Saha 


- Original Message -
 From: Sandro Mani manisan...@gmail.com
 To: Development discussions related to Fedora 
 devel@lists.fedoraproject.org, scit...@lists.fedoraproject.org
 Sent: Saturday, November 22, 2014 5:32:43 AM
 Subject: Fedora scientific packaging
 
 Hello,
 
 Some time ago I started working on packaging Salome, the platform for
 numerical simulation. As always, time is a limited resource, and things
 kinda stalled after hitting a few issues here and there, despite most of
 the work being done. Now, with Jiri Kastner joining the effort, we
 decided that it would be nice to attempt to make the effort of packaging
 scientific packages for Fedora in general more public, in particular
 considering the scientific-spin effort [1].
 Many of the larger scientific packages tend to be very complex and their
 build systems occasionally somewhat fragile... So getting more
 interested people involved would likely increase the chances of the
 efforts succeeding.
 
 That said, there is now a github repo which contains the
 work-in-progress stuff for packaging Salome (and some initial OpenFOAM
 work) here [2]. People interested in joining these efforts or sharing
 initial work on other scientific packages are very welcome to join the
 github project.


This is great. I created the Fedora Scientific organization on GitHub some time 
back [1].
Do you think you would want to get your repo moved here? I can of course make 
you an admin,
member, etc.

[1] https://github.com/FedoraScientific

Thanks,
Amit.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Fedora.NEXT Products and the fate of Spins

2014-01-29 Thread Amit Saha 
Hello,


- Original Message -
 From: inode0 ino...@gmail.com
 To: Development discussions related to Fedora 
 devel@lists.fedoraproject.org
 Sent: Thursday, January 30, 2014 8:01:15 AM
 Subject: Re: Fedora.NEXT Products and the fate of Spins
 
snip
..

 
 I guess I'd like those active in the spin community to make
 suggestions here. I imagine spins and other new creations built on
 Fedora to be things the project wants to promote, not push away. The
 reality may be that we can't do what we do now in support of spins,
 but I hope we can continue to do something that helps and encourages
 those making them.

I am the maintainer of the Fedora Scientific Spin and I speak wearing my Fedora 
community
member hat (not RH employee). 

A bit of background will put things into better perspective. The Fedora 
Scientific Spin
was first released during the Fedora 16 release cycle. I failed to fix a build 
failure 
due to package dep. issues during the F19 release cycle, so, we have had 4 
releases since then. 
I haven't been bombarded with emails from users, but I have had emails from 
users who find it 
useful and have requested for things to be included (which couldn't be included 
for other reasons). 
One good thing to come out of the failed F19 release was that I came to know 
that people do care 
about Fedora Scientific, since I had potential users looking to download it, 
but didn't find an ISO.

Now, I will begin the pitch for Fedora Scientific to exist. I think Fedora 
Scientific is a good thing to have
in the Open Source scientific computing ecosystem. Thanks to the packagers, we 
have all the tools/libraries that
the ecosystem boasts of ready to use in Fedora Scientific [1]. We may be even 
attracting users to Fedora due to it 
(no facts to back it up), since the closest distro that aims to achieve what 
Fedora Scientific does is 
Scientific Linux. 

Some more points re. specific issues pointed out and what can be done about it:

- Starting with Fedora 20, all the spin maintainers were supposed to fill a 
matrix 
  (as someone else already pointed out) which was a validation that the test 
composes, 
  the RCs, alphas and the betas worked correctly (installation, applications 
packaged, 
  etc.). Overall I think it was a good thing to have as it helped the spin 
maintainers
  to fix issues with their builds. So, +1 to that and we should continue it. [2]

- I am not exactly sure about the cost of doing the builds, checking why they 
may have failed, etc.
  So, perhaps, this can be something that my be off-shored to the spin 
maintainers? It increases
  our responsibilities, but helps lighten the load from rel-eng.

- In my moment of Is Fedora Scientific actually being used? or, more 
recently, Is it even a contribution worth a Fedora
  10-year anniversary T-shirt?, I have thought that perhaps, all the packages 
that Fedora Scientific ships
  can all be made into a yum group and the user can just do yum groupinstall 
fedora-scientific. Yeah, perhaps
  it can be done, but I hope we don't have to, since it still needs the user to 
download a whole bunch of stuff
  after the install, the exact problem I wanted to solve using Fedora 
Scientific. 

Overall, I think Fedora Spins are a good thing to have, and we must address the 
question of how we can keep them
by sharing the work that goes into having them, rather than eliminating them or 
converting them into Remixes.

Best,
Amit.

[1] http://fedora-scientific.readthedocs.org/en/latest/ (Needs a lot more work 
to make it complete)
[2] https://fedoraproject.org/wiki/Scientific_Packages_Testing


-- 
Amit Saha http://echorand.me
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Why is not enabled TapButton of touchpad on Fedora by default?

2012-09-12 Thread Amit Saha 
On Wed, Sep 12, 2012 at 4:44 PM, Ankur Sinha sanjay.an...@gmail.com wrote:
 On Tue, 2012-09-11 at 23:16 -0700, Adam Williamson wrote:
 So instead of /usr/share/X11/xorg.conf.d/50-synaptics.conf you should
 create /etc/X11/xorg.conf.d/50-synaptics.conf . Other than that, I
 think
 the advice is good.

 Hi,

 Thanks Adam, Onuralp, Alvaro.

 I've created a page here[1]. Please review it and correct it if
 required.

Thanks for putting this together. I, for one have had to search around
to enable tapping after a fresh install.


Cheers,
Amit.
-- 
http://echorand.me
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Netbeans IDE package for Fedora

2012-09-11 Thread Amit Saha 
On Tue, Sep 11, 2012 at 5:45 PM, Danishka Navin danis...@gmail.com wrote:
 Hi,

 Is there a specific reason that Netbeans IDE is not available in Fedora
 repository?

http://lists.fedoraproject.org/pipermail/devel/2012-January/161094.html

Cheers,
-Amit.

-- 
http://echorand.me
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Koji: fedora.cert

2012-06-08 Thread Amit Saha 
Hello:

A part of my GSoC project - On-Demand Fedora Build Service[1] involves
downloading packages via Koji. The build client can run simulatenously
on multiple nodes (separate machines). Is it OK to use the same
fedora.cert on all these? Or, is there any restrictions to
simultaenously using the same cert ?

[1] https://github.com/amitsaha/gsoc2012_fbs


Thanks!
-Amit




-- 
http://echorand.me
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Koji: fedora.cert

2012-06-08 Thread Amit Saha 
On Sat, Jun 9, 2012 at 1:56 AM, Dennis Gilmore den...@ausil.us wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 El Fri, 8 Jun 2012 19:04:29 +1000
 Amit Saha amitks...@fedoraproject.org escribió:
 Hello:

 A part of my GSoC project - On-Demand Fedora Build Service[1] involves
 downloading packages via Koji. The build client can run simulatenously
 on multiple nodes (separate machines). Is it OK to use the same
 fedora.cert on all these? Or, is there any restrictions to
 simultaenously using the same cert ?

 [1] https://github.com/amitsaha/gsoc2012_fbs

 you do not need a cert to download builds from koji, none of what you
 would do in finding and downloading builds requires authenticated
 access. so dont use it.

Oh Okay. Should have checked before assuming it needed it.

Thanks!
-Amit

-- 
http://echorand.me
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Kickstart packages --default parsing query

2012-05-22 Thread Amit Saha 
Hello:

I posted this to the Kickstart list [1], but thought of checking it
here in the interest of a faster turnaround time.

I am trying to add a repository to an existing KS file. This is the script [2].

The script is doing its job for KS files which do not have a
'--default' switch added to the %packages section. However, for a KS
file which has a %packages --default section added, the parser does
not read beyond it and hence creates a KS file which do not have any
of the following packages specified in the KS file.

To quickly verify the problem, I have added two KS files (basically
the fedora-install-fedora.ks used to create Fedora installation DVDs)
with one having the --default option, and the other not having it. I
have commented out the actual repo addition code so that the problem
can be reproduced easily.

For example, with the default.ks file:

$python ks_addrepo.py

#version=DEVEL
repo --name=fedora
--mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-$releaseverarch=$basearch
--excludepkgs=kernel*debug*,kernel-kdump*,syslog-ng*,java-1.5.0-gcj-devel,astronomy-bookmarks,generic*,java-1.5.0-gcj-javadoc,btanks*,GConf2-dbus*,bluez-gnome
repo --name=fedora-source
--mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-source-$releaseverarch=$basearch
--excludepkgs=kernel*debug*,kernel-kdump*,syslog-ng*,java-1.5.0-gcj-devel,astronomy-bookmarks,generic*,java-1.5.0-gcj-javadoc,btanks*,GConf2-dbus*,bluez-gnome
# Installation logging level
logging --level=info


%packages --default

%end

And with the nodefault.ks file:

$python ks_addrepo.py

#version=DEVEL
repo --name=fedora
--mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-$releaseverarch=$basearch
--excludepkgs=kernel*debug*,kernel-kdump*,syslog-ng*,java-1.5.0-gcj-devel,astronomy-bookmarks,generic*,java-1.5.0-gcj-javadoc,btanks*,GConf2-dbus*,bluez-gnome
repo --name=fedora-source
--mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-source-$releaseverarch=$basearch
--excludepkgs=kernel*debug*,kernel-kdump*,syslog-ng*,java-1.5.0-gcj-devel,astronomy-bookmarks,generic*,java-1.5.0-gcj-javadoc,btanks*,GConf2-dbus*,bluez-gnome
# Installation logging level
logging --level=info


%packages
@afrikaans-support
@albanian-support
@arabic-support
@armenian-support
@assamese-support
@basque-support
@belarusian-support
@bengali-support
@bhutanese-support
@bosnian-support
@brazilian-support
@breton-support
@british-support
@bulgarian-support
@burmese-support

..
..


[1] https://www.redhat.com/archives/kickstart-list/2012-May/msg2.html
[2] https://github.com/amitsaha/gsoc2012_fbs/blob/master/scripts/ks_addrepo.py

Have I hit a bug or is it something which is known can be worked around?


Thanks a lot in advance.

Best,
Amit

-- 
http://echorand.me
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Help with Mock error

2012-03-13 Thread Amit Saha 

Hello:

I am in the process of building my first package [1], and have got most 
of it sorted. 'rpmbuild -ba' executes successfully with the current SPEC 
file[3].


However, the SRPM [2] fails in Mock with the error:

RPM build errors:
File not found by glob: 
/builddir/build/BUILDROOT/python-picloud-2.4.2-3.fc16.i386/usr/bin/*

Child return code was: 1

I am not sure why? (Having the incorrect %{_bindir}/ in the SPEC file 
passes successfully).



[1] https://bugzilla.redhat.com/show_bug.cgi?id=799810
[2] 
http://amitksaha.fedorapeople.org/contribs/picloud_packaging/python-picloud-2.4.2-3.fc16.src.rpm
[3] 
http://amitksaha.fedorapeople.org/contribs/picloud_packaging/python-picloud.spec



I am probably missing something very basic here. Kindly suggest.

Thanks!
Amit

--
http://echorand.me

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Help with Mock error

2012-03-13 Thread Amit Saha 

Hello:

On 03/13/2012 06:50 PM, Alec Leamas wrote:

On 03/13/2012 08:43 AM, Alec Leamas wrote:

On 03/13/2012 07:21 AM, Amit Saha wrote:

Hello:

I am in the process of building my first package [1], and have got
most of it sorted. 'rpmbuild -ba' executes successfully with the
current SPEC file[3].

However, the SRPM [2] fails in Mock with the error:

RPM build errors:
File not found by glob:
/builddir/build/BUILDROOT/python-picloud-2.4.2-3.fc16.i386/usr/bin/*
Child return code was: 1

I am not sure why? (Having the incorrect %{_bindir}/ in the SPEC file
passes successfully).


[1] https://bugzilla.redhat.com/show_bug.cgi?id=799810
[2]
http://amitksaha.fedorapeople.org/contribs/picloud_packaging/python-picloud-2.4.2-3.fc16.src.rpm
[3]
http://amitksaha.fedorapeople.org/contribs/picloud_packaging/python-picloud.spec


I am probably missing something very basic here. Kindly suggest.

Thanks!
Amit


The spec most likely doesn't put anything in $RPM_BUILD_ROOT/usr/bin.
To verify, run rpmbuild -bi your spec, and look into
~/rpmbuild/BUILD/python-picloud-2.4.2* to find out what the thing
actually installs


Oops... that should be Look into
~/rpmbuild/BUILDROOT/python-picloud-2.4.2* to find out...


Just checked it. It places the 'picloud' binary in 
~/rpmbuild/BUILDROOT/python-picloud-2.4.2-3.fc16/usr/bin .


-Amit

--
http://echorand.me
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Help with Mock error

2012-03-13 Thread Amit Saha 

On 03/13/2012 07:48 PM, Alec Leamas wrote:

On 03/13/2012 08:58 AM, Amit Saha wrote:

Hello:

On 03/13/2012 06:50 PM, Alec Leamas wrote:

On 03/13/2012 08:43 AM, Alec Leamas wrote:

On 03/13/2012 07:21 AM, Amit Saha wrote:

Hello:

I am in the process of building my first package [1], and have got
most of it sorted. 'rpmbuild -ba' executes successfully with the
current SPEC file[3].

However, the SRPM [2] fails in Mock with the error:

RPM build errors:
File not found by glob:
/builddir/build/BUILDROOT/python-picloud-2.4.2-3.fc16.i386/usr/bin/*
Child return code was: 1

I am not sure why? (Having the incorrect %{_bindir}/ in the SPEC file
passes successfully).


[1] https://bugzilla.redhat.com/show_bug.cgi?id=799810
[2]
http://amitksaha.fedorapeople.org/contribs/picloud_packaging/python-picloud-2.4.2-3.fc16.src.rpm

[3]
http://amitksaha.fedorapeople.org/contribs/picloud_packaging/python-picloud.spec



I am probably missing something very basic here. Kindly suggest.

Thanks!
Amit


The spec most likely doesn't put anything in $RPM_BUILD_ROOT/usr/bin.
To verify, run rpmbuild -bi your spec, and look into
~/rpmbuild/BUILD/python-picloud-2.4.2* to find out what the thing
actually installs


Oops... that should be Look into
~/rpmbuild/BUILDROOT/python-picloud-2.4.2* to find out...


Just checked it. It places the 'picloud' binary in
~/rpmbuild/BUILDROOT/python-picloud-2.4.2-3.fc16/usr/bin .

-Amit


What a mess... I think I would run a mock build with the
--no-cleanup-after flag, and then a mock --shell. This way you should be
able to see what's built in mock in a similar way to rpmbuild -bi.


I did that. I think I should expect to see 'picloud' in /usr/bin and the 
man pages in /usr/share/man/man1/ ? I don't see any of after i do mock 
--shell.


From the build.log, the last few lines are:

+ cp -pr doc README.txt CHANGELOG 
/builddir/build/BUILDROOT/python-picloud-2.4.2-3.fc16.i386/usr/share/doc/python-picloud-2.4.2

+ exit 0
RPM build errors:
File not found by glob: 
/builddir/build/BUILDROOT/python-picloud-2.4.2-3.fc16.i386/usr/bin/*

Child return code was: 1


So, obviously something is wrong. What else I can look into?

Thanks!
-Amit








--
http://echorand.me
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Help with Mock error

2012-03-13 Thread Amit Saha 

On 03/13/2012 09:17 PM, Alec Leamas wrote:

On 03/13/2012 10:10 AM, Amit Saha wrote:

On 03/13/2012 07:48 PM, Alec Leamas wrote:

On 03/13/2012 08:58 AM, Amit Saha wrote:

Hello:

On 03/13/2012 06:50 PM, Alec Leamas wrote:

On 03/13/2012 08:43 AM, Alec Leamas wrote:

On 03/13/2012 07:21 AM, Amit Saha wrote:

Hello:

I am in the process of building my first package [1], and have got
most of it sorted. 'rpmbuild -ba' executes successfully with the
current SPEC file[3].

However, the SRPM [2] fails in Mock with the error:

RPM build errors:
File not found by glob:
/builddir/build/BUILDROOT/python-picloud-2.4.2-3.fc16.i386/usr/bin/*
Child return code was: 1

I am not sure why? (Having the incorrect %{_bindir}/ in the SPEC
file
passes successfully).


[1] https://bugzilla.redhat.com/show_bug.cgi?id=799810
[2]
http://amitksaha.fedorapeople.org/contribs/picloud_packaging/python-picloud-2.4.2-3.fc16.src.rpm


[3]
http://amitksaha.fedorapeople.org/contribs/picloud_packaging/python-picloud.spec




I am probably missing something very basic here. Kindly suggest.

Thanks!
Amit


The spec most likely doesn't put anything in $RPM_BUILD_ROOT/usr/bin.
To verify, run rpmbuild -bi your spec, and look into
~/rpmbuild/BUILD/python-picloud-2.4.2* to find out what the thing
actually installs


Oops... that should be Look into
~/rpmbuild/BUILDROOT/python-picloud-2.4.2* to find out...


Just checked it. It places the 'picloud' binary in
~/rpmbuild/BUILDROOT/python-picloud-2.4.2-3.fc16/usr/bin .

-Amit


What a mess... I think I would run a mock build with the
--no-cleanup-after flag, and then a mock --shell. This way you should be
able to see what's built in mock in a similar way to rpmbuild -bi.


I did that. I think I should expect to see 'picloud' in /usr/bin and
the man pages in /usr/share/man/man1/ ? I don't see any of after i do
mock --shell.

Yes, they should be there.


From the build.log, the last few lines are:

+ cp -pr doc README.txt CHANGELOG
/builddir/build/BUILDROOT/python-picloud-2.4.2-3.fc16.i386/usr/share/doc/python-picloud-2.4.2

+ exit 0
RPM build errors:
File not found by glob:
/builddir/build/BUILDROOT/python-picloud-2.4.2-3.fc16.i386/usr/bin/*
Child return code was: 1


So, obviously something is wrong. What else I can look into?

Thanks!
-Amit



I guess our common understanding is that the %install has failed...
sometimes, the installation paths are wrong. Have you looked into the
complete /builddir/build/BUILDROOT/python-picloud-2.4.2-3.fc16.i386 tree
to see if the %install has placed in other places there?


I see that the bash_completion file has been placed in 
etc/bash_completion.d directory and the man page has also been copied in 
usr/share/man/man1


So, the install step is obviously failing in mock.

Here is the complete build.log file: https://gist.github.com/2028090

Hope something can be identified.

Many thanks!
-Amit












--
http://echorand.me
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Help with Mock error

2012-03-13 Thread Amit Saha 

On 03/13/2012 10:45 PM, Alec Leamas wrote:

On 03/13/2012 11:55 AM, Amit Saha wrote:

On 03/13/2012 09:17 PM, Alec Leamas wrote:

On 03/13/2012 10:10 AM, Amit Saha wrote:

On 03/13/2012 07:48 PM, Alec Leamas wrote:

On 03/13/2012 08:58 AM, Amit Saha wrote:

Hello:

On 03/13/2012 06:50 PM, Alec Leamas wrote:

On 03/13/2012 08:43 AM, Alec Leamas wrote:

On 03/13/2012 07:21 AM, Amit Saha wrote:

Hello:

I am in the process of building my first package [1], and have got
most of it sorted. 'rpmbuild -ba' executes successfully with the
current SPEC file[3].

However, the SRPM [2] fails in Mock with the error:

RPM build errors:
File not found by glob:
/builddir/build/BUILDROOT/python-picloud-2.4.2-3.fc16.i386/usr/bin/*

Child return code was: 1

I am not sure why? (Having the incorrect %{_bindir}/ in the SPEC
file
passes successfully).


[1] https://bugzilla.redhat.com/show_bug.cgi?id=799810
[2]
http://amitksaha.fedorapeople.org/contribs/picloud_packaging/python-picloud-2.4.2-3.fc16.src.rpm



[3]
http://amitksaha.fedorapeople.org/contribs/picloud_packaging/python-picloud.spec





I am probably missing something very basic here. Kindly suggest.

Thanks!
Amit


The spec most likely doesn't put anything in
$RPM_BUILD_ROOT/usr/bin.
To verify, run rpmbuild -bi your spec, and look into
~/rpmbuild/BUILD/python-picloud-2.4.2* to find out what the thing
actually installs


Oops... that should be Look into
~/rpmbuild/BUILDROOT/python-picloud-2.4.2* to find out...


Just checked it. It places the 'picloud' binary in
~/rpmbuild/BUILDROOT/python-picloud-2.4.2-3.fc16/usr/bin .

-Amit


What a mess... I think I would run a mock build with the
--no-cleanup-after flag, and then a mock --shell. This way you
should be
able to see what's built in mock in a similar way to rpmbuild -bi.


I did that. I think I should expect to see 'picloud' in /usr/bin and
the man pages in /usr/share/man/man1/ ? I don't see any of after i do
mock --shell.

Yes, they should be there.


From the build.log, the last few lines are:

+ cp -pr doc README.txt CHANGELOG
/builddir/build/BUILDROOT/python-picloud-2.4.2-3.fc16.i386/usr/share/doc/python-picloud-2.4.2


+ exit 0
RPM build errors:
File not found by glob:
/builddir/build/BUILDROOT/python-picloud-2.4.2-3.fc16.i386/usr/bin/*
Child return code was: 1


So, obviously something is wrong. What else I can look into?

Thanks!
-Amit



I guess our common understanding is that the %install has failed...
sometimes, the installation paths are wrong. Have you looked into the
complete /builddir/build/BUILDROOT/python-picloud-2.4.2-3.fc16.i386 tree
to see if the %install has placed in other places there?


I see that the bash_completion file has been placed in
etc/bash_completion.d directory and the man page has also been copied
in usr/share/man/man1

So, the install step is obviously failing in mock.

Here is the complete build.log file: https://gist.github.com/2028090

Hope something can be identified.

Many thanks!
-Amit



Basically, this beats me. An educated guess is that something in your
own environment makes %install work when using rpmbuild. I note there
are some warnings when running setup.py...


Yes, the setup.py attempts to do a direct copy of the man and the bash 
completion files to /usr/share and /etc/ sub-dirs respectively. (I think 
i will patch it in the SPEC to work around this).




Hopefully, someone who knows this python stuff kan give you some advice
(that person is certainly not me, sorry :) )


Thank you for looking into this. I hope somebody can help.

Best,
Amit

--
http://echorand.me
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Help with Mock error

2012-03-13 Thread Amit Saha 

On 03/13/2012 11:10 PM, Mathieu Bridon wrote:

On Tue, 2012-03-13 at 22:48 +1100, Amit Saha wrote:

Hopefully, someone who knows this python stuff kan give you some advice
(that person is certainly not me, sorry :) )


Thank you for looking into this. I hope somebody can help.


 From your build.log:
--
/usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown
distribution option: 'entry_points'
   warnings.warn(msg)
/usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown
distribution option: 'install_requires'
   warnings.warn(msg)
--

Try adding BuildRequires: python-setuptools to your spec file.




And it succeeds. Thanks a lot, Mathieu!

Best,
-Amit

--
http://echorand.me
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: GSoC 2012 ideas - support expanding the list

2012-03-06 Thread Amit Saha 

Hello:

On 03/07/2012 03:08 AM, Buddhika Kurera wrote:

Hello Folks,

Please add your ideas and expand the GSoC 2012 idea list[1].
Ideas and mentors welcome, thanks.


I have an idea and I would like to work on it as a student. Is it 
appropriate to add it to the wiki page there and put myself in the 
contacts and leave the Mentor blank?


Thanks!
-Amit

--
http://echorand.me
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: GSoC 2012 ideas - support expanding the list

2012-03-06 Thread Amit Saha 

Hi Buddhika:

On 03/07/2012 02:00 PM, Buddhika Kurera wrote:

On Wed, Mar 7, 2012 at 7:04 AM, Amit Sahadroid...@gmail.com  wrote:

Hello:
I have an idea and I would like to work on it as a student. Is it
appropriate to add it to the wiki page there and put myself in the contacts
and leave the Mentor blank?

Thanks!
-Amit


Hello Amit,

I have added a new wiki page for Students Ideas[1], you can add your
idea to that page.
This age is linked with the main idea page so that every one can find
the students idea page as well.

Still I think it will be a good idea to forward your idea to the
mailing list after adding it to the wiki.

Thanks for the interest..


Thank you for setting up the page. I added my idea here at [1].

[1] 
https://fedoraproject.org/wiki/Summer_coding_ideas_for_2012/Students_Idea#Fedora_On-Demand_Build_Service



Best,
Amit
--
http://echorand.me
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Package Review Request: python-picloud

2012-03-04 Thread Amit Saha 

Hello:

Could someone please review my first package: 
https://bugzilla.redhat.com/show_bug.cgi?id=799810 ?


Since, this is my first, I am in need of a sponsor (FAS: amitksaha)

Thanks a lot !
-Amit
--
http://echorand.me
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: emacs and libotf.so.0

2011-09-04 Thread Amit Saha 
Hi,

On 09/05/2011 12:59 AM, Denis Arnaud wrote:
 Hello,

 I just came onto a tricky dependency issue, and thought it could be of
 interest to the list.
 emacs requires libotf.so.0, which is the library handling Open Type
 Fonts (OTF), provided by the libotf package.
 Well, fine enough. But libotf.so.0 is also provided by the OpenMPI
 package (not in /usr/lib, but rather in /usr/lib/openmpi/lib).

 So, RPM/Yum is misleaded when installing, whenever OpenMPI has
 installed. It results in a cryptic emacs: error while loading shared
 libraries: libotf.so.0: cannot open shared object file: No such file or
 directory error message (I put it here in plain, so that it can be
 indexed by our favourite Web crawlers), or so, when trying to launch
 emacs from a terminal.

 I see no clean solution, as both packages (libotf, openmpi) have some
 legitimity to name that libotf.so library like that. And it seems
 impracticable to have RPM handles full paths rather than just library names.

 I leave the floor open for debates :)

I have faced this issue before, and have also raised this on this list, 
Pls see [1] for the mail thread.


[1] http://lists.fedoraproject.org/pipermail/devel/2011-July/153812.html

-Amit

-- 
http://echorand.me
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: [OT] Stray Cats were added?

2011-07-17 Thread Amit Saha 
On 07/17/2011 07:15 PM, Jan Kratochvil wrote:
 On Sat, 09 Jul 2011 09:08:20 +0200, Amit Saha wrote:
 0 Stray cats were added..

 Was wondering what's the background?

 /usr/share/doc/man-db-*/man-db-manual.*

:-) Thanks Jan! So actually it does not have to do anything with a 
'real' cat.

Regards,
Amit

-- 
http://echorand.me
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

[OT] Stray Cats were added?

2011-07-09 Thread Amit Saha 
Hello all:

(Yes, Curiosity killed the cat, but never mind!)

I saw this message towards the end of building a custom Fedora spin:

0 Stray cats were added..

Was wondering what's the background?

Cheers,
Amit
-- 
http://echorand.me
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Request for Sponsor (was Re: Orphaning packages)

2011-07-07 Thread Amit Saha 
Hello all:

On 07/07/2011 11:54 PM, Bruno Wolff III wrote:
 On Thu, Jul 07, 2011 at 13:06:12 +1000,
Amit Sahadroid...@gmail.com  wrote:
 On Thu, Jul 7, 2011 at 4:23 AM, Jesse Keatingjkeat...@redhat.com  wrote:
 I no longer have a need/care for these packages, they are up for grabs:

 contacts
 inotail

 I haven't maintained a package before, but I am looking for a starting
 point and I would like to take up contacts.

 Note that you need a sponsor to become a packager. The requirements have
 loosened a bit in that you don't need to submit a new package for review.
 But a sponsor is likely to want some demostration that you have enough
 knowledge to start being a packager.

Thanks Bruno for the tip!

So, here goes an open request for sponsor. Is anyone interested in 
sponsoring me? I learn fast, so after the initial discussions I should 
be able to do things on my own. It won't be baby-sitting for too long!

My current Fedora activities include a Ready for Wrangler Fedora 
Scientific Spin [1] and i have few plans regarding the future trajectory 
of the SciTech SIG, which is where I intend to involve myself heavily. 
However, maintaining the contacts package looked an interesting place 
to begin!

My Fedora wiki page is at [2].

[1] https://fedoraproject.org/wiki/Scientific_Spin
[2] https://fedoraproject.org/wiki/User:Amitksaha

Many thanks in advance!

-Amit

-- 
http://echorand.me
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

OpenMPI, Emacs and libotf problems

2011-07-06 Thread Amit Saha 
Hello all:

I am hoping it is OK to discuss this here. I came across this problem
when I was building a custom spin where the kickstart file installs
'openmpi' before 'emacs'.

When I start emacs, here is what I get:

$emacs
emacs: error while loading shared libraries: libotf.so.0: cannot open
shared object file: No such file or directory

So, this library is missing. However, this should have been installed
as its a dependency, right?

It can be seen that there are two providers listed for libotf.so.0.
Since 'openmpi' was already installed, so it didn't bother installing
'libotf'. I could simulate the scenario on a Fedora 15 installation:


Step1: Dependency listing
-

$yum deplist emacs

 dependency: libotf.so.0
   provider: openmpi.i686 1.5-3.fc15
   provider: libotf.i686 0.9.12-2.fc15



To verify this scenario, the next step attempts to install emacs on a
machine without emacs, libotf and openmpi:

Step 2: Installing emacs
--

[gene@soma ~]$ sudo yum install emacs
Loaded plugins: langpacks, presto, refresh-packagekit
Setting up Install Process
Resolving Dependencies
-- Running transaction check
--- Package emacs.i686 1:23.2-19.fc15 will be installed
-- Processing Dependency: libotf.so.0 for package: 1:emacs-23.2-19.fc15.i686
-- Running transaction check
--- Package libotf.i686 0:0.9.12-2.fc15 will be installed
-- Finished Dependency Resolution

Dependencies Resolved

===
 PackageArch Version
Repository   Size
===
Installing:
 emacs  i686 1:23.2-19.fc15
updates 2.0 M
Installing for dependencies:
 libotf i686 0.9.12-2.fc15
fedora   82 k

Transaction Summary
===
Install   2 Package(s)

Total download size: 2.1 M


all good here.

(I don't proceed with the install)



Step 3: Installing openmpi
--
Next, I just install openmpi, which is listed as a provider for libotf.so.0:

[gene@soma ~]$ sudo yum install openmpi
Loaded plugins: langpacks, presto, refresh-packagekit
Setting up Install Process
Resolving Dependencies
-- Running transaction check
--- Package openmpi.i686 0:1.5-3.fc15 will be installed
-- Finished Dependency Resolution

Dependencies Resolved

===
 Package  Arch  Version
Repository   Size
===
Installing:
 openmpi  i686  1.5-3.fc15
fedora  1.7 M

Transaction Summary
===
Install   1 Package(s)

Total download size: 1.7 M
Installed size: 6.7 M


Install done.

Step 4: Installing Emacs after installing openmpi
---

[gene@soma ~]$ sudo yum install emacs
Loaded plugins: langpacks, presto, refresh-packagekit
Setting up Install Process
Resolving Dependencies
-- Running transaction check
--- Package emacs.i686 1:23.2-19.fc15 will be installed
-- Finished Dependency Resolution

Dependencies Resolved

===
 Package   Arch Version
Repository   Size
===
Installing:
 emacs i686 1:23.2-19.fc15
updates 2.0 M

Transaction Summary
===
Install   1 Package(s)

Total download size: 2.0 M
Installed size: 6.5 M
Is this ok [y/N]: y
Downloading Packages:
Setting up and reading Presto delta metadata
Processing delta metadata
Package(s) data still to download: 2.0 M
emacs-23.2-19.fc15.i686.rpm |
2.0 MB 00:00
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : 1:emacs-23.2-19.fc15.i686
1/1

Installed:
  emacs.i686 1:23.2-19.fc15


It doesn;t list the dependeny anymore on libotf.so.0, since openmpi is
already installed.

And the result:

$emacs
emacs: error while loading shared libraries: libotf.so.0: cannot open
shared object file: No such file or directory


I also noted this discrepancy:

$sudo yum whatprovides libotf.so.0

Loaded plugins: langpacks, presto, refresh-packagekit
openmpi-1.5-3.fc15.i686 : Open Message Passing Interface
Repo: fedora
Matched from:
Other   : libotf.so.0



libotf-0.9.12-2.fc15.i686 : A Library for

Re: Orphaning packages

2011-07-06 Thread Amit Saha 
On Thu, Jul 7, 2011 at 4:23 AM, Jesse Keating jkeat...@redhat.com wrote:
 I no longer have a need/care for these packages, they are up for grabs:

 contacts
 inotail

I haven't maintained a package before, but I am looking for a starting
point and I would like to take up contacts.

-Amit

-- 
http://echorand.me
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

RFC: Fedora Scientific release

2011-06-06 Thread Amit Saha 
Hello:

As an effort to avoid installing the same packages (like latex, emacs,
gnuplot..) everytime I do a fresh install of a Linux distro, I decided
to create a Fedora spin to cater the users who use Linux as their main
workstation to help them in their research.

I see from [1] that a Fedora Spin for Science is in the Ideas
section. However, the SciTech mailng list seems deactivated at the
moment and hence I had some discussions on the Release Engineering
mailing list [2].

At this point of time, here is what I have (based on the suggestions
by Bill Nottingham): An updated 'comps-f16-xml.in' whose current
version is at [3] and based on that a possible kickstart script[4].

Any thoughts/comments/suggestions appreciated.

[1] http://fedoraproject.org/wiki/SIGs/SciTech
[2] http://lists.fedoraproject.org/pipermail/rel-eng/2011-June/012301.html
[3] 
https://bitbucket.org/amitksaha/custom_linux/src/c94686fe43fe/comps-f16.xml.in
[4] 
https://bitbucket.org/amitksaha/custom_linux/src/c94686fe43fe/fedora-live-scientific.ks

Cheers,
Amit
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: RFC: Fedora Scientific release

2011-06-06 Thread Amit Saha 
On Mon, Jun 6, 2011 at 11:51 AM,  andrewnix...@gmail.com wrote:
 On , Amit Saha droid...@gmail.com wrote:
 Hello:



 As an effort to avoid installing the same packages (like latex, emacs,

 gnuplot..) everytime I do a fresh install of a Linux distro, I decided

 to create a Fedora spin to cater the users who use Linux as their main

 workstation to help them in their research.



 I see from [1] that a Fedora Spin for Science is in the Ideas

 section. However, the SciTech mailng list seems deactivated at the

 moment and hence I had some discussions on the Release Engineering

 mailing list [2].



 At this point of time, here is what I have (based on the suggestions

 by Bill Nottingham): An updated 'comps-f16-xml.in' whose current

 version is at [3] and based on that a possible kickstart script[4].



 Any thoughts/comments/suggestions appreciated.



 [1] http://fedoraproject.org/wiki/SIGs/SciTech

 [2] http://lists.fedoraproject.org/pipermail/rel-eng/2011-June/012301.html

 [3]
 https://bitbucket.org/amitksaha/custom_linux/src/c94686fe43fe/comps-f16.xml.in

 [4]
 https://bitbucket.org/amitksaha/custom_linux/src/c94686fe43fe/fedora-live-scientific.ks



 Cheers,

 Amit


 Amit, I would be keen to help with this spin. The SciTech SIG seems to be
 dead making it a little difficult for scientists to find common ground on
 the project.

Thanks Andrew for your interest. It should definitely be an
interesting addition to the fedora spin community.

-Amit
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel