Debian Bug report logs - #514305
smarty: Please sync the install path with Ubuntu

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Francois Marier <francois@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: smarty: Please sync the install path with Ubuntu

Date: Fri, 06 Feb 2009 17:27:20 +1300

Package: smarty
Version: 2.6.22-1
Severity: important

Currently, the Debian package for smarty installs it in:

  /usr/share/php/smarty/libs/

whereas the Ubuntu package install its files here:

  /usr/share/php/smarty/

This causes smarty-enabled applications in Debian to fail on Ubuntu because the
include path is different. Two such packages are Moodle and Mahara. They require Ubuntu
customisations to work around the different paths.

I'm not sure what the right path is, but there was a discussion in the Ubuntu tracker
which referred to the upstream install guide:

 https://bugs.launchpad.net/ubuntu/+source/smarty/+bug/118793

Francois

-- System Information:
Debian Release: 5.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.27.13-grsec (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages smarty depends on:
ii  php5-cli                  5.2.6.dfsg.1-3 command-line interpreter for the p

smarty recommends no packages.

smarty suggests no packages.

-- no debconf information

Message #10 received at 514305@bugs.debian.org (full text, mbox, reply):

From: Raphael Hertzog <hertzog@debian.org>

To: Francois Marier <francois@debian.org>, 514305@bugs.debian.org

Subject: Re: Bug#514305: smarty: Please sync the install path with Ubuntu

Date: Tue, 23 Jun 2009 19:20:22 +0200

On Fri, 06 Feb 2009, Francois Marier wrote:
> This causes smarty-enabled applications in Debian to fail on Ubuntu because the
> include path is different. Two such packages are Moodle and Mahara. They require Ubuntu
> customisations to work around the different paths.
> 
> I'm not sure what the right path is, but there was a discussion in the Ubuntu tracker
> which referred to the upstream install guide:
> 
>  https://bugs.launchpad.net/ubuntu/+source/smarty/+bug/118793

It was a poor choice of Ubuntu to diverge here... anyway I agree that at
this point it's best if Debian updates his package to use the new path.
It should however add some transition symlink /usr/share/php/smarty/libs
-> /usr/share/php/smarty to avoid breaking instantly. But this won't work
automatically if plugins are installed in libs/plugins/. You will have to
add a preinst snippet that moves files around...

However when you do that, please inform me as smarty-gettext and
smarty-validate will have to be updated at the same time. You should add
Breaks: smarty-gettext (<= 1.0b1-3), smarty-validate (<= 2.9-1)
to ensure that those package are updated at the same time
(the minimal version might need to be updated when you do it)

Cheers,
-- 
Raphaël Hertzog

Contribuez à Debian et gagnez un cahier de l'admin Debian Lenny :
http://www.ouaza.com/wp/2009/03/02/contribuer-a-debian-gagner-un-livre/

Message #15 received at 514305@bugs.debian.org (full text, mbox, reply):

From: Thijs Kinkhorst <thijs@debian.org>

To: 514305@bugs.debian.org, Raphael Hertzog <hertzog@debian.org>

Cc: Francois Marier <francois@debian.org>

Subject: Re: Bug#514305: smarty: Please sync the install path with Ubuntu

Date: Thu, 12 Aug 2010 22:39:48 +0200

[Message part 1 (text/plain, inline)]

Hi Raphaël,

> It was a poor choice of Ubuntu to diverge here... anyway I agree that at
> this point it's best if Debian updates his package to use the new path.
> It should however add some transition symlink /usr/share/php/smarty/libs
> -> /usr/share/php/smarty to avoid breaking instantly.

I agree that given that Ubuntu has made this rather poor decision, we're only 
left with this inelegant way forward to unify the packages again. Obviously we 
cannot have this changed for Squeeze anymore, so it'll have to be postponed 
for a bit.

> But this won't work automatically if plugins are installed in libs/plugins/.
> You will have to add a preinst snippet that moves files around...

/usr/share is the domain of the packaging system. So if there's anything in 
libs/plugins, that is installed by another package and we should rather not be 
moving that around in preinst. Those packages should be updated instead, no? 
You indicate this already for smarty-gettext and smarty-validate.


Cheers,
Thijs

[signature.asc (application/pgp-signature, inline)]

Message #20 received at 514305@bugs.debian.org (full text, mbox, reply):

From: Raphael Hertzog <hertzog@debian.org>

To: Thijs Kinkhorst <thijs@debian.org>

Cc: 514305@bugs.debian.org, Francois Marier <francois@debian.org>

Subject: Re: Bug#514305: smarty: Please sync the install path with Ubuntu

Date: Sun, 15 Aug 2010 11:00:34 +0200

On Thu, 12 Aug 2010, Thijs Kinkhorst wrote:
> I agree that given that Ubuntu has made this rather poor decision, we're only 
> left with this inelegant way forward to unify the packages again. Obviously we 
> cannot have this changed for Squeeze anymore, so it'll have to be postponed 
> for a bit.

Are you taking smarty over?

> > But this won't work automatically if plugins are installed in libs/plugins/.
> > You will have to add a preinst snippet that moves files around...
> 
> /usr/share is the domain of the packaging system. So if there's anything in 
> libs/plugins, that is installed by another package and we should rather not be 
> moving that around in preinst. Those packages should be updated instead, no? 
> You indicate this already for smarty-gettext and smarty-validate.

Yes, they must be updated instead. Smarty will have to add
conflicts:/breaks: statements to ensure they are upgraded.

But there's the possibility that some plugins have been manually installed
by the user.

With breaks, you would have to setup the symlink in postinst because
that's the only point where you can be sure that the other packages have
been upgraded.

With conflicts, you know in preinst already that other packages have been
removed or upgraded already and you can deal with the symlink there in
that case.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer ◈ [Flattr=20693]

Follow my Debian News ▶ http://RaphaelHertzog.com (English)
                      ▶ http://RaphaelHertzog.fr (Français)

Message #25 received at 514305@bugs.debian.org (full text, mbox, reply):

From: Thijs Kinkhorst <thijs@debian.org>

To: Raphael Hertzog <hertzog@debian.org>

Cc: 514305@bugs.debian.org, Francois Marier <francois@debian.org>

Subject: Re: Bug#514305: smarty: Please sync the install path with Ubuntu

Date: Sun, 15 Aug 2010 13:17:04 +0200

On snein 15 Augustus 2010, Raphael Hertzog wrote:
> On Thu, 12 Aug 2010, Thijs Kinkhorst wrote:
> > I agree that given that Ubuntu has made this rather poor decision, we're
> > only left with this inelegant way forward to unify the packages again.
> > Obviously we cannot have this changed for Squeeze anymore, so it'll have
> > to be postponed for a bit.
> 
> Are you taking smarty over?

Yes, as per http://bugs.debian.org/592797

> > > But this won't work automatically if plugins are installed in
> > > libs/plugins/. You will have to add a preinst snippet that moves files
> > > around...
> > 
> > /usr/share is the domain of the packaging system. So if there's anything
> > in libs/plugins, that is installed by another package and we should
> > rather not be moving that around in preinst. Those packages should be
> > updated instead, no? You indicate this already for smarty-gettext and
> > smarty-validate.
> 
> Yes, they must be updated instead. Smarty will have to add
> conflicts:/breaks: statements to ensure they are upgraded.
> 
> But there's the possibility that some plugins have been manually installed
> by the user.
> 
> With breaks, you would have to setup the symlink in postinst because
> that's the only point where you can be sure that the other packages have
> been upgraded.
> 
> With conflicts, you know in preinst already that other packages have been
> removed or upgraded already and you can deal with the symlink there in
> that case.

Yes. This would mean that if there are locally created Debian packages of 
those plugins then we would also be fiddling with their content. But perhaps 
there's no "perfect" solution and moving things over is the best of both 
options.


Cheers,
Thijs

Message #30 received at 514305-done@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 290176-done@bugs.debian.org,338422-done@bugs.debian.org,461006-done@bugs.debian.org,511219-done@bugs.debian.org,514305-done@bugs.debian.org,647857-done@bugs.debian.org,

Cc: smarty@packages.debian.org, smarty@packages.qa.debian.org

Subject: Bug#592797: Removed package(s) from unstable

Date: Sun, 04 Mar 2012 11:08:13 +0000

Version: 2.6.26-0.2+rm

Dear submitter,

as the package smarty has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see http://bugs.debian.org/592797

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@debian.org.

Debian distribution maintenance software
pp.
Joerg Jaspert (the ftpmaster behind the curtain)

Send a report that this bug log contains spam.