Re: [DRE-maint] Some comments on the redmine package
On Aug 30, 2008, at 5:11 AM| Aug 30, 2008, Jean-Philippe Garcia Ballester wrote: > However, since this is the first rails app that will be package in > Debian, I think that others will take it as an example, and I fear > that if > the package has a few things to fix, these few things will have to be > fixed in more that one package. AFAIK redmine won't be in lenny, so > I'd > rather see the first rails package to be as good as possible. Agreed! > Anyway, here is what I've seen so far: > * Use debconf in your postinst, to ask the user if > * he wants to configure the database.yml file > * he wants to create the db > * he wants to load default data > * he wants to configure a webserver (apache2 fcgid / apache2 > mod_rails / …) I'm not sure I want to use debconf, at least at first. I've never played with it and have no idea where to start. If someone had some input or wanted to take this on I would be grateful. Otherwise I think it will have to wait until the package gets a bit more time under its belt. > * The sample apache configuration you provide has AFAIK the > following problems: > * It will not work out of the box. If you do not wish to use > debconf to ask the user which way he wants, you should add in the > apache2.conf a working configuration (e.g. with mod_fcgid), and in > comments other working configurations (e.g. with mod_rails). This apache.conf does work out of the box on my test system. I'm not sure what else to put in here. Are you saying that the comments should be a little more verbose and explain how to set up mod_fcgid? > * Why put a VirtualHost with a DocumentRoot? This is > confusing, the Alias alone would work better IHMO. I think the upstream has it like this; I didn't even notice the problem. However, the DocuemntRoot is required unless you have a valid one somewhere else. If I remove it Apache complains about not being able to find "/htdocs", which is a default value. Also, I couldn't get the alias to work without reworking the routes so I am going to remove it completely. Is there a standard way to set up Apache? Should each app use its own VirtualHost or should it use Alias? Did I hear that the .htaccess file is a bad thing and will be going away in the future? If so, should I move all that stuff to the section? > > * The commented VirtualHost DocumentRoot lacks “/public” at > the end. Fixed. > * The README.Debian files contains requirements for running > redmine. They are IMHO useless, because it is the job of the package > to > ensure the requirements are fullfilled (except for optionnal stuff > like db > and webserver configuration). Thus, I think removing the first two > lines > and modifying debian/control to add dependency on ruby1.8 and rails > (>= 2.1), rails (<= 2.2) is better. Agreed & corrected. > * The debian/redmine.lintian-overrides overrides things that should > not be overriden, and hides bugs. > * The “script-not-executable” warnings: having a shebang and > not being executable is contradictory. Either the script can be used > as a > binary, and should be executable, or it is not and then the shebang > useless. The feedback I got from upstream was that these scripts were optional that are copied to other locations when setting up Apache controlled subversion access. Upstream decided that they should not be executable by default. I can patch them if its something that needs to be done. I agree with you but being as this is my first package I have no background on which to base my decision on. Anyone else have any comments? > * The ”package-contains-empty-directory”: your comment > says “These directories hold temporary data”. However, /usr/share is > meant to be read-only, and shipping empty directories there is a bug. > Either the program write something in the directory, and this is a > bug, > or the program doesn't write anything and the directory is useless. I think maybe my Rails inexperience is showing through. Can anyone shed some light on these directories and where they should be placed? I'm thinking that they are standard Rails procedures but might not be used in Redmine: * .../apps/view/members - I think this is part of scaffolding and can be removed. * .../apps/sweepers - If its empty the app doesn't use it and it can be removed. * .../lib/plugins - Future expansion and can be removed. * .../vendor/plugins/gloc-1.1.0/lang - No idea??? > * I think the “public” directory should go in /usr/share, because > AFAIK it is not meant to be changed, neither at runtime nor by the > user. I have really struggled with what to do with "public" but looking back on it I can see that you are probably correct. Based on this feedback I have moved .../public back to /usr/share. Does this work for everyone? The only weird thing is the .../public/plugin_assets directory. According to the REA
[DRE-maint] libgemplugin-ruby 0.2.3-2 MIGRATED to testing
FYI: The status of the libgemplugin-ruby source package in Debian's testing distribution has changed. Previous version: 0.2.3-1 Current version: 0.2.3-2 -- This email is automatically generated; the Debian Release Team <[EMAIL PROTECTED]> is responsible. See http://release.debian.org/testing-watch/ for more information. ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] mongrel 1.1.5-3 MIGRATED to testing
FYI: The status of the mongrel source package in Debian's testing distribution has changed. Previous version: 1.1.5-2 Current version: 1.1.5-3 -- This email is automatically generated; the Debian Release Team <[EMAIL PROTECTED]> is responsible. See http://release.debian.org/testing-watch/ for more information. ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] libgems-ruby 1.2.0-3 MIGRATED to testing
FYI: The status of the libgems-ruby source package in Debian's testing distribution has changed. Previous version: 1.1.1-1 Current version: 1.2.0-3 -- This email is automatically generated; the Debian Release Team <[EMAIL PROTECTED]> is responsible. See http://release.debian.org/testing-watch/ for more information. ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#485739: marked as done (libgems-ruby1.8: Installs gems multiple times)
Your message dated Fri, 5 Sep 2008 16:04:43 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: [DRE-maint] Bug#485739: Bug#485739: libgems-ruby1.8: Installs gems multiple times has caused the Debian Bug report #485739, regarding libgems-ruby1.8: Installs gems multiple times to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 485739: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485739 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: libgems-ruby1.8 Version: 1.1.1-1 Severity: normal I just ran 'gem update' and got the following output. Something odd is going on [EMAIL PROTECTED] sudo gem update Updating installed gems Bulk updating Gem source index for: http://gems.rubyforge.org/ Updating ParseTree Successfully installed RubyInline-3.7.0 Successfully installed ParseTree-2.2.0 Updating ZenTest Successfully installed RubyInline-3.7.0 Successfully installed ParseTree-2.2.0 Successfully installed ZenTest-3.9.3 Updating acts_as_reportable Bulk updating Gem source index for: http://gems.rubyforge.org/ Successfully installed RubyInline-3.7.0 Successfully installed ParseTree-2.2.0 Successfully installed ZenTest-3.9.3 Successfully installed acts_as_reportable-1.1.1 Updating murdoch Successfully installed RubyInline-3.7.0 Successfully installed ParseTree-2.2.0 Successfully installed ZenTest-3.9.3 Successfully installed acts_as_reportable-1.1.1 Successfully installed murdoch-1.0.1 Updating ruby2ruby Successfully installed RubyInline-3.7.0 Successfully installed ParseTree-2.2.0 Successfully installed ZenTest-3.9.3 Successfully installed acts_as_reportable-1.1.1 Successfully installed murdoch-1.0.1 Successfully installed ruby2ruby-1.1.9 Gems updated: RubyInline, ParseTree, RubyInline, ParseTree, ZenTest, RubyInline, ParseTree, ZenTest, acts_as_reportable, RubyInline, ParseTree, ZenTest, acts_as_reportable, murdoch, ruby2ruby] -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.25-jh (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libgems-ruby1.8 depends on: ii libopenssl-ruby1.81.8.7-2OpenSSL interface for Ruby 1.8 ii libruby1.81.8.7-2Libraries necessary to run Ruby 1. ii rdoc1.8 1.8.7-2Generate documentation from Ruby s Versions of packages libgems-ruby1.8 recommends: ii rubygems 1.1.1-1package management framework for R -- no debconf information --- End Message --- --- Begin Message --- Version: 1.2.0-3 On 05/09/08 at 23:20 +1000, James Healy wrote: > Ricardo Pérez López wrote: > > I can confirm this bug as well in my Ubuntu 8.04.1. > > > > I'm using rubygems version 1.1.1-1~hardy1. > > It's worth pointing out that this doesn't seem to occur in version > 1.2.0, the one we now have in Sid and lenny. > > Not sure how to drive the version pseudo-headers to indicate this. Like that (mail to -done with Version: pseudo-header) ;) -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | --- End Message --- ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#485739: Bug#485739: libgems-ruby1.8: Installs gems multiple times
Ricardo Pérez López wrote: > I can confirm this bug as well in my Ubuntu 8.04.1. > > I'm using rubygems version 1.1.1-1~hardy1. It's worth pointing out that this doesn't seem to occur in version 1.2.0, the one we now have in Sid and lenny. Not sure how to drive the version pseudo-headers to indicate this. -- James Healy Fri, 05 Sep 2008 23:18:46 +1000 ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#485739: libgems-ruby1.8: Installs gems multiple times
I can confirm this bug as well in my Ubuntu 8.04.1. I'm using rubygems version 1.1.1-1~hardy1. $ sudo gem update Updating installed gems Bulk updating Gem source index for: http://gems.rubyforge.org/ Updating actionmailer Bulk updating Gem source index for: http://gems.rubyforge.org/ Successfully installed activesupport-2.1.1 Successfully installed actionpack-2.1.1 Successfully installed actionmailer-2.1.1 Updating activerecord Successfully installed activesupport-2.1.1 Successfully installed actionpack-2.1.1 Successfully installed actionmailer-2.1.1 Successfully installed activerecord-2.1.1 Updating activeresource Successfully installed activesupport-2.1.1 Successfully installed actionpack-2.1.1 Successfully installed actionmailer-2.1.1 Successfully installed activerecord-2.1.1 Successfully installed activeresource-2.1.1 Updating rails Successfully installed activesupport-2.1.1 Successfully installed actionpack-2.1.1 Successfully installed actionmailer-2.1.1 Successfully installed activerecord-2.1.1 Successfully installed activeresource-2.1.1 Successfully installed rails-2.1.1 Updating ruby-debug Building native extensions. This could take a while... Successfully installed activesupport-2.1.1 Successfully installed actionpack-2.1.1 Successfully installed actionmailer-2.1.1 Successfully installed activerecord-2.1.1 Successfully installed activeresource-2.1.1 Successfully installed rails-2.1.1 Successfully installed ruby-debug-base-0.10.2 Successfully installed ruby-debug-0.10.2 Gems updated: activesupport, actionpack, actionmailer, activesupport, actionpack, actionmailer, activerecord, activesupport, actionpack, actionmailer, activerecord, activeresource, activesupport, actionpack, actionmailer, activerecord, activeresource, rails, activesupport, actionpack, actionmailer, activerecord, activeresource, rails, ruby-debug-base, ruby-debug ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-ruby-extras-maintainers
