7;s not something I've managed to find time
to do.
--
Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
been ABI updates anyway, particularly in
stable.
--
Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
7;t immediately obvious
to me. Sorry about the noise.
--
Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
ture for them.
That said, this is an architectural stab in the dark and I obviously don't
work on file system development, so maybe this isn't viable for some
reason that I'm not seeing.
--
Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
arget distribution before using it to
build the file system the actual installation is going into.
I suspect this won't be Ted's favorite option because this isn't a natural
way to think about the option space from a file system developer
perspective, but maybe we could find som
only going to care when stable is released; people doing
production work on unstable or testing already know that they're signing
up for occasional breakage. So the proximity-to-release argument to me
feels most relevant if this change is specifically a problem for the
release process and
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: 994...@bugs.debian.org
tripwire now segfaults when it tries to read information about a file.
Rebuilding the package from source makes the problem go away. The
problem appeared
rb5 (4.9-2) unstable; urgency=medium
+
+ * Apply upstream patch to avoid a double free if calling
+krb5_cc_get_principal on the new cache fails.
+
+ -- Russ Allbery Sun, 14 Mar 2021 12:31:39 -0700
+
libpam-krb5 (4.9-1) unstable; urgency=high
* New upstream release.
diff -Nru
libpam-krb5-4.9
'd prefer not to drop that until GnuPGv1 is no longer in the archive.
--
Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
cture around the
work, recruiting people, building a task list, and so forth, instead of
just assuming "oh, everything will work on i386, it always has."
Volunteering to do that sort of coordination is helpful even if you aren't
debugging FTBFS problems.
--
Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
tting
onto the amd64 kernel even if you keep an i386 userspace), but at some
point it seems likely they will no longer be. That means it may be time
to push our users a bit harder to switch to the amd64 kernel if they can.
--
Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
k on actual i386 hardware, and I don't know if it
has other issues that I personally happened not to notice.)
--
Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
xplicit language to allow the Release Team to downgrade requirements to
recommendations.
--
Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
let you
know when that's done. Once that's complete, we can do a reconciliation.
I'm inclined to downgrade Policy musts that the release team does not
consider likely to be release-critical in the future, for instance.
--
Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
Bastian Blank writes:
> On Sun, Nov 17, 2019 at 10:10:11AM -0800, Russ Allbery wrote:
>> +The Release Team may, at their discretion, downgrade a Policy requirement
>> +to a Policy recommendation for a given release of the Debian distribution.
>> +This may be done for only
Control: tag -1 -moreinfo
Jonathan Wiltshire writes:
> On Sat, Mar 09, 2019 at 12:44:59PM -0800, Russ Allbery wrote:
>> * Upload 1.02-1 to unstable and have you unblock that for propagation to
>> testing as a regular package update? This is a leaf package, so I'm
>&g
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
This is an unblock request for a package I've not yet uploaded, since I
wanted to get your guidance on how you'd prefer to get this update.
On March 15th, the Duo API is changing to require
Michael Biebl writes:
> Am 10.05.2018 um 19:22 schrieb Russ Allbery:
>> I may be misunderstanding the nature of the issue, but I believe that a
>> Type=oneshot service that runs a small C program that calls getrandom()
>> and then exit(0) when it returns would provide a use
ide to take this approach (this
seems obviously correct for kadmind, for instance), having this sort of
facility available would make it easy to declare the right dependency.
It's akin to systemd-networkd-wait-online.service.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
Adrian Bunk writes:
> On Thu, Apr 19, 2018 at 08:34:57PM -0700, Russ Allbery wrote:
>> I'm quite sure from past discussion that we want to be sure packages don't
>> Recommend contrib or non-free packages, and don't want to re-open that.
>> But that's n
and make the package buggy for multiple reasons, so no need
to change anything there.)
Release folks, why this exception in the release policy? Are you
comfortable with Debian releasing with packages that Recommend packages
that aren't part of the release? (Have we historically done this?)
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
because (as security software) the
consequences of making a small error in the API change can be very high.
Upstream is working on the changes and on comprehensive tests to ensure
that the port was done correctly, but their timeline doesn't line up well
with our release freeze.
--
Russ
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 open a separate bug to
remove it from testing as well, or do you want to just handle that as par
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Mini-transition for log4shib. All of the packages that depend on it are
part of the shibboleth-sp2 suite. There will also be a transition for
opensaml2 along the way, which has to under
y trivial fix. I
think replacing Digest::SHA1 with Digest::SHA is generally all that's
needed.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe".
Russ Allbery writes:
> The only specific claim that Francesco has made that I was able to find
> is that the choice of venue clause in CeCILL-C makes it incompatible.
> However, CeCILL also contains a choice of venue clause, and the FSF
> state that it is GPL-compatible. Given th
of this argument.
> What do you think should be done?
Nothing, in the absence of more credible evidence that there is a license
incomaptibility.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.deb
ere are other reasons why you may need to avoid it, such as needing to
insert code between specific things it does, so this isn't necessarily a
solution.)
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-release-requ...
ders are
"supposed" to interact, and a tiny bit more welcoming.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87388xywh0@hope.eyrie.org
had to fight my way forward to get my changes into
> Debian. Right now I'm really regretting even getting involved with
> util-linux in Debian.
I'm sorry. :/ I hadn't seen anything about this issue until just now.
If I had, I would have given advice on it earlier.
Thank you s
urse of action, Debian has been doing 3 for the
last ten years, so it has the power of precedent. :)
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "u
sets of functionality. We introduce new library dependencies or
just increases in size of existing libraries on that scale routinely
without anyone even noticing.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-release-re
cron facilities
in Debian.
Of course, if in your view as a maintainer this functionality isn't ready
for jessie or you don't want to support it, just backing out of the change
also works. (And to be clear I'm not on the release team, and it's their
opinion tha
and dropping
init-system-helpers isn't a good long-term solution. We'll instead need
to figure out the best way to make sure that what that package is doing
can be done correctly.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCR
"Adam D. Barratt" writes:
> On 2014-08-26 6:58, Russ Allbery wrote:
>> "Adam D. Barratt" writes:
>>> The patch looks fine, thanks. Just for a final confirmation, please
>>> could we have a debdiff of the proposed upload (against the current
>>
obnoxious patch of a patch; the
unstable version no longer uses single-debian-patch, but I was still using
it then. Regeneration of the diff of course changed the order of the
modified files, so the diff is particularly ugly.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.o
Package: release.debian.org
Severity: normal
Tags: wheezy
User: release.debian@packages.debian.org
Usertags: pu
Hello folks,
The current gnubg in stable segfaults during "end game" when run with
the -t flag. I got a request from one user to fix this in stable, at:
http://bugs.debian.org
ave happened in the past, they've released an "end of life" security
advisory to notify Debian stable users that a given package will not
receive security support and should be considered insecure.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.
n oversight. Sorry for the inconvenience.
Ah, okay, thanks! I'll work on a new upload, probably by this weekend, to
unblock the libmemcached transition.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.deb
w upstream version with the fix for the libmemcached
transition? Or keep holding off for the Boost transition?
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscri
s any support for whatsoever. Adding support for
some third option might be possible, but I'm dubious that's realistic for
a jessie release timeframe.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-release-re
the degree to which logind
forces systemd as init is disputed, and as yet no one has done the
concrete work to establish which technical opinion is correct with systemd
and logind >205.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, em
iece of software/packaging does not actually
exist yet, though, and people's time/motivation to work on it may be
affected by the outcome of the larger decision.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-re
used, so unless someone has a neat
solution, I'm inclined to not worry about it. (It doesn't feel like it
warrants a stable update.)
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
Antonio Terceiro writes:
> On Mon, Jan 06, 2014 at 01:22:15PM -0800, Russ Allbery wrote:
>> On my next package upload, should I just drop Ruby 1.8? I can easily
>> do that, but I wasn't sure if we were at the point where that was now
>> desirable, or if the upgrade p
l do another upload within at least the next couple of weeks
with that change (or sooner if it becomes more urgent).
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "
r now, I'm continuing to build 1.8 and 1.9.1 modules, but I can quickly
change that as soon as I know what to do.
(Due to the nature of this source package, it handles which Ruby versions
to build for itself, so it requires some minor source changes to fiddle
with the supported version list.)
--
There's a limit to what we can do inside Debian, and in some cases waiting
for upstream is the right approach.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subje
Julien Cristau writes:
> On Wed, May 29, 2013 at 16:48:19 -0700, Russ Allbery wrote:
>> I'm staging the packages in experimental and have everything done
>> except for the actual shibboleth-sp2 package and its Apache module,
>> which I'm going to work on to
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hello folks,
I'm preparing a new version of the Shibboleth packages, which as usual
involves three library transitions, although they're all used only by
this package set. libxml-securi
Niels Thykier writes:
> On 2013-05-20 01:54, Russ Allbery wrote:
>> Be aware that Perl 5.18.0 includes podlators 2.5.1, which means that
>> pod2man now exits with an error by default if there are POD syntax
>> errors. I believe this means that some fairly large percenta
TBFS once this becomes the
default version of Perl.
http://lintian.debian.org/tags/manpage-has-errors-from-pod2man.html
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of &qu
re all plugins and it's not
> going to be any useful to build anything against them.
I wouldn't fix this at this point in the release cycle if your other
changes are approved. Since these are *.la files for plugins, this is
fairly harmless and unlikely to cause issues.
--
epending on
whether we can track down all the odd dependency loops or not) that people
who don't read the release notes are going to get the infamous "could not
perform immediate configuration" error from apt. So chances may be higher
this upgrade than many. :)
--
Russ Allbery (r...@d
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package puredata to fix RC bug #690410.
As discussed in the bug log, the upstream source does strange things
with buffers that cause crashes when built with _FORTIFY_SOURCE.
es and protect against client parsing of
+ bad ACL entries. (CVE-2013-1794)
+- OPENAFS-SA-2013-002: Fix ptserver buffer overflow via integer
+ overflow in the IdToName RPC. (CVE-2013-1795)
+
+ -- Russ Allbery Mon, 04 Mar 2013 11:17:02 -0800
+
openafs (1.6.1-2) unstable; urgency=low
ading this can fill it in from memory. *grin*)
If we could find a way to release some of that tension, that would be
great, but it's a hard problem, and there's no way that we're going to
come up with a solution to it right now in the middle of the wheezy
freeze.
--
Russ Allbery (r...
and we don't
like a lot of the implications of that, but we don't know how to do better
and get releases out faster because there's a truly intimidating amount of
work that has to get done to do the release and all the alternatives seem
to make the work even worse.
--
Russ Allbery (r.
e buildds at testing since there would be no way to
stage library transitions that *are* going into the release, so let me
note that this is not a well-thought-out proposal, just the sketch of an
idea.) But that's all outside the scope of tech-ctte deliberation, since
that's technical d
s solution and the right
general solution.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Arc
Net::SNMP version always begins
with v, since 4 is always going to be lt any string starting with v. But
maybe the old version that this is checking against didn't use v in the
version number.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
recall if there's anything allowed in the sysklogd configuration
that rsyslog doesn't support, but at least for all of our systems
installing an /etc/rsyslog.d fragment that did:
$IncludeConfig /etc/syslog.conf
was all that was required to transition without changing any existing
configura
after -- or as the
+argument to another option. Verify that the -e option's value matches
+expectations rather than trying to look for invalid -e option values.
+(CVE-2012-2251)
+ * Reject the rsync --rsh option even if it does not contain a trailing
+equal sign. (CVE-2012-2252)
+
ock requests, I'll certainly keep from
clogging up the BTS, but I thought they wanted an unblock request for
*everything* that needs to migrate to testing at this point.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debia
lls
sasl_client_done() or sasl_server_done(). I've run into other Kerberos
load and unload bugs because of this when using Perl with
Authen::SASL::Cyrus, which calls those functions when the
Authen::SASL::Cyrus object is garbage-collected.
--
Russ Allbery (r...@debian.org) <http://ww
.0 to
+libwebauth-perl and of webauth-weblogin << 4.0.0 to libwebkdc-perl.
+The API of the Perl modules changed in 4.0.0. Thanks, Dameon Wagner.
+(Closes: #691878)
+
+ -- Russ Allbery Sun, 04 Nov 2012 13:57:09 -0800
+
webauth (4.1.1-1) unstable; urgency=low
* New upstream
remctl-3.2/debian/changelog 2012-06-28 13:57:33.0 -0700
+++ remctl-3.2/debian/changelog 2012-09-27 21:13:18.0 -0700
@@ -1,3 +1,10 @@
+remctl (3.2-4) unstable; urgency=low
+
+ * Cherry-pick upstream fix to close a file descriptor leak in remctld
+when checking access against ACL f
he answers to questions asked by
the config script.
I'm not sure that I would say "completely forbidden," but it's something
to avoid unless there's some overriding requirement for config to work
that way.
--
Russ Allbery (r...@debian.org) <http://www
7;t think I ever said that
explicitly.
I agree with Julien that there's no reason for the release-team to hold
off on unblocking the current package, since it doesn't make matters any
worse. But I also agree with Ian that I don't think this is what we
intended and we probably need to ta
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package krb5-sync for the fix to RC bug #687346.
Changelog:
* Apply upstream commit to silently ignore password changes with a NULL
password, only new keys. This repre
acy-96xx (96.43.20-8) unstable; urgency=low
+
+ [ Debconf translations ]
+ * Spanish (es): Camaleón (Closes: #686437)
+
+ -- Russ Allbery Mon, 03 Sep 2012 13:20:51 -0700
+
nvidia-graphics-drivers-legacy-96xx (96.43.20-7) unstable; urgency=low
[ Debconf translations ]
dif
ow
+
+ [ Debconf translations ]
+ * French (fr): Christian PERRIER (Closes: #683716)
+ * Portuguese (pt): Miguel Figueiredo (Closes: #685444)
+
+ -- Russ Allbery Fri, 31 Aug 2012 10:16:44 -0700
+
nvidia-graphics-drivers-legacy-96xx (96.43.20-6) unstable; urgency=low
[ Andreas Beckma
it 00fbf80098a1f8fea014c9849f8adcd615ff1687
Author: Russ Allbery
Date: Thu Aug 30 16:28:43 2012 -0700
Call the public kadm5 API functions instead of the internal ones
The kadm5_c_* functions are an internal API. The public functions
are the ones without the _c, which dispatch
Russ Allbery writes:
> Russ Allbery writes:
>> Andreas Beckmann writes:
>>> I haven't forgotten about this, but uploading this package I currently
>>> get a REJECT with a python traceback from dak (#685807).
>>> @Russ: in case someone fixes d
Russ Allbery writes:
> Andreas Beckmann writes:
>> I haven't forgotten about this, but uploading this package I currently
>> get a REJECT with a python traceback from dak (#685807).
>> @Russ: in case someone fixes dak, could you try to re-upload this, it's
>&
unstable. I am pre-requesting this since I am leaving for a
> weekend and I could forgot to do that after the weekend :).
FYI for the release team, a message from one of the maintainers in
debian-devel indicates that this NMU may be controversial.
--
Russ Allbery (r...@debian.org)
ld you try to re-upload this, it's
> tagged in SVN and builds in plain squeeze.
Sure, no problem.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of &q
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package openafs (translation updates only). Changelog:
* Translation updates:
- Fix German translation encoding. Thanks, Christian PERRIER.
(Closes: #678736)
+
+ * Apply upstream patch to close security vulnerability that permitted
+clever manipulation of environment variables on the ssh command line
+to bypass rssh checking. (CVE-2012-3478)
+
+ -- Russ Allbery Fri, 10 Aug 2012 22:14:34 -0700
+
rssh (2.3.3-4) unstable; urgency=low
* Forc
ped building my own
kernel a long time ago, so most of my understanding is hearsay.
I keep maintaining -source packages for other packages with kernel modules
mostly because I keep getting a small number of bug reports for them, so
people are clearly still using them.
--
Russ Allbery (r..
t doing
this.
I noticed that dkms now Recommends the tracking kernel header package, so
maybe that makes this somewhat more obsolete. That means that the average
user should, through the dependency tree, get the header package installed
when they install nvidia-modules-dkms, whic
ted Debian users. What
Andreas has been doing, which I think is fairly reasonable, is keeping
them out of testing until shortly before the freeze and then updating them
for the freeze, which means only doing new uploads for ABI changes that
happen during the freeze or in stable (relativel
ubuntu.com/MultiarchSpec#Dependencies_involving_Architecture:_all_packages
Oh, thank you. That was the bit that I was missing. It looks like I have
some updates to do on my packages!
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-release-r
ackages are already effectively
multi-arch without needing to use any of the new support?
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe
t for nearly all
of his projects), which clearly does state that all the files are now
public domain. So there's no need to parse that statement; it's
thankfully been superseded.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, e
b package (in particular,
cdb-0.75.tar.gz, with MD5 checksum 81fed54d0bde51b147dd6c20cdb92d51) into
the public domain. The package is no longer copyrighted.
So yes, agreed.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-re
s are working in both systems for the wheezy release
and then aim at removing the requirement to support update-mime for all
packages providing .desktop files for wheezy+1.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email t
shipping systemd service files with my
packages.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: h
approach makes sense for wheezy+1 if the
dpkg maintainers don't think that the move to package metadata will be
done in time.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subj
h simpler
debate about the right interface to view those files for installed
packages.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe".
e web and trying to do
archeology on what happened.
Saving the binary NMU changelog in a separate file feels like the right
solution to me.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.o
have a long release cycle, so there's always going to be a lot of
pressure, but there's always backports.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "
27;t the GCC documentation now non-free?
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/877gveaoz9@windlord.stanford.edu
the release team's job to
decide whether gcc-4.7 is acceptable as a release compiler for wheezy.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsub
also test make 3.82 at the same time. It's
currently in experimental, and we suspect that it may break some packages
that use a deprecated rule construct, but we have no idea how many
packages might break.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
to libssl-dev solves the FTBFS but
> libmysqlclient-dev should probably be the one depending on libssl-dev.
It should probably just be omitting all that stuff from its library
configuration and relying on transitive library dependencies.
--
Russ Allbery (r...@debian.org)
ly true. I kind of don't want the working packages
to be removed from testing, though (not that making the bugs RC causes
that directly).
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
wi
Cyril Brulebois writes:
> Russ Allbery (18/01/2012):
>> Petter Reinholdtsen from DebianEdu requested this change make it into
>> stable as well, since it's causing problems for them (they set up accounts
>> in Kerberos and LDAP only by default).
> If they're d
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: pu
Filing this in advance of actually doing the update work
libpam-krb5 4.4-3 in unstable added the following change (from
NEWS.Debian):
The default PAM configuration for the password stack
Julien Cristau writes:
> On Fri, Jan 6, 2012 at 10:27:49 -0800, Russ Allbery wrote:
>> The bug in g++ that was preventing shibboleth-sp2 from building with g++
>> 4.6 was fixed (#630752) and I removed the dependency on g++-4.4 on arm*
>> from the package at the gcc maintain
1 - 100 of 359 matches
Mail list logo
