to openssl 1.0 (Closes: #850882).
+
+ -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Tue, 31 Jan 2017 21:05:57 +0100
+
lastpass-cli (1.0.0-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru lastpass-cli-1.0.0/debian/control lastpass-cli-1.0.0/debian/control
--- la
On 2017-02-01 22:18:07 [+0100], Sebastian Andrzej Siewior wrote:
> Currently I am rebuilding testing with the same set of package against
> libssl-dev provided by libssl1.0-dev. After that I retry the failed
> packages above where I am not sure why they failed (mostly I suspect the
&
On 2017-02-02 22:26:35 [+0200], Adrian Bunk wrote:
> The kannel package does not claim to support parallel building.
>
> If you attempt parallel building on that,
> then any build failures are your fault.
what is wrong with passing -j16 to sbuild? Other packages, that do not
support parallel
On 2017-02-02 16:54:08 [+], Holger Levsen wrote:
>
> I'm surprised to see that many packages failing to build in parallel, as we're
> building everything in parallel and I dont remember such failures recentl.y
So retried them with -j1 [0] and:
- passed:
boxbackup 0.11.1~r2837-4
erlang
On 2017-01-28 19:37:09 [+0100], Julien Cristau wrote:
> At this point, it seems clear to me that we're getting nowhere fast.
> With the freeze looming in a few days, this is growing to be a very big
> risk for the stretch release.
I rebuild testing, with the subset of:
grep-dctrl -FDepends
-maintainer upload.
+ * Get it built with openssl 1.1. (Closes: #828376).
+
+ -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Sun, 29 Jan 2017 21:51:50 +0100
+
lcmaps-plugins-voms (1.6.2-2) unstable; urgency=low
[ Mischa Salle ]
diff -Nru lcmaps-plugins-voms-1.6.2/debian/p
Hi,
stumbled upon qterm [0] which is going to be autoremoved due to missing
build on mips64el. It waits for kwallet-kf5 which can't be build for
days. First it was due to a binutils bug (I think). Now it can't install
dbus, from [1]:
|Setting up pinentry-curses (1.0.0-1) ...
|Setting up
On 2016-12-31 17:35:47 [+0100], Julien Cristau wrote:
> Is this really something we need to be shipping? If yes, I'd personally
> really like this to get an explicit exemption from normal policy by the
> security team, so please talk to them (debian-security@ldo is not it).
I have been made
tl;dr: Has anyone a problem if sslscan embeds openssl 1.0.2 in its
source?
sslscan [0] as packaged in Debian currently relies on external libssl as
provided by the openssl package. The openssl package disables support
compression, SSLv2 and SSLv3 which is good but it also means that
sslscan can
On 2016-12-20 21:56:22 [+], Adam D. Barratt wrote:
> Please go ahead.
done, thx.
> Regards,
>
> Adam
Sebastian
.
+
+ -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Fri, 16 Dec 2016
21:38:26 +0100
+
libclamunrar (0.99-0+deb8u1) stable; urgency=medium
[ Scott Kitterman ]
@@ -10,7 +17,7 @@
* switch from libclamunrar6 to libclamunrar7
* copy clamav's watch file
* add pkg-
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: binnmu
Severity: normal
nmu libcrypt-openssl-bignum-perl_0.07-1 . ANY . unstable . -m "rebuild against
openssl 1.1.0"
This NMU should pickup libssl1.1 instead 1.0.2 which is it currently
linked against. Once this
On 2016-12-01 00:52:59 [+0200], Adrian Bunk wrote:
> Wouldn't "depends on libssl1.0.2 and does not build-depend on libssl1.0-dev"
> give a reasonably small superset of all packages that need a binNMU?
Do you mean something like
is_affected = .depends ~ /libssl1\.0\.2/ & ! .build-depends ~
On 2016-11-05 21:59:27 [+0100], Sebastian Andrzej Siewior wrote:
> I've been playing with ben. I tried a few things and this is the best I
> was able to achieve [0]:
>
> title = "openssl 1.0";
> is_affected = .build-depends ~ /libssl1.0-dev/;
> is_good = .depen
On 2016-11-18 13:27:10 [+], Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
>
> > block 827061 by 844366
> Bug #827061 [release.debian.org] transition: openssl
> Bug #844366 [libssl1.1] libssl1.1: 1.1.0c broke Python
How excatly is #844366 blocking the
On 2016-11-16 12:26:55 [+], Ian Jackson wrote:
> If we decide to wind back the transition and the openssl maintainers
> continue not to be available (within the short timeframes required),
> we have a lot of people who could competently prepare an NMU.
NMU openssl back to 1.0.2 or its rdeps
On 2016-11-15 12:39:25 [+0100], Apollon Oikonomopoulos wrote:
> Hi Ian,
Hi,
> On 11:16 Tue 15 Nov , Ian Jackson wrote:
> > 812166 is nothing to do with openssl AFAICT.
> > I don't think Xen is involved with the openssl transition.
> >
> > Did you get the wrong bug ?
>
> I'm terribly sorry
On 2016-10-26 10:55:19 [+0200], Emilio Pozuelo Monfort wrote:
> So let's do this. Let's try to get it finished and only ship openssl 1.1. We
> still have three months until the full freeze, and depending on how many
> packages (and which ones, for risk management etc) are left to be fixed after
>
On 2016-10-31 11:16:38 [-0400], Sam Hartman wrote:
> At least one of the clusters of packages I'm involved in--shibboleth and
> moonshot will require some real upstream porting effort.
> That's under way in a time scale that will work for buster, but is very
> unlikely to meet the stretch freeze
On 2016-10-26 21:31:26 [+0200], Kurt Roeckx wrote:
> > Is this situation
> > supported or should we expect things to break? This can easily happen if an
> > app
> > links against a library libA which uses openssl 1.0, and against libB which
> > uses
> > openssl 1.1.
>
> When linking you
On 2016-09-18 21:33:43 [+0200], Kurt Roeckx wrote:
>
> So OpenSSL 1.1.0 was released about 3 weeks ago. Since then we've
now a month and a few days now.
> been working on the key packages, to get them to build with
> OpenSSL 1.1.0. You can see that status of that at:
>
On 2016-06-24 10:35:43 [+0200], Yann Soubeyrand wrote:
> Le jeudi 23 juin 2016 à 23:13 +0200, jcris...@debian.org a écrit :
> > That doesn't sound suitable for a stable update, sorry.
> OK, I understand.
Closing with no change then.
Sebastian
On 2016-06-28 11:56:47 [+0200], Julien Cristau wrote:
> Please go ahead.
thanks, done.
> Cheers,
> Julien
Sebastian
406).
+
+ -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Mon, 06 Jun 2016 22:06:52 +0200
+
clamav (0.99.2+dfsg-0+deb8u1) stable; urgency=medium
* Import new Upstream.
diff --git a/debian/patches/ingore-AllowSupplementaryGroups-option.patch b/debian/patches/ingore-AllowSupplement
On 2016-05-23 19:38:27 [+0100], Adam D. Barratt wrote:
> Please go ahead.
Thanks, done.
> Regards,
>
> Adam
Sebastian
On 2016-05-14 17:46:19 [+0100], Adam D. Barratt wrote:
> > There were no
> > complains regarding the transition, upstream has no plans for 0.99.2
> > soon so I think the time might be good now :)
>
> In the meantime, 0.99.2 has ended up in unstable and testing; I guess
> that's the version we now
644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+openssl (1.0.1t-1+deb8u2) jessie; urgency=medium
+
+ * add Update-S-MIME-certificates.patch to update expired certificates to
+pass the test suite
+
+ -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Wed, 11 May 2016
On 2016-04-13 21:36:49 [+0100], Adam D. Barratt wrote:
> Assuming that we went ahead with upstream updates to Jessie (and future
> supported stable distributions), I'm presuming that the preferred
> workflow would be similar to other packages for which we ship upstream
> stable trees - via the
On 2016-03-01 20:19:13 [+], Adam D. Barratt wrote:
> Yep, that should be everything now. I'll look at getting an SUA sorted
> in the next few days.
Thank you.
> Regards,
>
> Adam
Sebastian
On 2016-02-24 19:59:03 [+], Adam D. Barratt wrote:
> > > with the FTBFS of c-icap-modules (which doesn't appear to be clamav's
> > > fault, but is blocking this being complete).
c-icap-modules built everywhere. So we are done with clamav on old-stable and
stable unless I missed something.
On 2016-02-26 21:51:40 [+0100], Mathieu Parent wrote:
> Why does it FTBFS on wheezy now?
According to #768684 it already was the case which went into oldstable.
> Please go ahead. Thanks
Thanks.
>
> Cheers,
Sebastian
On 2016-02-26 21:09:22 [+], Adam D. Barratt wrote:
> Please go ahead.
Thanks, done.
> Regards,
>
> Adam
>
Sebastian
d3 Mon Sep 17 00:00:00 2001
+From: Sebastian Andrzej Siewior <sebast...@breakpoint.cc>
+Date: Fri, 26 Feb 2016 15:21:11 +0100
+Subject: [PATCH] Rename CONF to C_ICAP_CONF
+
+Based on a patch by Mathieu Parent <math.par...@gmail.com> done by sed:
+
+ sed -i 's@\<CONF\>@C_ICAP
On 2016-02-24 19:42:57 [+], Adam D. Barratt wrote:
> On Tue, 2016-02-23 at 09:45 +0100, Sebastian Andrzej Siewior wrote:
> > On 2016-02-22 22:42:47 [+], Adam D. Barratt wrote:
> > > Please go ahead.
> >
> > Thanks, done.
>
> clamav itself has now b
On 2016-02-22 22:42:47 [+], Adam D. Barratt wrote:
> Please go ahead.
Thanks, done.
> Regards,
>
> Adam
Sebastian
+deb7u2) oldstable; urgency=medium
+
+ * Add libclamav-yara-avoid-unaliged-access-to-64bit-variab.patch to get the
+testsuite passed on sparc. It also seem avoid invalid loads on ARMv5 cpus.
+
+ -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Mon, 22 Feb 2016
23:05:03 +0100
+
On 2016-02-22 21:43:45 [+], Adam D. Barratt wrote:
> Please go ahead.
Thanks, done.
> Regards,
>
> Adam
Sebastian
libclamav-yara-avoid-unaliged-access-to-64bit-variab.patch to get the
+testsuite passed on sparc. It also seem avoid invalid loads on ARMv5 cpus.
+
+ -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Mon, 22 Feb 2016
21:12:51 +0100
+
clamav (0.99+dfsg-0+deb8u1) stable; urgency=
On 2016-02-20 11:43:41 [+], Julien Cristau wrote:
> > diff --git a/libclamav/yara_exec.c b/libclamav/yara_exec.c
> > index dbd7ae8..eb06fbb 100644
> > --- a/libclamav/yara_exec.c
> > +++ b/libclamav/yara_exec.c
> [...]
> > @@ -184,7 +194,7 @@ int yr_execute_code(
> > #endif
> >
> >
On 2016-02-19 05:56:27 [+], Adam D. Barratt wrote:
> The sparc build has now failed three times, across two different builds.
And why did mips pass? Isn't mips the difficult one?
The patch attached is a simplified version of what I had on smetana
during testing. I would give it another try
On 2016-02-03 23:05:27 [+], Adam D. Barratt wrote:
> > Okay. Uploaded the current package which hits first s-p-u. I hope to be
> > able to test the remaining two packages this weekend.
>
> Thanks. It should end up in NEW, as libclamav7 doesn't exist in stable.
> Once it does, we can ask the
On 2016-02-10 20:08:51 [+], Adam D. Barratt wrote:
> On Sun, 2016-02-07 at 20:54 +, Adam D. Barratt wrote:
> > On Sat, 2016-02-06 at 16:08 +, Adam D. Barratt wrote:
> > > On Sat, 2016-02-06 at 15:42 +, Adam D. Barratt wrote:
> > > > It's now built everywhere so I'll look at the
On 2016-02-06 16:00:22 [+], Adam D. Barratt wrote:
> The changelog says:
>
> + * don't links against libpcre if available.
>
> s/links/link/
argh. I uploaded it as-is but fixed in the source repo so the next upload
should have this corrected.
> Please go ahead.
Thanks, uploaded.
>
>
On 2016-02-02 20:31:23 [+], Adam D. Barratt wrote:
> Okay, thanks. Let's get this rolling; apologies for the delay in getting
> back to you.
No problem. It is better that way than just rubber-stamp it.
> > havp seems to work (installed old, dpkg -i new package, loaded a page
> > and the
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: jessie
Severity: normal
The upgrade of clamav in Jessie (#807969) requires a source upload of
libclamunrar building libclamunrar7 instead of libclamunrar6.
Please find attached a complete diff against
On 2015-12-28 16:57:27 [+], Adam D. Barratt wrote:
> I have bad memories of the last time we had a libclamav SONAME change in
> stable - more precisely, in volatile. When you say you've rebuilt the
> packages, I assume that this means that no source changes were needed? Have
correct, no
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: binnmu
Severity: normal
The package has been built against old libclamav6.
nmu c-icap-modules_1:0.4.2-1 . amd64 . unstable . -m "rebuild against
libclamav7"
Sebastian
On 2015-12-04 00:59:02 [+0100], Emilio Pozuelo Monfort wrote:
> > The auto tracker is okay, all reverse dependencies are:
> > - libclamunrar
> > - c-icap-modules
> > - dansguardian
> > - havp
> > - python-clamav
> >
> > In the last c-icap-modules upload (which is part of testing and
> > unstable)
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: transition
Severity: normal
The version 0.99 of clamav has SONAME bump. Currently we have 0.99-rc2
in experimental which built everywhere (mips is Needs-Build at the time
of writing). 0.99 and -rc2 are almost
On 2015-02-04 19:48:27 [+], Adam D. Barratt wrote:
Please go ahead.
Done, thanks.
Regards,
Adam
Sebastian
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
On 2015-01-14 19:45:18 [+], Adam D. Barratt wrote:
Please go ahead; thanks.
thanks, uploaded. Its been my first upload so if something went wrong
please let me know (the upload has been accepted however).
Regards,
Adam
Sebastian
--
To UNSUBSCRIBE, email to
-arithmetic-on-32bit to avoid overflow
+in pointer arithmetic causing a segfault on 32bit (Closes: #774767).
+
+ -- Sebastian Andrzej Siewior sebast...@breakpoint.cc Wed, 07 Jan 2015
21:56:21 +0100
+
clamav (0.98.5+dfsg-0+deb7u2) stable; urgency=medium
* Add libmspack-qtmd-fix-frame_end
2015-01-03 22:44:52.0 +0100
@@ -1,3 +1,12 @@
+clamav (0.98.5+dfsg-0+deb7u2) stable; urgency=medium
+
+ [ Sebastian Andrzej Siewior ]
+ * Add libmspack-qtmd-fix-frame_end-overflow to avoid endless-loop on
+special crafted quantum compressed cab files. Patch suggested by Andreas
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package xchat. Its been 16 days in unstable after an NMU
upload by Sven Hoexter. Sven fixed #766005 (severity important) which
allows users to connect via SSL to IRC servers which have SSLv3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
Please binnum libuuid-perl in unstable as it currently depends on
perlapi-5.14.2 but we have perlapi-5.18.1 provided by perl-base 5.18.1-2. In
my recent dist-upgraded I ended up without a
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
Please nmu libtext-iconv-per in unstable as it currently depends on
perlapi-5.12.2 but we have perlapi-5.18.1 provided by perl-base 5.18.1-2. In
my recent dist-upgraded I lost
On Tue, Aug 27, 2013 at 08:05:53PM +0200, gregor herrmann wrote:
Hi Sebastian,
Hi Gregor,
thanks for your bug reports.
You are right that libuuid-perl and libtext-iconv-per need binNMUs;
just like 525 other packages, as mentioned on
http://release.debian.org/transitions/html/perl5.18.html
* Niels Thykier | 2010-08-21 16:13:34 [+0200]:
Personally I am okay with doing it and it is the intention of the Java
Team to make openjdk the default on all architectures. The question is
if we should do it now or after Squeeze (CC'ed the release team) for
their comments.
The problem with the
* Matthew Johnson | 2010-08-22 15:01:23 [+0100]:
On Sun Aug 22 14:41, Sebastian Andrzej Siewior wrote:
The problem with the default-jdk is that most architectures have openjdk
as default. Some packages however don't build with default-jdk !=
openjdk. One of them on top of my head is jffi
* Niels Thykier | 2010-08-22 17:02:22 [+0200]:
I have committed the patch to the SVN. I intend to upload this after
java-common 0.39 migrates to testing (waiting for the mips binaries).
Thanks for that. You don't have to upload the package just due to this
change. I uploaded a changed version
201 - 260 of 260 matches
Mail list logo
