Re: [sane-devel] Fix PPA build

[m. allan noah]

this sounds like a reasonable plan to me, though I wonder what effect
it will have on the currently installed git-based packages. They are
already 1.0.26+git, and they will remain so after this release
(though the  part will be of a different format).

allan

On Thu, May 11, 2017 at 7:36 AM, Olaf Meeuwissen
 wrote:
> Hi all,
>
> This is something that I've been wondering about for a while and with
> the release coming up I thought I'd vent my thoughts/preferences on the
> version numbering of sane-backends (and sane-frontends if we should ever
> get around to releasing a new version of that).
>
> Rolf Bensch writes:
>
>> Hi James,
>>
>> Am 08.05.2017 um 22:22 schrieb James Duvall:
>>> Rolf,
>>>
>>> Thanks for getting your ppa back up and running.  However, I am not able
>>> to install the libsane package using apt, even when I try to force the
>>> version.  I believe that your new version numbering with ~ is causing
>>> the problem.
>>>
>>> ver=1.0.26~ppa20170508-yakkety0; sudo apt-get install libsane=$ver
>>> libsane-common=$versane-utils=$ver
>
> On Debian-based distributions:
>
>   1.0.26~this < 1.0.26 < 1.0.26+that
>
> I don't recall the details for RPM-based distributions re ~ (note that
> Fedora[1] says it should not be used), but the + works the same, so:
>
>   1.0.26 < 1.0.26+that
>
>   [1] https://fedoraproject.org/wiki/Packaging:Versioning
>
> The problem with the way we currently do the versioning of sane-backends
> is that we bump the version to what we *think* will be the next version.
> This would work for Debian-based distribution packages if they use a ~
> suffix to our version.  For RPM-based distributions I don't know what
> works.  It also causes confusing bug reports and mails to the list where
> people talk about using an upcoming release.
>
> To fix that, can we agree to a version number for HEAD on master that
> refers to the last *released* version?  Something like this
>
>   1.0.26+git
>
> for anything *after* the 1.0.26 release.  This should work for all folks
> rolling binary packages and indicates very clearly that it's 1.0.26 plus
> a bunch of edits.
>
> Actually, we may also want to look into using the output of
>
>   git describe
>
> When I run this on my current checkout of master, I get
>
>   RELEASE_1_0_25-552-ge6711c3
>
> This is --g, so this
> should work fine as long as people are using master.  The number of
> commits since the tag will sort later commits in the right order.
>
> # We haven't used branches much so far, so this would be a reasonably
> # safe assumption.  Anyway, if you're using any other branch, I would
> # assume you know what you're doing ;-)
>
> If we also switch tags to use the version number as is, that would
> become
>
>   1.0.25-552-ge6711c3
>
> # Debian-based distributions may need to replace the - with something
> # else.  Using `sed 's/-/+/g'` or something similar should work.
>
> Summarizing, let's use
>
>   +git
>
> from the 1.0.26 release onwards and look into using the output from `git
> describe` to get an even better idea of what people are really running
> when compiling from git.
>
> How's that sound?
>
> Hope this helps,
> --
> Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
>  GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
>  Support Free Softwarehttps://my.fsf.org/donate
>  Join the Free Software Foundation  https://my.fsf.org/join



-- 
"well, I stand up next to a mountain- and I chop it down with the edge
of my hand"

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] Fix PPA build

[Olaf Meeuwissen]

Hi all,

This is something that I've been wondering about for a while and with
the release coming up I thought I'd vent my thoughts/preferences on the
version numbering of sane-backends (and sane-frontends if we should ever
get around to releasing a new version of that).

Rolf Bensch writes:

> Hi James,
>
> Am 08.05.2017 um 22:22 schrieb James Duvall:
>> Rolf,
>>
>> Thanks for getting your ppa back up and running.  However, I am not able
>> to install the libsane package using apt, even when I try to force the
>> version.  I believe that your new version numbering with ~ is causing
>> the problem.
>>
>> ver=1.0.26~ppa20170508-yakkety0; sudo apt-get install libsane=$ver
>> libsane-common=$versane-utils=$ver

On Debian-based distributions:

  1.0.26~this < 1.0.26 < 1.0.26+that

I don't recall the details for RPM-based distributions re ~ (note that
Fedora[1] says it should not be used), but the + works the same, so:

  1.0.26 < 1.0.26+that

  [1] https://fedoraproject.org/wiki/Packaging:Versioning

