Your message dated Thu, 26 Jan 2017 00:33:46 +0000
with message-id <[email protected]>
and subject line Bug#852187: fixed in diaspora 0.6.0.1+debian-1
has caused the Debian Bug report #852187,
regarding diaspora: current installation report
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.)


-- 
852187: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852187
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: diaspora
Version: 0.6.0.0+debian-8
Severity: normal

Hi Pirate,

Here's a report on issues I've found trying to install the current
(0.6.0.0+debian-8) version of diaspora.

(1) The diaspora preinst reads on line 15:

    if su diaspora -s /bin/sh -c "psql  diaspora_production -c ''"

    Unfortunately, this may fail as the diaspora user is not created
    until the diaspora-common *postinst*, and the diaspora preinst may
    be run before this.  Instead, you probably want to change the user
    to be "su postgres" as the postgres user (if it exists at this
    point) will certainly be able to run this command.  (If postgres
    has not been installed, then dbexist will remain undefined.)

    I'd also add a "-" to the su command, and lose the output:
    
    su - postgres -c "psql diaspora_production -c ''" >&/dev/null

    Actually, if the diaspora package assumes that the backing
    database will be postgresql, (which may or may not be the case -
    I'm not sure), then it needs to Depends or Pre-Depends on an
    appropriate postgresql package - diaspora-common only depends on a
    choice of mysql or postgres.  And the diaspora-common package
    gives the option of psql or mysql, so this could be a problem.

(2) This is a serious bug, and renders diaspora not fit for testing;
    I'm not setting the severity right now to give the current
    unstable version a chance to enter testing, as the bug in the
    current testing version is even worse.

    The diaspora process writes to /usr, which is expressly forbidden
    by policy: /usr might be on a read-only filesystem.  See the FHS,
    very beginning of chapter 4:

        Chapter 4. The /usr Hierarchy

        Purpose

        /usr is the second major section of the filesystem. /usr is
        shareable, read-only data. That means that /usr should be
        shareable between various FHS-compliant hosts and must not be
        written to. Any information that is host-specific or varies
        with time is stored elsewhere.

    To be more precise, it stores temporary information in
    /usr/share/diaspora/tmp, rather than /var/run/diaspora.
    I *think* this can be solved by putting in a symlink
    /usr/share/diaspora/tmp -> /var/run/diaspora, but
    /var/run/diaspora would have to be created and owned by
    diaspora:nogroup before starting diaspora.  I haven't determined
    when this directory is and is not used, though - there's something
    weird going on on my machine regarding this, and I'm not convinced
    that this solution works.

    This also appears in /etc/nginx/sites-available/diaspora, where it
    listens on /usr/share/diaspora/tmp/diaspora.sock - this should be
    in /var/run.

(3) Following on from point (2), uploads I believe will be written to
    public/uploads (that's what happens on my production machine,
    running 0.6.2.0, and is implied by the nginx configuration).  So
    /usr/share/diaspora/public/uploads should be a symlink to some
    directory within /var/lib/diaspora, say
    /var/lib/diaspora/public/uploads, owned by diaspora:nogroup and
    with write permissions for diaspora.

    Again, this may need fixing in the nginx configuration, too,
    though if nginx follows the symlink it will be OK as is.

(4) /etc/diaspora/diaspora.yml still specifies: rails_environment:
    'development' rather than 'production'; this is also the case in
    /etc/diaspora/defaults.yml (which may not need modification; I
    presume that this is the defaults, and is overridden by
    diaspora.yml).

(5) I mentioned in an earlier email if I recall correctly that
    /etc/diaspora/diaspora.yml does not have url: set to the debconf
    setting; I'm unclear as to whether this is a problem as a reverse
    proxy is being used.

Best wishes,

   Julian

--- End Message ---
--- Begin Message ---
Source: diaspora
Source-Version: 0.6.0.1+debian-1

We believe that the bug you reported is fixed in the latest version of
diaspora, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pirate Praveen <[email protected]> (supplier of updated diaspora package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 17 Jan 2017 13:38:29 +0530
Source: diaspora
Binary: diaspora
Architecture: source
Version: 0.6.0.1+debian-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 
<[email protected]>
Changed-By: Pirate Praveen <[email protected]>
Description:
 diaspora   - distributed social networking service
Closes: 852187
Changes:
 diaspora (0.6.0.1+debian-1) unstable; urgency=medium
 .
   * New hotfix release
   * Remove database existence/previous version check in preinst
   * Create /run/gitlab and use it as tmp (for sockets and pids)
     (Closes: #852187)
   * Always generate Gemfile.lock
   * Regenerate Gemfile.lock when ruby packages are updated
Checksums-Sha1:
 2019abc0866e0e6d4d0c41537717d056bb6a3101 2070 diaspora_0.6.0.1+debian-1.dsc
 94306000c7015a92f00c4eb363d4b7119574e734 2668110 
diaspora_0.6.0.1+debian.orig.tar.gz
 e14d68672ab6b2515ae753a64f1fffd8fb90183b 23896 
diaspora_0.6.0.1+debian-1.debian.tar.xz
Checksums-Sha256:
 4566b8c5dd058b7325fc71ea79dfefe18fad11e9ddaab3a5347ca4e1b350240a 2070 
diaspora_0.6.0.1+debian-1.dsc
 c21eaef7c470555db3b72aa3cfc8875fa67311eb8f8073869b6e946c2cc37361 2668110 
diaspora_0.6.0.1+debian.orig.tar.gz
 b50e289b4012ea005219288b5338f347c82701f3084a7620b9a8b4c67e056f19 23896 
diaspora_0.6.0.1+debian-1.debian.tar.xz
Files:
 e036528e53ba8143137ae6d5c6768253 2070 contrib/web optional 
diaspora_0.6.0.1+debian-1.dsc
 31ed943261807f5af1ca05a686d688e0 2668110 contrib/web optional 
diaspora_0.6.0.1+debian.orig.tar.gz
 2888f0a4ad74c8217dd499949d3de068 23896 contrib/web optional 
diaspora_0.6.0.1+debian-1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAliJQYcACgkQzh+cZ0US
wirILRAAifIjMekhLyvNveU1WQhcyp6vPPdEHi6hg3FYMQ76XUEy7KtYzpQPvER1
EWPKn+bnZqZHrofIIhD+1jLcS+M4JKtP0rWsqsIWkdSrsYF2zIdfz9Sc5BEmU8vo
/qlGLe5Q0+V0h46K0N86E8f2+2wUkK/beXlRZhgHKV2HruZy0qqohiMxASA4P1e7
nWkyGQcVqIeYP5nk5ZXWYHtCwi2bUtmfErvJyeOuWuSxefYsXfsGYUxHuuB7/X4v
8tQt3G8AdAvayPI30cxcF1sBFwAnavGKYVaW3dBADDUXJhZm1JhP05wH7IS2VZ5i
a4Ko5nswYbgvm0g39KuE81LH7615Tl9jnslz05ETj7yHiZ8ctYmfbqjXfpaLCNeA
XYrkX8iUfvuJEaZBIS84K0b7wVk1zbNdeaUi4GoD8JTp6kCr0yzqgHSqhsuBbKkl
nhNZ1b2lhW+0HMghLn4vJyOdURQkywRK26Z0XmSCPy72zRLM/rFDElKYeZj5//Ju
/5HxHZIi+kT1QdtON6MZRlSFA3d/SeM0ut+nPiOEYiExH96sA5tyLDAoMC/PVCPh
HkpbLdT3YpabD4PeVb8rCQgUL6/IJXPPQgo1W+tjgLTloafp4lnlROnPxqSFWLUZ
eHGLZ9BhS/zFQYMMDvsyfdkAUhYYSIPNteKUUL7BrpRDCGPkbJo=
=g4+r
-----END PGP SIGNATURE-----

--- End Message ---
_______________________________________________
Pkg-ruby-extras-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

Reply via email to