Bug#842497: krb5: [INTL:de] German translation is missing

I'm aware of no issue. I'll look into it; will be packaging 1.15~beta1 soon, and this is almost certainly a packaging error, not an intentional change. Or rather, I'm sure the change is not intended; it's alomst certainly just that the file somehow got dropped.

Bug#841372: Kerberos config update for CS.CMU.EDU

Jeff, I've just uploaded kerberos configs 2.6. If you delete /etc/krb5.conf and then install krb5-config 2.6 and confirm that the entry there works for you, I'll fill out paperwork to request an unblock for stretch. (I don't think this will make it for the auto migration)

Bug#841372: Kerberos config update for CS.CMU.EDU

control: severity -1 important justification: As maintainer, I'd like to consider this issue important. If not promptly resolved, it will create an operational inconvenience on an ongoing basis for years. --Sam

Bug#805154: Please reconsider tagging this bug wontfix

I do understand that the proposed fix is inadequate. You'd need to not include nobarrier on the esp partition. However, the performance of vmdebootstrap is really fairly bad compared to other image creation solutions I've used in the past, and it does significantly impact the test/development

Bug#833057: does downgrading e2fsprogs to the jessie version help?

Does the e2fsprogs in jessie produce an image that works with syslinux and vmdebootstrap?

Bug#841372: Kerberos config update for CS.CMU.EDU

Your timing is dreadful.:-) I just uploaded a new krb5-config and am not 100% sure I'll have time to get in another one for stretch before the freeze. I considered dropping the kdc lines and depending on SRV records for cs.cmu.edu, but decided that you were picky enough that you would have sent in

Bug#836154: sbuild --no-arch-any --no-arch-all --source fails on all only dsc

I want consistency between the case where there is a binary build and the case where there is a source build. I want --source because I want the source package to be included in the .changes. I want to use one tool, (sbuildh) rather than having my scripts care about how it is being called.

Bug#836154: sbuild --no-arch-any --no-arch-all --source fails on all only dsc

> "Johannes" == Johannes Schauer writes: Johannes> Do you know a situation when it would be beneficial to let Johannes> sbuild create the source package *again* after it has Johannes> already been produced for sbuild? Sbuild can take a directory as input. I

Bug#839570: Browserified javascript and DFSG 2 (reopening)

>>>>> "Sam" == Sam Hartman <hartm...@debian.org> writes: Sam> Obviously, there's a level at which I agree with you. When Sam> this came around last time, I wanted us to issue advice. This was something I intended to send to Ian privately, n

Bug#839570: Browserified javascript and DFSG 2 (reopening)

Obviously, there's a level at which I agree with you. When this came around last time, I wanted us to issue advice. The advice I wanted to issue isn't the advice you wished we issued, but it would have at least been advice. However, I was the only one on the TC who wanted to touch the issue. It

Bug#839570: Browserified javascript and DFSG 2 (reopening)

Dear joseph: This message will be hurried: I'm on a train and approaching my stop. Thanks for your detailed message. I don't agree with all of it, but I find it a lot easier to interact with than some of the requests we've gotten related to this issue. Here are some factors to consider: 1)

Bug#839570: Browserified javascript and DFSG 2 (reopening)

Dear Pirate: I hear that you're fairly frustrated by the response you're getting from the TC. Speaking as someone who has read extensively the earlier bug log, I think that your cause would be advanced by getting an additional primary advocate who has a better understanding of what the TC can

Bug#839570: Browserified javascript and DFSG 2 (reopening)

> "Didier" == Didier 'OdyX' Raboud writes: Again, I'm fine with your current ballot. As stated, I don't think the TC should (and am skeptical of can) decide on the DFSG-freeness of a package directly. We could mediate, but it's clear we don't want to here. I do think there

Bug#839570: Browserified javascript and DFSG 2 (reopening)

I'd be willing to vote on the ballot you propose. I disagree with your rationale for why this bug is not for the TC to decide. But I agree that this bug is not for the TC to decide at this time. So, if that's all we're voting on, and I don't need to agree with your rationale to vote C, I'm fine

Bug#839172: TC decision regarding #741573 menu policy not reflected yet

package: tech-ctte In #741573, the TC produced a two-part decision. We approved specific wording regarding .desktop policy. That was folded into a policy NMU. We also approved the decision that packages should not include both a menu file and a desktop file. The action to draft language for

