By bengen on

A few hours ago, I uploaded a package of Drupal version 4.3.2 to Debian unstable. This upload will hopefully fix all the critical bugs of the previous package (and introduce no new ones). Another highlight is that the package supports PostgreSQL (although this may still need some polishing).

Please submit any bugs you find in my package through the Debian bug tracking system, since that's the quickest and most reliable way of reaching my attention.

I still need some help with the following:

  • Translation of debconf questions (Questions that are asked at installation time, such as "Please enter the name of the database Drupal should use.") into languages other than English, German, Spanish, and Catalan.
  • Testing of the automagic database update functions
  • Advice on how to resolve the remaining PostgreSQL issues: The database is owned by the Drupal user, but accessing the website fails due to permission problems in the DBMS (tested with 7.4.1)
  • Hints whether there are any bugs in the code that have been fixed for the 4.3 branch since 4.3.2.

If the package turns out to work well enough, I'll start working on a 4.4-pre package soon, then we'll have a working package soon after 4.4.0 is released.

Cheers,

-Hilko

Comments

qgil’s picture

qgil commented

I think my first post in drupal.org was precisely a request for an updated Debian package.

Thanks for the work, hopefully this would increase Drupal's popularity among Debian users (and viceversa) :)

mrowe’s picture

mrowe commented

apt-get update-ing as I type... :)

Thanks for your effort!

--
Michael Rowe
"A designer knows he has achieved perfection not when there is nothing left to add, but when there is nothing left to take away." -Antoine de Saint-Exupéry

moonfire’s picture

moonfire commented

I'm glad to hear about the debian packages, that would be one thing to move my last Gentoo box back to Libranet. Are you also considering doing the various modules also? Such as the image stuff, etc? Maybe the drupal site could put the debian repository tree on their site so we can use this as a common debian source and it gives those who want to test a chance to get everything sooner.

I really prefer everything as packages, makes it easier when something updates. And if module writers would add the database code into the module itself (I *love* that), then it would be easy. Otherwise you have to have "modulename-mysql" and "modulename-psql" (for the database-specific?)

Also, is the package creating the databases, populating them? How do you handle multiple databases? Right now, I have 6 drupal databases running 10 sites. I would love it if there was something that would update all of the databases at once (i.e. when I upgrade, it upgrades everything).

bengen’s picture

bengen commented

Are you also considering doing the various modules also? Such as the image stuff, etc.?

It would certainly be possible, but I really don't consider myself competent enough to chose the stable ones from the various modules at the moment.

Also, is the package creating the databases, populating them?

Yes.

How do you handle multiple databases?

I don't.

Right now, I have 6 drupal databases running 10 sites. I would love it if there was something that would update all of the databases at once

I am aware of the problem, but right now I don't see a solution. How do you organize configuration files in this case?

Cheers,

-Hilko

moonfire’s picture

moonfire commented

I'm dealing with the sites in a fairly simple manner. I have the base include file. Then a "mfgames.com.php" which include()'s the main one and overrides the database, prefix, and host. There is a "mfgames.com.9090.php" that catches the port 9090 stuff and includes the mfgames one, then overrides only the host. I pretty mudh do that for every single one of the sites, with each one pointing to the correct database.

It isn't the cleanest way, but frankly I've had a lot of trouble getting everything to work. Too many different ideas. :)

An idea is to create a "update-drupal" script which takes a module name and a database and runs the approprirate script (kind of like the automatic modules do). That was the "custom" people need to run that script. To be nice, you could ask a question for debconf for the "default" database to run all scripts on, then run those for the modules.

_paquin_’s picture

_paquin_ commented

I have translated those debconf questions for italian people, validating it using emacs and its funny PO mode :)

Where can I put the "it.po" file generated?

ciao

a.d.

_paquin_’s picture

_paquin_ commented

po.it file

ciao

a.d.