Orphaned several Python packages

Hi all, since I'm no longer using following Python packages and don't have time to maintain them, I'm orphaning them. Feel free to take them: python-dingus python-django-keyedcache python-django-profile python-django-roa python-django-sorting python-remoteobjects -- Regards, Slavek Kabrda _

Re: python: dropping the .py files [was Re: Fedora 23 cloud image (and, for that matter, minimal anything)] bloat

- Original Message - > On 09/25/2015 08:36 AM, Matthew Miller wrote: > > On Fri, Sep 25, 2015 at 10:09:50AM -0400, Paul Wouters wrote: > >> It's nice to be able to edit the .py for testing without going through > >> hoops or building/installing rpms. > > > > Right, but you know that if you'

Re: nothing provides /bin/python needed by mercurial-3.5-1.fc23.x86_64

- Original Message - > I'm stuck on this (again). According to advice here: > > https://lists.fedoraproject.org/pipermail/devel/2015-June/211666.html > > I just needed to use > Requires: /usr/bin/python > > But I tried changing > > Requires: python > > to > > Requires: /usr/bin/pytho

Re: [Guidelines change] Changes to the packaging guidelines

- Original Message - > On Thu, Aug 06, 2015 at 10:03:00AM -0400, Robert Kuska wrote: > > - Original Message - > > > From: "Jason L Tibbitts III" > > > To: devel-annou...@lists.fedoraproject.org > > > Sent: Tuesday, August 4, 2015 11:34:06 PM > > > Subject: [Guidelines change] Chang

Re: F23 System Wide Change: Python 3 as Default