Bug#835086: RFP: nextcloud -- self-hosted cloud services

> "Xavier" == Xavier Bestel writes: Xavier> Le mardi 20 septembre 2016 à 19:38 +0200, Moritz Mühlenhoff Xavier> a écrit : >> On Mon, Aug 22, 2016 at 12:02:59PM +0200, Xavier Bestel wrote: >> > >> > Package: wnpp > Severity: wishlist >> >

Bug#838393: PCA on a repository insufficient to update uploaders

So, I can see a couple of easy fixes: 1) have _uploaders be a class variable rather than an instance variable or 2) store a list ofweakrefs to extant demon objects then provide a class method to invalidate all the uploaders caches.

Bug#838393: PCA on a repository insufficient to update uploaders

package: mini-buildd version: 1.0.12 Hi. I'd expect that if I change the extra keyrings configuration in the repository, and then prepare/check/activate the repository, then any new uploaders would be able to upload. I've found that I need to restart the demon (I used systemctl, although

Bug#837000: kerberos-configs: FTBFS: Undefined subroutine ::read_config called at ./genblob line 9.

> "Lucas" == Lucas Nussbaum writes: Lucas> Hi, Lucas> During a rebuild of all packages in sid, your package failed Lucas> to build on amd64. Lucas> Relevant part (hopefully): >> fakeroot debian/rules binary ./genblob >tmp & tmp config-blob >>

Bug#836156: improper handling of source+binary changes triggering binary builds

>>>>> "Stephan" == Stephan Sürken <abs...@debian.org> writes: Stephan> Hi Sam, Stephan> On Di, 2016-08-30 at 21:27 -0400, Sam Hartman wrote: >> package: mini-buildd version: 1.0.12 severity: normal >> >> reprepro 4.1

Bug#836388: [pkg-go] Bug#836388: When cache is present, job run from incorrect working directory

>>>>> "Dmitry" == Dmitry Smirnov <only...@debian.org> writes: Dmitry> On Friday, 2 September 2016 10:01:14 AM AEST Sam Hartman wrote: >> If a job includes a cache, then it appears that the initial >> working directory is some di

Bug#836388: When cache is present, job run from incorrect working directory

package: gitlab-ci-multi-runner version: 1.4.2+dfsg-1 severity: important Hi. If a job includes a cache, then it appears that the initial working directory is some directory inside the cache, *not* the top of the project directory. In trying to diagnose build failures I produced the following

Bug#836193: Improper handling of arch all only package

package: mini-buildd version: 1.0.12 severity: normal I uploaded the source of an arch all package (no arch any in the resulting build) and got: 2016-08-30 22:06:57,398 mini_buildd.packager (0039): ERROR : Exceptio\ n DEBUG (Package 'hadron-ci_0.2' FAILED: 1 mandatory architecture(s)

Bug#836156: improper handling of source+binary changes triggering binary builds

package: mini-buildd version: 1.0.12 severity: normal reprepro 4.17.1-1 The CI on our source control runs sbuild -d sid-hadron-snapshot --arch-all --source . Producing a changes file that includes binaries and sources. If that succeeds in passing some tests, we upload to mini-buildd. I

Bug#836154: sbuild --no-arch-any --no-arch-all --source fails on all only dsc

package: sbuild version: 0.70.0 severity: normal what happened: $ sbuild --source --no-arch-any --no-arch-all -c unstable -d sid-hadron-snapshot . dh clean dh_testdir dh_auto_clean dh_clean dpkg-source: info: using source format '3.0 (native)' dpkg-source: info: building hadron-ci in

Bug#806617: freeradius: FTBFS when built with dpkg-buildpackage -A (dh_install: freeradius-common missing files)

> "Raphael" == Raphael Hertzog writes: Raphael> It would seem natural to orphan it and to let the new Raphael> maintainer deal with updating it to version 3.x. I think 3.x is likely to be new packaging and entirely breaks compatibility with the 2.x config. If we

Bug#806617: freeradius: FTBFS when built with dpkg-buildpackage -A (dh_install: freeradius-common missing files)

> "Josip" == Josip Rodin writes: Josip> On Tue, Aug 30, 2016 at 11:20:50AM +0200, Raphael Hertzog wrote: >> Josip, do you really still care about this package? Josip> I'm pretty sure I told Sam to take it over a few years Josip> back...? O, if

Bug#806617: freeradius: FTBFS when built with dpkg-buildpackage -A (dh_install: freeradius-common missing files)

> "Raphael" == Raphael Hertzog writes: Raphael> On Thu, 14 Jul 2016 22:09:52 + Santiago Vila wrote: >> I have the ok from the Release Managers to consider this issue as >> RC for stretch. I'm going to wait at least one week before

Bug#835507: Please clarify that sysvinit support decision is not going to expire

> "Bart" == Bart Schouten writes: >> I agree on this too. To the extent it should be considered >> time-limited, it should be «until N releases after sysvinit is >> removed» or somesuch, if that happens. Bart> In legal terms, in law, it would be

Bug#835507: Please clarify that sysvinit support decision is not going to expire

>>>>> "Ansgar" == Ansgar Burchardt <ans...@debian.org> writes: Ansgar> On Fri, 26 Aug 2016 08:50:13 -0400 Sam Hartman wrote: >> I think we want to reaffirm that policy section 9.3.2 and section Ansgar> 9.3.3 >> represent curr

Bug#835520: Policy 9.3.1 is inaccurate to the point of being harmful

package: debian-policy severity: normal Hi. As part of reviewing an issue for the technical committee, I just read policy section 9.3 in its entirety. Section 9.3.1 really seems to be showing its age. That section covers runlevels and the sequencing numbers after S and K in rc.d links without

Bug#835507: Please clarify that sysvinit support decision is not going to expire

>>>>> "Ian" == Ian Jackson <ijack...@chiark.greenend.org.uk> writes: Ian> Sam Hartman writes ("Re: Bug#835507: Please clarify that Ian> sysvinit support decision is not going to expire"): >> Ian, quick question for you because you

Bug#835507: Please clarify that sysvinit support decision is not going to expire

Ian, quick question for you because you might know the answer off the top of your head. Does running stretch with sysvinit as your init system work reasonably well, or at least work well enough that there are a small number of bugs we will likely be able to fix in the stretch time frame? What I

Bug#830344: Project Roadmap question - Call for votes

>>>>> "Sam" == Sam Hartman <hartm...@debian.org> writes: >> 1) The TC volunteers to be the Roadmap team 2) The TC volunteers >> to be part of the regular workflow of the Roadmap team, as an >> advisory body. 3) The TC shouldn't be p

