rebuild of custom package does not have the correct version

What steps have you performed?
Have you changed the version number before re-building the packages?

Hi,

In essence I have done this...

apt-get source exim4
cd exim4-4.82
fakeroot debian/rules unpack-configs
export my_pkg_name=custom
cp EDITME.exim4-heavy EDITME.exim4-$my_pkg_name
fakeroot debian/rules pack-configs
/usr/lib/pbuilder/pbuilder-satisfydepends
debuild -us -uc

I have not changed the version number before rebuilding as I didn't see
that anywhere in the docs I found.

Cheers

Andy

On 03/16/2016 12:17 PM, Manfred Hampl wrote:
> Your question #288714 on exim4 in Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/exim4/+question/288714
>
> Status: Open => Needs information
>
> Manfred Hampl requested more information:
> What steps have you performed?
> Have you changed the version number before re-building the packages?
>

What is the output of the commands

uname -a
lsb_release -crid
apt-cache policy exim4

# uname -a
Linux smtpcleaner2 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
# lsb_release -crid
Distributor ID: Ubuntu
Description: Ubuntu 14.04.2 LTS
Release: 14.04
Codename: trusty
# apt-cache policy exim4
exim4:
   Installed: (none)
   Candidate: 4.82-3ubuntu2.1
   Version table:
      4.82-3ubuntu2.1 0
         500 http://gb.archive.ubuntu.com/ubuntu/ trusty-updates/main
amd64 Packages
         500 http://security.ubuntu.com/ubuntu/ trusty-security/main
amd64 Packages
      4.82-3ubuntu2 0
         500 http://gb.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

On 03/16/2016 01:07 PM, Manfred Hampl wrote:
> uname -a
> lsb_release -crid
> apt-cache policy exim4

ok, and what is the output of