- Original Message - > On Thu, Jun 18, 2015 at 9:54 AM, Bohuslav Kabrda wrote: > >> It is written in a scope what does 'default' stands for. > >> Also from a additional porting POV (packages which ain't covered by scope > >> and are python2

Re: F23 System Wide Change: Python 3 as Default

- Original Message - > - Original Message - > > From: "Kevin Fenzi" > > To: devel@lists.fedoraproject.org > > Sent: Wednesday, June 17, 2015 9:11:36 PM > > Subject: Re: F23 System Wide Change: Python 3 as Default > > > > Greetings. > > > > In today's FESCo meeting we had a lot of

Re: F23 System Wide Change: Python 3 as Default

- Original Message - > On Thu, Jun 11, 2015, at 04:40 PM, Adam Miller wrote: > > > I think the point that Colin is trying to make is that while Atomic > > Host does not depend on Ansible being installed, it is a very popular > > utility used to remotely manage (potentially large) sets of A

Re: F23 System Wide Change: Python 3 as Default

- Original Message - > On Thu, Jun 11, 2015, at 09:03 AM, Bohuslav Kabrda wrote: > > > > > Which means that it isn't *in* the Atomic host itself, but it is only used > > to *control instances* of Atomic host, is that correct? If so, I see no > >

Re: F23 System Wide Change: Python 3 as Default

- Original Message - > > > On Thu, Jun 11, 2015, at 04:01 AM, Robert Kuska wrote: > > > Does it mean that Ansible is shipped by default with Atomic host? > > > > We were working with data provided by > > https://git.fedorahosted.org/git/fedora-atomic.git > > and there is no ansible list

Reverting "Python 3 Migration Improvements" Change

Hi, I have to inform you that I had to revert the "Python 3 Migration Improvements" change for F22 - more precisely, its parts that would've caused both Python 2 and Python 3 being on atomic host or minimal cloud image. The reason is mentioned in [1] - in short, policycoreutils-python3 has only

Re: Filing Bugs for Python 3 Switch

- Original Message - > On Fri, 30 Jan 2015 04:44:19 -0500 (EST) > Bohuslav Kabrda wrote: > > > I just had a quick IRC chat with DNF maintainer and he said we still > > wants to switch to py3 for F22. > > Lovely. > > Perhaps we could get the dnf

Re: Filing Bugs for Python 3 Switch

- Original Message - > On Thu, 2015-01-29 at 08:56 -0500, Bohuslav Kabrda wrote: > > I'm regularly talking to some of Anaconda devs (mostly Vrata > > Podzimek) and they still think this is doable *without* introducing > > high number of regressions, that would b

Re: Filing Bugs for Python 3 Switch

- Original Message - > On Thu, 29 Jan 2015 09:39:28 -0500 (EST) > Bohuslav Kabrda wrote: > > > Not sure about it being the default, but we've been testing it in > > DevAssistant for dependency installation on Python 3 and never > > encountered any probl

Re: Filing Bugs for Python 3 Switch

- Original Message - > On 29 January 2015 at 07:39, Bohuslav Kabrda < bkab...@redhat.com > wrote: > > - Original Message - > > > > On Thu, Jan 29, 2015 at 8:56 AM, Bohuslav Kabrda < bkab...@redhat.com > > > > wrote: > > > >

Re: Filing Bugs for Python 3 Switch

- Original Message - > On Thu, Jan 29, 2015 at 8:56 AM, Bohuslav Kabrda wrote: > > - Original Message - > >> On Thu, Jan 29, 2015 at 7:38 AM, Miloslav Trmač wrote: > >> > (Speaking only for myself, not for all of FESCo; hoping others will > >

Re: Filing Bugs for Python 3 Switch

- Original Message - > On Thu, Jan 29, 2015 at 7:38 AM, Miloslav Trmač wrote: > > (Speaking only for myself, not for all of FESCo; hoping others will chime > > in.) > >> - What if Anaconda does make it? :) > > I don’t know. > > I'm skeptical that will happen. Even if it does, that alone

Re: Filing Bugs for Python 3 Switch

- Original Message - > > > So, at today's FESCo meeting there was a good deal of discussion about > > > python as default: > > > http://meetbot.fedoraproject.org/fedora-meeting/2015-01-28/fesco.2015-01-28-18.02.log.html#l-41 > > > > > > in which we agreed defer this to F23, file bugs again

Re: Filing Bugs for Python 3 Switch

- Original Message - > On Wed, Jan 28, 2015 at 11:09:08AM -0500, Bohuslav Kabrda wrote: > > Some general notes: > > If your package depends on Python because of a Python script that has > > /usr/bin/python in hashbang, you need to change this to /usr/bin/python3. &

Re: Filing Bugs for Python 3 Switch

- Original Message - > On Wed, 28 Jan 2015 11:09:08 -0500 (EST) > Bohuslav Kabrda wrote: > > > Hi, > > I just filed 2 bugs [A], [B] for the Python 3 switch [C] and I > > realized that I should probably follow the mass bug filing policy. As > > I've s

Filing Bugs for Python 3 Switch

Hi, I just filed 2 bugs [A], [B] for the Python 3 switch [C] and I realized that I should probably follow the mass bug filing policy. As I've said previously, we've already had both Python 2 and Python 3 on LiveCDs for few releases, so it makes sense to move as much as possible to Python 3. My i

Re: Python 3 as a Default - Status

- Original Message - > > > On Thu, Jan 22, 2015, at 12:00 PM, Bohuslav Kabrda wrote: > > > How exactly is Fedora Atomic generated? It seems that > > fedpra-cloud-atomic.ks has no %packages section... > > I can find out how we're doing with Atomic assum

Re: Python 3 as a Default - Status

- Original Message - > On Thu, Jan 22, 2015 at 11:31:12AM -0500, Bohuslav Kabrda wrote: > > Yeah, as I've noted in the sum-up mail, it's clear that we won't be > > able to switch server (and possibly workstation) completely, although > > I'm quite s

Re: Python 3 as a Default - Status

- Original Message - > On Tue, Jan 20, 2015, at 08:22 AM, Bohuslav Kabrda wrote: > > Hi all, > > since the "Python 3 as a Default" change [1] has been accepted a while ago > > and is scheduled for F22, I'd like to share with you the status. > > &g

Re: Python 3 as a Default - Status

- Original Message - > On 21. 1. 2015 at 01:44:32, Haïkel wrote: > > Thanks for the heads-up. > > > > As for the cloud image, if we switch to yum, python-urlgrabber won't > > be needed anymore. > > Umm, yes, it will be - yum uses python-urlgrabber internally. Also worth > mentioning that

Re: Python 3 as a Default - Status

- Original Message - > On Tue, Jan 20, 2015 at 08:22:25AM -0500, Bohuslav Kabrda wrote: > > Hi all, > > since the "Python 3 as a Default" change [1] has been accepted a while ago > > and is scheduled for F22, I'd like to share with you the status. >

Re: Meeting minutes for Env-and-Stacks WG meeting (2015-01-14)

- Original Message - > On 19 January 2015 at 05:08, Bohuslav Kabrda < bkab...@redhat.com > wrote: > > - Original Message - > > > > Bohuslav Kabrda wrote: > > > > > Please note, that this proposal is absolutely not about imposing some

Python 3 as a Default - Status

Hi all, since the "Python 3 as a Default" change [1] has been accepted a while ago and is scheduled for F22, I'd like to share with you the status. The proposed change [1] mentions several goals that should be reached to pronounce python3 the "default": 1) DNF is the default package manager inst

Re: Meeting minutes for Env-and-Stacks WG meeting (2015-01-14)

- Original Message - > Bohuslav Kabrda wrote: > > Please note, that this proposal is absolutely not about imposing some > > restrictions on who can/should maintain what. It's really just a > > categorization of packages based on our WG's perception of impo

Re: Meeting minutes for Env-and-Stacks WG meeting (2015-01-14)

- Original Message - > On 16 January 2015 at 01:31, Bohuslav Kabrda < bkab...@redhat.com > wrote: > > - Original Message - > > > > Honza Horak wrote: > > > > > * Fedora Rings (hhorak, 12:03:21) > > > > [snip] > > >

Re: Meeting minutes for Env-and-Stacks WG meeting (2015-01-14)

- Original Message - > Honza Horak wrote: > > * Fedora Rings (hhorak, 12:03:21) > [snip] > >* IDEA: definition of ring 1 is a minimal set of packages that give > > you a functional system, with some sort of approval (hhorak, > > 13:31:21) > >* IDEA: ring 1 should be self

Re: Remove gcc, gcc-c++ and make from minimal build root

- Original Message - > Dear Fedora developers, > > I'd like to collect some feedback about the $SUBJECT, i.e. making > minimal build root really minimal, explicitly specifying build > dependencies, etc. > > The topic originally spring out in this [1] discussion on packaging > list. Intere

Re: [RFC] Python_Eggs packaging guideline clarification draft

- Original Message - > Changes > --- > > 1. Replaced the term 'eggs' with 'egg metadata' in the whole wiki, while >not messing up the URLs to this[1] on both occurances. > > 2. In section '1.1 Why egg metadata', changed the phrase "Allowing end >users to install eggs not made

Re: Ramblings and questions regarding Fedora, but stemming from gnome-software and desktop environments

- Original Message - > On 02/01/15 11:42, Richard Hughes wrote: > > >> Because as of now, gnome-software just doesn't fit the workstation bill > > > > I think you're misunderstanding what most developers do. We probably > > spend about 10 minutes installing development packages (on the com

Re: Maybe it is time to move tools to Python 3.x?

- Original Message - > Hi, > > On 12/05/2014 03:08 PM, Bohuslav Kabrda wrote: > > - Original Message - > >> Hi, > >> > >> On 12/04/2014 02:30 AM, Matthew Miller wrote: > >>> On Wed, Dec 03, 2014 at 08:13:42PM +0100, Marcin Jusz

Re: Maybe it is time to move tools to Python 3.x?

- Original Message - > Hi, > > On 12/04/2014 02:30 AM, Matthew Miller wrote: > > On Wed, Dec 03, 2014 at 08:13:42PM +0100, Marcin Juszkiewicz wrote: > >> When I worked at Canonical there was a goal to move both internal and > >> public tools to Python 3.x version. IIRC started somewhere ar

Re: Maybe it is time to move tools to Python 3.x?

- Original Message - > W dniu 03.12.2014 o 20:30, Matthew Miller pisze: > > On Wed, Dec 03, 2014 at 08:13:42PM +0100, Marcin Juszkiewicz wrote: > >> When I worked at Canonical there was a goal to move both internal and > >> public tools to Python 3.x version. IIRC started somewhere around 1

Re: Meeting minutes from Env-and-Stacks WG meeting (2014-12-03)

> Action Items > > * bkabrda will ask java guys to create a wiki page summarizing the >approaches we thought of and why we think it's not worth the effort + >post the link to WG ML once it's ready Here it is: https://fedoraproject.org/wiki/User:Mizdebsk/FedoraMavenRepository

Re: Idea: Ability to define dependencies between coprs (correctly)

- Original Message - > Hi all, > > I have a proposal that would change how dependencies are defined in copr: > > Problem: > Currently, copr allows to add a link to an arbitrary repo URL that is > available for installing dependencies during building in copr. Using > this dependent repo li

Re: request for pygrib packaging debug help

- Original Message - > Hi everyone, > > I am having a small issue with the pygrib package that I am maintaining. > The package depends on pyproj, but when I install it with yum it also > pulls in python3-pyproj. > All python3 related things are wrapped in "%if 0%{?with_python3}" > macros,

Re: Python 3.4 merged into Rawhide

- Original Message - > > All the other packages built fine for me locally, so the mass rebuild > > should get the job done for these. > > No, you cannot rely on the mass rebuild here. The reason is that the > mass rebuild goes from a-z, in the alphabetical order and _not_ in the > dependen

Re: Python 3.4 merged into Rawhide

- Original Message - > > On 27.05.2014 16:14, Bohuslav Kabrda wrote: > > Hi all, > > the f21-python side tag, containing Python 3.4, has been merged into > > Rawhide. > I guess this is due to the merge: > > DEBUG util.py:282: Error: Package: python

Python 3.4 merged into Rawhide

Hi all, the f21-python side tag, containing Python 3.4, has been merged into Rawhide. We managed to rebuild 216 packages out of 452 that BR: python3-devel and 7 that BR: python3 - these were the packages (or dependencies of packages) that failed to build in my local mockchain build for some reaso

Re: Python 3 and mod_wsgi

- Original Message - > I naively ported my Django app to Python 3 and didn't realize WSGI was going > to be an issue. I saw python3-django was available for Fedora 20 and thought > I was all set until I saw in my httpd logs that python2.7 seems to be the > assumed default for mod_wsgi. Aft

Re: python packages versus pydoc -k

- Original Message - > Sorry, I should have tried pdb first, because this one has nothing to do > with rpm-python. I can see modname='PyQt4.uic.pyuic', and prior to the > exception site is a line 'loader = importer.find_module(modname)', which > is where the None came from. I can confirm

Summary/Minutes from today's Env-and-Stacks WG meeting (2014-02-18)

= #fedora-meeting: Env and Stacks (2014-02-18) = Meeting started by bkabrda at 13:02:21 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-02-18/env-and-stacks.2014-02-18

Re: Packages installing files to /etc/rpm

- Original Message - > bkabrda python3 amcnabb,bkabrda,mstuchli,tomspur Fixed in python3-3.3.2-9.fc21 > bkabrda python bkabrda,dmalcolm,ivazquez,jsteffan,mstuchli,tomspur,tradej Fixed in python-2.7.6-2.fc21 -- Regards, Bohuslav "Slavek" Kabrda. -- devel mailing list devel@lists.fedora

Summary/Minutes from today's Env-and-Stacks WG Meeting (2014-02-04)

#fedora-meeting: Env and Stacks (2014-02-04) Meeting started by bkabrda at 13:03:24 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-02-04/env_and_stacks.2014-02-04-13

Re: Meeting minutes Env-and-Stacks WG meeting (2014-01-28)

- Original Message - > On 4 February 2014 12:02, Bohuslav Kabrda wrote: > > I tried to rewrite the DevAssistant part to be more high-level and to also > > include information on what we should do with DevAssistant. Hope it's > > enough. > > Should DevA

Re: Meeting minutes Env-and-Stacks WG meeting (2014-01-28)

> ACTION: bkabrda will write more about devassistant (mmaslano, > 16:44:20) I tried to rewrite the DevAssistant part to be more high-level and to also include information on what we should do with DevAssistant. Hope it's enough. Slavek. -- devel mailing list devel@lists.fedoraproject.o

Meeting minutes - today's Env-and-Stacks WG meeting (2013-12-10)

#fedora-meeting: Env and Stacks (2013-12-10) Meeting started by bkabrda at 13:02:36 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2013-12-10/env_and_stacks.2013-12-10-13

Agenda for today's Env-and-Stacks WG meeting (2013-12-10)

WG meeting will be today at 13:00 UTC in #fedora-meeting on Freenode. == Next Steps == - PRD - based on discussion on env-and-stacks mailing list (some discussion on pad: http://piratepad.net/PwUiH4MEPR) == Open Floor == -- devel mailing list devel@lists.fedoraproject.org https://admin.fedora

Python 3.4, ensurepip and wheels

Hi all, so I started to work on packaging Python 3.4 beta 1 and I wanted to create ensurepip patch also acceptable for upstream - Toshio and Nick talked about that at [1]. I tried to analyze the situation and here is what I have. First some facts: - with ensurepip, Python 3.4 bundles setuptools

Re: Meeting minutes - today's Env-and-Stacks WG meeting (2013-11-19)

> * PRD (mmaslano, 16:19:29) >* LINK: http://piratepad.net/PwUiH4MEPR (abadger1999, 17:04:53) >* ACTION: everyone to send one general thing they want the WG to > enable and one specific thing they'd personally want to work on to > the mailing list this week (abadger1999, 17:37

Re: Summary/Minutes from today's FESCo Meeting (2013-10-23)

- Original Message - > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 10/24/2013 02:45 AM, Bohuslav Kabrda wrote: > >> * ticket #1182 F21/F22 System Wide Change: Python 3 as the > >> Default Implementation - > >> https://fedoraproje

Re: Summary/Minutes from today's FESCo Meeting (2013-10-23)

> * ticket #1182 F21/F22 System Wide Change: Python 3 as the Default > Implementation - > https://fedoraproject.org/wiki/Changes/Python_3_as_Default (nirik, > 18:10:29) > * AGREED: Feature is approved, provided that the contingency plan is > updated with permitting a mixed environment

Re: F21/F22 System Wide Change: Python 3 as the Default Implementation

- Original Message - > On Mon, Oct 14, 2013 at 11:05:52PM -0500, Dennis Gilmore wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > El Mon, 14 Oct 2013 02:19:15 -0400 (EDT) > > Bohuslav Kabrda escribió: > > > - Original M

Re: F21/F22 System Wide Change: Python 3 as the Default Implementation

- Original Message - > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > El Thu, 10 Oct 2013 05:35:18 -0400 (EDT) > Bohuslav Kabrda escribió: > > - Original Message - > > > -BEGIN PGP SIGNED MESSAGE- > > > Hash: SHA1 > >

Re: F21/F22 System Wide Change: Python 3 as the Default Implementation

- Original Message - > Is DNF ready for prime time, the is no API at the moment, so it is not > possible to convert tool using the yum api to use a DNF api > I am working on a Python 3 version af yumex, there is package manager for the > XFCE spin, I have isolated all the yum actions in DB

Re: F21/F22 System Wide Change: Python 3 as the Default Implementation

- Original Message - > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Wed, 09 Oct 2013 14:07:12 +0200 > Jaroslav Reznik wrote: > > > ** Request Koji side tag and encourage packagers to rebuilt their > > packages with Python 3 there > python is not in the minimal build root python

Re: Multirelease effort: Moving to Python 3

- Original Message - > On Jul 25, 2013 12:13 AM, "Bohuslav Kabrda" < bkab...@redhat.com > wrote: > > > > - Original Message - > > > Since Python upstream really cares about these things, I started a > > > discussion > > > a

Re: Multirelease effort: Moving to Python 3

- Original Message - > Since Python upstream really cares about these things, I started a discussion > about this on their mailing list [1]. So far, it seems that people prefer my > mental model, but this is judging from just 4 answers, 2 of which mentioned > this. So let's wait and see. >

Re: Multirelease effort: Moving to Python 3

- Original Message - > On Tue, Jul 23, 2013 at 02:40:56AM -0400, Bohuslav Kabrda wrote: > > > > The problem is that you're basically saying "my mental model is the right > > one", which is not necessarily true for everyone (and not necessarily true >

Re: Multirelease effort: Moving to Python 3

- Original Message - > On 23/07/13 03:16 -0400, Bohuslav Kabrda wrote: > > - Original Message - > >> On 19/07/13 02:41 -0400, Bohuslav Kabrda wrote: > >>> - Original Message - > >>>> On Thu, Jul 18, 2013 at 11:24:22AM -0400,

Re: Multirelease effort: Moving to Python 3

- Original Message - > On Tue, 2013-07-23 at 02:40 -0400, Bohuslav Kabrda wrote: > > > python2 and python3 are separate languages. There is a lot of > > similarity > > > between the two and with recent enough versions of python2 (2.7) and > > python3 &g

Re: Multirelease effort: Moving to Python 3

- Original Message - > On 19/07/13 02:41 -0400, Bohuslav Kabrda wrote: > > - Original Message - > >> On Thu, Jul 18, 2013 at 11:24:22AM -0400, Bohuslav Kabrda wrote: > >>> FAQ: > >>> Q: Why do we need to switch to Python 3? > >>

Re: Multirelease effort: Moving to Python 3

- Original Message - > I'm okay with this portion of the definition. One note is I would be > hesitant > about the timing of python3 being the only python that is installed into the > minimal buildroot. This should probably happen in rawhide right after > a branching. > To be more specif

Re: Multirelease effort: Moving to Python 3

- Original Message - > On Thu, Jul 18, 2013 at 11:24:22AM -0400, Bohuslav Kabrda wrote: > > 3) Making all livecd packages depend on Python 3 by default (and > > eventually getting rid of Python 2 from livecd) - this will also require > > switching from Yum to DNF

Re: Multirelease effort: Moving to Python 3

- Original Message - > On Fri, Jul 19, 2013 at 08:20:02AM +0200, Marcela Mašláňová wrote: > > On 07/19/2013 05:44 AM, Toshio Kuratomi wrote: > > > > > >On Jul 18, 2013 5:42 PM, "Michael Catanzaro" > >> wrote: > > > > > > > > On Thu, 2013-07-18 at 09:53 -070

Re: Multirelease effort: Moving to Python 3

- Original Message - > On Thu, Jul 18, 2013 at 11:24:22AM -0400, Bohuslav Kabrda wrote: > > Hi all, > > as a new Fedora Python maintainer, I have set myself a goal of moving > > Fedora to Python 3 as a default. > > I'm not sure we want to make python

Re: Multirelease effort: Moving to Python 3

- Original Message - > On Thu, Jul 18, 2013 at 11:24:22AM -0400, Bohuslav Kabrda wrote: > > Hi all, > > as a new Fedora Python maintainer, I have set myself a goal of > > moving Fedora to Python 3 as a default. > That's a worthy goal! > > > From packa

Multirelease effort: Moving to Python 3

Hi all, as a new Fedora Python maintainer, I have set myself a goal of moving Fedora to Python 3 as a default. This is going to be a multirelease effort that is going to affect lots of Fedora parts. Since we will need to switch default package manager from Yum to DNF (which is supposed to work w

Re: Developers guide for Fedora Linux

- Original Message - > Hello, > > I'm writing some apps for Linux, from time to time. I'd like to know if > there is any comprehensive developers guide for Fedora. I see lot of > changes are made to Fedora (and maybe soon RHEL) like no syslog by > default, systemd machinery, etc. How can o

Re: New package written in Python, without python-*

- Original Message - > Hi everybody, > > I have a question about the name of a new package and would like > everyone's opinion on this issue, because in our wiki > (http://fedoraproject.org/wiki/Features/PythonNamingDependingOnImplementation) > practically forces whatever is written in

Re: packaging java unix sockets library

- Original Message - > Hi, > I recently run into situation where I need to use unix socket in java > program. Fro obvious reasons JAVA doesn't support it out of the box, so > I have to use 3rd party library. After some googling I came to > conclusion that there is no such library in Fedora

Re: Koji - Errno::ECONNREFUSED: Connection refused - getaddrinfo

- Original Message - > Hi, > > Since not a long ago, I cannot build Ruby for Rawhide, while it works > just fine for F19. I observe following 4 errors in its test suite: > > >7) Error: > test_proxy_eh_ENV_no_proxy(TestNetHTTP): > Errno::ECONNREFUSED: Connection refused - getaddrinfo

Re: Django-1.5 for F19

- Original Message - > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Thu 11 Apr 2013 02:56:16 AM EDT, Bohuslav Kabrda wrote: > > - Original Message - > >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > >> > >> On 04/11/2013

Re: Django-1.5 for F19

- Original Message - > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 04/11/2013 04:27 AM, Toshio Kuratomi wrote: > > On Wed, Apr 10, 2013 at 07:53:28AM -0400, Stephen Gallagher wrote: > >> 2) The python-django14 package should add: Obsoletes: > >> python-django < 1.5 Conflicts: py

