Re: Bug#858973: wheezy-pu: package ejabberd/2.1.10-4+deb7u2

[Guido Günther <agx@sigxcpu.org>]

Hi Philipp,
On Wed, Mar 29, 2017 at 09:13:43PM +0200, Philipp Huebner wrote:
> Hi Guido,
> 
> > The changes look sane to me. Could you upload to wheezy-security? If you
> > don't want to prepare the DLA yourself I can do that but then it would
> > be awesome if this cold happen on Friday earliest since I'm currently
> > bit tight on time.
> > 
> > I can test the package beforehand if you have built binaries for amd64
> > already.
> 
> you can grab the package from here:
> https://apt.debalance.de/pool/main/e/ejabberd/

I've tested the package (ejabberdctl, connecting different clients) and
it looks good. During the upgrade I get this list of errors though:

    dpkg -i ejabberd_2.1.10-4+deb7u2_amd64.deb 
    (Reading database ... 29454 files and directories currently installed.)
    Preparing to replace ejabberd 2.1.10-4+deb7u1 (using ejabberd_2.1.10-4+deb7u2_amd64.deb) ...
    {error_logger,{{2017,3,31},{14,9,43}},std_error,"File operation error: eacces. Target: .. Function: read_file_info. Process: code_server."}
    {error_logger,{{2017,3,31},{14,9,43}},std_error,"File operation error: eacces. Target: ./standard_error.beam. Function: get_file. Process: code_server."}
    {error_logger,{{2017,3,31},{14,9,43}},std_error,"File operation error: eacces. Target: ./supervisor_bridge.beam. Function: get_file. Process: code_server."}
    {error_logger,{{2017,3,31},{14,9,43}},std_error,"File operation error: eacces. Target: ./user_sup.beam. Function: get_file. Process: code_server."}
    {error_logger,{{2017,3,31},{14,9,43}},std_error,"File operation error: eacces. Target: ./user.beam. Function: get_file. Process: code_server."}
    {error_logger,{{2017,3,31},{14,9,43}},std_error,"File operation error: eacces. Target: ./kernel_config.beam. Function: get_file. Process: code_server."}
    {error_logger,{{2017,3,31},{14,9,43}},std_error,"File operation error: eacces. Target: ./queue.beam. Function: get_file. Process: code_server."}

    =ERROR REPORT==== 31-Mar-2017::16:09:43 ===
    File operation error: eacces. Target: .. Function: read_file_info. Process: code_server.

    =ERROR REPORT==== 31-Mar-2017::16:09:43 ===
    File operation error: eacces. Target: ./standard_error.beam. Function: get_file. Process: code_server.

    …[lots more eaccess]…

    =ERROR REPORT==== 31-Mar-2017::14:09:43 ===
    File operation error: eacces. Target: ./string.beam. Function: get_file. Process: code_server.

    =ERROR REPORT==== 31-Mar-2017::14:09:43 ===
    File operation error: eacces. Target: ./dist_util.beam. Function: get_file. Process: code_server.

    The ejabberd database has been backed up to /var/backups/ejabberd-2017-03-31T14:09:43.WvoEep/ejabberd-database.

    Stopping jabber server: ejabberd.
    Unpacking replacement ejabberd ...
    Setting up ejabberd (2.1.10-4+deb7u2) ...
    Starting jabber server: ejabberd.
    Waiting for ejabberd to register admin user.
    Admin user "admin@sigxcpu.org" is already registered. Password IS NOT changed.
    Processing triggers for man-db ...

which is probably harmless but a bit confusing.

Note that this:

   ejabberd (2.1.10-4+deb7u2) oldstable; urgency=high

should be changed to:

   ejabberd (2.1.10-4+deb7u2) wheezy-security; urgency=high

Feel free to upload after your tests, I'll issue the DLA then, the
package is accepted automatically.

Thanks for caring about ejabberd in wheezy.
pCheers,
 -- Guido


> I haven't had time yet to test it, I intend to do that on the weekend.
> 
> Uploading it afterwards is no problem, as for the DLA I'd be happy if
> you would do it.
> Will the security-upload automatically enter the archive or is some
> manual intervention necessary?
> 
> Regards,
> -- 
>  .''`.   Philipp Huebner <debalance@debian.org>
> : :'  :  pgp fp: 6719 25C5 B8CD E74A 5225  3DF9 E5CA 8C49 25E4 205F
> `. `'`
>   `-
>