> "Ole" == Ole Streicher writes:
Ole> We already have more that 5700 popcon-counted installations
Ole> with the blends selection in the installer. This should give
Ole> some base for that.
Hi.
Speaking with my TC hat on.
I don't find quoting popcon stats useful. You've used them
Is our intent to override the maintainer or provide advice?
I don't care what the answer is but perhaps we want to be clear.
I'm fine with this ballot beyond that.
Perhaps we want to override the blends-tasks maintainers to the extent
that they disagree with the tasksel maintainers?
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.
My understanding of the current plan is that we're adding openssl 1.1.0
to unstable, but will make a decision about whether to drop libssl1.0.2
later.
That's really frustrating for the rest of the ecosystem--our users and
our upstreams, and I'd ask the release team to commit now to 1.0.2 being
av
> "Sebastian" == Sebastian Andrzej Siewior writes:
Sebastian> control: tags -1 patch
Sebastian> On 2016-06-26 12:23:04 [+0200], Kurt Roeckx wrote:
>> OpenSSL 1.1.0 is about to released. During a rebuild of all
>> packages using OpenSSL this package fail to build. A log of th
>>>>> "Sebastian" == Sebastian Andrzej Siewior writes:
Sebastian> 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
> "Chris" == Chris Leick writes:
Chris> Package: krb5 Version: 1.14.3+dfsg Severity: minor Tags: l10n
Chris> Hi,
Chris> I've seen, that the German translation isn't included in
Chris> version 1.14.3. Is there an issue with the translated file?
Chris> Please let me know,
package: fai
version: 5.2
severity: wishlist.
FAI has a great feature in the class directory that allows a
configuration space to infer classes from things such as the installed
hardware.
This is not currently available from fai-diskimage.
I'd really like to have a feature like that for fai-diski
package: lvm2
version: 2.02.167-1
This bug is opened to document some problems discovered in an IRC
conversation on #debian-devel between Sam Hartman and Bastian Blank
The problem seemed to be that often (although not in all the time in
Sam's experience)
lvcreate --type raid5 -L 12
Hmm.
So, first, the file refers to a modified copy of the Alladin free
public license, from a kit for implementing filesystems.
I'm kind of boggled that someone would start from the Alladin license,
but since I have no idea what modifications they made, I have no idea
whether it's free.
However t
To be clear I've contacted upstream off-list and we'll see what we find
in the next few days.
> "Ron" == Ron writes:
Ron> Hi OdyX,
Ron> On Wed, Nov 16, 2016 at 03:23:47PM +0100, Didier 'OdyX' Raboud wrote:
>> Hi there,
>>
>> I've been mostly VAC, and only now found enough time to properly
>> read through this bug log. In the interest of transparency and to
I'd really like to see the TC offer at least the following advice:
1) We believe that strong evidence is required to hold back integrating
new versions of software like global. The burden of proof is on those
who propose not to update, not on those who would like Debian to contain
current upstr
Like you I want to see global6 for stretch.
I'm not sure I want to see it bad enough to override someone.
I'd rank doing so above FD though but below a pure advice option.
>>>>> "Ian" == Ian Jackson writes:
Ian> Sam Hartman writes ("Bug#841294: Global Ballot Thoughts"):
>> Like you I want to see global6 for stretch. I'm not sure I want
>> to see it bad enough to override someone. I'd rank do
> "Ian" == Ian Jackson writes:
Ian> I know that you do not _set out_ reinforce Ron's position of
Ian> power over his victims. That is not your goal. You are trying
Ian> to come to an amicable settlement. You are trying to get
Ian> everyone to be nice.
Ian> But when peo
So, does someone want to propose a resolution so we can move this
forward?
> "Chris" == Chris Leick writes:
Chris> Hi,
Chris> It seams, that the German translation isn't included in
Chris> version 1.15-1. Is there an issue with the translated file?
Chris> Please let me know, if I can help. The
You filed a substantially similar bug on the previous
So,
can we (Debian) support SSL 1.1 with Shibboleth?
That is, are the patches something you're comfortable integrating as
Debian?
So, what impact does having blends-tasks have besides wasting disk
space.
It adds tasks to the installer menu. Are those tasks we want on all
system installs or not?
If this is purely about disk space, I think it's less of an issue than
if it provides a bad user experience.
For what it's worth, I think the policy question here is not a
significant one.
Holger is right that we should either fix policy or fix both
(tasksel-data and blends-tasks).
I think that is a bug that should get hashed out. I don't think it is
all that timely, and I don't think it matters much ho
package: dpkg
version: 1.18.10
Hi. For a non-debian archive, I've been packaging up some disk images
into debian packages, because we tend to use debs for software
distribution.
It's not working very well.
When I run dpkg -x hadron-installer-efi_0.10_all.deb /tmp/foo,
I get
root@mini-buildd:/tm
Hi.
I'd really appreciate comments from debian-release on this issue.
Would debian-release like us to take this up?
If so, I have a proposal for how to fast-track this situation, but I am
only comfortable doing that if the release team is involved.
Hi.
As you are probably aware, the question of what to do about linking on
mips and stretch has been referred to the TC.
There's a reasonable probability that we're going to want to move very
quickly on this issue, and I wanted to reach out to you and see how we
could best work with you to colle
>>>>> "Lisandro" == Lisandro Damián Nicanor Pérez Meyer
>>>>> writes:
Lisandro> On miércoles, 11 de enero de 2017 09:39:25 ART Sam Hartman wrote:
>> Hi.
>>
>> As you are probably aware, the question of what to do abou
I'll note that the practice of hard-coding paths is fairly common.
One common cause for this is programs that don't want to rely on PATH
for calling exec. Systemd is a particularly interesting example.
ExecStart and related arguments in systemd units are required to include
full paths.
I am ver
I heard back from doko today. We can expect a reply tomorrow. We also
talked briefly about the issue.
Realistically, i cannot imagine the TC coming to any final decision on
something like this in under three weeks. That timeline seems fairly
aggressive actually.
However, I think the TC could
> "Ian" == Ian Jackson writes:
Ian> You should explicitly state whether you want this NMU to be
Ian> DELAYED.
Good point.
I think we don't want a delay.
Updated the ballot in git.
As a FYI, Matthias wrote to me in IRC just now indicating that he plans
to upload a patch in the next couple of days.
(He needs to get to the location where he has the right environment
before preparing the upload).
As such, I'm planning on holding off on calling for any votes.
> "Josh" == Josh Triplett writes:
Josh> As another technical alternative, which I haven't seen
Josh> mentioned elsewhere in this thread or related bug reports:
Josh> when I need to override a packaged binary or file temporarily
Josh> for debugging purposes, without forgetting
Dear Matthias:
Hi. As I understand our IRC conversation, you asked me to keep the TC
bug regarding mips binutils open even after your upload.
First, I want to confirm that understanding.
Second, what are you hoping for from the TC at this point? I think
you've resolved the issue that came to
I posted this to the wrong bug, now reposting:
Dear Matthias:
Hi. As I understand our IRC conversation, you asked me to keep the TC
bug regarding mips binutils open even after your upload.
First, I want to confirm that understanding.
Second, what are you hoping for from the TC at this point? I
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 w
>>>>> "Sam" == Sam Hartman 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, not to the bug.
Apologies for the
> "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 tend to use it in that
> "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
>> raising this to "serious".
Rapha
> "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 that's what you were trying to
> "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 orphan 2.x someone m
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
h
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 expecte
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)
m
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 jo
>>>>> "Dmitry" == Dmitry Smirnov 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 directory inside the cache, *not*
>>>>> "Stephan" == Stephan Sürken 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.17.1-1
Stephan> fwi
> "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 &&mv tmp config-blob
>> Undefined subroutine
Yeah, thanks for reminding me of this.
I had intended to apply it from the launchpad bug but just forgot.
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 system
> "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> /etc/resolv.conf for images base
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 that'
control: retitle -1 kdb5_util hangs forever on 32-bit systems
--Sam
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 si
Hi.
Apologies for the delay.
I plan to fix this issue this weekend.
For debian, is there any reason not to build krb5 with
_LARGEFILE_SOURCE?
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 i
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 compl
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.
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
Does the e2fsprogs in jessie produce an image that works with syslinux
and vmdebootstrap?
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 c
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
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)
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
perhaps
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.
> "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
>> >
>> > * Package name:
>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 Dis
>>>>> "Sam" == Sam Hartman 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 part of the regular
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
>>>>> "Ian" == Ian Jackson 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 might know the answer off
>
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
re
>>>>> "Ansgar" == Ansgar Burchardt 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 current policy for init scripts, quo
> "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 considered that the burden
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
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 that
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 wit
> "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 are things we cou
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 do,
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)
> "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 longer in doubt.
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 krb5.
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
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 ho
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 repro
>>>>> "Raphael" == Raphael Hertzog 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 than the old PTS. The big pr
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
>>>>> "Raphael" == Raphael Hertzog 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 you've made it a link, I&#
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 wo
> "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 approach to pushing a butt
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 frustrin
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
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
betwe
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. Is
> "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 removing comments and r
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-- would
> "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 ftpmasters or the release team, is doing
> "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 > other, with Debian, and
I wanted to briefly summarize an irc conversation we had on
#debian-devel for anyone reading this bug.
In general, we want to get rid of libpam0g as soon as possible, because
you cannot have both libpam0g and libpam0t64 installed at the same time.
Steve is working on a series of NMUs to make tha
> "Helmut" == Helmut Grohne writes:
Helmut> I believe pam will have to be reverted and implemented as
Helmut> dual ABI instead.
I'm not very comfortable with this approach.
The tentative patch did not fill me with confidence; my gut is that it
was not as robust as an approach that li
> "Colin" == Colin Watson writes:
Colin> in those doc-base files but are in fact missing. I don't
Colin> know whether this is intentional (in which case the doc-base
Colin> registrations should be removed to match), or an accidental
Colin> build issue that should be fixed.
I
package: pam
version: 1.5.3-5
severity: serious
This version of pam drops pam_userdb which can break systems that use
pam_userdb in their configuration. Long term we do want to split it out
and possibly drop. However, this change is purely for the time_t
transition and will be reverted.
This ve
> "Christoph" == Christoph Anton Mitterer writes:
Christoph> Do you happen to know whether there's anything needed in
Christoph> terms of clean up for people who had already upgraded
Christoph> now? Like manually doing whatever was done via the
Christoph> runuser?
I think that
501 - 600 of 1339 matches
Mail list logo