Re: package, package2, package3 naming-with-version exploit

- Original Message - > On 28. 3. 2013 at 17:45:27, Vít Ondruch wrote: > > Dne 28.3.2013 17:13, seth vidal napsal(a): > > > On Thu, 28 Mar 2013 16:36:27 +0100 > > > > > > Vít Ondruch wrote: > > >> > > >> Ah, are we going to distribute this howtos instead of binary > > >> RPM's > > >> now?

Re: package, package2, package3 naming-with-version exploit

- Original Message - > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 03/28/2013 08:30 AM, Jan Zelený wrote: > > On 28. 3. 2013 at 12:59:44, Vít Ondruch wrote: > >> Dne 28.3.2013 12:09, Florian Festi napsal(a): > >>> This is done to make life easier for package maintainers. > >> >

Re: Python libraries and backwards compat [was Re: What would it take to make Software Collections work in Fedora?]

- Original Message - > On Thu, 2012-12-06 at 07:06 -0800, Adam Williamson wrote: > > On Thu, 2012-12-06 at 15:30 +0100, Nicolas Mailhot wrote: > > > IMHO use of software collections is a symptom of a badly run > > > organisation > > > not devoting enough cycles to maintain the software it u

Re: Django-1.5 build

- Original Message - > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 03/01/2013 02:56 AM, Bohuslav Kabrda wrote: > > - Original Message - On 02/28/2013 05:46 PM, Stephen > > Gallagher wrote: > >>>>> That seems to be a good propos