Bug#830344: Project Roadmap question - Call for votes

>1) The TC volunteers to be the Roadmap team >2) The TC volunteers to be part of the regular workflow of the >Roadmap team, as an advisory body. >3) The TC shouldn't be part of the regular workflow of the Roadmap team. >We will always be available for escalations, as usual. >4) Further

Bug#831187: moonshot-gss-eap: FTBFS with GCC 6: util_shib.cpp:126:5: error: 'template class std::auto_ptr' is deprecated [-Werror=deprecated-declarations]

Hi. Apologies for taking a while. I wanted to understand c++ 11 and unique_ptr and shared_ptr better. It turns out c++ 11 is kind of complicated. Replacing auto_ptr with unique_ptr will certainly work in this code at least as well as auto_ptr. Figuring out the upstream patch is a bit more

Bug#777182: kerberos-configs: please make the build reproducible

Hi. kerberos-configs also hasn't been uploaded in 555 days:-) It's a fairly static package, and I don't think reproducible builds adds enough value to this package to justify an upload just for this patch. That said, I've reviewed the patch, and it seems entirely reasonable, so I will include it

Bug#834035: kdb5_util hangs forever

For debian, is there any reason not to build krb5 with _LARGEFILE_SOURCE?

Bug#831187: moonshot-gss-eap: FTBFS with GCC 6: util_shib.cpp:126:5: error: 'template class std::auto_ptr' is deprecated [-Werror=deprecated-declarations]

Hi. Apologies for the delay. I plan to fix this issue this weekend.

Bug#830344: Moving forward with the Project Roadmap question

I think that calling for that vote would be fine. I view that as an informalish internal vote, not some formal resolution that we're going to announce on d-d-a. Mostly I think we're going to try and figure out the direction at a high level. For options 1, 2, 4, and possibly 3, I think we'll need

Bug#834035: kdb5_util hangs forever

