Julien Valroff's weblog and personal homepage
Posts tagged Debian
Adobe Reader available again
Feb 17th
Following to a request made on the debian-user-french list, I have worked again on my French packages of Adobe Reader. The updated packages are back again on my repository, in the non-free section.
It was actually argued that free PDF readers do not reach Adobe Reader’s quality, and lack of features for advanced users. I won’t use the packages myself, but as I have received Adobe’s official permission to distribute their product, I thought it was worth sharing to others.
Note that these packages are still based on Christian Marillat’s work.
Debian bugs activity
Jan 27th
I have recently been quite active reporting and forwarding bugs, as the following reports show:
Good to see the majority Debian Developers answer really quick, even for minor bugs.
Upgraded to kernel 2.6.19.2
Jan 13th
Following to the release of Grsecurity 2.1.10 I have upgraded my servers to kernel 2.6.19.2, which made me aware that the ov511-source package failed to build with this kernel (see bug report), as well as ltmodem-source, for which I uploaded an updated package.
Installed Etch on my UML virtual servers
Dec 25th
I have decided to upgrade my two UML instances to Etch, the next Debian stable release. The process ran smoothly, except a problem with the transition from ssh to openssh-server and openssh-client. I will test again and report the problem if it fails again.
The [other] man who did not know he had an amd64
Nov 8th
Thanks to Julien Danjou, I am now aware I have to re-install my main desktop/development machine to take advantage of the 64 bits support of my Pentium 4 processor.
I think I will take the time to study what are the advantages and the drawbacks (OpenOffice.org in a chroot etc.), but I think I am too curious to wait too long!
This will surely have some consequences on my unofficial packages, as the unstable arch-dependent packages will have to be rebuilt so that I can at least use them.
Update: given the low advantages of the 64 bits architectures, and the numerous drawbacks it would bring for my desktop machine, I have decided to stick with i386 – at least for the moment
Removed acroread-fr from my repository
Oct 29th
I removed acroread-fr and co. from my repository, as Christian Marillat now provides acroread-l10n-XX packages (including the acroread-l10n-fr which my packages were supposed to provide).
If you want to use Christian’s packages, please update your /etc/apt/sources.list file according to instructions on debian-multimedia.org, purge acroread-fr and all related packages, and install acroread-l10n-fr and acroread-spell-fr packages (acroread and plugins will be pulled as dependencies).
To change the default language of the GUI, read the README.Debian file in package doc directory.
Update: To be able to have the GUI translated, you have to modify /usr/lib/Adobe/Acrobat7.0/bin/acroread as follows:
[diff]
— /usr/lib/Adobe/Acrobat7.0/bin/acroread.distrib 2006-06-16 19:46:28.000000000 +0200
+++ /usr/lib/Adobe/Acrobat7.0/bin/acroread 2006-11-12 10:46:32.000000000 +0100
@@ -707,9 +707,6 @@
ACRO_RES_DIR=$ACRO_INSTALL_DIR/../Resource
export ACRO_RES_DIR
-ACRO_LANG=$ST_LANG
-export ACRO_LANG
-
# Adobe Reader/Acrobat uses gconftool-2 to check whether accessibility support is enabled. Please refer to the Readme file to work around this.
check_file_in_path gconftool-2
if [ $? -eq 0 ]
[/diff]
Better use a local diversion so as to avoid that an upgraded package destroys these changes.
Then, run ACRO_LANG=FRA acroread and choose French as the GUI language.
mplayer now in Debian… what about tovid?
Oct 28th
Thanks to Joey Hess for posting his DWN items, I have learned that mplayer had been accepted into the archive, which means I might now think about finding a sponsor for my unofficial tovid packages. Well, there is still a lot of work I would like to do before upoading this set of packages, but it is a first step!
Am I supposed… ?
Oct 24th
… to be aware of the bugs reported on Ubuntu’s launchpad against the packages I (co-)maintain for Debian?
Especially for the packages in the “universe” component?
For those who wonder:
The universe component is a snapshot of the free, open source, and Linux world. In universe you can find almost every piece of open source software, and software available under a variety of less open licences, all built automatically from a variety of public sources.
Source: http://www.ubuntu.com/ubuntu/components
Of course, Debian repositories are included in these public sources. This means that, without you are aware of it, you can maintain packages for Ubuntu.
This is my case for at least the nautilus-open-terminal package: a bug was reported on Sunday on the BTS, and I have found that this bug was already reported in launchpad since February!
And as the packages in universe are not officially supported by Ubuntu, nobody will fix the bug. And as I wasn’t aware of this, I couldn’t do anything on my side.
Now, the upstream’s mailbox is over quota and I am not able to fix this bug myself.
Am I supposed to look on launchpad for bugs reported against my packages?
Maybe one could work on a system that would show these bugs on the PTS, as it is already the case for patches. I will try and make this propsal to Raphaël after Alioth’s servers have been migrated.
Recent Comments