Re: Django-1.5 build

- Original Message - > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 02/28/2013 05:46 PM, Stephen Gallagher wrote: > >> That seems to be a good proposal for me. Review request is > >> here[1], based on the current python-django package. Shouldn't > >> be an issue. For EPEL, we hav

License Changes of jnr-* Packages

Hi all, I've just updated the jnr-* package stack (dependencies of JRuby and Gradle) and there were some license changes: jnr-constants - previously MIT, now ASL 2.0 jnr-ffi - previously ASL 2.0 or LGPLv3+, now ASL 2.0 jnr-netdb - previously LGPLv3, now ASL 2.0 jnr-x86asm - previously LGPLv3, now

Re: Proposed F19 Feature: JRuby 1.7 - JRuby is an alternative Ruby implementation

- Original Message - > Hello, > On Thu, Jan 24, 2013 at 7:58 AM, Bohuslav Kabrda > wrote: > > - Original Message - > >> What problem are the _mri_/_jruby_ parameters solving? > >> a) If a script or command-line user requires a specific > >>

Re: Proposed F19 Feature: JRuby 1.7 - JRuby is an alternative Ruby implementation

- Original Message - > On Wed, Jan 16, 2013 at 2:05 PM, Jaroslav Reznik > wrote: > > As decided by FESCo on 2012-12-05 meeting, all proposed Features > > are required > > to pass through the community review by announcing them on > > devel-announce list. > > FESCo votes on new features no

