Hello.
"¡Lo prometido es deuda!" as we say in Uruguay (what is promised is a debt).
Tested your packages and now I can see correctly all the scanners,
local and networked ones!
So everything looks good to push those to Debian Stretch.
Thanks a lot for doing all this!
Greetings from another Allegro
Hi,
The package is in this state since Aug 17, I think we can afford to wait
a few more days for testing.
So yes, please do test on Tuesday.
Cheers!
Sylvain
On 03/10/2020 00:41, Ivan Baldo wrote:
> Hello.
> The soonest I could try to check, is this Tuesday 6th 19:00 -0300, sorry.
> Let me know
Hello.
The soonest I could try to check, is this Tuesday 6th 19:00 -0300, sorry.
Let me know if that's useful or too late.
Thanks!
El vie., 2 de oct. de 2020 a la(s) 10:22, Sylvain Beucler
(b...@beuc.net) escribió:
>
> Hi,
>
> On 02/10/2020 13:51, Ivan Baldo wrote:
> > El vie., 2 de oct. de 2020
Hi,
On 02/10/2020 13:51, Ivan Baldo wrote:
> El vie., 2 de oct. de 2020 a la(s) 06:48, Sylvain Beucler
> (b...@beuc.net) escribió:
>>
>> Hi,
>>
>>> El jue., 1 de oct. de 2020 a la(s) 19:32, Sylvain Beucler
>>> (b...@beuc.net) escribió:
This could be due to a bug when building the 'all' and
Great, thanks a lot!!!
El vie., 2 de oct. de 2020 a la(s) 06:48, Sylvain Beucler
(b...@beuc.net) escribió:
>
> Hi,
>
> > El jue., 1 de oct. de 2020 a la(s) 19:32, Sylvain Beucler
> > (b...@beuc.net) escribió:
> >> This could be due to a bug when building the 'all' and 'amd64' packages
> >>
Hi,
> El jue., 1 de oct. de 2020 a la(s) 19:32, Sylvain Beucler
> (b...@beuc.net) escribió:
>> This could be due to a bug when building the 'all' and 'amd64' packages
>> separately.
I can reproduce the 2 debdiff-s with 'debuild -A' and 'debuild -B'
respectively.
I'm currently backporting fixes
Hello.
So I did check too this way:
docker pull debian:stretch
docker run --rm -it debian:stretch
Inside that container:
sed 's/deb http/deb-src http/' /etc/apt/sources.list
>/etc/apt/sources.list.d/sources.list
cd /tmp
apt-get update && apt-get install devscripts
apt-get build-dep
Hi,
Thanks for report this issue.
Something must have gone wrong when rebuilding the packages at Debian,
because the packages I had built didn't have these differences. I just
ran a local rebuild and I still have valid packages, with all the files.
It's night-time here so I won't look in depth
Package: libsane-common
Version: 1.0.25-4.1+deb9u1
Severity: important
Scanners look differently now, some not even appear on the network
(through saned), etc.
debdiff libsane-common_1.0.25-4.1_all.deb
libsane-common_1.0.25-4.1+deb9u1_all.deb shows:
Files in first .deb but not in second
9 matches
Mail list logo
