Your message dated Tue, 28 May 2019 20:41:13 +0200
with message-id
and subject line Re: unblock: heimdal/7.5.0+dfsg-3
has caused the Debian Bug report #929665,
regarding unblock: heimdal/7.5.0+dfsg-3
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package heimdal
* Security fixes for CVE-2018-16860 and CVE-2019-12098.
* FTBFS bug fix.
Note I excluded the changes to the certificates from the following patch,
because a
On Mon, Nov 13, 2017 at 10:07:11 +0100, Ondřej Surý wrote:
> Hi Johan,
>
> you are the first one to notice :).
>
> There was a time shortly before stable freeze when Heimdal team
> requested removal of heimdal from Debian (#837724), but instead this
> activity woke up
Hi Johan,
you are the first one to notice :).
There was a time shortly before stable freeze when Heimdal team
requested removal of heimdal from Debian (#837724), but instead this
activity woke up the upstream, so they released new upstream version
(#849706). Somewhere in between something went
Your message dated Thu, 27 Apr 2017 07:25:00 +
with message-id <9af1f9bc-fab3-2394-23ca-b6180f75b...@thykier.net>
and subject line Re: Bug#861276: unblock: heimdal/7.1.0+dfsg-13
has caused the Debian Bug report #861276,
regarding unblock: heimdal/7.1.0+dfsg-13
to be marked as done.
This
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package heimdal
Re-add base64_decode and base64_encode back into libroken, solving
backward compatability issues. See #848694.
Tested by compiling base64-test.c (supplied
Your message dated Fri, 14 Apr 2017 13:11:10 +
with message-id
and subject line unblock heimdal
has caused the Debian Bug report #860288,
regarding unblock: heimdal/7.1.0+dfsg-12
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package heimdal
Security update from upstream. For CVE-2017-6594. Seee
https://www.h5l.org/releases.html?show=7.3.0
diff -Nru heimdal-7.1.0+dfsg/debian/changelog
heimdal
Your message dated Sun, 09 Apr 2017 19:26:00 +
with message-id
and subject line Re: Bug#859863: unblock: heimdal/7.1.0+dfsg-11
has caused the Debian Bug report #859863,
regarding unblock: heimdal/7.1.0+dfsg-11
to be marked as done.
This means that you claim that the problem has been dealt
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package heimdal
Depreciated servers and clients were removed from both heimdal-clients
and heimdal-servers. However the meta information was not updated to
reflect these
Your message dated Wed, 18 Jan 2017 00:01:29 +0100
with message-id <9619cab4-357a-38d2-841b-e73d905af...@debian.org>
and subject line Re: Bug#837728: Heimdal has done a new release
has caused the Debian Bug report #837728,
regarding RM: heimdal/1.7~git20150920+dfsg-4
to be marked as done.
Heimdal has done a new release, which has been packaged and will
hopefully make it into stretch, rendering this removal request
unnecessary.
The only thing that's preventing its migration to testing at the
moment is a regression in binutils on MIPS
(https://bugs.debian.org/cgi-bin/bugrepor
Just a quick update to this bug: some awesome people upstream (thanks!) have
taken on the effort of getting another Heimdal release out. A RC has been
pushed out, and hopefully a final 7 release will follow before the end of the
year.
Unfortunately, with the release schedule for Debian being
Processing control commands:
> block 837728 with -1
Bug #837728 [release.debian.org] RM: heimdal/1.7~git20150920+dfsg-4
837728 was blocked by: 837628 806264 837716 836885 837724
837728 was not blocking any bugs.
Added blocking bug(s) of 837728: 845146
--
837728: http://bugs.debian.org/cgi-
still open.
>
> I can drop libpam-heimdal from the libpam-krb5 source package (and will
> get that in the next upload, hopefully pretty soon). For
> libheimdal-kadm5-perl, there isn't really anything one can do with the
> package, since it's Heimdal-specific. Should I op
Jelmer Vernooij writes:
> On Sun, Oct 02, 2016 at 06:28:05PM +0200, Emilio Pozuelo Monfort wrote:
>> Please make those bugs block this one so we can track progress.
> I've added them as blockers. There are four still open.
I can drop libpam-heimdal from the libpam-krb5 source
Hi Emilio,
On Sun, Oct 02, 2016 at 06:28:05PM +0200, Emilio Pozuelo Monfort wrote:
> On 14/09/16 01:23, Jelmer Vernooij wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: rm
> >
> > P
On 14/09/16 01:23, Jelmer Vernooij wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: rm
>
> Please remove the heimdal source package from testing. As maintainers,
> we believe that Heimdal is not in a good enough
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
Please remove the heimdal source package from testing. As maintainers,
we believe that Heimdal is not in a good enough state to be included in
a stable release.
There is still some activity in
On Sun, Nov 28, 2010 at 08:24:20 +0100, Alexander Wirt wrote:
> Brian May schrieb am Sunday, den 28. November 2010:
>
> Hi,
>
> > Would you be willing to accept a new version of amavisd-new into
> > testing that does nothing but update the Maintainer header field?
> >
> > -Maintainer: Brian May
gssapi-mit | grep Conflicts
> > Conflicts: libsasl2-modules-gssapi-heimdal
> > l...@gismo:~$
> > =
> >
> > So, if you want to debug the GSSAPI Heimdal library you need
> > cyrus-sasl2-heimdal-dbg and, I guess, at the same time
> > libsasl2-modules-gss
sasl2-2 -plibsasl2-modules
> >> > -plibsasl2-modules-ldap -plibsasl2-modules-otp -plibsasl2-modules-sql
> >> > -plibsasl2-modules-gssapi-mit -plibsasl2-dev
> >> > -Nlibsasl2-modules-gssapi-heimdal --dbg-package=cyrus-sasl2-dbg
> >> > dh_strip -s -pl
ibsasl2-modules-sql
>> > -plibsasl2-modules-gssapi-mit -plibsasl2-dev
>> > -Nlibsasl2-modules-gssapi-heimdal --dbg-package=cyrus-sasl2-dbg
>> > dh_strip -s -plibsasl2-modules-gssapi-heimdal -Nsasl2-bin -Nlibsasl2-2
>> > -Nlibsasl2-modules -Nlibsasl2-modules-lda
on are -dbg packages that are
> > created by dh_strip, excerpted from debian/rules below:
> >
> > dh_strip -s -psasl2-bin -plibsasl2-2 -plibsasl2-modules
> > -plibsasl2-modules-ldap -plibsasl2-modules-otp -plibsasl2-modules-sql
> > -plibsasl2-modules-gssapi-mit -plibsasl2-dev
> dh_strip -s -psasl2-bin -plibsasl2-2 -plibsasl2-modules
> -plibsasl2-modules-ldap -plibsasl2-modules-otp -plibsasl2-modules-sql
> -plibsasl2-modules-gssapi-mit -plibsasl2-dev
> -Nlibsasl2-modules-gssapi-heimdal --dbg-package=cyrus-sasl2-dbg
> dh_strip -s -plibsasl2-modules-g
Brian May schrieb am Sunday, den 28. November 2010:
Hi,
> Would you be willing to accept a new version of amavisd-new into
> testing that does nothing but update the Maintainer header field?
>
> -Maintainer: Brian May
> +Maintainer: Brian May
>
> I committed a change on the 17/March/2010 into
Hello Debian Release Team,
Would you be willing to accept a new version of amavisd-new into
testing that does nothing but update the Maintainer header field?
-Maintainer: Brian May
+Maintainer: Brian May
I committed a change on the 17/March/2010 into the Debian source code
revision system, but
Russ Allbery wrote:
> I've finished the work to take advantage of the new -multidev packages and
> build libpam-heimdal from the same source package as libpam-krb5, which
> I'd like to get done for squeeze. However, while getting ready to upload,
> I see that Heimdal curren
I've finished the work to take advantage of the new -multidev packages and
build libpam-heimdal from the same source package as libpam-krb5, which
I'd like to get done for squeeze. However, while getting ready to upload,
I see that Heimdal currently hasn't migrated to testi
Ok if I go ahead and upload this?
=== cut ===
heimdal (1.2.e1.dfsg.1-1) unstable; urgency=low
* New upstream version.
* Increase soname of libhx509-3-heimdal to libhx509-4-heimdal.
-- Brian May Mon, 13 Jul 2009 14:43:12 +1000
=== cut ===
--
Brian May
--
To UNSUBSCRIBE, email to
Guido Günther <[EMAIL PROTECTED]> writes:
> heimdal (1.2.dfsg.1-2.1) unstable; urgency=low
Unblocked.
Marc
--
BOFH #244:
Your cat tried to eat the mouse.
pgpFSJMBA64gM.pgp
Description: PGP signature
Hi,
From the changelog:
heimdal (1.2.dfsg.1-2.1) unstable; urgency=low
* Non-maintainer upload.
* fix segfaults when using pkinit with wrong PIN. Closes: #499405
-- Guido Günther <[EMAIL PROTECTED]> Sun, 05 Oct 2008 15:12:05 +0200
Without this patch PKINIT via pkcs11 is comp
Roberto C. Sánchez wrote:
> Here are the relevant changelog entries:
>
> cyrus-sasl2 (2.1.22.dfsg1-23) unstable; urgency=low
>
>* Add README.source to comply with Standards-Version 3.8.0
>* Fix watch file to use dversionmangle instead of uversionmangle
>
> cyr
Here are the relevant changelog entries:
cyrus-sasl2 (2.1.22.dfsg1-23) unstable; urgency=low
* Add README.source to comply with Standards-Version 3.8.0
* Fix watch file to use dversionmangle instead of uversionmangle
cyrus-sasl2-heimdal (2.1.22.dfsg1-23) unstable; urgency=high
Magnus Holmgren wrote:
> Adeodato Simó <[EMAIL PROTECTED]> writes:
>> * Russ Allbery [Mon, 04 Aug 2008 21:38:44 -0700]:
>>> It looks correct to me for the krb5 interface. It looks like some of the
>>> internal libraries that Heimdal uses (maybe libroken and l
Adeodato Simó <[EMAIL PROTECTED]> writes:
> * Russ Allbery [Mon, 04 Aug 2008 21:38:44 -0700]:
> > It looks correct to me for the krb5 interface. It looks like some of the
> > internal libraries that Heimdal uses (maybe libroken and libasn1,
> > although I'
to me for the krb5 interface. It looks like some of the
> internal libraries that Heimdal uses (maybe libroken and libasn1, although
> I'm not sure) aren't using symbol versioning, but since that isn't the API
> that's shared with MIT Kerberos, that shouldn't matter
* Brian May [Sat, 16 Aug 2008 14:03:01 +1000]:
> Adeodato Simó wrote:
>> The problem is that version of heimdal bumped the SONAME of one of the
>> libraries, namely libkrb5-24-heimdal -> libkrb5-25-heimdal.
>> Nowadays it's really encouraged that any SONAME bump i
Adeodato Simó wrote:
The problem is that version of heimdal bumped the SONAME of one of the
libraries, namely libkrb5-24-heimdal -> libkrb5-25-heimdal.
Nowadays it's really encouraged that any SONAME bump is checked with the
release team first. The release team needs to be notified a
* Fabian Fagerholm [Fri, 08 Aug 2008 21:54:30 +0300]:
> Hi!
Hello,
> cyrus-sasl2-heimdal has received a freeze exception [0], but it won't
> migrate to testing because it was built against heimdal 1.2.dfsg.1-2.
> There's apparently a freeze exception for heimdal
Hi!
cyrus-sasl2-heimdal has received a freeze exception [0], but it won't
migrate to testing because it was built against heimdal 1.2.dfsg.1-2.
There's apparently a freeze exception for heimdal 1.2.dfsg.1-1 which is
invalidated by the newer upload. The newer version doesn't seem t
asek and Russ
> Allbery; I think they have the required knowledge to do the checking,
> and hopefully can donate a bit of their time for this. (Many thanks in
> advance!)
It looks correct to me for the krb5 interface. It looks like some of the
internal libraries that Heimdal uses (maybe li
m somewhat
> curious now. The release critical bug wasn't filled until rather
> late (about the same time as the freeze).
The problem is that version of heimdal bumped the SONAME of one of the
libraries, namely libkrb5-24-heimdal -> libkrb5-25-heimdal.
Nowadays it's reall
Fabian Fagerholm wrote:
> Hello,
>
> I'd like to request a freeze exception for cyrus-sasl2 2.1.22.dfsg1-22
> and cyrus-sasl2-heimdal 2.1.22.dfsg1-22.
unblocked
Cheers
Luk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hello,
I'd like to request a freeze exception for cyrus-sasl2 2.1.22.dfsg1-22
and cyrus-sasl2-heimdal 2.1.22.dfsg1-22.
The changes are as follows:
--8<--
cyrus-sasl2 (2.1.22.dfsg1-22) unstable; urgency=low
[ Roberto C. Sanchez ]
* Added Slovak translation, thanks to Ivan Masár
Hello,
Heimdal in unstable (1.2.dfsg.1-2) needs to get pushed through to
testing/lenny.
The testing version 1.1-3:
* contains non-free RFC documents (no bug report opened).
* supposedly solved version symbols (#453241
<http://bugs.debian.org/453241>) on AMD64, unfortunat
On Sun, Nov 04, 2007 at 03:41:37PM +0100, Adeodato Simó wrote:
> A new heimdal was uploaded last month to unstable with several soname
> bumps. The following libraries disappeared from unstable:
> libroken16-heimdal
> libkrb5-17-heimdal
> libhdb7-heimdal
> lib
Hello.
A new heimdal was uploaded last month to unstable with several soname
bumps. The following libraries disappeared from unstable:
libroken16-heimdal
libkrb5-17-heimdal
libhdb7-heimdal
libkadm5clnt4-heimdal
libgssapi4-heimdal
libkadm5srv7-heimdal
libasn1-6-heimdal
Brian May <[EMAIL PROTECTED]> writes:
>* Include Spanish po-debconf translation (closes: #403481).
Unblocked.
Marc
--
Fachbegriffe der Informatik - Einfach erklärt
235: Kommentierter Quellkode
Hier programmiert ein Germanist oder Anglist. (Manfred Worm
Schäfer)
pgpR8n8gmrwfs.
Yesterday I uploaded:
Successfully uploaded heimdal_0.7.2.dfsg.1-9.dsc to ftp-master.debian.org.
Successfully uploaded heimdal_0.7.2.dfsg.1-9.diff.gz to ftp-master.debian.org.
Successfully uploaded heimdal-docs_0.7.2.dfsg.1-9_all.deb to
ftp-master.debian.org.
Successfully uploaded heimdal
On Tue, 12 Dec 2006, Brian May wrote:
> FYI.
>
> Also see the "update-inetd" thread I started on debian-devel.
>
> heimdal (0.7.2.dfsg.1-7) unstable; urgency=high
>
> * Don't change services on upgrades, only on fresh installation, purge, and
> upgr
> "Andreas" == Andreas Barth <[EMAIL PROTECTED]> writes:
Andreas> Thanks, approved.
-7 had a single character typo, and was broken for new installations,
so I uploaded -8.
See:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=401258
--
Brian May <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE
* Brian May ([EMAIL PROTECTED]) [061212 07:09]:
> Also see the "update-inetd" thread I started on debian-devel.
Thanks, approved.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTE
FYI.
Also see the "update-inetd" thread I started on debian-devel.
heimdal (0.7.2.dfsg.1-7) unstable; urgency=high
* Don't change services on upgrades, only on fresh installation, purge, and
upgrade from old versions. Closes: #401258.
-- Brian May <[EMAIL PROTECTED]&
On Sat, 02 Dec 2006, Peter Palfrader wrote:
> It seems the heimdal-kdc upgrade disables hpropd in inetd
> unconditionally on upgrades:
I have just uploaded the following NMU to delayed-1 on gluck, which
fixes #401258.
diff -u heimdal-0.7.2.dfsg.1/debian/heimdal-kdc.postinst
heimdal
d RC. The binary
> > > > that fails comes from the old version of the package, which did have
> > > > correct dependencies on libkrb5-17-heimdal; and the database
> > > > dump/restore is normally done as part of the upgrade, AIUI; so this
> > > > r
Thank you for the additional information you have supplied regarding
this problem report. It has been forwarded to the package maintainer(s)
and to other interested parties to accompany the original report.
Your message has been sent to the package maintainer(s):
Oliver Elphick <[EMAIL PROTECTED
Processing commands for [EMAIL PROTECTED]:
> severity 236554 important
Bug#236554: Postgresql does not depend on libkrb5-17-heimdal but it is needed
for upgrades
Severity set to `important'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian b
asek wrote:
> > > I question whether this bug should really be considered RC. The binary
> > > that fails comes from the old version of the package, which did have
> > > correct dependencies on libkrb5-17-heimdal; and the database
> > > dump/restore is normally do
fails comes from the old version of the package, which did have
> > correct dependencies on libkrb5-17-heimdal; and the database
> > dump/restore is normally done as part of the upgrade, AIUI; so this
> > really ought to only fail if something else forced the removal of the
&
On Tue, Dec 23, 2003 at 11:54:52PM -0500, Nathanael Nerode wrote:
> From bjorn.haxx.se:
> ># Updating krb4 makes 1 packages uninstallable on alpha: libpam-heimdal
> ># Updating krb4 makes 3 packages uninstallable due to depending on
> >krb4: arla, heimdal, cyrus-sasl2
>
From bjorn.haxx.se:
># Updating krb4 makes 1 packages uninstallable on alpha: libpam-heimdal
># Updating krb4 makes 3 packages uninstallable due to depending on
>krb4: arla, heimdal, cyrus-sasl2
So it looks like libpam-heimdal is the only thing preventing the
arla/heimdal/cyrus-sasl2/k
On Fri, Nov 14, 2003 at 02:01:15PM +1000, Anthony Towns wrote:
> AFAICS, the patch is about preventing some information leaks (as an
> unprivleged user, you can use suidperl to find some information about
> files you don't otherwise have access to - mainly whether they exist, and
> if they're setu
Various Cc's dropped, [EMAIL PROTECTED] added.
bod: we're talking about the grave perl bug, ie the patch for improving
the security model.
On Thu, Nov 13, 2003 at 03:28:35PM -0500, Matt Zimmerman wrote:
> On Thu, Nov 13, 2003 at 02:22:43PM -0600, Steve Langasek wrote:
> > On Thu, Nov 13, 2003 at
On Thu, Nov 13, 2003 at 02:22:43PM -0600, Steve Langasek wrote:
> On Thu, Nov 13, 2003 at 09:13:37PM +0100, Adrian Bunk wrote:
> > But that's the decision of the perl maintainer and the security team.
>
> I think it's silly to claim that a flaw that's been well-known for ages
> constitutes an RC
On Thu, Nov 13, 2003 at 09:13:37PM +0100, Adrian Bunk wrote:
> > And although the patch in 220486 is a nice improvement if it works as
> > advertised, I don't think it should be considered RC given that suidperl
> > has been using the same flawed security model for years. So getting it
> > in syn
ething?
>
> > According to update_output, at least PostgreSQL needs to go into
> > testing before heimdal can go into testing.
>
> > PostgreSQL waits for glibc and perl.
>
> > glibc waits for linux-kernel-headers.
>
> > perl has a RC bug.
>
> It
gt; testing before heimdal can go into testing.
> PostgreSQL waits for glibc and perl.
> glibc waits for linux-kernel-headers.
> perl has a RC bug.
It also is out of date on mips and m68k.
And although the patch in 220486 is a nice improvement if it works as
advertised, I don't
On Thu, Nov 13, 2003 at 12:28:39AM -0500, Nathanael Nerode wrote:
> Are these four ready to be hinted in together, or am I missing something?
According to update_output, at least PostgreSQL needs to go into
testing before heimdal can go into testing.
PostgreSQL waits for glibc and perl.
gl
Are these four ready to be hinted in together, or am I missing something?
70 matches
Mail list logo