control: retitle -1 kdb5_util hangs forever on 32-bit systems --Sam

Bug#834035: kdb5_util hangs forever

So, in particular, it looks like kdb5_util is acquiring a lock from 0 to bignum that fails, acquiring a lock from 0 to 0 that succeeds, releasing the lock from 0 to bignum (which succeeds?), and then while still holding the lock from 0 to 0 tries to get another lock from 0 to bignum. At least

Bug#833882: Duplicate of 831439?

> "Neil" == Neil Williams writes: Neil> Hi Sam, From the description, this sounds like a duplicate of Neil> 831439 vmdebootstrap: stretch image has no DNS setup. The fix Neil> for 831439 enables systemd-resolved and creates the symlink to Neil>

Bug#833882: vmdebootstrap: --enable-dhcp doesn't handle resolv.conf

Package: vmdebootstrap Version: 1.5-1 Severity: important When --enable-dhcp is used and systemd-network is used, systemd-resolved is not started. In addition, I think even if you start systemd-resolved, you still need to point resolv.conf at 127.0.0.53. Installing resolvconf and enabling

Bug#833798: krb5: FTBFS with -O3: uninitialized variables

Yeah, thanks for reminding me of this. I had intended to apply it from the launchpad bug but just forgot.

Bug#833398: vmdebootstrap: correcting broken after custom packages fails to pass yes

Package: vmdebootstrap Version: 1.5-1 Severity: normal ERROR: command failed: ['chroot', '/tmp/tmpuio60u', 'apt-get', '-f', '--no-remov e', 'install'] Reading package lists... Building dependency tree... Correcting dependencies... Done The following additional packages

Bug#830344: How should the TC help with a project roadmap?

I'm not really advocating that the TC would be a very good help promote your ideas team. However, I'm struck by the following even if I don't entirely know what to make of it. > "Ian" == Ian Jackson writes: Ian> * To be accessible and approachable,

Bug#830978: Sam's Comments on What I Source Code

I was working on the following comments in hopes of turning them into a draft resolution for the TC. The TC adopted not to take that approach, but I thought I'd submit these as my individual opinion in the interest of sharing them and starting discussion. In #730978, the Technical Committee was

Bug#830978: Browserified javascript and DFSG 2

> "Neil" == Neil Williams writes: >> > * The point of having the source code (with an appropriate >> licence > etc.) is so that all our contributors, downstreams, and >> users are > able to modify the code and to share their >> modifications with each >

Bug#830978: Browserified javascript and DFSG 2

> "Ian" == Ian Jackson writes: Ian> I would like to comment briefly on the general idea about the Ian> TC offering advice and making statements of opinion. Ian> If someone in authority in the project, such as a maintainer of Ian> the

Bug#830978: Browserified javascript and DFSG 2

Hi. Speaking as an individual TC member, here's my personal reading of the TC discussion. It's not clear that the TC is the right body for this discussion. We certainly could offer advice, but it's not clear that the ftpmasters or release team--the parties most likely to need such advice--

Bug#830978: Browserified javascript and DFSG 2

> "Paul" == Paul R Tagliamonte writes: Paul> Traditionally, ftpteam has had to take this role, since it is Paul> the body that decides if an upload is fit for main. Paul> I am one of those folks that treat minified JS as binary, Paul> since things like

Bug#830978: Browserified javascript and DFSG 2

So, my first question is whether this is a matter that it's reasonable for the TC to rule on. I definitely think we're not an appropriate body to rule on a question like whether a particular license is DFSG free. However, here we're asked to give advice on whether something is source code.

Bug#830796: pidgin-otr: You don't have OTR link could be more useful to debian users

Your proposed format string replacement looks good. I don't have the available time to start a conversation with upstream about the OS detection etc. I was just reporting a wishlist bug because I ran across this helping a user. I think the format string fix is likely to be a good compromise

Bug#830796: pidgin-otr: You don't have OTR link could be more useful to debian users

Package: pidgin-otr Version: 4.0.2-1 Severity: wishlist Almost all the users at our company are Debian users. If you don't have pidgin-otr installed, your are linked to https://otr.cypherpunks.ca As a co-worker just pointed out to me it's really hard to get from there to finding that you want

Bug#830344: How should the TC help with a project roadmap?

