From unapersson at linuxmail.org Fri Feb 1 07:24:22 2008 From: unapersson at linuxmail.org (Ian Davey) Date: Fri, 01 Feb 2008 12:24:22 +0000 Subject: [Alexandria-list] CSV import In-Reply-To: <20080131200909.0b095f73@matilda> References: <1201711602.6948.5.camel@timdesktop> <20080131200909.0b095f73@matilda> Message-ID: <47A30F76.4080702@linuxmail.org> Cathal Mc Ginley wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Wed, 30 Jan 2008 11:46:42 -0500 > Timothy Malone wrote: > >> I've been working on an import filter for CSV files and had a few >> questions. The primary focus of my filter is the CSV format used by >> goodreads.com (sorta like librarything). > > Neat. LibraryThing import is also somewhere on our list of things to do. One useful feature that LibraryThing also has is an RSS feed of recently added books. So Alexandria could potentially plug into that to automatically update a library (or perhaps just show the feed results as some kind of virtual library to let you drag books into one of the static libraries you've defined). As for the reading management side of things, I'm happy to do some work on that once the core has been stabilised. I made a start in the past, and added some elements as a new tab in the UI and adding some of the required fields. It was done as more of a learning exercise to get to grips with Ruby/Glade/GTK and I've still got the code lying around somewhere, but there have been quite a few releases since then. As a more immediate thing I could pad out the wiki page with some more detailed requirements. ian. From tristil at gmail.com Fri Feb 1 12:22:44 2008 From: tristil at gmail.com (Joseph Method) Date: Fri, 1 Feb 2008 12:22:44 -0500 Subject: [Alexandria-list] CSV import In-Reply-To: <47A30F76.4080702@linuxmail.org> References: <1201711602.6948.5.camel@timdesktop> <20080131200909.0b095f73@matilda> <47A30F76.4080702@linuxmail.org> Message-ID: <167b6aa00802010922l6bf62f1bx5b1249583bae96e0@mail.gmail.com> > As for the reading management side of things, I'm happy to do some work > on that once the core has been stabilised. I made a start in the past, > and added some elements as a new tab in the UI and adding some of the > required fields. It was done as more of a learning exercise to get to > grips with Ruby/Glade/GTK and I've still got the code lying around > somewhere, but there have been quite a few releases since then. The code described here is supposed to be a kind of reading manager: http://blog.alexandria-projects.org/2008/1/16/setup-for-alexandria-development-iii and here: http://alexandria.rubyforge.org/svn/trunk/readinglist/lib/readinglist.rb For big, untested changes to the main UI, I'd like for us to use branches to show feasibility and get reactions from the list. You do that by first doing an svn cp of alexandria trunk to a branch, checking that out and working with that. Later you merge code back and forth between trunk and the branch copy. Standalone applications can go straight into their own directories under http://alexandria.rubyforge.org/svn/trunk/. -- -J. Method From hdevalence at gmail.com Fri Feb 1 12:34:21 2008 From: hdevalence at gmail.com (Henry de Valence) Date: Fri, 1 Feb 2008 12:34:21 -0500 Subject: [Alexandria-list] Alexandria on KDE Message-ID: <200802011234.21680.hdevalence@gmail.com> I personally like KDE (KDE4 blows GNOME out of the water IMO, but this isn't the place for flamewars about that), but I've found alexandria to be the best book manager out there (that's a compliment, btw). I've found, however, that using GNOME programs in KDE4 makes them stick out like a sore thumb, not because they look worse, but just because they are totally inconsistent with the "look", if you know what I mean. As far as I can tell, it shouldn't be *too* difficult (a lot of work though) to write a QT4/KDE4 based frontend. If I were to do that, would you be interested in including it or do you want to stick to just having a gnome frontend? -- Harry de Valence From tristil at gmail.com Fri Feb 1 12:39:01 2008 From: tristil at gmail.com (Joseph Method) Date: Fri, 1 Feb 2008 12:39:01 -0500 Subject: [Alexandria-list] CSV import In-Reply-To: <1201812556.6932.16.camel@timdesktop> References: <1201711602.6948.5.camel@timdesktop> <20080131200909.0b095f73@matilda> <1201812556.6932.16.camel@timdesktop> Message-ID: <167b6aa00802010939m2a90608dse1f54992931b5985@mail.gmail.com> > That is a really good point. I did write a patch for the "Date Read" > field and it worked in all my testing with no compatibility problems, so > I ended up committing it (revision 892 I believe). Feel free to reverse > that if it was a bit premature. I hadn't considered the reading > management issue before. My two cents on it would be that it should be a > tab of its own (or plugin like the wiki suggests), but that "Date Read" > is used commonly enough that it should remain on the main properties > page. I noticed that, Timothy. Thanks for implementing that feature! I had started working on this but you got there first with a smaller UI imprint. There are a couple of places where the date read field needs to be added to the UI now: in the main @listview columns and in the column visibility list under Preferences. That is, perhaps date read will not be a visible column default, but it should be an option to see it. I'll get around to adding these if you don't. About the commit messages from the alexandria-commits lists: sometimes an email ends up in my mail box asking me to approve a commit message because it's too long. I'm not sure I even have the password for the commits list. Another way to get commit messages is here: http://wiki.alexandria-projects.org/changesets and for the rss feed: http://wiki.alexandria-projects.org/rss/changesets. -- -J. Method From tristil at gmail.com Fri Feb 1 13:04:51 2008 From: tristil at gmail.com (Joseph Method) Date: Fri, 1 Feb 2008 13:04:51 -0500 Subject: [Alexandria-list] Alexandria on KDE In-Reply-To: <200802011234.21680.hdevalence@gmail.com> References: <200802011234.21680.hdevalence@gmail.com> Message-ID: <167b6aa00802011004v5d0f4b08rcedc98cc18ef5742@mail.gmail.com> I think it's fine. If you put in a check for the current window manager, it could even have the same executable. I'm actually strongly in favor of this simply because it will help us with getting cleaner separation of concerns. But let's hear what others think. And *please* no Gnome/KDE flamewars :) On Feb 1, 2008 12:34 PM, Henry de Valence wrote: > I personally like KDE (KDE4 blows GNOME out of the water IMO, but this isn't > the place for flamewars about that), but I've found alexandria to be the best > book manager out there (that's a compliment, btw). I've found, however, that > using GNOME programs in KDE4 makes them stick out like a sore thumb, not > because they look worse, but just because they are totally inconsistent with > the "look", if you know what I mean. As far as I can tell, it shouldn't be > *too* difficult (a lot of work though) to write a QT4/KDE4 based frontend. If > I were to do that, would you be interested in including it or do you want to > stick to just having a gnome frontend? > -- > Harry de Valence > _______________________________________________ > Alexandria-list mailing list > Alexandria-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/alexandria-list > -- -J. Method From unapersson at linuxmail.org Fri Feb 1 13:06:19 2008 From: unapersson at linuxmail.org (Ian Davey) Date: Fri, 01 Feb 2008 18:06:19 +0000 Subject: [Alexandria-list] Alexandria on KDE In-Reply-To: <200802011234.21680.hdevalence@gmail.com> References: <200802011234.21680.hdevalence@gmail.com> Message-ID: <47A35F9B.9080800@linuxmail.org> Henry de Valence wrote: > I personally like KDE (KDE4 blows GNOME out of the water IMO, but this isn't > the place for flamewars about that), but I've found alexandria to be the best > book manager out there (that's a compliment, btw). I've found, however, that > using GNOME programs in KDE4 makes them stick out like a sore thumb, not > because they look worse, but just because they are totally inconsistent with > the "look", if you know what I mean. As far as I can tell, it shouldn't be > *too* difficult (a lot of work though) to write a QT4/KDE4 based frontend. If > I were to do that, would you be interested in including it or do you want to > stick to just having a gnome frontend? You can always use this plugin: http://gtk-qt.ecs.soton.ac.uk/ ian. From hdevalence at gmail.com Fri Feb 1 13:11:07 2008 From: hdevalence at gmail.com (Henry de Valence) Date: Fri, 1 Feb 2008 13:11:07 -0500 Subject: [Alexandria-list] Alexandria on KDE In-Reply-To: <167b6aa00802011004v5d0f4b08rcedc98cc18ef5742@mail.gmail.com> References: <200802011234.21680.hdevalence@gmail.com> <167b6aa00802011004v5d0f4b08rcedc98cc18ef5742@mail.gmail.com> Message-ID: <200802011311.08023.hdevalence@gmail.com> On Friday 01 February 2008 1:04:51 pm Joseph Method wrote: > I think it's fine. If you put in a check for the current window > manager, it could even have the same executable. I'm actually strongly > in favor of this simply because it will help us with getting cleaner > separation of concerns. But let's hear what others think. > > And *please* no Gnome/KDE flamewars :) Yeah, I really don't want to get into that. It's not like anyone changes their opinion based on a flamewar anyways. And also, just pointing out, I don't have lots of free time, so it would take a while. Also while I know there are QT4 bindings for ruby, I don't know what the state of KDE4 bindings for ruby (is/are?). -- Harry de Valence From timothy.malone at gmail.com Fri Feb 1 13:36:55 2008 From: timothy.malone at gmail.com (Timothy Malone) Date: Fri, 01 Feb 2008 13:36:55 -0500 Subject: [Alexandria-list] Snart-libraries and time Message-ID: <1201891015.7133.11.camel@timdesktop> So as it stands, smart libraries don't work correctly with Time based data (loaned since and now date read). This is because you cannot compare two Time entries with < or >. I have a patch that fixes that aspect (that I'm committing right now), but I'm wondering if we should also add some code to sanitize these values. Right now, if you have ever had a book as loaned it retains the loaned_since field even after the book is "returned". As far as I can tell there is no way to have the smart-library filter on more than one data point (you can't check to see if a book is loaned while filtering on the loaned_since entry) unless the user chooses that explicitly. This makes the smart_library show the user books that are not still loaned. This is especially confusing for the user since we don't fill the loaned_since entry in the gui with a date unless the loaned checkbox is active (even if a loaned_since value is stored in the file, we only show it to the user if the book is currently loaned). My initial reaction to finding this out was to look for all the places we need to scrub this data out, but then I realized that maybe there is some value to keeping the data around. Perhaps users would like to be able to see when the last time a book was loaned? In which case I guess we should actually load that data into the GUI? Either way I think something needs to be fixed, I'm just not sure what. :) Tim From devi.webmaster at gmail.com Fri Feb 1 14:00:10 2008 From: devi.webmaster at gmail.com (Daniel Brumbaugh Keeney) Date: Fri, 1 Feb 2008 13:00:10 -0600 Subject: [Alexandria-list] Alexandria on KDE In-Reply-To: <200802011234.21680.hdevalence@gmail.com> References: <200802011234.21680.hdevalence@gmail.com> Message-ID: <3bceeb2d0802011100y21266ac1m284f6498d267307d@mail.gmail.com> On Feb 1, 2008 11:34 AM, Henry de Valence wrote: > I personally like KDE (KDE4 blows GNOME out of the water IMO, but this isn't > the place for flamewars about that), but I've found alexandria to be the best > book manager out there (that's a compliment, btw). I've found, however, that > using GNOME programs in KDE4 makes them stick out like a sore thumb, not > because they look worse, but just because they are totally inconsistent with > the "look", if you know what I mean. As far as I can tell, it shouldn't be > *too* difficult (a lot of work though) to write a QT4/KDE4 based frontend. If > I were to do that, would you be interested in including it or do you want to > stick to just having a gnome frontend? > -- > Harry de Valence If we are going to go to the trouble of writing an additional frontend, I would recommend WxRuby, which uses the native toolkit. (I haven't tested on KDE to actually see how "normal" it is). As opposed to writing a second interface that will only work on one desktop environment, why not write a second interface for many environments? Daniel Brumbaugh Keeney From hdevalence at gmail.com Fri Feb 1 14:05:58 2008 From: hdevalence at gmail.com (Henry de Valence) Date: Fri, 1 Feb 2008 14:05:58 -0500 Subject: [Alexandria-list] Alexandria on KDE In-Reply-To: <3bceeb2d0802011100y21266ac1m284f6498d267307d@mail.gmail.com> References: <200802011234.21680.hdevalence@gmail.com> <3bceeb2d0802011100y21266ac1m284f6498d267307d@mail.gmail.com> Message-ID: <200802011405.58969.hdevalence@gmail.com> On Friday 01 February 2008 2:00:10 pm Daniel Brumbaugh Keeney wrote: > If we are going to go to the trouble of writing an additional > frontend, I would recommend WxRuby, which uses the native toolkit. (I > haven't tested on KDE to actually see how "normal" it is). As opposed > to writing a second interface that will only work on one desktop > environment, why not write a second interface for many environments? > > Daniel Brumbaugh Keeney I've never used or heard much about WxRuby. -- Harry de Valence From hdevalence at gmail.com Fri Feb 1 14:08:05 2008 From: hdevalence at gmail.com (Henry de Valence) Date: Fri, 1 Feb 2008 14:08:05 -0500 Subject: [Alexandria-list] Alexandria on KDE (oops) In-Reply-To: <3bceeb2d0802011100y21266ac1m284f6498d267307d@mail.gmail.com> References: <200802011234.21680.hdevalence@gmail.com> <3bceeb2d0802011100y21266ac1m284f6498d267307d@mail.gmail.com> Message-ID: <200802011408.05875.hdevalence@gmail.com> Accidentally pressed 'send'. Sorry. On Friday 01 February 2008 2:00:10 pm Daniel Brumbaugh Keeney wrote: > If we are going to go to the trouble of writing an additional > frontend, I would recommend WxRuby, which uses the native toolkit. (I > haven't tested on KDE to actually see how "normal" it is). As opposed > to writing a second interface that will only work on one desktop > environment, why not write a second interface for many environments? > > Daniel Brumbaugh Keeney I've never used or heard much about WxRuby. I would point out, however, that KDE/Qt works on all platforms (X11/OSX/Win) and looks native on each of them. -- Harry de Valence From marrakis at gmail.com Fri Feb 1 14:15:24 2008 From: marrakis at gmail.com (Mathieu Leduc-Hamel) Date: Fri, 1 Feb 2008 14:15:24 -0500 Subject: [Alexandria-list] Alexandria on KDE (oops) In-Reply-To: <200802011408.05875.hdevalence@gmail.com> References: <200802011234.21680.hdevalence@gmail.com> <3bceeb2d0802011100y21266ac1m284f6498d267307d@mail.gmail.com> <200802011408.05875.hdevalence@gmail.com> Message-ID: Yes but Qt will not look native on gnome... And I'm not sure it's really an improvement to use a toolkit like Wx which is great but is like a stranger everywhere On Feb 1, 2008 2:08 PM, Henry de Valence wrote: > Accidentally pressed 'send'. Sorry. > On Friday 01 February 2008 2:00:10 pm Daniel Brumbaugh Keeney wrote: > > If we are going to go to the trouble of writing an additional > > frontend, I would recommend WxRuby, which uses the native toolkit. (I > > haven't tested on KDE to actually see how "normal" it is). As opposed > > to writing a second interface that will only work on one desktop > > environment, why not write a second interface for many environments? > > > > Daniel Brumbaugh Keeney > I've never used or heard much about WxRuby. I would point out, however, that > KDE/Qt works on all platforms (X11/OSX/Win) and looks native on each of them. > -- > Harry de Valence > _______________________________________________ > Alexandria-list mailing list > Alexandria-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/alexandria-list > From cathal.alexandria at gnostai.org Fri Feb 1 18:32:54 2008 From: cathal.alexandria at gnostai.org (Cathal Mc Ginley) Date: Fri, 1 Feb 2008 23:32:54 +0000 Subject: [Alexandria-list] Alexandria on KDE In-Reply-To: <200802011311.08023.hdevalence@gmail.com> References: <200802011234.21680.hdevalence@gmail.com> <167b6aa00802011004v5d0f4b08rcedc98cc18ef5742@mail.gmail.com> <200802011311.08023.hdevalence@gmail.com> Message-ID: <20080201233254.5872990b@matilda> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 1 Feb 2008 13:11:07 -0500 Henry de Valence wrote: > On Friday 01 February 2008 1:04:51 pm Joseph Method wrote: > > I think it's fine. If you put in a check for the current window > > manager, it could even have the same executable. The (abandoned) OSX GUI did that, and ended up tangling GNOME & Ruby/COCOA code throughout several files (I disentangled it just before the 0.6.2 release). If the core is cleanly designed, a separate application for each GUI front-end would probably be best. > > I'm actually > > strongly in favor of this simply because it will help us with > > getting cleaner separation of concerns. Domain analysis would also serve that end. However, I agree that if we create a well-factored "Application Facade" layer, then both a GNOME and a KDE front-end could be supported, preferably as a thin display layer on top of common application code. I have been developing a proof-of-concept application (in a different application domain) to try out very clean separation of domain and GUI. Perhaps a small-scale test of attaching a KDE GUI to a common application core would be helpful. Perhaps I can ping a few people when I have my sample app ready to try this out. > And also, just pointing out, I don't have lots of free time, so it > would take a while. Also while I know there are QT4 bindings for > ruby, I don't know what the state of KDE4 bindings for ruby > (is/are?). Korundum and QtRuby only mention KDE/Qt 3.x support on their web page: http://developer.kde.org/language-bindings/ruby/index.html But apparently 4.x support is possible, or at least in progress: http://dot.kde.org/1189467731/1189482359/ There's also some talk of QtRuby being used with Kross, the scripting framework for KDE 4: http://www.kdedevelopers.org/node/3187 - C. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE iD8DBQFHo6wwfMAUnRdb+8oRAm+sAJ0b+PVhtRMcGzIRwC72hXVwZW2JOwCeOpUQ GtaGTmXzsZFaFJFr4Kh6GqY= =71BV -----END PGP SIGNATURE----- From hdevalence at gmail.com Fri Feb 1 23:32:14 2008 From: hdevalence at gmail.com (Henry de Valence) Date: Fri, 1 Feb 2008 23:32:14 -0500 Subject: [Alexandria-list] Alexandria on KDE In-Reply-To: <20080201233254.5872990b@matilda> References: <200802011234.21680.hdevalence@gmail.com> <200802011311.08023.hdevalence@gmail.com> <20080201233254.5872990b@matilda> Message-ID: <200802012332.15029.hdevalence@gmail.com> On Friday 01 February 2008 6:32:54 pm Cathal Mc Ginley wrote: > On Fri, 1 Feb 2008 13:11:07 -0500 > > Henry de Valence wrote: > > On Friday 01 February 2008 1:04:51 pm Joseph Method wrote: > > > I think it's fine. If you put in a check for the current window > > > manager, it could even have the same executable. > > The (abandoned) OSX GUI did that, and ended up tangling GNOME & > Ruby/COCOA code throughout several files (I disentangled it just > before the 0.6.2 release). If the core is cleanly designed, a separate > application for each GUI front-end would probably be best. > > > > I'm actually > > > strongly in favor of this simply because it will help us with > > > getting cleaner separation of concerns. > > Domain analysis would also serve that end. However, I agree that if we > create a well-factored "Application Facade" layer, then both a GNOME > and a KDE front-end could be supported, preferably as a thin display > layer on top of common application code. > > I have been developing a proof-of-concept application (in a different > application domain) to try out very clean separation of domain and GUI. > Perhaps a small-scale test of attaching a KDE GUI to a common > application core would be helpful. Perhaps I can ping a few people when > I have my sample app ready to try this out. > > > And also, just pointing out, I don't have lots of free time, so it > > would take a while. Also while I know there are QT4 bindings for > > ruby, I don't know what the state of KDE4 bindings for ruby > > (is/are?). > > Korundum and QtRuby only mention KDE/Qt 3.x support on their web page: > http://developer.kde.org/language-bindings/ruby/index.html > But apparently 4.x support is possible, or at least in progress: > http://dot.kde.org/1189467731/1189482359/ > > There's also some talk of QtRuby being used with Kross, the scripting > framework for KDE 4: > http://www.kdedevelopers.org/node/3187 > > > - C. AFAIK Kross is supposed to be used to script with a normal Qt/C++ application, but I might be wrong. It would, IMO, be worth looking into whether one could use Kross so that the frontend would be written in C++ and it would talk to the main alexandria ruby app using Kross. I have no idea if this is possible, but it seems like something Kross is supposed to do. Before I get flamed for suggesting C++, I'd like to point out that I'm not against using Qt/Ruby, I just think this is worth considering. * Most KDE programs are written in C++. This means there are a lot more people who would be willing to contribute than if they were deterred by having to learn the Qt/Ruby bindings. * A binary Qt/C++ program will probably run slightly faster than a Ruby program, although nowadays this isn't as big of a factor, because computers are, in general, faster. * Related to the first point, since most KDE programs are written in C++, you will have more up-to-date tools. Keep in mind that I'm not suggesting you rewrite any of Alexandria to use Qt, I'm just saying that if you're writing a new frontend/backend architecture anyways, you should probably write the KDE frontend (if there is one) in C++, because of the reasons I listed above. -- Harry de Valence From cathal.alexandria at gnostai.org Thu Feb 7 22:33:45 2008 From: cathal.alexandria at gnostai.org (Cathal Mc Ginley) Date: Fri, 8 Feb 2008 03:33:45 +0000 Subject: [Alexandria-list] Amazon AWS 3.0 deprecation, switch to ECS 4.0 Message-ID: <20080208033345.24b89c1f@matilda> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I recently got this reminder from the "Amazon Web Services Developer Connection Newsletter": This is an important reminder that the Amazon E-Commerce Web Service 3.0 will be deprecated on March 31st, 2008, after which we will no longer accept Amazon ECS 3.0 requests. Ruby/Amazon is based upon the AWS v3 API, so I think we're going to have to rewrite our Amazon provider. There exists a small, simple ruby library for dealing with Amazon ECS version 4.0 (the RESTful API): amazon-ecs http://www.pluitsolutions.com/projects/amazon-ecs which has an MIT license (not very clear from the website, but in the code). The library is 300 lines of Ruby, so there is a case for incorporating it directly into Alexandria, perhaps even cutting it down and modifying it as needed (being careful with the copyright notices of course!). As it's such a small lib, a lot of the nice object structure provided by Ruby/Amazon is absent (from what I've seen with a quick glance). But it does allow us to interact with the RESTful web service on a fine-grained level. Anyway, I was thinking of writing this thing myself, but I've plenty of other stuff to be working on & I've decided not to be greedy! :^) So, in case anyone else wants to have a go, this could be a good place to start coding on Alexandria. You just have to read up on Amazon ECS 4.0, there's a migration guide here: http://developer.amazonwebservices.com/connect/entry.jspa?externalID=627 Then have a look at the current provider: lib/alexandria/book_providers/amazon.rb and create a new one in its image (amazon_ecs.rb) and start switching over the features. Anyway, we're going to need new Amazon ECS support for our next release, so if no-one gets around to writing this I'm sure I can handle it. If I do, I'll write a tutorial on how I approached it. - Cathal. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE iD8DBQFHq82kfMAUnRdb+8oRAgs8AKDTeL8b4akEcOcJVCvuSrqDj3tzUQCgpixE oFrYU/YHvL8YvCHtMGDT7Tk= =3Voa -----END PGP SIGNATURE----- From mariusmeinert at monroebrothers.org Sat Feb 9 15:23:25 2008 From: mariusmeinert at monroebrothers.org (Marius Meinert) Date: Sat, 9 Feb 2008 21:23:25 +0100 Subject: [Alexandria-list] Screencast on ShowMeD Message-ID: <38DFDDB7-4A4F-4A6F-933F-53599EA90C89@monroebrothers.org> #Hi, since Alexandria was standard in Ubuntu Breezy I loved it, but I couldn't use it, because this Amazon-bug for non-US Amazons. I subscribed to the Mailinglist and used the first svn builds to solve this problem. Since then I really love Alexandria and that's why I made a screencast. A screencast is a recording of the screen and speech by the author of the screencast. This technique can be used to explain almost everything that you can do on a computer to new users. ShowMeDo is a website that allows you upload your own screencasts. This website has a great international community, that initially came from the Python but has been growing since 2005. At ShowMeDo we made a new series of screencasts called "My favourite apps", where people can showcase their favourite applications. So I made a video about Alexandria, showing some basic functionality and I think it might be useful to new users (Even if i have to apologise for my English.). You can find it on . Cheers, Marius -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/alexandria-list/attachments/20080209/088e272d/attachment.html From tristil at gmail.com Sat Feb 9 20:00:29 2008 From: tristil at gmail.com (Joseph Method) Date: Sat, 9 Feb 2008 20:00:29 -0500 Subject: [Alexandria-list] Screencast on ShowMeD In-Reply-To: <38DFDDB7-4A4F-4A6F-933F-53599EA90C89@monroebrothers.org> References: <38DFDDB7-4A4F-4A6F-933F-53599EA90C89@monroebrothers.org> Message-ID: <167b6aa00802091700u28d5ad8m36b4762213b8a92d@mail.gmail.com> That's awesome, Marius. Thanks for doing this! We're working on making the install process easier. On Feb 9, 2008 3:23 PM, Marius Meinert wrote: > #Hi, > since Alexandria was standard in Ubuntu Breezy I loved it, but I couldn't > use it, because this Amazon-bug for non-US Amazons. I subscribed to the > Mailinglist and used the first svn builds to solve this problem. Since then > I really love Alexandria and that's why I made a screencast. > A screencast is a recording of the screen and speech by the author of the > screencast. This technique can be used to explain almost everything that you > can do on a computer to new users. > ShowMeDo is a website that allows you upload your own screencasts. This > website has a great international community, that initially came from the > Python but has been growing since 2005. > At ShowMeDo we made a new series of screencasts called "My favourite apps", > where people can showcase their favourite applications. > So I made a video about Alexandria, showing some basic functionality and I > think it might be useful to new users (Even if i have to apologise for my > English.). You can find it on > . > Cheers, > Marius > _______________________________________________ > Alexandria-list mailing list > Alexandria-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/alexandria-list > -- -J. Method From tristil at gmail.com Sat Feb 9 23:07:00 2008 From: tristil at gmail.com (Joseph Method) Date: Sat, 9 Feb 2008 23:07:00 -0500 Subject: [Alexandria-list] Amazon AWS 3.0 deprecation, switch to ECS 4.0 In-Reply-To: <20080208033345.24b89c1f@matilda> References: <20080208033345.24b89c1f@matilda> Message-ID: <167b6aa00802092007m3563cfd7g88850ae0f658be93@mail.gmail.com> Hey, this all sounds good, although I don't know anything about it :). One thought, maybe we should just check in the source and start maintaining it here, since we're probably one of the main consumers of it now? Maybe not. On Feb 7, 2008 10:33 PM, Cathal Mc Ginley wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I recently got this reminder from the "Amazon Web Services Developer > Connection Newsletter": > > This is an important reminder that the Amazon > E-Commerce Web Service 3.0 will be deprecated on March 31st, 2008, > after which we will no longer accept Amazon ECS 3.0 requests. > > Ruby/Amazon is based upon the AWS v3 API, so I think we're going to > have to rewrite our Amazon provider. There exists a small, simple ruby > library for dealing with Amazon ECS version 4.0 (the RESTful API): > amazon-ecs http://www.pluitsolutions.com/projects/amazon-ecs > which has an MIT license (not very clear from the website, but in the > code). The library is 300 lines of Ruby, so there is a case for > incorporating it directly into Alexandria, perhaps even cutting it down > and modifying it as needed (being careful with the copyright notices > of course!). > > As it's such a small lib, a lot of the nice object structure provided by > Ruby/Amazon is absent (from what I've seen with a quick glance). But it > does allow us to interact with the RESTful web service on a > fine-grained level. > > Anyway, I was thinking of writing this thing myself, but I've plenty > of other stuff to be working on & I've decided not to be greedy! :^) So, > in case anyone else wants to have a go, this could be a good place to > start coding on Alexandria. You just have to read up on Amazon ECS 4.0, > there's a migration guide here: > http://developer.amazonwebservices.com/connect/entry.jspa?externalID=627 > > Then have a look at the current provider: > lib/alexandria/book_providers/amazon.rb > and create a new one in its image (amazon_ecs.rb) and start switching > over the features. > > Anyway, we're going to need new Amazon ECS support for our next > release, so if no-one gets around to writing this I'm sure I > can handle it. If I do, I'll write a tutorial on how I approached it. > > - Cathal. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2.2 (GNU/Linux) > Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE > > iD8DBQFHq82kfMAUnRdb+8oRAgs8AKDTeL8b4akEcOcJVCvuSrqDj3tzUQCgpixE > oFrYU/YHvL8YvCHtMGDT7Tk= > =3Voa > -----END PGP SIGNATURE----- > _______________________________________________ > Alexandria-list mailing list > Alexandria-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/alexandria-list > -- -J. Method From tristil at gmail.com Mon Feb 11 19:32:53 2008 From: tristil at gmail.com (Joseph Method) Date: Mon, 11 Feb 2008 19:32:53 -0500 Subject: [Alexandria-list] New packages in alexandria-team PPA Message-ID: <167b6aa00802111632l2d3c53d4p9c6cdccf4efcacc9@mail.gmail.com> Hi all, The spirit finally came over me and I decided to learn how to package debs. I'm still pretty wobbly, but after many hours of trial and error I managed to get a couple packages to build on the Ubuntu build servers: * readinglist (the simple tutorial app I wrote a while ago, doesn't even include a menu entry) * libzoom-ruby * yaz packages (dependency for libzoom-ruby) To get them, add the repository entries on this page, https://launchpad.net/~alexandria-team/+archive/, or you can try installing them directly. RIght now they're only built for Hardy, but it's possible that they'll install on Gutsy (depends on whether dependencies are met). I'll try to get them built for Gutsy as soon as possible. The next packages to get built on the server are libamazon-ruby and alexandria itself. It would be great if others would join alexandria-team on Launchpad and help to distribute the labor of maintaining all the packages. For anyone new to packaging, I would suggest starting with a simple toy app or script like the one I did for readinglist and following these guides: * http://doc.ubuntu.com/ubuntu/packagingguide/C/index.html * https://help.launchpad.net/PPAQuickStart BTW, I'd much rather people give it a shot and make terrible mistakes than not to have help! :) -- -J. Method From tristil at gmail.com Mon Feb 11 22:11:48 2008 From: tristil at gmail.com (Joseph Method) Date: Mon, 11 Feb 2008 22:11:48 -0500 Subject: [Alexandria-list] New packages in alexandria-team PPA In-Reply-To: <167b6aa00802111632l2d3c53d4p9c6cdccf4efcacc9@mail.gmail.com> References: <167b6aa00802111632l2d3c53d4p9c6cdccf4efcacc9@mail.gmail.com> Message-ID: <167b6aa00802111911g5173bca4g88b22d77c029c87f@mail.gmail.com> Some other points I forgot to include in the original email: * I'll try to write a deb packaging tutorial, better conveying the gist of packaging than I've seen elsewhere. For now, let me say that using pbuilder is an essential step for getting packages to build on a server. I set up pbuilder on my machine with this command: sudo pbuilder create --distribution hardy --othermirror "deb http://us.archive.ubuntu.com/ubuntu hardy universe multiverse| deb http://ppa.launchpad.net/alexandria-team/ubuntu hardy main" * We should work with Daniel Brumbaugh Keeney's http://apt.rubyforge.org repository to sync mature packages over. That way the stability of packages will be, in ascending order, alexandria-team PPA, apt.rubyforge.org, (hopefully) Hardy-universe 0.6.3 package. * Speaking of which, getting 0.6.3 into Hardy (and possibly gutsy-backports) should be our victory condition for this development cycle. It would be great if someone would take on the task of preparing a checklist of steps necessary to accomplish this (I _think_ it mainly involves having the packages reviewed and then "advocated" by a MOTU (Master of the Universe)). On Feb 11, 2008 7:32 PM, Joseph Method wrote: > Hi all, > > The spirit finally came over me and I decided to learn how to package > debs. I'm still pretty wobbly, but after many hours of trial and error > I managed to get a couple packages to build on the Ubuntu build > servers: > > * readinglist (the simple tutorial app I wrote a while ago, doesn't > even include a menu entry) > * libzoom-ruby > * yaz packages (dependency for libzoom-ruby) > > To get them, add the repository entries on this page, > https://launchpad.net/~alexandria-team/+archive/, or you can try > installing them directly. RIght now they're only built for Hardy, but > it's possible that they'll install on Gutsy (depends on whether > dependencies are met). I'll try to get them built for Gutsy as soon as > possible. > > The next packages to get built on the server are libamazon-ruby and > alexandria itself. It would be great if others would join > alexandria-team on Launchpad and help to distribute the labor of > maintaining all the packages. For anyone new to packaging, I would > suggest starting with a simple toy app or script like the one I did > for readinglist and following these guides: > > * http://doc.ubuntu.com/ubuntu/packagingguide/C/index.html > * https://help.launchpad.net/PPAQuickStart > > BTW, I'd much rather people give it a shot and make terrible mistakes > than not to have help! :) > -- > -J. Method > -- -J. Method From tristil at gmail.com Tue Feb 12 22:43:22 2008 From: tristil at gmail.com (Joseph Method) Date: Tue, 12 Feb 2008 22:43:22 -0500 Subject: [Alexandria-list] New packages in alexandria-team PPA In-Reply-To: <167b6aa00802111911g5173bca4g88b22d77c029c87f@mail.gmail.com> References: <167b6aa00802111632l2d3c53d4p9c6cdccf4efcacc9@mail.gmail.com> <167b6aa00802111911g5173bca4g88b22d77c029c87f@mail.gmail.com> Message-ID: <167b6aa00802121943o2a1317c1w2a3ac73016cb15@mail.gmail.com> Hardy and Gutsy packages for the whole stack are out. Please test them out and file bugs against them, especially any regressions in zoom. On Feb 11, 2008 10:11 PM, Joseph Method wrote: > Some other points I forgot to include in the original email: > > * I'll try to write a deb packaging tutorial, better conveying the > gist of packaging than I've seen elsewhere. For now, let me say that > using pbuilder is an essential step for getting packages to build on a > server. I set up pbuilder on my machine with this command: > sudo pbuilder create --distribution hardy --othermirror "deb > http://us.archive.ubuntu.com/ubuntu hardy universe multiverse| deb > http://ppa.launchpad.net/alexandria-team/ubuntu hardy main" > > * We should work with Daniel Brumbaugh Keeney's > http://apt.rubyforge.org repository to sync mature packages over. That > way the stability of packages will be, in ascending order, > alexandria-team PPA, apt.rubyforge.org, (hopefully) Hardy-universe > 0.6.3 package. > > * Speaking of which, getting 0.6.3 into Hardy (and possibly > gutsy-backports) should be our victory condition for this development > cycle. It would be great if someone would take on the task of > preparing a checklist of steps necessary to accomplish this (I _think_ > it mainly involves having the packages reviewed and then "advocated" > by a MOTU (Master of the Universe)). > > > On Feb 11, 2008 7:32 PM, Joseph Method wrote: > > Hi all, > > > > The spirit finally came over me and I decided to learn how to package > > debs. I'm still pretty wobbly, but after many hours of trial and error > > I managed to get a couple packages to build on the Ubuntu build > > servers: > > > > * readinglist (the simple tutorial app I wrote a while ago, doesn't > > even include a menu entry) > > * libzoom-ruby > > * yaz packages (dependency for libzoom-ruby) > > > > To get them, add the repository entries on this page, > > https://launchpad.net/~alexandria-team/+archive/, or you can try > > installing them directly. RIght now they're only built for Hardy, but > > it's possible that they'll install on Gutsy (depends on whether > > dependencies are met). I'll try to get them built for Gutsy as soon as > > possible. > > > > The next packages to get built on the server are libamazon-ruby and > > alexandria itself. It would be great if others would join > > alexandria-team on Launchpad and help to distribute the labor of > > maintaining all the packages. For anyone new to packaging, I would > > suggest starting with a simple toy app or script like the one I did > > for readinglist and following these guides: > > > > * http://doc.ubuntu.com/ubuntu/packagingguide/C/index.html > > * https://help.launchpad.net/PPAQuickStart > > > > BTW, I'd much rather people give it a shot and make terrible mistakes > > than not to have help! :) > > -- > > -J. Method > > > > > > -- > -J. Method > -- -J. Method From tristil at gmail.com Thu Feb 14 13:38:35 2008 From: tristil at gmail.com (Joseph Method) Date: Thu, 14 Feb 2008 13:38:35 -0500 Subject: [Alexandria-list] New packages in alexandria-team PPA In-Reply-To: <1203013681.18333.33.camel@rubidium01> References: <167b6aa00802111632l2d3c53d4p9c6cdccf4efcacc9@mail.gmail.com> <167b6aa00802111911g5173bca4g88b22d77c029c87f@mail.gmail.com> <1203013681.18333.33.camel@rubidium01> Message-ID: <167b6aa00802141038n714845e1rba119421c27665a5@mail.gmail.com> Hi Lennart, I think there's some hope. I believe the deadline for new _universe_ packages is February 13th, BetaFreeze. Thanks for taking the step of filing that bug. We'll all have to keep our eye on this and help to move this along. Otherwise, it'll be another release cycle without an update. > Unfortunately I just read that today is feature freeze for Hardy, so I > guess it's too late to try and get 0.6.2 approved for Hardy :-(. > > I found this page on the Ubuntu wiki that describes how to get a package > into Universe: https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages and > https://wiki.ubuntu.com/MOTU/Packages/REVU > The first page suggested to file a bug report and tag it with > 'needs-packaging', so I did that: > https://bugs.launchpad.net/ubuntu/+source/alexandria/+bug/191905 and > pointed the to the alexandria Team PPA. > > Hope it helps... > > > Lennart. > > > > > > > > On Feb 11, 2008 7:32 PM, Joseph Method wrote: > > > Hi all, > > > > > > The spirit finally came over me and I decided to learn how to package > > > debs. I'm still pretty wobbly, but after many hours of trial and error > > > I managed to get a couple packages to build on the Ubuntu build > > > servers: > > > > > > * readinglist (the simple tutorial app I wrote a while ago, doesn't > > > even include a menu entry) > > > * libzoom-ruby > > > * yaz packages (dependency for libzoom-ruby) > > > > > > To get them, add the repository entries on this page, > > > https://launchpad.net/~alexandria-team/+archive/, or you can try > > > installing them directly. RIght now they're only built for Hardy, but > > > it's possible that they'll install on Gutsy (depends on whether > > > dependencies are met). I'll try to get them built for Gutsy as soon as > > > possible. > > > > > > The next packages to get built on the server are libamazon-ruby and > > > alexandria itself. It would be great if others would join > > > alexandria-team on Launchpad and help to distribute the labor of > > > maintaining all the packages. For anyone new to packaging, I would > > > suggest starting with a simple toy app or script like the one I did > > > for readinglist and following these guides: > > > > > > * http://doc.ubuntu.com/ubuntu/packagingguide/C/index.html > > > * https://help.launchpad.net/PPAQuickStart > > > > > > BTW, I'd much rather people give it a shot and make terrible mistakes > > > than not to have help! :) > > > -- > > > -J. Method > > > > > > > > > > -- > ---------------------------------------------------- > L.C. Karssen > Utrecht > The Netherlands > > lennart at karssen.org > > Stuur me aub geen Word of Powerpoint bestanden! > Zie http://www.gnu.org/philosophy/no-word-attachments.nl.html > ---------------------------------------------------- > -- -J. Method From lennart at karssen.org Thu Feb 14 14:20:59 2008 From: lennart at karssen.org (L.C. Karssen) Date: Thu, 14 Feb 2008 20:20:59 +0100 Subject: [Alexandria-list] New packages in alexandria-team PPA In-Reply-To: <167b6aa00802141038n714845e1rba119421c27665a5@mail.gmail.com> References: <167b6aa00802111632l2d3c53d4p9c6cdccf4efcacc9@mail.gmail.com> <167b6aa00802111911g5173bca4g88b22d77c029c87f@mail.gmail.com> <1203013681.18333.33.camel@rubidium01> <167b6aa00802141038n714845e1rba119421c27665a5@mail.gmail.com> Message-ID: <1203016859.18333.48.camel@rubidium01> Hi Joseph, Well, I just checked via IRC in #ubuntu-motu, but FeatureFreeze also holds for Universe :-(. At https://wiki.ubuntu.com/FreezeExceptionProcess#head-9523bc4076ff011324d67cddc97969ec609618d6 I found a section called "Exceptions for Universe/Multiverse" that states the following requirements to get an exception: FeatureFreeze for new upstream versions If you want to introduce a new upstream version with new features and/or ABI/API changes, please * [WWW] file a bug * state the reason why you feel it is necessary * (other bugs it fixes, etc.) * attach (as files) * diffstat of the upstream tarballs diff -ruN -{old-version,new-version} | diffstat > diffstat.txt * diff of the Upstream ChangeLog (not debian/changelog) diff -u -{old-version,new-version}/ChangeLog > changelog.diff * note that the ChangeLog sometimes is called CHANGES, is missing or the tarball merely has a NEWS file. * this does not mean debian/changelog * the NEWS file, if you think that this information helps reviewing your request (true for most gnome packages) * build log (as file) * pbuilder has the --logfile option. * install log * for instance a copy and paste of the install messages from console when installing * mention what testing you've done to see that it works * a screenshot showing the main features could also be nice * subscribe (not assign) it to the 'motu-release' team. Please note that we expect requesters to have an updated package already prepared and tested! You will need this anyway to provide proper diffstats and buildlogs. Once one of the [WWW] team members marks the bug as Confirmed you can either proceed with uploading (in case you're in [WWW] motu or [WWW] ubuntu-core-dev), else please follow SponsorshipProcess. So if we want to get that exception some work needs to be done. The bug is filed, and we also know it fixes many bugs, so the first two items are (almost) complete (almost because we might want to state the actual number of fixed bugs in the report). Joseph, since you've been working on the PPA I guess you could most easily get the requested diffs. I hope to have some time this weekend to do some tests with your PPA packages. To expedite matters we might want to contact one of the MOTUs (via mail or IRC) to have a look at the bug report after all the necessary files have been uploaded. Lennart. On Thu, 2008-02-14 at 13:38 -0500, Joseph Method wrote: > Hi Lennart, > > I think there's some hope. I believe the deadline for new _universe_ > packages is February 13th, BetaFreeze. Thanks for taking the step of > filing that bug. We'll all have to keep our eye on this and help to > move this along. Otherwise, it'll be another release cycle without an > update. > > > Unfortunately I just read that today is feature freeze for Hardy, so I > > guess it's too late to try and get 0.6.2 approved for Hardy :-(. > > > > I found this page on the Ubuntu wiki that describes how to get a package > > into Universe: https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages and > > https://wiki.ubuntu.com/MOTU/Packages/REVU > > The first page suggested to file a bug report and tag it with > > 'needs-packaging', so I did that: > > https://bugs.launchpad.net/ubuntu/+source/alexandria/+bug/191905 and > > pointed the to the alexandria Team PPA. > > > > Hope it helps... > > > > > > Lennart. > > > > > > > > > > > > > > On Feb 11, 2008 7:32 PM, Joseph Method wrote: > > > > Hi all, > > > > > > > > The spirit finally came over me and I decided to learn how to package > > > > debs. I'm still pretty wobbly, but after many hours of trial and error > > > > I managed to get a couple packages to build on the Ubuntu build > > > > servers: > > > > > > > > * readinglist (the simple tutorial app I wrote a while ago, doesn't > > > > even include a menu entry) > > > > * libzoom-ruby > > > > * yaz packages (dependency for libzoom-ruby) > > > > > > > > To get them, add the repository entries on this page, > > > > https://launchpad.net/~alexandria-team/+archive/, or you can try > > > > installing them directly. RIght now they're only built for Hardy, but > > > > it's possible that they'll install on Gutsy (depends on whether > > > > dependencies are met). I'll try to get them built for Gutsy as soon as > > > > possible. > > > > > > > > The next packages to get built on the server are libamazon-ruby and > > > > alexandria itself. It would be great if others would join > > > > alexandria-team on Launchpad and help to distribute the labor of > > > > maintaining all the packages. For anyone new to packaging, I would > > > > suggest starting with a simple toy app or script like the one I did > > > > for readinglist and following these guides: > > > > > > > > * http://doc.ubuntu.com/ubuntu/packagingguide/C/index.html > > > > * https://help.launchpad.net/PPAQuickStart > > > > > > > > BTW, I'd much rather people give it a shot and make terrible mistakes > > > > than not to have help! :) > > > > -- > > > > -J. Method > > > > > > > > > > > > > > > -- > > ---------------------------------------------------- > > L.C. Karssen > > Utrecht > > The Netherlands > > > > lennart at karssen.org > > > > Stuur me aub geen Word of Powerpoint bestanden! > > Zie http://www.gnu.org/philosophy/no-word-attachments.nl.html > > ---------------------------------------------------- > > > > > -- ---------------------------------------------------- L.C. Karssen Utrecht The Netherlands lennart at karssen.org Stuur me aub geen Word of Powerpoint bestanden! Zie http://www.gnu.org/philosophy/no-word-attachments.nl.html ---------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://rubyforge.org/pipermail/alexandria-list/attachments/20080214/6cda4b16/attachment.bin From lennart at karssen.org Thu Feb 14 17:48:51 2008 From: lennart at karssen.org (L.C. Karssen) Date: Thu, 14 Feb 2008 23:48:51 +0100 Subject: [Alexandria-list] New packages in alexandria-team PPA In-Reply-To: <1203016859.18333.48.camel@rubidium01> References: <167b6aa00802111632l2d3c53d4p9c6cdccf4efcacc9@mail.gmail.com> <167b6aa00802111911g5173bca4g88b22d77c029c87f@mail.gmail.com> <1203013681.18333.33.camel@rubidium01> <167b6aa00802141038n714845e1rba119421c27665a5@mail.gmail.com> <1203016859.18333.48.camel@rubidium01> Message-ID: <1203029331.9721.7.camel@sidonia.karssen.org> I just got a reply to the bug report in Launchapd for the 0.6.1 -> 0.6.2. Check it out at https://bugs.launchpad.net/bugs/191905 It appears that we need to follow a slightly different protocol, since we already have the packages in the PPA. https://wiki.ubuntu.com/SyncRequestProcess Lennart. On Thu, 2008-02-14 at 20:20 +0100, L.C. Karssen wrote: > Hi Joseph, > > Well, I just checked via IRC in #ubuntu-motu, but FeatureFreeze also > holds for Universe :-(. > > At > https://wiki.ubuntu.com/FreezeExceptionProcess#head-9523bc4076ff011324d67cddc97969ec609618d6 I found a section called "Exceptions for Universe/Multiverse" that states the following requirements to get an exception: > > FeatureFreeze for new upstream versions > If you want to introduce a new upstream version with new features and/or > ABI/API changes, please > > * [WWW] file a bug > * state the reason why you feel it is necessary > * (other bugs it fixes, etc.) > * attach (as files) > * diffstat of the upstream tarballs > diff -ruN -{old-version,new-version} | diffstat > diffstat.txt > * diff of the Upstream ChangeLog (not debian/changelog) > diff -u -{old-version,new-version}/ChangeLog > changelog.diff > * note that the ChangeLog sometimes is called CHANGES, is > missing or the tarball merely has a NEWS file. > * this does not mean debian/changelog > * the NEWS file, if you think that this information helps > reviewing your request (true for most gnome packages) > * build log (as file) > * pbuilder has the --logfile option. > * install log > * for instance a copy and paste of the install > messages from console when installing > * mention what testing you've done to see that it works > * a screenshot showing the main features could > also be nice > * subscribe (not assign) it to the 'motu-release' team. > > Please note that we expect requesters to have an updated package already > prepared and tested! You will need this anyway to provide proper > diffstats and buildlogs. > > Once one of the [WWW] team members marks the bug as Confirmed you can > either proceed with uploading (in case you're in [WWW] motu or [WWW] > ubuntu-core-dev), else please follow SponsorshipProcess. > > > So if we want to get that exception some work needs to be done. The bug > is filed, and we also know it fixes many bugs, so the first two items > are (almost) complete (almost because we might want to state the actual > number of fixed bugs in the report). > Joseph, since you've been working on the PPA I guess you could most > easily get the requested diffs. I hope to have some time this weekend to > do some tests with your PPA packages. > To expedite matters we might want to contact one of the MOTUs (via mail > or IRC) to have a look at the bug report after all the necessary files > have been uploaded. > > > Lennart. > > On Thu, 2008-02-14 at 13:38 -0500, Joseph Method wrote: > > Hi Lennart, > > > > I think there's some hope. I believe the deadline for new _universe_ > > packages is February 13th, BetaFreeze. Thanks for taking the step of > > filing that bug. We'll all have to keep our eye on this and help to > > move this along. Otherwise, it'll be another release cycle without an > > update. > > > > > Unfortunately I just read that today is feature freeze for Hardy, so I > > > guess it's too late to try and get 0.6.2 approved for Hardy :-(. > > > > > > I found this page on the Ubuntu wiki that describes how to get a package > > > into Universe: https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages and > > > https://wiki.ubuntu.com/MOTU/Packages/REVU > > > The first page suggested to file a bug report and tag it with > > > 'needs-packaging', so I did that: > > > https://bugs.launchpad.net/ubuntu/+source/alexandria/+bug/191905 and > > > pointed the to the alexandria Team PPA. > > > > > > Hope it helps... > > > > > > > > > Lennart. > > > > > > > > > > > > > > > > > > > > On Feb 11, 2008 7:32 PM, Joseph Method wrote: > > > > > Hi all, > > > > > > > > > > The spirit finally came over me and I decided to learn how to package > > > > > debs. I'm still pretty wobbly, but after many hours of trial and error > > > > > I managed to get a couple packages to build on the Ubuntu build > > > > > servers: > > > > > > > > > > * readinglist (the simple tutorial app I wrote a while ago, doesn't > > > > > even include a menu entry) > > > > > * libzoom-ruby > > > > > * yaz packages (dependency for libzoom-ruby) > > > > > > > > > > To get them, add the repository entries on this page, > > > > > https://launchpad.net/~alexandria-team/+archive/, or you can try > > > > > installing them directly. RIght now they're only built for Hardy, but > > > > > it's possible that they'll install on Gutsy (depends on whether > > > > > dependencies are met). I'll try to get them built for Gutsy as soon as > > > > > possible. > > > > > > > > > > The next packages to get built on the server are libamazon-ruby and > > > > > alexandria itself. It would be great if others would join > > > > > alexandria-team on Launchpad and help to distribute the labor of > > > > > maintaining all the packages. For anyone new to packaging, I would > > > > > suggest starting with a simple toy app or script like the one I did > > > > > for readinglist and following these guides: > > > > > > > > > > * http://doc.ubuntu.com/ubuntu/packagingguide/C/index.html > > > > > * https://help.launchpad.net/PPAQuickStart > > > > > > > > > > BTW, I'd much rather people give it a shot and make terrible mistakes > > > > > than not to have help! :) > > > > > -- > > > > > -J. Method > > > > > > > > > > > > > > > > > > > > -- > > > ---------------------------------------------------- > > > L.C. Karssen > > > Utrecht > > > The Netherlands > > > > > > lennart at karssen.org > > > > > > Stuur me aub geen Word of Powerpoint bestanden! > > > Zie http://www.gnu.org/philosophy/no-word-attachments.nl.html > > > ---------------------------------------------------- > > > > > > > > > > _______________________________________________ > Alexandria-list mailing list > Alexandria-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/alexandria-list -- ---------------------------------------------------- L.C. Karssen Utrecht The Netherlands lennart at karssen.org http://www.karssen.org Stuur me aub geen Word of Powerpoint bestanden! Zie http://www.gnu.org/philosophy/no-word-attachments.nl.html ---------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://rubyforge.org/pipermail/alexandria-list/attachments/20080214/c54f1e69/attachment.bin From cathal.alexandria at gnostai.org Fri Feb 15 11:31:10 2008 From: cathal.alexandria at gnostai.org (Cathal Mc Ginley) Date: Fri, 15 Feb 2008 16:31:10 +0000 Subject: [Alexandria-list] New packages in alexandria-team PPA In-Reply-To: <1203029331.9721.7.camel@sidonia.karssen.org> References: <167b6aa00802111632l2d3c53d4p9c6cdccf4efcacc9@mail.gmail.com> <167b6aa00802111911g5173bca4g88b22d77c029c87f@mail.gmail.com> <1203013681.18333.33.camel@rubidium01> <167b6aa00802141038n714845e1rba119421c27665a5@mail.gmail.com> <1203016859.18333.48.camel@rubidium01> <1203029331.9721.7.camel@sidonia.karssen.org> Message-ID: <20080215163110.6506fef8@matilda> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 14 Feb 2008 23:48:51 +0100 "L.C. Karssen" wrote: > I just got a reply to the bug report in Launchapd for the 0.6.1 -> > 0.6.2. Check it out at https://bugs.launchpad.net/bugs/191905 > It appears that we need to follow a slightly different protocol, since > we already have the packages in the PPA. > https://wiki.ubuntu.com/SyncRequestProcess > I realise that large organisations like Debian and Ubuntu need to have bureaucracy to run smoothly, but I don't understand the latest two comments on that report. - From Daniel Holbach: - -------------------- Lots of changes have been made in the packaging: - dropped changelog entries, - changed maintainer - added generated postinst/postrm/prerm? - dropped watch file, dropped menu file, dropped manpage. - From Siegfried Gevatter: - ------------------------ Please address Daniel's concerns... I didn't know that Daniel had raised concerns, those just look like comments. Inaccurate comments at that. And I can't see what answers we can give to them. Or if we're supposed to. Anyway: Lots of changes have been made in the packaging: [Yes, it's been two years, and we now create the deb files ourselves.] - dropped changelog entries, [They're generated by 'svn log' now] - changed maintainer [Because the old maintainer left the project, what ya gonna do?] - added generated postinst/postrm/prerm? [Um, I don't know what 'added generated' means, but we do now have those files as part of the installation process] - dropped watch file, dropped menu file, dropped manpage. [Not sure about the watch file, menu files are deprecated anyway, and in fact we have a new manpage which I wrote myself] Does this address the concerns? I'm not going to comment directly on the report (and please don't just copy and paste my comments) since my inherent grumpiness will no doubt needlessly irritate the Ubuntu people when the only problem really is that I don't understand the process they're following. Anywho... cheers, - C. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE iD8DBQFHtb5YfMAUnRdb+8oRAvV5AJ4/yaflzpFVhbJJhae4fYu8Tin4fwCgn/bg 3bLKlYl/BGe0qTO1dXlJrUE= =fMr4 -----END PGP SIGNATURE----- From lennart at karssen.org Fri Feb 15 11:50:41 2008 From: lennart at karssen.org (L.C. Karssen) Date: Fri, 15 Feb 2008 16:50:41 +0000 Subject: [Alexandria-list] New packages in alexandria-team PPA In-Reply-To: <20080215163110.6506fef8@matilda> References: <167b6aa00802111632l2d3c53d4p9c6cdccf4efcacc9@mail.gmail.com> <167b6aa00802111911g5173bca4g88b22d77c029c87f@mail.gmail.com> <1203013681.18333.33.camel@rubidium01> <167b6aa00802141038n714845e1rba119421c27665a5@mail.gmail.com> <1203016859.18333.48.camel@rubidium01> <1203029331.9721.7.camel@sidonia.karssen.org> <20080215163110.6506fef8@matilda> Message-ID: <1203094241.22283.46.camel@rubidium01> On Fri, 2008-02-15 at 16:31 +0000, Cathal Mc Ginley wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Thu, 14 Feb 2008 23:48:51 +0100 > "L.C. Karssen" wrote: > > I realise that large organisations like Debian and Ubuntu need to > have bureaucracy to run smoothly, but I don't understand the latest two > comments on that report. > > I didn't know that Daniel had raised concerns, those just look like > comments. I didn't understand Daniel's remarks either so I e-mailed him asking whether action was required from our side. Haven't had a reply yet. I guess the problem lies in the fact that the new Ubuntu version (Hardy) is now in Feature Freeze. So normally they wouldn't accept big changes in packages anymore. The question is if they consider our changes as too big or not. I assume Daniel and Siegfried think so. > Inaccurate comments at that. And I can't see what answers > we can give to them. Or if we're supposed to. Anyway: > > Lots of changes have been made in the packaging: > [Yes, it's been two years, and we now create the deb files ourselves.] > > - dropped changelog entries, > [They're generated by 'svn log' now] I haven't checked the old and new Changelog, but from the comment I assume that some of the entries of the old Changelog are not present in the new one. For continuity purposes that might be considered harmful or at least make things unclear. > > - changed maintainer > [Because the old maintainer left the project, what ya gonna do?] > > - added generated postinst/postrm/prerm? > [Um, I don't know what 'added generated' means, but we do now have those > files as part of the installation process] I guess he wants to say that compared to the 0.6.1 package we added several automatically generated files? I'm also a bit in the dark here. > > - dropped watch file, dropped menu file, dropped manpage. > [Not sure about the watch file, menu files are deprecated anyway, and > in fact we have a new manpage which I wrote myself] That's a good point. > > Does this address the concerns? I'm not going to comment directly on > the report (and please don't just copy and paste my comments) since my > inherent grumpiness will no doubt needlessly irritate the Ubuntu people > when the only problem really is that I don't understand the process > they're following. > > Anywho... cheers, > > - C. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2.2 (GNU/Linux) > Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE > > iD8DBQFHtb5YfMAUnRdb+8oRAvV5AJ4/yaflzpFVhbJJhae4fYu8Tin4fwCgn/bg > 3bLKlYl/BGe0qTO1dXlJrUE= > =fMr4 > -----END PGP SIGNATURE----- -- ---------------------------------------------------- L.C. Karssen Utrecht The Netherlands lennart at karssen.org Stuur me aub geen Word of Powerpoint bestanden! Zie http://www.gnu.org/philosophy/no-word-attachments.nl.html ---------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://rubyforge.org/pipermail/alexandria-list/attachments/20080215/cb5814b3/attachment.bin From tristil at gmail.com Fri Feb 15 13:19:10 2008 From: tristil at gmail.com (Joseph Method) Date: Fri, 15 Feb 2008 13:19:10 -0500 Subject: [Alexandria-list] New packages in alexandria-team PPA In-Reply-To: <1203094241.22283.46.camel@rubidium01> References: <167b6aa00802111632l2d3c53d4p9c6cdccf4efcacc9@mail.gmail.com> <167b6aa00802111911g5173bca4g88b22d77c029c87f@mail.gmail.com> <1203013681.18333.33.camel@rubidium01> <167b6aa00802141038n714845e1rba119421c27665a5@mail.gmail.com> <1203016859.18333.48.camel@rubidium01> <1203029331.9721.7.camel@sidonia.karssen.org> <20080215163110.6506fef8@matilda> <1203094241.22283.46.camel@rubidium01> Message-ID: <167b6aa00802151019m753c18a6p9a693bca3afcf11c@mail.gmail.com> > > I didn't know that Daniel had raised concerns, those just look like > > comments. > I didn't understand Daniel's remarks either so I e-mailed him asking > whether action was required from our side. Haven't had a reply yet. > I guess the problem lies in the fact that the new Ubuntu version (Hardy) > is now in Feature Freeze. So normally they wouldn't accept big changes > in packages anymore. The question is if they consider our changes as too > big or not. I assume Daniel and Siegfried think so. Yeah, the basic problem may be that they expect an "upstream update" closely matching old packages and we're uploading basically a new package. I agree with Cathal's sentiment that, well, it's been two years and we lost our maintainer! On the other hand, we're late :( > > - added generated postinst/postrm/prerm? > > [Um, I don't know what 'added generated' means, but we do now have those > > files as part of the installation process] > I guess he wants to say that compared to the 0.6.1 package we added > several automatically generated files? I'm also a bit in the dark here. Hehe. "Whose business is it whether I generate my files?" Do we know if it's against policy? Actually, Cathal, could you explain the strategy for generating those files, just in case I built the package wrong? For the record, after making some fixes in the Rakefile I just stepped into the directory and ran `debuild -S -sa`, stepped down and did `dput alexandria-team *.dsc`. So I didn't make the package directly using `rake package`, but just allowed the package to build in pbuilder and on the Launchpad server. > > [Not sure about the watch file, menu files are deprecated anyway, and > > in fact we have a new manpage which I wrote myself] I checked using `dpkg-query --listfiles alexandria` and the manpage is there. Lennart, you sent the email directly to Daniel Holbach? Because the one you sent to the bug doesn't seem to be there. In general, we should emphasize the newness of this package and that it meets the criterion that a "new feature is needed for the release and will not introduce more problems than it fixes" -- certainly Alexandria is *way* more buggy/feature-incomplete at just 0.6.1. In any case, if we fail at this, we should try to get into Debian ASAP. It'll be less of this headache in the future, because of the automatic sync. -- -J. Method From lennart at karssen.org Fri Feb 15 13:36:51 2008 From: lennart at karssen.org (L.C. Karssen) Date: Fri, 15 Feb 2008 18:36:51 +0000 Subject: [Alexandria-list] New packages in alexandria-team PPA In-Reply-To: <167b6aa00802151019m753c18a6p9a693bca3afcf11c@mail.gmail.com> References: <167b6aa00802111632l2d3c53d4p9c6cdccf4efcacc9@mail.gmail.com> <167b6aa00802111911g5173bca4g88b22d77c029c87f@mail.gmail.com> <1203013681.18333.33.camel@rubidium01> <167b6aa00802141038n714845e1rba119421c27665a5@mail.gmail.com> <1203016859.18333.48.camel@rubidium01> <1203029331.9721.7.camel@sidonia.karssen.org> <20080215163110.6506fef8@matilda> <1203094241.22283.46.camel@rubidium01> <167b6aa00802151019m753c18a6p9a693bca3afcf11c@mail.gmail.com> Message-ID: <1203100611.22283.53.camel@rubidium01> On Fri, 2008-02-15 at 13:19 -0500, Joseph Method wrote: > Lennart, you sent the email directly to Daniel Holbach? Because the > one you sent to the bug doesn't seem to be there. You're right, it doesn't seem to show up in the bug report. Well, I could send it to his personal address again, maybe with an extra note explaining that I'm not trying to be pushy if this is the second time he gets the mail. What do you think? > In general, we > should emphasize the newness of this package and that it meets the > criterion that a "new feature is needed for the release and will not > introduce more problems than it fixes" -- certainly Alexandria is > *way* more buggy/feature-incomplete at just 0.6.1. Agreed. > > In any case, if we fail at this, we should try to get into Debian > ASAP. It'll be less of this headache in the future, because of the > automatic sync. I agree, but I'm wondering whether Debian has the right (version of) dependencies. However, I guess the Ubuntu folks will iron that out themselves, since we won't be the only ones with that problem. -- ---------------------------------------------------- L.C. Karssen Utrecht The Netherlands lennart at karssen.org Stuur me aub geen Word of Powerpoint bestanden! Zie http://www.gnu.org/philosophy/no-word-attachments.nl.html ---------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://rubyforge.org/pipermail/alexandria-list/attachments/20080215/6a597e70/attachment.bin From tristil at gmail.com Fri Feb 15 13:40:12 2008 From: tristil at gmail.com (Joseph Method) Date: Fri, 15 Feb 2008 13:40:12 -0500 Subject: [Alexandria-list] New packages in alexandria-team PPA In-Reply-To: <1203100611.22283.53.camel@rubidium01> References: <167b6aa00802111632l2d3c53d4p9c6cdccf4efcacc9@mail.gmail.com> <167b6aa00802111911g5173bca4g88b22d77c029c87f@mail.gmail.com> <1203013681.18333.33.camel@rubidium01> <167b6aa00802141038n714845e1rba119421c27665a5@mail.gmail.com> <1203016859.18333.48.camel@rubidium01> <1203029331.9721.7.camel@sidonia.karssen.org> <20080215163110.6506fef8@matilda> <1203094241.22283.46.camel@rubidium01> <167b6aa00802151019m753c18a6p9a693bca3afcf11c@mail.gmail.com> <1203100611.22283.53.camel@rubidium01> Message-ID: <167b6aa00802151040l1be29b5al9f1154c3e91d3974@mail.gmail.com> On Fri, Feb 15, 2008 at 1:36 PM, L.C. Karssen wrote: > > On Fri, 2008-02-15 at 13:19 -0500, Joseph Method wrote: > > Lennart, you sent the email directly to Daniel Holbach? Because the > > one you sent to the bug doesn't seem to be there. > You're right, it doesn't seem to show up in the bug report. Well, I > could send it to his personal address again, maybe with an extra note > explaining that I'm not trying to be pushy if this is the second time he > gets the mail. What do you think? Sure, or just paste it as a comment on the bug report. I'll condense/paraphrase Cathal's points and add them as well. -- -J. Method From lennart at karssen.org Fri Feb 15 13:59:34 2008 From: lennart at karssen.org (L.C. Karssen) Date: Fri, 15 Feb 2008 18:59:34 +0000 Subject: [Alexandria-list] New packages in alexandria-team PPA In-Reply-To: <167b6aa00802151040l1be29b5al9f1154c3e91d3974@mail.gmail.com> References: <167b6aa00802111632l2d3c53d4p9c6cdccf4efcacc9@mail.gmail.com> <167b6aa00802111911g5173bca4g88b22d77c029c87f@mail.gmail.com> <1203013681.18333.33.camel@rubidium01> <167b6aa00802141038n714845e1rba119421c27665a5@mail.gmail.com> <1203016859.18333.48.camel@rubidium01> <1203029331.9721.7.camel@sidonia.karssen.org> <20080215163110.6506fef8@matilda> <1203094241.22283.46.camel@rubidium01> <167b6aa00802151019m753c18a6p9a693bca3afcf11c@mail.gmail.com> <1203100611.22283.53.camel@rubidium01> <167b6aa00802151040l1be29b5al9f1154c3e91d3974@mail.gmail.com> Message-ID: <1203101974.22283.59.camel@rubidium01> Done, I submitted the email to the bug report and added a question to Siegfried as well. By the way, I just noticed that the 'trunk' SVN sync has been done a few hours ago. So it is probably a good idea to remove the old 'main' branch which still linked to CVS and could/has not been updated for a year. (I don't think I've got enough privileges to delete it myself.) Lennart. On Fri, 2008-02-15 at 13:40 -0500, Joseph Method wrote: > On Fri, Feb 15, 2008 at 1:36 PM, L.C. Karssen wrote: > > > > On Fri, 2008-02-15 at 13:19 -0500, Joseph Method wrote: > > > Lennart, you sent the email directly to Daniel Holbach? Because the > > > one you sent to the bug doesn't seem to be there. > > You're right, it doesn't seem to show up in the bug report. Well, I > > could send it to his personal address again, maybe with an extra note > > explaining that I'm not trying to be pushy if this is the second time he > > gets the mail. What do you think? > > Sure, or just paste it as a comment on the bug report. I'll > condense/paraphrase Cathal's points and add them as well. > -- ---------------------------------------------------- L.C. Karssen Utrecht The Netherlands lennart at karssen.org Stuur me aub geen Word of Powerpoint bestanden! Zie http://www.gnu.org/philosophy/no-word-attachments.nl.html ---------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://rubyforge.org/pipermail/alexandria-list/attachments/20080215/6f484213/attachment.bin From tristil at gmail.com Fri Feb 15 23:17:32 2008 From: tristil at gmail.com (Joseph Method) Date: Fri, 15 Feb 2008 23:17:32 -0500 Subject: [Alexandria-list] New packages in alexandria-team PPA In-Reply-To: <1203101974.22283.59.camel@rubidium01> References: <167b6aa00802111632l2d3c53d4p9c6cdccf4efcacc9@mail.gmail.com> <167b6aa00802141038n714845e1rba119421c27665a5@mail.gmail.com> <1203016859.18333.48.camel@rubidium01> <1203029331.9721.7.camel@sidonia.karssen.org> <20080215163110.6506fef8@matilda> <1203094241.22283.46.camel@rubidium01> <167b6aa00802151019m753c18a6p9a693bca3afcf11c@mail.gmail.com> <1203100611.22283.53.camel@rubidium01> <167b6aa00802151040l1be29b5al9f1154c3e91d3974@mail.gmail.com> <1203101974.22283.59.camel@rubidium01> Message-ID: <167b6aa00802152017j55c73b49k825748d1d8f816c3@mail.gmail.com> They don't seem to let you delete it... > By the way, I just noticed that the 'trunk' SVN sync has been done a few > hours ago. So it is probably a good idea to remove the old 'main' branch > which still linked to CVS and could/has not been updated for a year. (I > don't think I've got enough privileges to delete it myself.) > > > Lennart. -- -J. Method From tristil at gmail.com Mon Feb 18 03:14:39 2008 From: tristil at gmail.com (Joseph Method) Date: Mon, 18 Feb 2008 03:14:39 -0500 Subject: [Alexandria-list] 0.6.3 release? Message-ID: <167b6aa00802180014n28e235eaxa9370d70eb4d9461@mail.gmail.com> Should we go ahead and do an 0.6.3 release and call it another cycle? Seems like this one has kind of run down... -- -J. Method From lennart at karssen.org Mon Feb 18 06:49:05 2008 From: lennart at karssen.org (L.C. Karssen) Date: Mon, 18 Feb 2008 12:49:05 +0100 Subject: [Alexandria-list] 0.6.3 release? In-Reply-To: <167b6aa00802180014n28e235eaxa9370d70eb4d9461@mail.gmail.com> References: <167b6aa00802180014n28e235eaxa9370d70eb4d9461@mail.gmail.com> Message-ID: <1203335345.1508.4.camel@rubidium01> I guess it's a good idea. However, the translators need some time as well. If you want to do a quick release to get the Ubuntu packaging for Hardy sorted out we could do the translations later, because the translation freeze is April 10 IIRC. Lennart. On Mon, 2008-02-18 at 03:14 -0500, Joseph Method wrote: > Should we go ahead and do an 0.6.3 release and call it another cycle? > Seems like this one has kind of run down... > -- ---------------------------------------------------- L.C. Karssen Utrecht The Netherlands lennart at karssen.org Stuur me aub geen Word of Powerpoint bestanden! Zie http://www.gnu.org/philosophy/no-word-attachments.nl.html ---------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://rubyforge.org/pipermail/alexandria-list/attachments/20080218/39e4a78f/attachment.bin From cathal.alexandria at gnostai.org Mon Feb 18 08:59:01 2008 From: cathal.alexandria at gnostai.org (Cathal Mc Ginley) Date: Mon, 18 Feb 2008 13:59:01 +0000 Subject: [Alexandria-list] 0.6.3 release? In-Reply-To: <167b6aa00802180014n28e235eaxa9370d70eb4d9461@mail.gmail.com> References: <167b6aa00802180014n28e235eaxa9370d70eb4d9461@mail.gmail.com> Message-ID: <20080218135901.259ef0d5@matilda> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 18 Feb 2008 03:14:39 -0500 "Joseph Method" wrote: > Should we go ahead and do an 0.6.3 release and call it another cycle? > Seems like this one has kind of run down... Hmm, I would have preferred to get the Amazon ECS stuff into 0.6.3 - I'm working on it myself at the moment. Otherwise, we may have a new widely-released version which will break Amazon support in 6 weeks time. Other than that, we've /mostly/ fixed all the issues noted on the wiki: http://wiki.alexandria-projects.org/wiki/Milestone-0-6-3 Fortunately, I'm in the mood to hack today - so shall we call a feature freeze at around Midnight GMT, see what we can get done by then? Joseph and I can coordinate this via Jabber. Then, when we're happy with the feature list, we can call a string freeze too, but release a quick 0.6.3 if we want. I think there have been next to no string changes anyway: I've noted the introduction of 3 fuzzy translations into previously 100% po files. Cheers, - Cathal. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE iD8DBQFHuY8ufMAUnRdb+8oRAl3RAJwOGPj8peYmPDsNjky+cZ4dm112TgCgupBh qu6C8o7iOxkv52/IO2TGRJg= =ur0L -----END PGP SIGNATURE----- From cathal.alexandria at gnostai.org Mon Feb 18 16:54:54 2008 From: cathal.alexandria at gnostai.org (Cathal Mc Ginley) Date: Mon, 18 Feb 2008 21:54:54 +0000 Subject: [Alexandria-list] 0.6.3 release? In-Reply-To: <20080218135901.259ef0d5@matilda> References: <167b6aa00802180014n28e235eaxa9370d70eb4d9461@mail.gmail.com> <20080218135901.259ef0d5@matilda> Message-ID: <20080218215454.6e901c0d@matilda> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 18 Feb 2008 13:59:01 +0000 Cathal Mc Ginley wrote: > Hmm, I would have preferred to get the Amazon ECS stuff into 0.6.3 - > I'm working on it myself at the moment. Otherwise, we may have a > new widely-released version which will break Amazon support in 6 weeks > time. > Okay, so I added Amazon ECS support [svn r917]. It seems to work okay, but it's not yet tested very fully. For the moment, I've left the old Ruby/Amazon provider in place, but I might remove that if the Amazon ECS provider works better - it'd remove our libamazon-ruby dependency, but would add a dependency on libhpricot-ruby. (I documented my progress on the feature, so I can write a journal entry about how I approached it whenever the dust from this release has settled.) Anyway, can some people grab the latest SVN and test it a bit? Particularly if anyone could check that it goes through HTTP proxies alright... > Other than that, we've /mostly/ fixed all the issues noted on the > wiki: http://wiki.alexandria-projects.org/wiki/Milestone-0-6-3 > I've also fixed the Z39.50 piggybacking issue that BIBSYS Norway had [bug #13302] There's one or two more issues I might look at. Give a quick shout to the list if you've noticed any new ones while testing. > Fortunately, I'm in the mood to hack today - Well, I wasn't wrong there!! Time for a coffee break, I reckon... - Cathal Magus. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE iD8DBQFHuf66fMAUnRdb+8oRAq/QAKDQDwj6jz8lDUKI31E9frcfnHUZaACdGaWt Xfwr4DEK/fifdCZc4nN7R6s= =86k7 -----END PGP SIGNATURE----- From cathal.alexandria at gnostai.org Tue Feb 19 13:55:57 2008 From: cathal.alexandria at gnostai.org (Cathal Mc Ginley) Date: Tue, 19 Feb 2008 18:55:57 +0000 Subject: [Alexandria-list] 0.6.3 release soon... In-Reply-To: <20080218215454.6e901c0d@matilda> References: <167b6aa00802180014n28e235eaxa9370d70eb4d9461@mail.gmail.com> <20080218135901.259ef0d5@matilda> <20080218215454.6e901c0d@matilda> Message-ID: <20080219185557.5e76c930@matilda> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just to update. I've now dealt with all the bugs listed on the 0.6.3 Milestone and announced a string freeze on the i18n list. So, the release of 0.6.3 is imminent. http://wiki.alexandria-projects.org/wiki/Milestone-0-6-3 The current svn is r927. If you spot any show-stoppers or annoying snags in r927, let us know. (In particular, try out the Amazon ECS provider.) There will be no beta period for this cycle. The 0.6.3 release will probably be done some time within the next day or so, whenever Joseph and I are both online together to co-ordinate. Cheers, - Cathal. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE iD8DBQFHuyZGfMAUnRdb+8oRAnIGAJ45gIQ1cnXoIIB9k++N8Pgna9W8qACgqv8n smUixjTp85sY+ZXN7Dl9h+U= =l2aq -----END PGP SIGNATURE----- From tristil at gmail.com Wed Feb 20 03:16:25 2008 From: tristil at gmail.com (Joseph Method) Date: Wed, 20 Feb 2008 03:16:25 -0500 Subject: [Alexandria-list] 0.6.3 release soon... In-Reply-To: <20080219185557.5e76c930@matilda> References: <167b6aa00802180014n28e235eaxa9370d70eb4d9461@mail.gmail.com> <20080218135901.259ef0d5@matilda> <20080218215454.6e901c0d@matilda> <20080219185557.5e76c930@matilda> Message-ID: <167b6aa00802200016p18f54592rf0be4109de9e1ce6@mail.gmail.com> Hi, this is the first draft of a release announcement. I'm thinking about the gnome-announce list. http://alexandria.rubyforge.org/svn/trunk/alexandria/NEWS Edit it for style, facticity, etc. It especially needs the list of updated translations. On Tue, Feb 19, 2008 at 1:55 PM, Cathal Mc Ginley wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Just to update. I've now dealt with all the bugs listed on the 0.6.3 > Milestone and announced a string freeze on the i18n list. So, the > release of 0.6.3 is imminent. > > http://wiki.alexandria-projects.org/wiki/Milestone-0-6-3 > > The current svn is r927. If you spot any show-stoppers or annoying snags > in r927, let us know. (In particular, try out the Amazon ECS provider.) > There will be no beta period for this cycle. The 0.6.3 release will > probably be done some time within the next day or so, whenever Joseph > and I are both online together to co-ordinate. > > Cheers, > > - Cathal. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2.2 (GNU/Linux) > Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE > > iD8DBQFHuyZGfMAUnRdb+8oRAnIGAJ45gIQ1cnXoIIB9k++N8Pgna9W8qACgqv8n > smUixjTp85sY+ZXN7Dl9h+U= > =l2aq > -----END PGP SIGNATURE----- > -- -J. Method From cathal.alexandria at gnostai.org Wed Feb 20 09:15:20 2008 From: cathal.alexandria at gnostai.org (Cathal Mc Ginley) Date: Wed, 20 Feb 2008 14:15:20 +0000 Subject: [Alexandria-list] 0.6.3 release soon... In-Reply-To: <167b6aa00802200016p18f54592rf0be4109de9e1ce6@mail.gmail.com> References: <167b6aa00802180014n28e235eaxa9370d70eb4d9461@mail.gmail.com> <20080218135901.259ef0d5@matilda> <20080218215454.6e901c0d@matilda> <20080219185557.5e76c930@matilda> <167b6aa00802200016p18f54592rf0be4109de9e1ce6@mail.gmail.com> Message-ID: <20080220141520.1fea9a02@matilda> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 20 Feb 2008 03:16:25 -0500 "Joseph Method" wrote: > Hi, this is the first draft of a release announcement. I'm thinking > about the gnome-announce list. > > http://alexandria.rubyforge.org/svn/trunk/alexandria/NEWS > > Edit it for style, facticity, etc. It especially needs the list of > updated translations. * I added Galician & Chinese (Traditional) to the NEWS file. (I left out my partial Irish translation since it's only 55% done.) * I wonder... the release note compares Alexandria to Tellico and Delicious Library. Is this necessary? They're both more fully-featured than Alexandria (they both support music & movies too), so the comparison is sort of unfavourable for us. And people who don't know those programs won't be any the wiser. Perhaps a short description of the core utility of the program would be more useful? * Anyway, I also did a couple of touch-ups here and there, including in the README and Rakefile to make sure the version number is consistent at 0.6.3. * I added libhpricot-ruby to the debian Recommends - it's needed for Amazon ECS. * Also, since I noticed a problem with libgettext-ruby 1.1.0 (on gNewSense) - I set a minimum version of 1.10.0, is that a widely available version? * One more thing, I don't *think* libyaml-ruby1.8 needs to be included explicitly - ruby1.8 requires libruby1.8 which provides libyaml-ruby1.8. No harm though. Before releasing, we should check that there's a copyright & GPL license notice on every ruby file, especially those originally written by Laurent Sansonetti et al. Some of the copyright notices were mislaid during refactoring, when files were split up or code was moved about. (I know, I'm a real nerd about these things...) - C. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE iD8DBQFHvDYBfMAUnRdb+8oRAiPLAKCiukiqfsOH20J1lMoYgsE4fxJ+uwCaA9jO 0rGD0Zg7OV+KpWEi0HwTIb4= =9Xfb -----END PGP SIGNATURE----- From tristil at gmail.com Wed Feb 20 13:54:26 2008 From: tristil at gmail.com (Joseph Method) Date: Wed, 20 Feb 2008 13:54:26 -0500 Subject: [Alexandria-list] 0.6.3 release soon... In-Reply-To: <20080220141520.1fea9a02@matilda> References: <167b6aa00802180014n28e235eaxa9370d70eb4d9461@mail.gmail.com> <20080218135901.259ef0d5@matilda> <20080218215454.6e901c0d@matilda> <20080219185557.5e76c930@matilda> <167b6aa00802200016p18f54592rf0be4109de9e1ce6@mail.gmail.com> <20080220141520.1fea9a02@matilda> Message-ID: <167b6aa00802201054ra328e1pe5f9540b5b45556d@mail.gmail.com> > * I added Galician & Chinese (Traditional) to the NEWS file. (I left out > my partial Irish translation since it's only 55% done.) Added the more-complete Czech translation. > * I wonder... the release note compares Alexandria to Tellico and > Delicious Library. Is this necessary? They're both more fully-featured > than Alexandria (they both support music & movies too), so the > comparison is sort of unfavourable for us. And people who don't know > those programs won't be any the wiser. Perhaps a short description of > the core utility of the program would be more useful? Added more explanation, but I thought the comparison would help people who know those programs. It's not too important. > Before releasing, we should check that there's a copyright & GPL > license notice on every ruby file, especially those originally written > by Laurent Sansonetti et al. Some of the copyright notices were mislaid > during refactoring, when files were split up or code was moved about. > (I know, I'm a real nerd about these things...) Personally, I don't like to scroll through the copyright notices, but I don't have any real objection to doing this. BTW, I added some "thank yous" to the release and put names to the new translations. I wanted to highlight the notable and new efforts, but should I have erred on the side of not leaving anyone out? We can list all the updated translations with translators, I just don't know all of them :). I figure the last thing we should do is make sure that *everyone* gets properly credited in the About dialog, and then we can release. -- -J. Method From lennart at karssen.org Wed Feb 20 13:56:57 2008 From: lennart at karssen.org (L.C. Karssen) Date: Wed, 20 Feb 2008 19:56:57 +0100 Subject: [Alexandria-list] 0.6.3 release soon... In-Reply-To: <20080220141520.1fea9a02@matilda> References: <167b6aa00802180014n28e235eaxa9370d70eb4d9461@mail.gmail.com> <20080218135901.259ef0d5@matilda> <20080218215454.6e901c0d@matilda> <20080219185557.5e76c930@matilda> <167b6aa00802200016p18f54592rf0be4109de9e1ce6@mail.gmail.com> <20080220141520.1fea9a02@matilda> Message-ID: <1203533817.12214.66.camel@rubidium01> On Wed, 2008-02-20 at 14:15 +0000, Cathal Mc Ginley wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Wed, 20 Feb 2008 03:16:25 -0500 > "Joseph Method" wrote: > > Hi, this is the first draft of a release announcement. I'm thinking > > about the gnome-announce list. > > > > http://alexandria.rubyforge.org/svn/trunk/alexandria/NEWS > > > > Edit it for style, facticity, etc. It especially needs the list of > > updated translations. > > * I wonder... the release note compares Alexandria to Tellico and > Delicious Library. Is this necessary? They're both more fully-featured > than Alexandria (they both support music & movies too), so the > comparison is sort of unfavourable for us. And people who don't know > those programs won't be any the wiser. Perhaps a short description of > the core utility of the program would be more useful? I agree with Cathal, I'm not sure whether the comparison actually does us any good. As for the description, maybe the Description field from the Debian control file will do? > > > * Anyway, I also did a couple of touch-ups here and there, including in > the README and Rakefile to make sure the version number is consistent at > 0.6.3. Don't forget to update it in the documentation too. Or do you want to update the docs with the new features and screenshots first? > * Also, since I noticed a problem with libgettext-ruby 1.1.0 > (on gNewSense) - I set a minimum version of 1.10.0, is that a widely > available version? Ubuntu Gutsy (the present version) and Hardy (the upcoming release) have 1.9.0, so, considering we're hoping for inclusion in Hardy I suggest using that version. > Before releasing, we should check that there's a copyright & GPL > license notice on every ruby file, especially those originally written > by Laurent Sansonetti et al. Some of the copyright notices were mislaid > during refactoring, when files were split up or code was moved about. > (I know, I'm a real nerd about these things...) I did a quick check using find . -iname "*.rb" | xargs head and found the following files that did not mention the GPL in the first few lines: ./lib/alexandria/ui/listview.rb ./lib/alexandria/ui/dndable.rb ./lib/alexandria/ui/iconview.rb ./lib/alexandria/ui/ui_manager.rb ./lib/alexandria/ui/callbacks.rb ./lib/alexandria/ui/init.rb ./lib/alexandria/console.rb ./lib/alexandria/about.rb ./spec/alexandria/ui/listview.rb ./spec/alexandria/ui/iconview.rb ./spec/alexandria/ui/sidepane.rb ./spec/alexandria/ui/ui_manager.rb ./tests/test_application.rb ./tests/test.rb ./tests/test_providers.rb ./tests/test_isbn.rb Lennart. > > - C. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2.2 (GNU/Linux) > Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE > > iD8DBQFHvDYBfMAUnRdb+8oRAiPLAKCiukiqfsOH20J1lMoYgsE4fxJ+uwCaA9jO > 0rGD0Zg7OV+KpWEi0HwTIb4= > =9Xfb > -----END PGP SIGNATURE----- > _______________________________________________ > Alexandria-list mailing list > Alexandria-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/alexandria-list -- ---------------------------------------------------- L.C. Karssen Utrecht The Netherlands lennart at karssen.org Stuur me aub geen Word of Powerpoint bestanden! Zie http://www.gnu.org/philosophy/no-word-attachments.nl.html ---------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://rubyforge.org/pipermail/alexandria-list/attachments/20080220/2f5e0fcd/attachment.bin From cathal.alexandria at gnostai.org Wed Feb 20 14:43:27 2008 From: cathal.alexandria at gnostai.org (Cathal Mc Ginley) Date: Wed, 20 Feb 2008 19:43:27 +0000 Subject: [Alexandria-list] 0.6.3 release soon... In-Reply-To: <1203533817.12214.66.camel@rubidium01> References: <167b6aa00802180014n28e235eaxa9370d70eb4d9461@mail.gmail.com> <20080218135901.259ef0d5@matilda> <20080218215454.6e901c0d@matilda> <20080219185557.5e76c930@matilda> <167b6aa00802200016p18f54592rf0be4109de9e1ce6@mail.gmail.com> <20080220141520.1fea9a02@matilda> <1203533817.12214.66.camel@rubidium01> Message-ID: <20080220194327.3c408837@matilda> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 20 Feb 2008 19:56:57 +0100 "L.C. Karssen" wrote: - --------- 8<------------- snip ------------ 8<--------------- > > * Anyway, I also did a couple of touch-ups here and there, > > including in the README and Rakefile to make sure the version > > number is consistent at 0.6.3. > Don't forget to update it in the documentation too. Or do you want to > update the docs with the new features and screenshots first? It would take a while to make new screenshots without the Refresh button, and there are only a handful of new features (which don't require much description) so I figure I'll leave the manual at 0.6.2 for now. (It mentions in the meta-data that it documents version 0.6.2). > > * Also, since I noticed a problem with libgettext-ruby 1.1.0 > > (on gNewSense) - I set a minimum version of 1.10.0, is that a widely > > available version? > Ubuntu Gutsy (the present version) and Hardy (the upcoming release) > have 1.9.0, so, considering we're hoping for inclusion in Hardy I > suggest using that version. I've changed it to 1.7.0 which is used in Debian (etch), and tested it successfully on gNewSense. I'll sort out the copyright notices next. - C. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE iD8DBQFHvILpfMAUnRdb+8oRAtSqAKCU1ah4S0diMcKMXRMhqkXmpYi+pQCfU6zm 7uxaoZXi9wJpWMpp2DBpR3I= =v9oW -----END PGP SIGNATURE----- From cathal.alexandria at gnostai.org Wed Feb 20 17:24:13 2008 From: cathal.alexandria at gnostai.org (Cathal Mc Ginley) Date: Wed, 20 Feb 2008 22:24:13 +0000 Subject: [Alexandria-list] 0.6.3 release imminent In-Reply-To: <20080220194327.3c408837@matilda> References: <167b6aa00802180014n28e235eaxa9370d70eb4d9461@mail.gmail.com> <20080218135901.259ef0d5@matilda> <20080218215454.6e901c0d@matilda> <20080219185557.5e76c930@matilda> <167b6aa00802200016p18f54592rf0be4109de9e1ce6@mail.gmail.com> <20080220141520.1fea9a02@matilda> <1203533817.12214.66.camel@rubidium01> <20080220194327.3c408837@matilda> Message-ID: <20080220222413.1efaf56d@matilda> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Okay, I fixed the copyright and license notices. And I made the tooltips look a bit nicer. And I solved the problem where Amazon ECS wasn't looking up all the locales in turn. So, does anyone think we should go ahead and remove the old Amazon provider in this release? I'm sort of thinking in terms of 'untested' (Amazon ECS) versus 'outdated'... (old Amazon provider). If we drop the old provider and there's a problem with the new one - everyone loses Amazon support. On the other hand, there's still that locale-related Ruby/Amazon problem (with people not upgrading to Ruby/Amazon 0.9.2), and the provider will expire in 6 weeks (while still making requests, no doubt, to unmaintained URLs). Hmmm, I think it'll probably be okay for one more release... Anyway, apart from writing a few more versions of the release notes (for RubyForge, for our website etc.) we are pretty much good to go for 0.6.3. - C. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE iD8DBQFHvKiYfMAUnRdb+8oRAi8HAKC18o7yEGn2J1755oUJ6HgO8Ss37QCfQMG0 A7Wp233SMinWnPbBmn7OX3Q= =J1v1 -----END PGP SIGNATURE----- From timothy.malone at gmail.com Wed Feb 20 19:19:25 2008 From: timothy.malone at gmail.com (Tim Malone) Date: Wed, 20 Feb 2008 19:19:25 -0500 Subject: [Alexandria-list] CSV import In-Reply-To: <167b6aa00802010939m2a90608dse1f54992931b5985@mail.gmail.com> References: <1201711602.6948.5.camel@timdesktop> <20080131200909.0b095f73@matilda> <1201812556.6932.16.camel@timdesktop> <167b6aa00802010939m2a90608dse1f54992931b5985@mail.gmail.com> Message-ID: Oops, this email seems to have slipped through my inbox. No problem, I've been wanting that feature for a while. I haven't had a chance to look into implementing it in other parts of the GUI yet. I haven't been following development all that well lately as I've been trying to get my graduate school application together for the past few weeks. I'm going to download the new release soon and check out what's been happening lately. I also realize now that I never committed my goodreads import support. At this point I guess that should wait until after 0.6.3. Well, just wanted to let you all know I haven't disappeared completely. :) Tim On Fri, Feb 1, 2008 at 12:39 PM, Joseph Method wrote: > > That is a really good point. I did write a patch for the "Date Read" > > field and it worked in all my testing with no compatibility problems, so > > I ended up committing it (revision 892 I believe). Feel free to reverse > > that if it was a bit premature. I hadn't considered the reading > > management issue before. My two cents on it would be that it should be a > > tab of its own (or plugin like the wiki suggests), but that "Date Read" > > is used commonly enough that it should remain on the main properties > > page. > > I noticed that, Timothy. Thanks for implementing that feature! I had > started working on this but you got there first with a smaller UI > imprint. There are a couple of places where the date read field needs > to be added to the UI now: in the main @listview columns and in the > column visibility list under Preferences. That is, perhaps date read > will not be a visible column default, but it should be an option to > see it. I'll get around to adding these if you don't. > > About the commit messages from the alexandria-commits lists: sometimes > an email ends up in my mail box asking me to approve a commit message > because it's too long. I'm not sure I even have the password for the > commits list. Another way to get commit messages is here: > http://wiki.alexandria-projects.org/changesets and for the rss feed: > http://wiki.alexandria-projects.org/rss/changesets. > > -- > -J. Method > From costanti at cs.st-andrews.ac.uk Thu Feb 21 03:14:54 2008 From: costanti at cs.st-andrews.ac.uk (Marco Costantini) Date: Thu, 21 Feb 2008 09:14:54 +0100 Subject: [Alexandria-list] 0.6.3 release soon... In-Reply-To: <20080219185557.5e76c930@matilda> References: <167b6aa00802180014n28e235eaxa9370d70eb4d9461@mail.gmail.com> <20080218215454.6e901c0d@matilda> <20080219185557.5e76c930@matilda> Message-ID: <200802210914.54573.costanti@cs.st-andrews.ac.uk> Dear all, there was a bug in 0.6.2, to be fixed before releasing 0.6.3: the Ubuntu/Debian package should depend on these packets: libwww-mechanize-ruby libimage-size-ruby or libimage-size-ruby1.8 in order to install them when installing Alexandria. I designed Alexandria to work even without these packets (altough with reduced functionality), however I think that we should let the Debian package system install them automatically with Alexandria. Greetings, Marco From cathal.alexandria at gnostai.org Thu Feb 21 12:38:12 2008 From: cathal.alexandria at gnostai.org (Cathal Mc Ginley) Date: Thu, 21 Feb 2008 17:38:12 +0000 Subject: [Alexandria-list] [ANN] Alexandria 0.6.3 Message-ID: <20080221173812.7d38a6f8@matilda> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Alexandria 0.6.3 has just been released. Alexandria is a GNOME application to help you manage your book collection. Alexandria 0.6.3 is a maintenance release of this program, continuing the new development effort begun last year. It brings greater overall stability and a more responsive user-interface, as well as fixing many bugs. New features in 0.6.3: * Asynchronous loading of libraries and visual feedback to make the GUI feel more responsive. * Export to iPod Notes format. * New Amazon ECS 4.0 support to replace the old AWS 3.x Amazon provider. AWS 3.x will be deprecated by Amazon on March 31 2008. * Tooltips for the icon view of books, to allow you to see more information at a glance. * New Galician and Chinese (Traditional) translations as well as an updated Czech translation and a Japanese translation of the Alexandria manual. Online release notes may be found here: http://alexandria.rubyforge.org/news/2008-02-21--0.6.3-released.html These include instructions for downloading and installing the new release. Please report any problems you encounter installing or upgrading on the RubyForge Tracker or the mailing list. Special thanks to L.C. Karssen for important bug triage work which helped us sort out and solve the most serious bugs in this iteration. Also thanks to our newest developer, Timothy Malone, for the totally original idea of iPod Notes export. And thanks to everyone who helped with the development of the 0.6.3 release. We hope that you enjoy it. - Cathal Mc Ginley. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE iD8DBQFHvbcNfMAUnRdb+8oRAslJAKCmBJVfEQKT0xkG85VLjg6sEnNSpQCfSHvY uUzU9v9StQeN6fpHvE7S8vQ= =DUwi -----END PGP SIGNATURE----- From tristil at gmail.com Thu Feb 21 19:32:08 2008 From: tristil at gmail.com (Joseph Method) Date: Thu, 21 Feb 2008 19:32:08 -0500 Subject: [Alexandria-list] 0.6.3 release soon... In-Reply-To: <200802210914.54573.costanti@cs.st-andrews.ac.uk> References: <167b6aa00802180014n28e235eaxa9370d70eb4d9461@mail.gmail.com> <20080218215454.6e901c0d@matilda> <20080219185557.5e76c930@matilda> <200802210914.54573.costanti@cs.st-andrews.ac.uk> Message-ID: <167b6aa00802211632w413aee36lbe6ee89f91c96c16@mail.gmail.com> Hi Marco, The repository here https://launchpad.net/~alexandria-team/+archive/ has packages with everything thrown into depends (and you can even install libzoom-ruby, but I forgot to add it to either list), but right now there's a debate going on about what the right thing to do is. On Thu, Feb 21, 2008 at 3:14 AM, Marco Costantini wrote: > Dear all, > there was a bug in 0.6.2, to be fixed before releasing 0.6.3: > the Ubuntu/Debian package should depend on these packets: > libwww-mechanize-ruby > libimage-size-ruby or libimage-size-ruby1.8 > in order to install them when installing Alexandria. > I designed Alexandria to work even without these packets (altough with reduced > functionality), however I think that we should let the Debian package system > install them automatically with Alexandria. > Greetings, > Marco > > > > > _______________________________________________ > Alexandria-list mailing list > Alexandria-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/alexandria-list > -- -J. Method From lennart at karssen.org Thu Feb 21 22:29:57 2008 From: lennart at karssen.org (L.C. Karssen) Date: Fri, 22 Feb 2008 04:29:57 +0100 Subject: [Alexandria-list] [ANN] Alexandria 0.6.3 In-Reply-To: <20080221173812.7d38a6f8@matilda> References: <20080221173812.7d38a6f8@matilda> Message-ID: <1203650997.6286.28.camel@rubidium01> Congratulations to all people who helped getting this release out! Most of all Joseph and Cathal who have made a big effort to get to this release fast, hoping to get it included in Ubuntu Hardy. Thanks guys! Lennart. PS: Shouldn't there also be a 0.6.3 tag made in SVN now? On Thu, 2008-02-21 at 17:38 +0000, Cathal Mc Ginley wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Alexandria 0.6.3 has just been released. > > Alexandria is a GNOME application to help you manage your book > collection. > > Alexandria 0.6.3 is a maintenance release of this program, continuing > the new development effort begun last year. It brings greater overall > stability and a more responsive user-interface, as well as fixing many > bugs. > > New features in 0.6.3: > > * Asynchronous loading of libraries and visual feedback to make > the GUI feel more responsive. > * Export to iPod Notes format. > * New Amazon ECS 4.0 support to replace the old AWS 3.x Amazon > provider. AWS 3.x will be deprecated by Amazon on March 31 2008. > * Tooltips for the icon view of books, to allow you to see more > information at a glance. > * New Galician and Chinese (Traditional) translations as well as an > updated Czech translation and a Japanese translation of the > Alexandria manual. > > Online release notes may be found here: > http://alexandria.rubyforge.org/news/2008-02-21--0.6.3-released.html > > These include instructions for downloading and installing the new > release. Please report any problems you encounter installing or > upgrading on the RubyForge Tracker or the mailing list. > > Special thanks to L.C. Karssen for important bug triage work which > helped us sort out and solve the most serious bugs in this iteration. > Also thanks to our newest developer, Timothy Malone, for the totally > original idea of iPod Notes export. > > And thanks to everyone who helped with the development of the 0.6.3 > release. We hope that you enjoy it. > > - Cathal Mc Ginley. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2.2 (GNU/Linux) > Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE > > iD8DBQFHvbcNfMAUnRdb+8oRAslJAKCmBJVfEQKT0xkG85VLjg6sEnNSpQCfSHvY > uUzU9v9StQeN6fpHvE7S8vQ= > =DUwi > -----END PGP SIGNATURE----- > _______________________________________________ > Alexandria-list mailing list > Alexandria-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/alexandria-list -- ---------------------------------------------------- L.C. Karssen Utrecht The Netherlands lennart at karssen.org Stuur me aub geen Word of Powerpoint bestanden! Zie http://www.gnu.org/philosophy/no-word-attachments.nl.html ---------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://rubyforge.org/pipermail/alexandria-list/attachments/20080222/0f02fe60/attachment.bin From cathal.alexandria at gnostai.org Fri Feb 22 12:31:07 2008 From: cathal.alexandria at gnostai.org (Cathal Mc Ginley) Date: Fri, 22 Feb 2008 17:31:07 +0000 Subject: [Alexandria-list] [ANN] Alexandria 0.6.3 In-Reply-To: <1203650997.6286.28.camel@rubidium01> References: <20080221173812.7d38a6f8@matilda> <1203650997.6286.28.camel@rubidium01> Message-ID: <20080222173107.4bb28ed3@matilda> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 22 Feb 2008 04:29:57 +0100 "L.C. Karssen" wrote: > Congratulations to all people who helped getting this release out! > Most of all Joseph and Cathal who have made a big effort to get to > this release fast, hoping to get it included in Ubuntu Hardy. > Thanks guys! > > Lennart. > > PS: Shouldn't there also be a 0.6.3 tag made in SVN now? Thanks for the reminder, I've tagged it now: 'alexandria/tags/alexandria/0.6.3'. I also tagged the www module so we know what the state of the website at the 0.6.3 release is: 'alexandria/tags/www/0.6.3'. Get the tags by going to the tags directory in the root of the *full* svn checkout:: cd alexandria/tags; svn update It being Subversion, it's possible to make tags of earlier releases at any stage in the future - but it's definitely easiest to make 'em right away. Cheers, - C. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE iD8DBQFHvwbmfMAUnRdb+8oRAmIRAKCXQsG/px5GnhBnj+yyvNax+gHSlQCeLyad BDjeDPUTtfvtRpsbxX3lAFA= =+AxX -----END PGP SIGNATURE----- From marrakis at gmail.com Fri Feb 22 12:42:07 2008 From: marrakis at gmail.com (Mathieu Leduc-Hamel) Date: Fri, 22 Feb 2008 12:42:07 -0500 Subject: [Alexandria-list] [ANN] Alexandria 0.6.3 In-Reply-To: <20080221173812.7d38a6f8@matilda> References: <20080221173812.7d38a6f8@matilda> Message-ID: Congratulation for this release of Alexandria! I think the codebased of alexandria has matured a lot since the last release! Maybe the next could be to push for it's inclusion as a default module of gnome? Why not? By the way, is there any roadmap for the next release and what you see as big improvement? Congratulation! Mathieu Leduc-Hamel On Thu, Feb 21, 2008 at 12:38 PM, Cathal Mc Ginley wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Alexandria 0.6.3 has just been released. > > Alexandria is a GNOME application to help you manage your book > collection. > > Alexandria 0.6.3 is a maintenance release of this program, continuing > the new development effort begun last year. It brings greater overall > stability and a more responsive user-interface, as well as fixing many > bugs. > > New features in 0.6.3: > > * Asynchronous loading of libraries and visual feedback to make > the GUI feel more responsive. > * Export to iPod Notes format. > * New Amazon ECS 4.0 support to replace the old AWS 3.x Amazon > provider. AWS 3.x will be deprecated by Amazon on March 31 2008. > * Tooltips for the icon view of books, to allow you to see more > information at a glance. > * New Galician and Chinese (Traditional) translations as well as an > updated Czech translation and a Japanese translation of the > Alexandria manual. > > Online release notes may be found here: > http://alexandria.rubyforge.org/news/2008-02-21--0.6.3-released.html > > These include instructions for downloading and installing the new > release. Please report any problems you encounter installing or > upgrading on the RubyForge Tracker or the mailing list. > > Special thanks to L.C. Karssen for important bug triage work which > helped us sort out and solve the most serious bugs in this iteration. > Also thanks to our newest developer, Timothy Malone, for the totally > original idea of iPod Notes export. > > And thanks to everyone who helped with the development of the 0.6.3 > release. We hope that you enjoy it. > > - Cathal Mc Ginley. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2.2 (GNU/Linux) > Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE > > iD8DBQFHvbcNfMAUnRdb+8oRAslJAKCmBJVfEQKT0xkG85VLjg6sEnNSpQCfSHvY > uUzU9v9StQeN6fpHvE7S8vQ= > =DUwi > -----END PGP SIGNATURE----- > _______________________________________________ > Alexandria-list mailing list > Alexandria-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/alexandria-list > From cathal.alexandria at gnostai.org Fri Feb 22 14:56:13 2008 From: cathal.alexandria at gnostai.org (Cathal Mc Ginley) Date: Fri, 22 Feb 2008 19:56:13 +0000 Subject: [Alexandria-list] CSV import (goodreads) In-Reply-To: References: <1201711602.6948.5.camel@timdesktop> <20080131200909.0b095f73@matilda> <1201812556.6932.16.camel@timdesktop> <167b6aa00802010939m2a90608dse1f54992931b5985@mail.gmail.com> Message-ID: <20080222195613.13c7e980@matilda> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 20 Feb 2008 19:19:25 -0500 "Tim Malone" wrote: > Oops, this email seems to have slipped through my inbox. No problem, > I've been wanting that feature for a while. I haven't had a chance to > look into implementing it in other parts of the GUI yet. I haven't > been following development all that well lately as I've been trying to > get my graduate school application together for the past few weeks. > I'm going to download the new release soon and check out what's been > happening lately. Just as you were writing those words, Joseph and I we were working on the 0.6.3 release. It's out now, and with a couple of your contributions included - check out the About box Credits! > I also realize now that I never committed my goodreads import support. > At this point I guess that should wait until after 0.6.3. I've just tagged the 0.6.3 release, so you can start committing to svn trunk again. > Well, just wanted to let you all know I haven't disappeared > completely. :) Cool. Hope to hear more from you anon, - Cathal. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE iD8DBQFHvyjofMAUnRdb+8oRAsM5AJ9laKc7yQajhL27WtIFNdAKcrqSfQCeNbuX tqwzv0osWbGsJ/U9SMsbsHs= =Yj4b -----END PGP SIGNATURE----- From cathal.alexandria at gnostai.org Fri Feb 22 16:50:11 2008 From: cathal.alexandria at gnostai.org (Cathal Mc Ginley) Date: Fri, 22 Feb 2008 21:50:11 +0000 Subject: [Alexandria-list] [ANN] Alexandria 0.6.3 In-Reply-To: <20080221173812.7d38a6f8@matilda> References: <20080221173812.7d38a6f8@matilda> Message-ID: <20080222215011.08266260@matilda> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 21 Feb 2008 17:38:12 +0000 Cathal Mc Ginley wrote: > > Alexandria 0.6.3 has just been released. > Perhaps I'm just easily impressed, but I think it's great to see the 0.6.3 release announcement make the RubyForge main page (while Alexandria is still amongst the projects "Most Active This Week"). Joseph Method also put out notifications on GnomeFiles and FreshMeat, while I requested that Alexandria's Free Software Directory listing be updated (that last might take a while). Hopefully, this slightly higher profile will bring us a few extra users; we should try to keep on top of any new bug reports or comments. In particular, we should make sure that new users are using the latest version - there was already a (duplicate) feature request today from a user reporting with Alexandria 0.6.1. - Cathal. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE iD8DBQFHv0OdfMAUnRdb+8oRAiXbAJ9I/qpPj+EfS4ZgIOCZhRjcQo8VdwCdGJuE a4Id1e4WDoYoWbH7GzYG0Yg= =Md64 -----END PGP SIGNATURE----- From tristil at gmail.com Sat Feb 23 00:10:47 2008 From: tristil at gmail.com (Joseph Method) Date: Sat, 23 Feb 2008 00:10:47 -0500 Subject: [Alexandria-list] [ANN] Alexandria 0.6.3 In-Reply-To: References: <20080221173812.7d38a6f8@matilda> Message-ID: <167b6aa00802222110s30d90cd2x14f25d87d45c9d00@mail.gmail.com> No, but we're about to discuss this together. On Fri, Feb 22, 2008 at 12:42 PM, Mathieu Leduc-Hamel wrote: > Congratulation for this release of Alexandria! > > I think the codebased of alexandria has matured a lot since the last release! > > Maybe the next could be to push for it's inclusion as a default module > of gnome? Why not? > > By the way, is there any roadmap for the next release and what you see > as big improvement? > > Congratulation! > > Mathieu Leduc-Hamel > > On Thu, Feb 21, 2008 at 12:38 PM, Cathal Mc Ginley > > wrote: > > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Alexandria 0.6.3 has just been released. > > > > Alexandria is a GNOME application to help you manage your book > > collection. > > > > Alexandria 0.6.3 is a maintenance release of this program, continuing > > the new development effort begun last year. It brings greater overall > > stability and a more responsive user-interface, as well as fixing many > > bugs. > > > > New features in 0.6.3: > > > > * Asynchronous loading of libraries and visual feedback to make > > the GUI feel more responsive. > > * Export to iPod Notes format. > > * New Amazon ECS 4.0 support to replace the old AWS 3.x Amazon > > provider. AWS 3.x will be deprecated by Amazon on March 31 2008. > > * Tooltips for the icon view of books, to allow you to see more > > information at a glance. > > * New Galician and Chinese (Traditional) translations as well as an > > updated Czech translation and a Japanese translation of the > > Alexandria manual. > > > > Online release notes may be found here: > > http://alexandria.rubyforge.org/news/2008-02-21--0.6.3-released.html > > > > These include instructions for downloading and installing the new > > release. Please report any problems you encounter installing or > > upgrading on the RubyForge Tracker or the mailing list. > > > > Special thanks to L.C. Karssen for important bug triage work which > > helped us sort out and solve the most serious bugs in this iteration. > > Also thanks to our newest developer, Timothy Malone, for the totally > > original idea of iPod Notes export. > > > > And thanks to everyone who helped with the development of the 0.6.3 > > release. We hope that you enjoy it. > > > > - Cathal Mc Ginley. > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.4.2.2 (GNU/Linux) > > Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE > > > > iD8DBQFHvbcNfMAUnRdb+8oRAslJAKCmBJVfEQKT0xkG85VLjg6sEnNSpQCfSHvY > > uUzU9v9StQeN6fpHvE7S8vQ= > > =DUwi > > -----END PGP SIGNATURE----- > > _______________________________________________ > > Alexandria-list mailing list > > Alexandria-list at rubyforge.org > > http://rubyforge.org/mailman/listinfo/alexandria-list > > > _______________________________________________ > Alexandria-list mailing list > Alexandria-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/alexandria-list > -- -J. Method From girish at hri.res.in Sat Feb 23 00:33:57 2008 From: girish at hri.res.in (Girish Kulkarni) Date: Sat, 23 Feb 2008 11:03:57 +0530 Subject: [Alexandria-list] [ANN] Alexandria 0.6.3 In-Reply-To: <20080221173812.7d38a6f8@matilda> References: <20080221173812.7d38a6f8@matilda> Message-ID: <8a2141c0802222133m51bf02b7yef080454b8e82cff@mail.gmail.com> On Thu, Feb 21, 2008 at 11:08 PM, Cathal Mc Ginley wrote: > Alexandria 0.6.3 has just been released. Thank you! Nice to see this happen! But I noticed that the Ubuntu repositories still provide v0.6.2b2. I really am not aware of how Ubuntu packaging system works, but when should we expect the availability of v0.6.3 there? Girish. From tristil at gmail.com Sat Feb 23 03:20:45 2008 From: tristil at gmail.com (Joseph Method) Date: Sat, 23 Feb 2008 03:20:45 -0500 Subject: [Alexandria-list] [ANN] Alexandria 0.6.3 In-Reply-To: <8a2141c0802222133m51bf02b7yef080454b8e82cff@mail.gmail.com> References: <20080221173812.7d38a6f8@matilda> <8a2141c0802222133m51bf02b7yef080454b8e82cff@mail.gmail.com> Message-ID: <167b6aa00802230020oe9a2702jaac6872b5f530afd@mail.gmail.com> Hi Girish, I think the _Ubuntu_ repositories only have 0.6.1. Have you tried the Alexandria repository? You can get information here: https://launchpad.net/~alexandria-team/+archive/ It may be that 0.6.2b2 won't update because of the name. If that's the case try removing it first. On Sat, Feb 23, 2008 at 12:33 AM, Girish Kulkarni wrote: > On Thu, Feb 21, 2008 at 11:08 PM, Cathal Mc Ginley wrote: > > Alexandria 0.6.3 has just been released. > > Thank you! Nice to see this happen! > > But I noticed that the Ubuntu repositories still provide v0.6.2b2. I > really am not aware of how Ubuntu packaging system works, but when > should we expect the availability of v0.6.3 there? > > Girish. > > > _______________________________________________ > Alexandria-list mailing list > Alexandria-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/alexandria-list > -- -J. Method From lennart at karssen.org Sat Feb 23 07:02:10 2008 From: lennart at karssen.org (L.C. Karssen) Date: Sat, 23 Feb 2008 13:02:10 +0100 Subject: [Alexandria-list] What is supposed to be the contents of a yaml file in Alexandria Message-ID: <1203768130.8126.3.camel@barabas.karssen.org> Hi all, I was looking around the .alexandria directory today (trying to find out more about bug #18308) and I came across several yaml files that had more than one book in them. I thought that each book was suposed to have its own yaml file named after its ISBN (and the opposite, each yaml file contains only one book). Is my assumption right and is my library corrupt, or am I wrong? Another thing I noticed is that I have several yaml files that start with a - (dash). This makes using tools like grep impossible. Are these files there for a reason? Lennart. -- ---------------------------------------------------- L.C. Karssen Utrecht The Netherlands lennart at karssen.org http://www.karssen.org Stuur me aub geen Word of Powerpoint bestanden! Zie http://www.gnu.org/philosophy/no-word-attachments.nl.html ---------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://rubyforge.org/pipermail/alexandria-list/attachments/20080223/242f4734/attachment.bin From lennart at karssen.org Sat Feb 23 07:26:33 2008 From: lennart at karssen.org (L.C. Karssen) Date: Sat, 23 Feb 2008 13:26:33 +0100 Subject: [Alexandria-list] [ANN] Alexandria 0.6.3 In-Reply-To: <20080222173107.4bb28ed3@matilda> References: <20080221173812.7d38a6f8@matilda> <1203650997.6286.28.camel@rubidium01> <20080222173107.4bb28ed3@matilda> Message-ID: <1203769593.8126.9.camel@barabas.karssen.org> Hi Cathal, I'm just starting to work with SVN, so I might be wrong here, but I wonder whether a 0.6.3 branch should also be created? I guess that that branch should be the place for bug fixes leading up to 0.6.3.1. New features (and the bug fixes) should then end up in trunk. By splitting the code up in this way we can supply bug fix releases to distributions, that might otherwise be denied because of the addition of new features (I'm thinking Ubuntu here :-)). Lennart. On Fri, 2008-02-22 at 17:31 +0000, Cathal Mc Ginley wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Fri, 22 Feb 2008 04:29:57 +0100 > "L.C. Karssen" wrote: > > > Congratulations to all people who helped getting this release out! > > Most of all Joseph and Cathal who have made a big effort to get to > > this release fast, hoping to get it included in Ubuntu Hardy. > > Thanks guys! > > > > Lennart. > > > > PS: Shouldn't there also be a 0.6.3 tag made in SVN now? > > Thanks for the reminder, I've tagged it now: > 'alexandria/tags/alexandria/0.6.3'. I also tagged the www module so we > know what the state of the website at the 0.6.3 release is: > 'alexandria/tags/www/0.6.3'. Get the tags by going to the tags directory > in the root of the *full* svn checkout:: cd alexandria/tags; svn update > > It being Subversion, it's possible to make tags of earlier releases at > any stage in the future - but it's definitely easiest to make 'em right > away. > > Cheers, > > - C. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2.2 (GNU/Linux) > Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE > > iD8DBQFHvwbmfMAUnRdb+8oRAmIRAKCXQsG/px5GnhBnj+yyvNax+gHSlQCeLyad > BDjeDPUTtfvtRpsbxX3lAFA= > =+AxX > -----END PGP SIGNATURE----- > _______________________________________________ > Alexandria-list mailing list > Alexandria-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/alexandria-list -- ---------------------------------------------------- L.C. Karssen Utrecht The Netherlands lennart at karssen.org http://www.karssen.org Stuur me aub geen Word of Powerpoint bestanden! Zie http://www.gnu.org/philosophy/no-word-attachments.nl.html ---------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://rubyforge.org/pipermail/alexandria-list/attachments/20080223/6ec67d4e/attachment.bin From cathal.alexandria at gnostai.org Sat Feb 23 17:05:13 2008 From: cathal.alexandria at gnostai.org (Cathal Mc Ginley) Date: Sat, 23 Feb 2008 22:05:13 +0000 Subject: [Alexandria-list] What is supposed to be the contents of a yaml file in Alexandria In-Reply-To: <1203768130.8126.3.camel@barabas.karssen.org> References: <1203768130.8126.3.camel@barabas.karssen.org> Message-ID: <20080223220513.5664871a@matilda> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, 23 Feb 2008 13:02:10 +0100 "L.C. Karssen" wrote: > Hi all, > > I was looking around the .alexandria directory today (trying to find > out more about bug #18308) and I came across several yaml files that > had more than one book in them. I thought that each book was suposed > to have its own yaml file named after its ISBN (and the opposite, > each yaml file contains only one book). Is my assumption right and is > my library corrupt, or am I wrong? You're right. Each YAML file should have exactly one book in it. Okay, this would be a major problem. I imagine it's something to do with the recent changes to the Book and Library classes - Book now contains an embedded link back to its containing Library. This is supposed to get nil'ed out before it's serialized to YAML, but this mightn't be happening everywhere. Can you send me an example YAML file with this corruption? If this is the case, we have a serious showstopper bug on our hands which would require an emergency bugfix release. I also had a look at the debug log for #18308, and an InvalidISBNError should not be causing a crash like that :^( > > Another thing I noticed is that I have several yaml files that start > with a - (dash). This makes using tools like grep impossible. Are > these files there for a reason? > Yep, this is an annoyance I've noticed before. When a book doesn't have an ISBN, it's 'ident' or identifier, is generated by taking the hash-code of its title (a number generated from the title string, called a hash-code because it's often used in hashtables). Sometimes this number is negative. The YAML filename uses the 'ident', so this sometimes results in filenames beginning with a '-'. grep does indeed have trouble with this, it thinks you're trying to specify an option like -77516869.yaml; but you can tell it to stop expecting options by using -- as follows: grep -i -- title *.yaml It's annoying, though, and it's a 'feature' I'd love to remove somehow. > > Lennart. - C. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE iD8DBQFHwJiifMAUnRdb+8oRAhndAJ9KvwNiTb/+peboYDyR2jbXEPUBRwCfZTot bDirNpv2OK2Pc+A5cT1R0E4= =EJPx -----END PGP SIGNATURE----- From cathal.alexandria at gnostai.org Sat Feb 23 17:19:46 2008 From: cathal.alexandria at gnostai.org (Cathal Mc Ginley) Date: Sat, 23 Feb 2008 22:19:46 +0000 Subject: [Alexandria-list] [ANN] Alexandria 0.6.3 In-Reply-To: <1203769593.8126.9.camel@barabas.karssen.org> References: <20080221173812.7d38a6f8@matilda> <1203650997.6286.28.camel@rubidium01> <20080222173107.4bb28ed3@matilda> <1203769593.8126.9.camel@barabas.karssen.org> Message-ID: <20080223221946.3fbbc208@matilda> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, 23 Feb 2008 13:26:33 +0100 "L.C. Karssen" wrote: > Hi Cathal, > > I'm just starting to work with SVN, so I might be wrong here, but I > wonder whether a 0.6.3 branch should also be created? I guess that > that branch should be the place for bug fixes leading up to 0.6.3.1. > New features (and the bug fixes) should then end up in trunk. > By splitting the code up in this way we can supply bug fix releases to > distributions, that might otherwise be denied because of the addition > of new features (I'm thinking Ubuntu here :-)). > Good plan! Especially considering the bugs that have shown up recently. I've created a new 0.6.3-maintenance branch for such work. Developers can use subversion to switch to the branch. The command 'svn switch svn+ssh://USERNAME at rubyforge.org/var/svn/alexandria/branches/alexandria/0.6.3-maintenance' will make bring your current svn working directory into line with the branch. Make sure to use your real RubyForge USERNAME... Be sure you're in the right branch when you commit (check with 'svn info .') and don't add new features to the 0.6.3-maintenance branch. - C. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE iD8DBQFHwJwKfMAUnRdb+8oRAiPMAJ0f8+H8DFNhu0JktrBIiR7KkIZnBgCfWjor gJJQecuw0c0unKoURkubpzY= =qUMz -----END PGP SIGNATURE----- From timothy.malone at gmail.com Sat Feb 23 17:37:03 2008 From: timothy.malone at gmail.com (Tim Malone) Date: Sat, 23 Feb 2008 17:37:03 -0500 Subject: [Alexandria-list] What is supposed to be the contents of a yaml file in Alexandria In-Reply-To: <20080223220513.5664871a@matilda> References: <1203768130.8126.3.camel@barabas.karssen.org> <20080223220513.5664871a@matilda> Message-ID: oops, I had sent an email in response to this and forgot to cc the list. Anyway, the problem was something I had fixed a little while ago after noticing that my yaml files were getting quite large. The problem was the pointer to the Library was getting written to each file. It doesn't seem to cause any dire consequences (files load properly and I've seen no instances of duplicate books getting loaded). However, with the patch I committed (before 0.6.3), simply opening a book's properties and then hitting the save button fixes the file. Lennart replied to my offlist email and confirmed that this was the problem and that re-saving the file fixed it. It would be interesting to know if the Library link was in any release versions of Alexandria. If so we might want to include a check for affected files when loading a library just in case a problem shows up with them later on. Tim On Sat, Feb 23, 2008 at 5:05 PM, Cathal Mc Ginley wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Sat, 23 Feb 2008 13:02:10 +0100 > > "L.C. Karssen" wrote: > > > > Hi all, > > > > I was looking around the .alexandria directory today (trying to find > > out more about bug #18308) and I came across several yaml files that > > had more than one book in them. I thought that each book was suposed > > to have its own yaml file named after its ISBN (and the opposite, > > each yaml file contains only one book). Is my assumption right and is > > my library corrupt, or am I wrong? > > You're right. Each YAML file should have exactly one book in it. > > Okay, this would be a major problem. I imagine it's something to do > with the recent changes to the Book and Library classes - Book now > contains an embedded link back to its containing Library. This is > supposed to get nil'ed out before it's serialized to YAML, but this > mightn't be happening everywhere. > > Can you send me an example YAML file with this corruption? > If this is the case, we have a serious showstopper bug on our hands > which would require an emergency bugfix release. > > I also had a look at the debug log for #18308, and an InvalidISBNError > should not be causing a crash like that :^( > > > > > > Another thing I noticed is that I have several yaml files that start > > with a - (dash). This makes using tools like grep impossible. Are > > these files there for a reason? > > > > Yep, this is an annoyance I've noticed before. When a book doesn't have > an ISBN, it's 'ident' or identifier, is generated by taking the > hash-code of its title (a number generated from the title string, > called a hash-code because it's often used in hashtables). Sometimes > this number is negative. The YAML filename uses the 'ident', so this > sometimes results in filenames beginning with a '-'. > > grep does indeed have trouble with this, it thinks you're trying to > specify an option like -77516869.yaml; but you can tell it to stop > expecting options by using -- as follows: > grep -i -- title *.yaml > > It's annoying, though, and it's a 'feature' I'd love to remove somehow. > > > > > Lennart. > > - C. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2.2 (GNU/Linux) > Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE > > iD8DBQFHwJiifMAUnRdb+8oRAhndAJ9KvwNiTb/+peboYDyR2jbXEPUBRwCfZTot > bDirNpv2OK2Pc+A5cT1R0E4= > =EJPx > -----END PGP SIGNATURE----- > > > _______________________________________________ > Alexandria-list mailing list > Alexandria-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/alexandria-list > From lennart at karssen.org Sat Feb 23 17:48:41 2008 From: lennart at karssen.org (L.C. Karssen) Date: Sat, 23 Feb 2008 23:48:41 +0100 Subject: [Alexandria-list] What is supposed to be the contents of a yaml file in Alexandria In-Reply-To: References: <1203768130.8126.3.camel@barabas.karssen.org> <20080223220513.5664871a@matilda> Message-ID: <1203806921.8055.41.camel@barabas.karssen.org> On Sat, 2008-02-23 at 17:37 -0500, Tim Malone wrote: > oops, I had sent an email in response to this and forgot to cc the > list. Oops, and apparently I forgot to add the list as well, when I replied :-D. Well, for the record: your suggestions works. Double click on a book and hitting the save button works. Lennart. > > Tim > > On Sat, Feb 23, 2008 at 5:05 PM, Cathal Mc Ginley > wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > On Sat, 23 Feb 2008 13:02:10 +0100 > > > > "L.C. Karssen" wrote: > > > > > > > Hi all, > > > > > > I was looking around the .alexandria directory today (trying to find > > > out more about bug #18308) and I came across several yaml files that > > > had more than one book in them. I thought that each book was suposed > > > to have its own yaml file named after its ISBN (and the opposite, > > > each yaml file contains only one book). Is my assumption right and is > > > my library corrupt, or am I wrong? > > > > You're right. Each YAML file should have exactly one book in it. > > > > Okay, this would be a major problem. I imagine it's something to do > > with the recent changes to the Book and Library classes - Book now > > contains an embedded link back to its containing Library. This is > > supposed to get nil'ed out before it's serialized to YAML, but this > > mightn't be happening everywhere. > > > > Can you send me an example YAML file with this corruption? > > If this is the case, we have a serious showstopper bug on our hands > > which would require an emergency bugfix release. > > > > I also had a look at the debug log for #18308, and an InvalidISBNError > > should not be causing a crash like that :^( > > > > > > > > > > Another thing I noticed is that I have several yaml files that start > > > with a - (dash). This makes using tools like grep impossible. Are > > > these files there for a reason? > > > > > > > Yep, this is an annoyance I've noticed before. When a book doesn't have > > an ISBN, it's 'ident' or identifier, is generated by taking the > > hash-code of its title (a number generated from the title string, > > called a hash-code because it's often used in hashtables). Sometimes > > this number is negative. The YAML filename uses the 'ident', so this > > sometimes results in filenames beginning with a '-'. > > > > grep does indeed have trouble with this, it thinks you're trying to > > specify an option like -77516869.yaml; but you can tell it to stop > > expecting options by using -- as follows: > > grep -i -- title *.yaml > > > > It's annoying, though, and it's a 'feature' I'd love to remove somehow. > > > > > > > > Lennart. > > > > - C. > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.4.2.2 (GNU/Linux) > > Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE > > > > iD8DBQFHwJiifMAUnRdb+8oRAhndAJ9KvwNiTb/+peboYDyR2jbXEPUBRwCfZTot > > bDirNpv2OK2Pc+A5cT1R0E4= > > =EJPx > > -----END PGP SIGNATURE----- > > > > > > _______________________________________________ > > Alexandria-list mailing list > > Alexandria-list at rubyforge.org > > http://rubyforge.org/mailman/listinfo/alexandria-list > > -- ---------------------------------------------------- L.C. Karssen Utrecht The Netherlands lennart at karssen.org http://www.karssen.org Stuur me aub geen Word of Powerpoint bestanden! Zie http://www.gnu.org/philosophy/no-word-attachments.nl.html ---------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://rubyforge.org/pipermail/alexandria-list/attachments/20080223/60bf3170/attachment.bin From cathal.alexandria at gnostai.org Sat Feb 23 18:00:05 2008 From: cathal.alexandria at gnostai.org (Cathal Mc Ginley) Date: Sat, 23 Feb 2008 23:00:05 +0000 Subject: [Alexandria-list] What is supposed to be the contents of a yaml file in Alexandria In-Reply-To: References: <1203768130.8126.3.camel@barabas.karssen.org> <20080223220513.5664871a@matilda> Message-ID: <20080223230005.17f3c2d1@matilda> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, 23 Feb 2008 17:37:03 -0500 "Tim Malone" wrote: > oops, I had sent an email in response to this and forgot to cc the > list. Anyway, the problem was something I had fixed a little while ago > after noticing that my yaml files were getting quite large. The > problem was the pointer to the Library was getting written to each > file. It doesn't seem to cause any dire consequences (files load > properly and I've seen no instances of duplicate books getting > loaded). However, with the patch I committed (before 0.6.3), simply > opening a book's properties and then hitting the save button fixes the > file. Lennart replied to my offlist email and confirmed that this was > the problem and that re-saving the file fixed it. Glad to hear it causes no long-term problems. And that the issue is not actually present in a formal release. > It would be interesting to know if the Library link was in any release > versions of Alexandria. If so we might want to include a check for > affected files when loading a library just in case a problem shows up > with them later on. It was only ever in subversion between 0.6.2 and 0.6.3, there were no interim releases. However, I did notice one thing and forgot to bring it up (a cardinal error, I didn't write it down). In order to set the library to nil, you have the following lines in library.rb (434 & 435) temp_book=book temp_book.library=nil And then you write out temp_book. That first line there only copies the *reference*, you probably wanted temp_book=book.dup to copy the object. I don't know what effect setting a book's library to nil will have in the grander scheme of things. In reality, I think book.library is only used by the ReadingList application. - C. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE iD8DBQFHwKV9fMAUnRdb+8oRAhA+AJ9zT7ihFoxtCtkdozZhcmxTXtG3yQCgqnlU yFJS9Tpv5QskMPayLubIwz8= =qq6R -----END PGP SIGNATURE----- From lennart at karssen.org Sat Feb 23 18:15:02 2008 From: lennart at karssen.org (L.C. Karssen) Date: Sun, 24 Feb 2008 00:15:02 +0100 Subject: [Alexandria-list] What is supposed to be the contents of a yaml file in Alexandria In-Reply-To: <20080223220513.5664871a@matilda> References: <1203768130.8126.3.camel@barabas.karssen.org> <20080223220513.5664871a@matilda> Message-ID: <1203808502.18875.1.camel@rubidium01> On Sat, 2008-02-23 at 22:05 +0000, Cathal Mc Ginley wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Sat, 23 Feb 2008 13:02:10 +0100 > "L.C. Karssen" wrote: > > > > > Another thing I noticed is that I have several yaml files that start > > with a - (dash). This makes using tools like grep impossible. Are > > these files there for a reason? > > > > Yep, this is an annoyance I've noticed before. When a book doesn't have > an ISBN, it's 'ident' or identifier, is generated by taking the > hash-code of its title (a number generated from the title string, > called a hash-code because it's often used in hashtables). Sometimes > this number is negative. The YAML filename uses the 'ident', so this > sometimes results in filenames beginning with a '-'. Would it be a good idea to prefix all yaml files with 'alex' or even 'alexandria' so that the minus doesn't really matter any more? -- ---------------------------------------------------- L.C. Karssen Utrecht The Netherlands lennart at karssen.org Stuur me aub geen Word of Powerpoint bestanden! Zie http://www.gnu.org/philosophy/no-word-attachments.nl.html ---------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://rubyforge.org/pipermail/alexandria-list/attachments/20080224/bc170ffc/attachment.bin From timothy.malone at gmail.com Sat Feb 23 23:04:42 2008 From: timothy.malone at gmail.com (Timothy Malone) Date: Sat, 23 Feb 2008 23:04:42 -0500 Subject: [Alexandria-list] What is supposed to be the contents of a yaml file in Alexandria In-Reply-To: <20080223230005.17f3c2d1@matilda> References: <1203768130.8126.3.camel@barabas.karssen.org> <20080223220513.5664871a@matilda> <20080223230005.17f3c2d1@matilda> Message-ID: <1203825882.7070.8.camel@timdesktop> You're right, I think I did mean book.dup, must have not occurred to me that it was just a reference at the time. You're also right that it isn't used by the main app, as far as I could tell with a quick grep of trunk, though it is probably a good idea to preserve the reference in case it's needed later, or if Reading-List uses library.rb to write to files (I don't think it writes anything to book files yet). Tim On Sat, 2008-02-23 at 23:00 +0000, Cathal Mc Ginley wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Sat, 23 Feb 2008 17:37:03 -0500 > "Tim Malone" wrote: > > > oops, I had sent an email in response to this and forgot to cc the > > list. Anyway, the problem was something I had fixed a little while ago > > after noticing that my yaml files were getting quite large. The > > problem was the pointer to the Library was getting written to each > > file. It doesn't seem to cause any dire consequences (files load > > properly and I've seen no instances of duplicate books getting > > loaded). However, with the patch I committed (before 0.6.3), simply > > opening a book's properties and then hitting the save button fixes the > > file. Lennart replied to my offlist email and confirmed that this was > > the problem and that re-saving the file fixed it. > > Glad to hear it causes no long-term problems. And that the issue is not > actually present in a formal release. > > > It would be interesting to know if the Library link was in any release > > versions of Alexandria. If so we might want to include a check for > > affected files when loading a library just in case a problem shows up > > with them later on. > > It was only ever in subversion between 0.6.2 and 0.6.3, there were no > interim releases. However, I did notice one thing and forgot to bring > it up (a cardinal error, I didn't write it down). In order to set the > library to nil, you have the following lines in library.rb (434 & 435) > temp_book=book > temp_book.library=nil > And then you write out temp_book. That first line there only copies the > *reference*, you probably wanted temp_book=book.dup to copy the object. > I don't know what effect setting a book's library to nil will have in > the grander scheme of things. In reality, I think book.library is only > used by the ReadingList application. > > - C. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2.2 (GNU/Linux) > Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE > > iD8DBQFHwKV9fMAUnRdb+8oRAhA+AJ9zT7ihFoxtCtkdozZhcmxTXtG3yQCgqnlU > yFJS9Tpv5QskMPayLubIwz8= > =qq6R > -----END PGP SIGNATURE-----