The problem with the way we currently do the versioning of sane-backends
is that we bump the version to what we *think* will be the next version.
This would work for Debian-based distribution packages if they use a ~
suffix to our version.  For RPM-based distributions I don't know what
works.  It also causes confusing bug reports and mails to the list where
people talk about using an upcoming release.

To fix that, can we agree to a version number for HEAD on master that
refers to the last *released* version?  Something like this

  1.0.26+git

for anything *after* the 1.0.26 release.  This should work for all folks
rolling binary packages and indicates very clearly that it's 1.0.26 plus
a bunch of edits.

Actually, we may also want to look into using the output of

  git describe

When I run this on my current checkout of master, I get

  RELEASE_1_0_25-552-ge6711c3

This is --g, so this
should work fine as long as people are using master.  The number of
commits since the tag will sort later commits in the right order.

# We haven't used branches much so far, so this would be a reasonably
# safe assumption.  Anyway, if you're using any other branch, I would
# assume you know what you're doing ;-)

If we also switch tags to use the version number as is, that would
become

  1.0.25-552-ge6711c3

# Debian-based distributions may need to replace the - with something
# else.  Using `sed 's/-/+/g'` or something similar should work.

Summarizing, let's use

  +git

from the 1.0.26 release onwards and look into using the output from `git
describe` to get an even better idea of what people are really running
when compiling from git.

How's that sound?

Hope this helps,
--
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Softwarehttps://my.fsf.org/donate
 Join the Free Software Foundation  https://my.fsf.org/join

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] Fix PPA build (was Re: sane-backends release 1.0.26 schedule)

[Olaf Meeuwissen]

Hi Rolf,

Rolf Bensch writes:

> @Olaf: Thanks for your patch. It's working with the ppa.

Good!

> Please have a look at the attached patches. Maybe there are additional
> fixes for SANE (fix_avahi_error_paths.patch) or there are needful
> additional options for configure possible or just keep them inside the ppa?

I will take a look at the patches, maybe this weekend, but unless they
fix bugs on the sane-backends side, they'll have to wait until after the
release.

If other binary package maintainers are listening, I welcome patches in
the Alioth bug tracker (even though I rather dislike that bug tracker
itself ;-).  Feel free to add any that haven't been submitted yet,
assign them to me and, please!, prefix a [PATCH] to the summary line so
I can quickly find them.

> Many thanks for your help.

You're welcome.

Hope this helps,
--
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Softwarehttps://my.fsf.org/donate
 Join the Free Software Foundation  https://my.fsf.org/join

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] Fix PPA build

[Rolf Bensch]

Hi James,

I just found the problem in the build control file. Please test the
recent version from my ppa again.

Many thanks for your help.

Cheers,
Rolf