Here are my thoughts on the road map and TC involvement. There is value in two levels of thing: * Goals that we've committed totrying as a community. For these, RC bugs or NMUing a package are valuable. At this level it's desirable to have review of the plan to achieve a goal. It's

Bug#830213: tracker.debian.org: Accessibility regressions over old pts

> "Raphael" == Raphael Hertzog writes: Sort of. First, that didn't make it clickable. In general, I'd expect focusing on a button and pushing space to activate the button. Enter sometimes activates a default action for a form, and definitely is the wrong keyboard

Bug#830667: speechd-el: Fails to honor XDG_RUNTIME_DIR

Package: speechd-el Version: 2.7-1 Severity: grave Justification: renders package unusable In modern gnome at least, speech-dispatcher's socket lives in XDG_RUNTIME_DIR, which is rooted at /run/user/uid. This package seems hard-coded for unix sockets in the user home directory, so it doesn't

Bug#830213: tracker.debian.org: Accessibility regressions over old pts

>>>>> "Raphael" == Raphael Hertzog <hert...@debian.org> writes: Raphael> Hi Sam, Raphael> On Fri, 08 Jul 2016, Sam Hartman wrote: >> Now I can interact with the toggle details string, but nothing >> happens when I do. Since yo

Bug#830213: tracker.debian.org: Accessibility regressions over old pts

Now I can interact with the toggle details string, but nothing happens when I do. Since you've made it a link, I'm going to interact with it that way. Are you expecting it to be clicked on rather than selected as a link? Other accessibility problems: * The page is hard to navigate. There are no

Bug#830213: tracker.debian.org: Accessibility regressions over old pts

>>>>> "Raphael" == Raphael Hertzog <hert...@debian.org> writes: Raphael> Hi Sam, Raphael> On Thu, 07 Jul 2016, Sam Hartman wrote: >> The new tracker is significantly less accessible using the Orca >> screen reader on firefox th

Bug#830213: tracker.debian.org: Accessibility regressions over old pts

Package: tracker.debian.org Severity: important Hi. The new tracker is significantly less accessible using the Orca screen reader on firefox than the old PTS. The big problem is that I cannot find a way to easily expand the collapsed tabs, so I cannot get to most of the information. to

Bug#829749: krb5-kdc-ldap: kerberos.schema.gz is a config file

I'm not entirely sure either. One thing to consider is that Debian's openldap doesn't typically use schema files; it instead uses the ldap configuration schema, so you'd need to produce an ldif of the schema and submit that to Kerberos. That is in fact a major pain and I'm open to thoughts about

Bug#829704: Voting for TC Chair

The ballot is the following: ===BEGIN=== The chair of the Debian Technical Committee will be: A: Andreas Barth B: Don Armstrong C: Keith Packard D: Didier Raboud E: Tollef Fog Heen F: Sam Hartman G: Phil Hands H: Margarita Manterola ===END=== I vote d > c=e=f=g >h > a=b sign

Bug#829671: krb5-config: debconf seeding is not working when installing/reconfiguring the package

In general, the krb5 configuration should respect values already in /etc/krb5.conf if there is an existing krb5.conf on the system, and the values from that file will override preseeding. That's according to debian policy and I can look up the reference if you'd like. However, if there is no

Bug#822803: Call for votes for new TC member

> "Didier" == Didier 'OdyX' Raboud writes: Didier> Dear TC members, I hereby call for votes on the following Didier> ballot to fill the vacancy in the TC. The voting period Didier> starts now and lasts for up to one week, or until the Didier> outcome is no

Bug#829044: krb5-admin-server failed to start because of read-only filesystem

This doesn't sound like a bug to me. You modified the krb5 configuration to log to /var/log/kadmind.log, but didn't make the corresponding change to the systemd unit. krb5 by default logs to syslog; if you chose to configure your system that way it would work as shipped. Am I missing something?

Bug#828946: krb5: FTBFS in testing (LaTeX Error: File `iftex.sty' not found)

For my notes, iftex.sty is in texlive-generic-extra on my system. I did the most recent build for sid in a chroot including the arch all packages, so it's more likely to be something changing than a then-missing-build-dep-indep, but I'll take a look while at Debconf.

Bug#827208: libgssapi-krb5 changes versions for some functions in .symbols