Re: Proposed F19 Feature: JRuby 1.7 - JRuby is an alternative Ruby implementation

- Original Message - > On Wed, Jan 16, 2013 at 2:05 PM, Jaroslav Reznik > wrote: > > = Features/JRuby 1.7 = > > https://fedoraproject.org/wiki/Features/JRuby_1.7 > > > What should "/usr/bin/ruby" point to? During standard Gem > > packaging process, > > the executable files in Gems get

Re: Proposed F19 Feature: JRuby 1.7 - JRuby is an alternative Ruby implementation

- Original Message - > I think the more interesting question is what to do about extensions > (ie. not pure Ruby gems that contain C code). Last time I looked > JRuby was pretty incompatible; in fact for libguestfs we recommend > that people use the *Java* bindings with JRuby ... > > Rich

Re: Proposed F19 Feature: JRuby 1.7 - JRuby is an alternative Ruby implementation

- Original Message - > On Wed, Jan 16, 2013 at 08:05:23AM -0500, Jaroslav Reznik wrote: > > > > - Changes in packaging > > None yet. JRuby will be able to use pure Ruby Gems packaged into > > RPM out of > > the box, but packaging of Gems with JRuby extensions is turning > > out to be >

Re: Ruby 2.0 in F19

- Original Message - > On Thu, 20 Dec 2012 13:47:56 +0100 > Vít Ondruch wrote: > > > Hi everybody, > > ...snip... > > >- Due to better integration of JRuby into Fedora [3], we would > > like to take this opportunity to restructure RubyGems folder > > layout. This should allow u