Am 09.05.2017 um 22:06 schrieb James Duvall:
> Rolf,
> 
> OK, now it makes more sense to me.  I saw that the last released version
> was 1.0.25, but I didn't fully comprehend that your ppa is a pre-release
> for 1.0.26.  When 1.0.26 is released, of course you would want these
> builds to compare earlier than the released version.
> 
> One thing I still don't fully comprehend.  libsane=1.0.26~preXXX depends
> on libsane-common=1.0.26~preXXX, but libsane=1.0.26~preXXX also breaks
> libsane-common<<1.0.26
> 
> This seems like a conflict.  Isn't this saying that libsane breaks the
> same version that it depends on?
> 
> Sorry if I am being frustrating or dense on this topic.  As I
> understand, apt and dpkg won't allow 2 different versions of the same
> package to be simultaneously installed.  If the pre-release libsane
> requires a specific version of libsane-common, doesn't that
> automatically imply that it breaks/conflicts with any other version? 
> libsane=1.0.26~preXXX will also break 1.0.27 or 1.1 or anything else
> that is released in the future, right?
> 
> Using your instructions, I still can't install using apt, dpkg.  I
> installed synaptic, but I get the same error and refusal to install (). 
> I am running yakkety, so maybe there is some difference from trusty.
> 
> However, this is not a big problem for me.  I am able to automatically
> build from the sane-backends package on your ppa, so I can test my
> MG5420 with the latest fixes.  I'll send another email once I have
> verified all functions and the scanbd script you sent me.
> 
> Many thanks,
> James
> On Tuesday, May 9, 2017 11:36 AM, Rolf Bensch  wrote:
> 
> 
> Hi James,
> 
> Am 08.05.2017 um 22:22 schrieb James Duvall:
>> Rolf,
>>
>> Thanks for getting your ppa back up and running.  However, I am not able
>> to install the libsane package using apt, even when I try to force the
>> version.  I believe that your new version numbering with ~ is causing
>> the problem.
>>
>> ver=1.0.26~ppa20170508-yakkety0; sudo apt-get install libsane=$ver
>> libsane-common=$versane-utils=$ver
>>
> 
> I used synaptic for Trusty and it's working.
> 
> You can use an alternative more complex procedure to get the updates
> from my ppa:
> 
> (1) search for installed SANE packages:
> $ dpkg -l *sane*
> 
> (2) purge all SANE packages with the version '1.0.26[-+]ppa{date}
> *without* removing dependent packages:
> $ sudo dpkg --force-all -P libsane libsane-common sane-utils [other
> installed packages]
> 
> (3) reinstall SANE:
> $ apt-get -f install
> 
> (4) reinstall all other removed packages, e.g.:
> $ sudo apt-get install libsane-dev
> 
>> Apt complains that
>>
>> The following packages have unmet dependencies:
>>  libsane : Breaks: libsane-common (< 1.0.26)
>>Breaks: libsane-common:i386 (< 1.0.26)
>> E: Unable to correct problems, you have held broken packages.
>>
>> I think the issue is that version 1.0.26~ppa20170508-yakkety0 compares
>> less than 1.0.26 due to special rules for handling ~ in version
>> numbers.  The following shows this:
>>
>> dpkg --compare-versions 1.0.26~ppa20170508-yakkety0 lt 1.0.26 && echo true
>> true
>>
> 
> This is correct. SANE 1.0.26 isn't released yet.
> Inspired from your comment I renamed the version in my ppa to
> '1.0.26~pre{date}'. This makes it more transparent that this is a
> pre-release.
> 
>> I created a local repository and re-packaged as version
>> 1.0.26+ppa20170508-yakkety0 and was able to install with no problems, so
>> maybe change the ~ for + or some other separator?  I am not experienced
>> with debian package management, so please disregard if I am missing
>> something.
>>
> 
> Then you'll get the next update after we started the development of SANE
> version 1.0.27, then AKA version 1.0.27~pre{date} from my ppa repository
> 
> Many thanks for your report.
> 
> Hope this helps.
> 
> Cheers,
> 
> Rolf
> 
> 

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] Fix PPA build

[Rolf Bensch]

Hi James,

Am 08.05.2017 um 22:22 schrieb James Duvall:
> Rolf,
> 
> Thanks for getting your ppa back up and running.  However, I am not able
> to install the libsane package using apt, even when I try to force the
> version.  I believe that your new version numbering with ~ is causing
> the problem.
> 
> ver=1.0.26~ppa20170508-yakkety0; sudo apt-get install libsane=$ver
> libsane-common=$versane-utils=$ver
> 

I used synaptic for Trusty and it's working.

You can use an alternative more complex procedure to get the updates
from my ppa:

(1) search for installed SANE packages:
$ dpkg -l *sane*

(2) purge all SANE packages with the version '1.0.26[-+]ppa{date}
*without* removing dependent packages:
$ sudo dpkg --force-all -P libsane libsane-common sane-utils [other
installed packages]

(3) reinstall SANE:
$ apt-get -f install

(4) reinstall all other removed packages, e.g.:
$ sudo apt-get install libsane-dev

> Apt complains that
> 
> The following packages have unmet dependencies:
>  libsane : Breaks: libsane-common (< 1.0.26)
>Breaks: libsane-common:i386 (< 1.0.26)
> E: Unable to correct problems, you have held broken packages.
> 
> I think the issue is that version 1.0.26~ppa20170508-yakkety0 compares
> less than 1.0.26 due to special rules for handling ~ in version
> numbers.  The following shows this:
> 
> dpkg --compare-versions 1.0.26~ppa20170508-yakkety0 lt 1.0.26 && echo true
> true
> 

This is correct. SANE 1.0.26 isn't released yet.
Inspired from your comment I renamed the version in my ppa to
'1.0.26~pre{date}'. This makes it more transparent that this is a
pre-release.

> I created a local repository and re-packaged as version
> 1.0.26+ppa20170508-yakkety0 and was able to install with no problems, so
> maybe change the ~ for + or some other separator?  I am not experienced
> with debian package management, so please disregard if I am missing
> something.
> 

Then you'll get the next update after we started the development of SANE
version 1.0.27, then AKA version 1.0.27~pre{date} from my ppa repository