source: krb5 source-version: 1.14.2+dfsg-1 > "Lars" == Lars Uebernickel writes: Lars> Package: libgssapi-krb5-2 Version: 1.14.2 Lars> Dear maintainers, Lars> Some functions in libgssapi-krb5-2.symbols have different Lars> versions than they did in 1.10.

Bug#825952: nmu: libauthen-krb5-admin-perl_0.17-1

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu libauthen-krb5-admin-perl_0.17-1 . ALL . -m "rebuild for new krb5 admin libs" as part of krb5 transition. -- System Information: Debian Release: jessie/sid APT prefers

Bug#825951: nmu: pam-krb5-migrate_0.0.11-3

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu pam-krb5-migrate_0.0.11-3 . ALL . -m "Rebuild for new krb5 admin libraries" As part of the krb5 transition. -- System Information: Debian Release: jessie/sid APT prefers

Bug#825950: nmu: krb5-sync_3.1-1

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu krb5-sync_3.1-1 . ALL . -m "Rebuild for new krb5 admin libs" NMU for krb5 transition. -- System Information: Debian Release: jessie/sid APT prefers stable-updates APT policy: (500,

Bug#819017: kadm5.acl stub should be provided as is

Hi. I took a look at this in preparation for the 1.14.2 update. Unfortunately, I can't really do what you ask and ship kadm5.acl as a conffile. to be a conffile, in the usual case, the file needs to not be modified from what the package ships. However, by default we currently ship a version

Bug#823096: krb5-kdc, krb5-admin-server: fail to listen on IPv6 addresses ("Cannot request packet info")

I'd expect this to be fixed with a newer krb5. It's hard to get to pktinfo6 without defining _GNU_SOURCE. So, I'd definitely expect this is fixed in experimental and probably sid. Unfortunately, there were concerns about turning on _GNU_SOURCE for the version of krb5 in jessie.

Bug#824609: aptly: with architectures specified in config file source indexes are not generated

Package: aptly Version: 0.9.6-1 Severity: normal Hi. I noticed that even though I included --with-sources=true in my mirror create when I published the snapshot, source indexes were not being generated, even though .dsc files were being included in the public pool. The issue seems to be that I

Bug#821361: Voting for CTTE Chair

A: Don Armstrong B: Andreas Barth C: Phil Hands D: Sam Hartman E: Tollef Fog Heen F: Keith Packard G: Didier Raboud ===END=== I vote g>B=E>F=D=C>A for TC chair. pgpjaqMmOsHJ3.pgp Description: PGP signature

Bug#819017: kadm5.acl stub should be provided as is

Policy says that one package can't mess with another package's configuration. That is, it's not really OK from a policy POV for anything besides krb5 to mess with the configuration files for krb5. However, you can of course coordinate other things. I can dig up specific citations if you'd like.

Bug#819017: kadm5.acl stub should be provided as is

Not really. The acl is clearly not a conffile, because there is no default that is correct for a majority of sites. So, it's not appropriate to ship in a package, but instead should be created by a postinst somewhere. (I've been planning to get rid of krb5_newrealm and move realm setup into

Bug#816548: krb5: [INTL:de] Initial German translation

control: tags -1 -moreinfo O, you're talking about upstream translations for the source (error messages), not for debconf. I'm sorry. Thanks very much, and yes I do know what to do with this.

Bug#816548: krb5: [INTL:de] Initial German translation

control: tags -1 moreinfo I'm confused. krb5 has had a de.po for several years. Why are you sending in an initial po again?

Bug#815677: krb5-kdc: kdb5_util fails to load propagated database under heavy load

> "Christopher" == Christopher Odenbach writes: Christopher> Hi, Christopher> Any chance to see this small change in jessie? I think it would be a good idea, but realistically unless I'm preparing another jessie update I probably won't get to it. I don't

Bug#815677: krb5-kdc: kdb5_util fails to load propagated database under heavy load

I've merged the patch into the 1.14 upload I'm preparing.

Bug#813126: Fixes for stretch?

I have an upgrade to 1.14 (plus these patches and a few others) sitting on the experimental branch of the git repo. I had be planning to push that to experimental and then if there were no problems through to sid and stretch. I had not been planning to make a specific upload to sid. I guess it

Bug#812131: krb5: Please package 1.14 (willing to provide assistance)

Hi. I've pushed an experimental, upstream and pristine-tar branch. I think the package is more or less ready to build for experimental, except that I'd like to merge in the patches to splint out slave support into its own package and to include init scripts there. I've picked up most of the

Bug#812131: krb5: Please package 1.14 (willing to provide assistance)

I've done the import and rebase and have confirmed the result builds. I need to adjust symbols files, pull in a few patches from the 1.14 branch, etc. But progress is happening here.

Bug#812131: krb5: Please package 1.14 (willing to provide assistance)

Hi. I hope to get to this in the next week or so; sorry about the delay.

Bug#813126: krb5: Memory leak caused by supplying a null principal name in request

How can a memory leak be grave?

Bug#808293: freeradius stopped working after kernel upgrade

control: -1 severity important I'm not sure what the best way to avoid freeradius being pulled out of jessie is besides dropping the severity. If tagging it wheezy and bringing the severity back up would work feel free to do that. Is anyone seeing this with jessie or is this a wheezy-only issue?

Bug#806928: krb5-kdc: Remove DES from supported_enctypes in default kdc.conf

I tend to agree with the change you propose. However, note that the DES keys are harmless with allow_weak_crypto set to false. They won't be used. The advantage of the current configuration is that if you discover you need DES, you can turn it on without rekeying your realm. That said, you don't

Bug#806928: krb5-kdc: Remove DES from supported_enctypes in default kdc.conf

> "Benjamin" == Benjamin Kaduk writes: Benjamin> I'm not really sure that the Debian packaging should even Benjamin> be in the business of setting default supported_enctypes Benjamin> (or other things, perhaps). Upstream seems to be doing Benjamin> okay at it,

Bug#804093: krb5-clients: Error message from telnet.krb5 is strange

You should be aware that Debian 7.x is the last version of Debian that has krb5-clients. The package has been desupported and is no longer maintained and has been removed from future versions of Debian. The Kerberos telnet application is insecure. While I don't know of specific security problems

Bug#803962: config-package-dev: Requires leading slashes in debian/*.displace

Package: config-package-dev Version: 5.1.2 Severity: normal Hi. According to the dh_configpackage man page, the paths in debian/*.displace need not have a leading slash, just like other debhelper inputs. However, the code generates errors like the following if you leave out the leading slash.

Bug#803083: CVE-2015-2695 in libgssapi-krb5-2, SPNEGO context aliasing

Do I need to do anything here? I have availability this evening and Wednesday evening.

Bug#803083: CVE-2015-2695 in libgssapi-krb5-2, SPNEGO context aliasing

Also, do you want to fix the not a DD problem?

Bug#775277: should we split krb5-kpropd into a separate package?

I'm sorry. I thought I had responded long ago on this, but apparently not. I think the package split makes sense.

Bug#707851: Debian Menu Systems : Implementation of the TC decision

>>>>> "Wouter" == Wouter Verhelst <w...@uter.be> writes: Wouter> On Tue, Oct 13, 2015 at 07:56:03AM -0400, Sam Hartman wrote: >> >>>>> "Wouter" == Wouter Verhelst <wou...@debian.org> writes: >>

Bug#707851: Debian Menu Systems : Implementation of the TC decision

> "Wouter" == Wouter Verhelst writes: Wouter> So, I'm with Guillem on this one. Wouter> But _forbidding_ maintainers who want to from shipping a Wouter> second file, if that somehow makes the experience of menu Wouter> users better than what the fdo menu

Bug#707851: Debian Menu Systems : Implementation of the TC decision

> "Didier" == Didier 'OdyX' Raboud writes: Didier> Le mardi, 13 octobre 2015, 08.55:07 Wouter Verhelst a écrit Didier> : >> But _forbidding_ maintainers who want to from shipping a second >> file, if that somehow makes the experience of menu users better

Bug#595817: pam-ssh-agen-auth deb package

I have not looked at the specifics of this package. I know that I want something that has a similar user interface for sudo. I have no idea though whether this implementation is any good and don't have time to investigate.

Bug#801065: Section 6.4 - discourage failing install or upgrade when service fails to start

> "Marvin" == Marvin Renich writes: Marvin> As discussed on debian-devel starting at [1], I would like a Marvin> comment added to Section 6.4 "Best practices for maintainer Marvin> scripts" that recommends preventing the postinst script from Marvin> returning

<    2   3   4   5   6   7   8   9   10   11   >