Re: What would it take to make Software Collections work in Fedora?

- Original Message - > On Thu, 2012-12-06 at 02:57 -0500, Bohuslav Kabrda wrote: > > Packaging two parallel versions of interpreters brings not only the > > burden of maintaining them, but also the work to make them not > > conflict. E.g. renaming binaries, checking

Re: What would it take to make Software Collections work in Fedora?

- Original Message - > Hi > On Wed, Dec 5, 2012 at 4:04 PM, Matthew Miller wrote: > > 1) Fedora is big enough that we have concrete situations where one > > size > > > doesn't fit all. Puppet being broken on F17 (and probably F18 as > > well) > > > is a fine example of something within

Re: Packages in need of new maintainers

I'll take rubygem-bacon rubygem-sinatra since I'm already their comaintainer. FAS name: bkabrda Thanks, Slavek. -- Regards, Bohuslav "Slavek" Kabrda. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel

Rails updated to 3.2.6 in Rawhide

Hi all! The Ruby on Rails stack has been updated to 3.2.6 version in Rawhide, as it was submitted in the Rails 3.2 Feature [1]. I'd like to ask all owners of depending packages to start rebuilding (or updating, if necessary). The depending packages are listed at [2]. Thanks! -- Regards, Bohusl

Re: Django-* to python-django-* rename