grep trusty- /etc/apt/sources.list /etc/apt/sources.list.d/*.list

Hi,

Here you go:

/etc/apt/sources.list:deb http://gb.archive.ubuntu.com/ubuntu/
trusty-updates main restricted
/etc/apt/sources.list:deb-src http://gb.archive.ubuntu.com/ubuntu/
trusty-updates main restricted
/etc/apt/sources.list:deb http://gb.archive.ubuntu.com/ubuntu/
trusty-updates universe
/etc/apt/sources.list:deb-src http://gb.archive.ubuntu.com/ubuntu/
trusty-updates universe
/etc/apt/sources.list:deb http://gb.archive.ubuntu.com/ubuntu/
trusty-updates multiverse
/etc/apt/sources.list:deb-src http://gb.archive.ubuntu.com/ubuntu/
trusty-updates multiverse
/etc/apt/sources.list:deb http://gb.archive.ubuntu.com/ubuntu/
trusty-backports main restricted universe multiverse
/etc/apt/sources.list:deb-src http://gb.archive.ubuntu.com/ubuntu/
trusty-backports main restricted universe multiverse
/etc/apt/sources.list:deb http://security.ubuntu.com/ubuntu
trusty-security main restricted
/etc/apt/sources.list:deb-src http://security.ubuntu.com/ubuntu
trusty-security main restricted
/etc/apt/sources.list:deb http://security.ubuntu.com/ubuntu
trusty-security universe
/etc/apt/sources.list:deb-src http://security.ubuntu.com/ubuntu
trusty-security universe
/etc/apt/sources.list:deb http://security.ubuntu.com/ubuntu
trusty-security multiverse
/etc/apt/sources.list:deb-src http://security.ubuntu.com/ubuntu
trusty-security multiverse

On 03/16/2016 06:37 PM, Manfred Hampl wrote:
> grep trusty-/etc/apt/sources.list /etc/apt/sources.list.d/*.list

The sources.list configuration looks correct.

What surprises me a bit is the Ubuntu release number shown with the lsb_release command: 14.04.2 LTS
On a fully updated system it should (currently) show 14.04.4

Is your system fully updated (sudo apt-get update && sudo apt-get dist-upgrade)?

If you try specifying a release number for the download, something like
apt-get source exim4=4.82-3ubuntu2.1
or
apt-get -t=trusty-updates source exim4
what do you get then?

Hi

The system automatically applies security updates, hence it is still on
14.04.2 - its a very busy production MTA.

I have noticed that the command pulled down
exim4_4.82-3ubuntu2.1.debian.tar.gz as part of the command run originally

Andy

On 03/17/2016 10:22 AM, Manfred Hampl wrote:
> Your question #288714 on exim4 in Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/exim4/+question/288714
>
> Status: Open => Needs information
>
> Manfred Hampl requested more information:
> The sources.list configuration looks correct.
>
> What surprises me a bit is the Ubuntu release number shown with the lsb_release command: 14.04.2 LTS
> On a fully updated system it should (currently) show 14.04.4
>
> Is your system fully updated (sudo apt-get update && sudo apt-get dist-
> upgrade)?
>
> If you try specifying a release number for the download, something like
> apt-get source exim4=4.82-3ubuntu2.1
> or
> apt-get -t=trusty-updates source exim4
> what do you get then?
>

# apt-get source exim4=4.82-3ubuntu2.1
Reading package lists... Done
Building dependency tree
Reading state information... Done
NOTICE: 'exim4' packaging is maintained in the 'Git' version control
system at:
git://anonscm.debian.org/pkg-exim4/exim4.git
Skipping already downloaded file 'exim4_4.82-3ubuntu2.1.dsc'
Skipping already downloaded file 'exim4_4.82.orig.tar.bz2'
Skipping already downloaded file 'exim4_4.82-3ubuntu2.1.debian.tar.gz'
Need to get 0 B of source archives.
Skipping unpack of already unpacked source in exim4-4.82

On 03/17/2016 10:22 AM, Manfred Hampl wrote:
> apt-get source exim4=4.82-3ubuntu2.1

It seems to have used the 4.82-3ubuntu2.1 package already before. Weird that the version number is different then.

Hence my question...

Also the unattended security updates update the other exim packages,
config etc, which is a bit of a pain as for historical reason we use the
mail user not Debian-exim and the updates changed all the permissions on
the log directory and also /var/spool/exim4 directories, is there any
way to change that behaviour?

In the interim, where would I change the version number to rebuild the
deb with the correct versions?

Andy

On 03/17/2016 02:22 PM, Manfred Hampl wrote:
> Your question #288714 on exim4 in Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/exim4/+question/288714
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> It seems to have used the 4.82-3ubuntu2.1 package already before. Weird
> that the version number is different then.
>

Do all packages that you create have the version number 4.82-3ubuntu2 (instead of 4.82-3ubuntu2.1) in their file name?
What is the 'Version' value in the control file inside the packages?

Yes they all have the 4.82ubuntu2 version number.

Where do I find the control file?

On 03/18/2016 09:27 AM, Manfred Hampl wrote:
> Your question #288714 on exim4 in Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/exim4/+question/288714
>
> Status: Open => Needs information
>
> Manfred Hampl requested more information:
> Do all packages that you create have the version number 4.82-3ubuntu2 (instead of 4.82-3ubuntu2.1) in their file name?
> What is the 'Version' value in the control file inside the packages?
>

dpkg -f exim4-daemon-custom_4.82-3ubuntu2_amd64.deb

should extract and show the info.

OK,

I have just moved all the old files and started again.

All has worked OK.

Does that mean I will need to wipe out all the old build stuff to do a
rebuild on a minor update?

This should not be necessary, but maybe it is better to always start with a clean (=empty) environment.

Have you any thoughts on how to prevent the automatic security updates
for exim overwriting the custom built ones? This is largely due to
EXIM_USER and EXIM_GROUP having been changed to mail and mail.

When the automatic update came out it changed all the folder permission
in /var/log/exim4 and in /var/spool/exim4 so exim essentially failed
after logrotate.

On 03/18/2016 11:43 AM, Manfred Hampl wrote:
> Your question #288714 on exim4 in Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/exim4/+question/288714
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> This should not be necessary, but maybe it is better to always start
> with a clean (=empty) environment.
>

You can set the status of your current private version to "hold" in the package management system. Then the update-manager will not install any other version.
https://help.ubuntu.com/community/PinningHowto#Introduction_to_Holding_Packages
(Of course it is then your own responsibility to check for bug fixes etc.)

Thanks for all your help on this Manfred.

Is there a mailing list I can subscribe to about the ubuntu exim
packages? It is the only one I roll a custom build for.

Again many thanks

Andy

On 03/18/2016 02:32 PM, Manfred Hampl wrote:
> Your question #288714 on exim4 in Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/exim4/+question/288714
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> You can set the status of your current private version to "hold" in the package management system. Then the update-manager will not install any other version.
> https://help.ubuntu.com/community/PinningHowto#Introduction_to_Holding_Packages
> (Of course it is then your own responsibility to check for bug fixes etc.)
>

http://www.exim.org/ for general information about exim.
I do not think that there is something especially for Ubuntu.