On 06/30/2011 10:25 AM, Mathias Homann wrote:
nope, my package works fine, I just don't know if the requirement "python>= 2.7.1" on calibre's website is just a quirk or actually justified...
I think the author actually meant "Don't use Python3". So please submit updated calibre to Factory and we can move on :)
Hi Ismail,
Ismail Doenmez idoenmez@suse.de wrote at Thursday 30 June 2011:
On 06/30/2011 10:25 AM, Mathias Homann wrote:
nope, my package works fine, I just don't know if the requirement "python>= 2.7.1" on calibre's website is just a quirk or actually justified...
I think the author actually meant "Don't use Python3". So please submit updated calibre to Factory and we can move on :)
Better submit to the official devel Project Documentation:Tools instead of Factory. :-)
Heya;
On 06/30/2011 02:08 PM, Sascha Manns wrote:
Hi Ismail,
Ismail Doenmezidoenmez@suse.de wrote at Thursday 30 June 2011:
On 06/30/2011 10:25 AM, Mathias Homann wrote:
nope, my package works fine, I just don't know if the requirement "python>= 2.7.1" on calibre's website is just a quirk or actually justified...
I think the author actually meant "Don't use Python3". So please submit updated calibre to Factory and we can move on :)
Better submit to the official devel Project Documentation:Tools instead of Factory. :-)
Can you update it and push to Factory now? We shouldn't make our users wait much more :)
Regards.
Ismail Doenmez schrieb:
Heya;
On 06/30/2011 02:08 PM, Sascha Manns wrote:
Hi Ismail,
Ismail Doenmezidoenmez@suse.de wrote at Thursday 30 June 2011:
On 06/30/2011 10:25 AM, Mathias Homann wrote:
nope, my package works fine, I just don't know if the requirement "python>= 2.7.1" on calibre's website is just a quirk or actually justified...
I think the author actually meant "Don't use Python3". So please submit updated calibre to Factory and we can move on :)
Better submit to the official devel Project Documentation:Tools instead of Factory. :-)
Can you update it and push to Factory now? We shouldn't make our users wait much more :)
Seeing how every new version of calibre brings new newsfeeds to be autofetched, I think any new calibre package should actually go into openSUSE:11.x:Update as well, but that's just me thinking.
bye, MH
Hi,
On Friday 01 July 2011 Mathias Homann wrote:
[...] Seeing how every new version of calibre brings new newsfeeds to be autofetched, I think any new calibre package should actually go into openSUSE:11.x:Update as well, but that's just me thinking.
Unfortunately, this is almost impossible. Calibre can be very challenging when trying to package it. Every release brings new suprises. It has so much dependencies to other packages that an update can bring you LOTS of updated or new packages. Calibre is one of the packages that tries to be as "bleeding-edge" as possible.
Thomas Schraitle schrieb:
Hi,
On Friday 01 July 2011 Mathias Homann wrote:
[...] Seeing how every new version of calibre brings new newsfeeds to be autofetched, I think any new calibre package should actually go into openSUSE:11.x:Update as well, but that's just me thinking.
Unfortunately, this is almost impossible. Calibre can be very challenging when trying to package it. Every release brings new suprises. It has so much dependencies to other packages that an update can bring you LOTS of updated or new packages. Calibre is one of the packages that tries to be as "bleeding-edge" as possible.
amen to that.
unfortunately it is also the best package for managing ebooks on an ebook reader device that I know of...
bye, MH