- Original Message - > 2012/7/11 Matthias Runge : > > On 07/11/2012 02:33 PM, Rakesh Pandit wrote: > >> > >> @devel > >> May someone take care of this rename and review so that it happens > >> before f18 branching ? > >> > >> Regards, > >> > > done > > > > https://bugzilla.redhat.com/show_b

Re: Introducing pyp2rpm - A python package to rpm specfile convertor

- Original Message - > Hi all, > for past few days, I've been working on a project called pyp2rpm. > It's a tool that allows you to easily convert python package from > PyPI to an RPM specfile. I would like to get it tested before I > package it into Fedora, so if anyone is interested, here

Ruby and Fedora 17

Hi all, since Ruby/Fedora integration had some significant changes from F16 to F17, I thought it might be a good idea to write a summary of new features and send it out for all - see [1]. All comments and suggestions for further development are welcome. -- Regards, Bohuslav "Slavek" Kabrda. [

Re: Introducing pyp2rpm - A python package to rpm specfile convertor

- Original Message - > On 05/23/2012 06:55 PM, Bohuslav Kabrda wrote: > >> # monkey patch ZipFile to behave like TarFile > >> ZipFile.getmembers = ZipFile.infolist > >> ZipFile.extractfile = ZipFile.open > >> ZipFile.open = ZipFile # this

rubygem-main and rubygem-fattr license change

Hi all, due to license change in Ruby, rubygem-main and rubygem-fattr licenses have been changed (after clarification with the author). Previous licenses were GPLv2+ or Ruby, current licenses are BSD or Ruby. The change applies to F17 and rawhide. -- Regards, Bohuslav "Slavek" Kabrda. -- devel

Re: Bug #787712 threaded python deadlocks

- Original Message - > Hey folks, > https://bugzilla.redhat.com/show_bug.cgi?id=787712 > I am hitting this bug very frequently on Fedora 16 where python > deadlocks. I tried to apply the patch in this bug to python.src.rpm > currently in Fedora 16, but my local rpmbuild fails with a test

Re: [Guidelines Change] Changes to the Packaging Guidelines

older version, but from user point of view almost the same as current one). - Original Message - > On 02/07/2012 03:50 PM, Bohuslav Kabrda wrote: > > Ralf Corsepius wrote: > >> I am inclined to agree, but why would the Fedora project want to > >> do

  1   2   >