Many thanks for your report.

Hope this helps.

Cheers,
Rolf

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] Fix PPA build (was Re: sane-backends release 1.0.26 schedule)

[Rolf Bensch]

Hello All,

My Ubuntu ppa (ppa:rolfbensch/sane-git
) is
working again. It distributes pre-built packages for all supported
Ubuntu distributions (amd64, i386 and armhf architectures).

I changed the package names to fit the packages version convention a
little bit more. I hope that this helps to change the package names
provided from Ubuntu.

If you are already using my ppa, you must use the "Force Version"
function of your package manager once to get the updates.

Please report if you may have any problems.

Hope this helps.

Cheers,
Rolf


Am 07.05.2017 um 13:15 schrieb Rolf Bensch:
> Hi,
>
> @Olaf: Thanks for your patch. It's working with the ppa.
>
> Please have a look at the attached patches. Maybe there are additional
> fixes for SANE (fix_avahi_error_paths.patch) or there are needful
> additional options for configure possible or just keep them inside the ppa?
>
> Many thanks for your help.
>
> Cheers,
> Rolf
>
>
> Am 06.05.2017 um 14:00 schrieb Olaf Meeuwissen:
>> Hi Rolf,
>>
>> Rolf Bensch writes:
>>
>>> Hi Olaf,
>>>
>>> I tried to build a recent version for zesty some weeks ago with my test
>>> ppa: https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-test/+packages .
>> Thanks for the link!  Now I can see the build failures.
>> BTW, it looks like the build does not apply the debian/patches/.  Don't
>> know if that's intentional or not.
>>
>>> I'll try to investigate this issue next week. If you can provide a patch
>>> before, I can merge it into the build system very quickly.
>> See the attached.
>>  - debian/rules: modified a few configure flags and added one for the
>>API spec (BTW, 6ffeb909 fixed a brain fart for that option)
>>  - debian/control: add transfig as a build dependency for the spec (BTW,
>>we do PDF now too but that requires pdflatex and gs as well)
>>  - debian/patches/multiarch_dll_searc_path.patch: adjust to upstream
>>changes
>>
>> Note that this only aims to fix the xenial build but the other builds
>> should be mostly identical if not exactly.
>>
>> I've checked
>>
>>   debian/rules binary
>>   dpkg-buildpackage -b
>>
>> and both complete without a hitch, on xenial (in a Docker container).
>>
>> Hope this helps,
>> --
>> Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
>>  GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
>>  Support Free Softwarehttps://my.fsf.org/donate
>>  Join the Free Software Foundation  https://my.fsf.org/join
>>

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] Fix PPA build (was Re: sane-backends release 1.0.26 schedule)

[Rolf Bensch]

Hi,

@Olaf: Thanks for your patch. It's working with the ppa.

Please have a look at the attached patches. Maybe there are additional
fixes for SANE (fix_avahi_error_paths.patch) or there are needful
additional options for configure possible or just keep them inside the ppa?

Many thanks for your help.

Cheers,
Rolf


Am 06.05.2017 um 14:00 schrieb Olaf Meeuwissen:
> Hi Rolf,
> 
> Rolf Bensch writes:
> 
>> Hi Olaf,
>>
>> I tried to build a recent version for zesty some weeks ago with my test
>> ppa: https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-test/+packages .
> 
> Thanks for the link!  Now I can see the build failures.
> BTW, it looks like the build does not apply the debian/patches/.  Don't
> know if that's intentional or not.
> 
>> I'll try to investigate this issue next week. If you can provide a patch
>> before, I can merge it into the build system very quickly.
> 
> See the attached.
>  - debian/rules: modified a few configure flags and added one for the
>API spec (BTW, 6ffeb909 fixed a brain fart for that option)
>  - debian/control: add transfig as a build dependency for the spec (BTW,
>we do PDF now too but that requires pdflatex and gs as well)
>  - debian/patches/multiarch_dll_searc_path.patch: adjust to upstream
>changes
> 
> Note that this only aims to fix the xenial build but the other builds
> should be mostly identical if not exactly.
> 
> I've checked
> 
>   debian/rules binary
>   dpkg-buildpackage -b
> 
> and both complete without a hitch, on xenial (in a Docker container).
> 
> Hope this helps,
> --
> Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
>  GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
>  Support Free Softwarehttps://my.fsf.org/donate
>  Join the Free Software Foundation  https://my.fsf.org/join
> 



patches.tar.gz
Description: application/gzip
-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org