r 50 RC bugs only for packages
> already in etch, just for renaming apache2-common to apache2.2-common.
> Is/Was that really necessary?
Yes, modules built for Apache 2.0 will not work with Apache 2.2. They
have to be rebuilt.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie
fffd
Could you send the entirety of the oops? Thanks!
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Russ Allbery <[EMAIL PROTECTED]> writes:
> Andree Leidenfrost <[EMAIL PROTECTED]> writes:
>> Package: openafs-modules-source
>> Version: 1.4.2~fc4-2
>> Severity: important
>> Hi Russ again,
>> Sorry for being a pain.
>> I've just buil
on to specify whether you
want forwardable tickets by default. Add:
forwardable = true
to the [libdefaults] section of your krb5.conf if you want programs
requesting Kerberos tickets to get forwardable ones.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagl
seen one, and
interface specifications are not copyrightable under US law.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: apache2.2-common
Version: 2.2.3-1
Severity: grave
Justification: renders package unusable
apache2.2-common won't install, at least within a pbuilder chroot.
The postinst aborts with the following error:
touch: cannot touch `/var/log/apache2/error.log': No such file or directory
touch: ca
Frank Burkhardt <[EMAIL PROTECTED]> writes:
> On Mon, Oct 02, 2006 at 12:53:37PM -0700, Russ Allbery wrote:
>> I don't think it's appropriate to make this sort of policy decision in
>> the module. This is why there's a krb5.conf option to specify whethe
t's going
to be to fix. We're not sure yet whether it's specific to AMD64 or
whether it's any not-i386 system.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
he exception of some older ones that predate the current copyright
policy) and cannot be distributed in main.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ring to that one. Which is kind of silly.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
pstream. I'd thought it was only a Mac OS X
problem but it was actually cross-platform. I'm applying the relevant
delta now and will be uploading new packages shortly.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, emai
etty clear that he either completely
missed the point or didn't get the point.
> things can be distributed according to the License granted by the
> copyright holder.
Yes, and the license in this case is non-free, so it's good that the
material wasn't copyrightable in the fi
install openssh-server and openssh-client directly
+ and remove this package. Just make sure that /etc/ssh/sshd_config
+ contains:
+
+GSSAPIAuthentication yes
+GSSAPIKeyExchange yes
+
+ if you want to support GSSAPI authentication to your ssh server.
+
+ -- Russ Allbery <[EMAIL PROT
eople to the relevant RFC,
and then remove the IESG license as well.
For core.schema, there's only one comment that probably isn't long enough
to be anything other than fair use, but some of the other schemas contain
much more substantial comments.
--
Russ Allbery ([EMAIL PROTECTED
ed (and I would have
thought it would be a change warranting a minor version increase).
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
r me. New package being uploaded
momentarily (I'd have you test beforehand this time to be sure, but since
I now have a presumably equivalent test environment, I'm more confident in
it this time).
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
with openafs-modules-source 1.4.2~fc4-2.
I'm about to upload a new version with a patch that works for me on a
AMD64 2.6.18 (and fixes some other problems).
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
w
it appears to do the right thing
with a NULL context, so I'll go ahead and make this change.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Douglas E Engert <[EMAIL PROTECTED]> writes:
> P.S. I got the PKINIT code in PAM working this afternoon too. There are
> some questions about how the MIT code will handle PKINIT. I will send a
> note to you, MIT Heimdal and UMich on this tommorrow.
Excellent! Thank you.
-
custom --section main
I'll update the man page to be clearer about how lintian constructs the
path to the package repository.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
but contains little of use in actually verifying the
contents of the control file. At least a syntax specification would seem
to be in order here.
Is the intention for cli-policy to eventually become a subpolicy of the
main Debian Policy manual?
--
Russ Allbery ([EMAIL PROTECTED]) &
hard time seeing what damage could be caused by lintian recognizing it,
other than maybe a wasted upload.
I have a sneaking suspicion that if we do recognize it, we'll immediately
get a request from someone to stop recognizing it since they were using
lintian to remind themselves to change the distr
closing it so that someone else can look at those
reports for inspiration.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
te that nearly all of the RC bugs
would probably go away just by packaging the current version. Upstream is
very active; the current version (0.43 -- Debian has 0.36.2) was released
June 8th.
I'm happy to sponsor uploads of Arla although I don't use it personally.
I'm happy to see more AF
Sebastian Dröge <[EMAIL PROTECTED]> writes:
> On Fr, 2006-08-18 at 18:11 -0700, Russ Allbery wrote:
>> Did this replace netlibs, or is netlibs still also of interest? I seem
>> to recall that CLI and .NET are two different ways of talking about the
>> same general se
martin f krafft <[EMAIL PROTECTED]> writes:
> also sprach Russ Allbery <[EMAIL PROTECTED]> [2006.08.19.0549 +0100]:
>> I have a sneaking suspicion that if we do recognize it, we'll
>> immediately get a request from someone to stop recognizing it
>> s
on interpreter, that should be added to its long description so that
there's documentation that this is an invariant and a promise that won't
be changed later.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Pierre Habouzit <[EMAIL PROTECTED]> writes:
> Le lun 21 août 2006 02:30, Russ Allbery a écrit :
>> If it's really the intention that python-support will always provide
>> a Python interpreter, that should be added to its long description so
>> that there's do
by simply looking for
packages that depend on Python (rather than having to also factor in
packages that use transitive dependencies)?
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: lintian
Version: 1.23.23
Severity: wishlist
Currently, lintian doesn't catch typos like "medim" for "medium" in either
the changelog checks or the frontend *.changes checks for urgency. The
latter at least should be checked; the former may also be a good idea.
-- System Information:
Deb
ries, or possibly even argue
that CDBS should be doing this automatically.
I'd be curious to hear other opinions on this, though. I may be missing
something.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
the next
release of lintian to include versioned variants as well.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
ted by dak.
Could you add support to dput and dupload to see if the Distribution in
the *.changes file is set to UNRELEASED and reject the upload if so?
After that's done, we'll make the change to lintian.
Thanks!
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyri
ontributed to debian in any way, but hope this
> makes a start.
> I ask you to include the translation if it is apropiate und works.
Sure, I'd be happy too. Unfortunately, it looks like it didn't get
attached. Could you resend it? Thanks!
--
Russ Allbery ([EMAIL PROTECTED])
e was
probably intended for packages to depend on when they need time
synchronization but don't care how it happens (for instance, AFS and
Kerberos servers can get fairly unhappy unless their time is
synchronized). However, if it's not being used, probably no point in
keeping
CDIR)$(S)profile.h
+ $(INSTALL_DATA) $(srcdir)/gssapi.h $(DESTDIR)$(KRB5_INCDIR)$(S)gssapi.h
Index: src/include/gssapi.h
===
--- src/include/gssapi.h(revision 0)
+++ src/include/gssapi.h(revision 0)
@@ -0,0 +1,5 @@
+/*
+ * Wrapper so that #include will work without special
allow this, but right now it's really unclear. The right course of action
may be to reassign this bug to doc-base (or to both doc-base and lintian)
and ask the doc-base maintainer to clarify the specification.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle
,
+ the following parts are in sorted order: ~~,
+ ~~a, ~, the empty part, a.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
t doing that. I'm releasing a new
version of remctl that just doesn't declare the struct const, which isn't
my favorite workaround but which seems cleaner than adding a bunch of
casts. It should be uploaded to Debian later today.
Thank you very much for the report!
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
top dependencies.
Sorry about that; the code was supposed to handle this, but was missing a
defined check. Will be fixed in the next upload.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
e for qof before the Debcheck
> becomes an RC bug.
While priority inversion is a policy violation, it has not historically
been an RC bug. Not all policy violations are RC.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to
g-www source: unknown-po-debconf-file debian/po/cs.po.Miroslav_Kure
This is an example of an extra file that, on its surface, seems
legitimate.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Thomas Huriaux <[EMAIL PROTECTED]> writes:
> Russ Allbery <[EMAIL PROTECTED]> (13/09/2006):
>> > W: dpkg-www source: unknown-po-debconf-file debian/po/cs.po.Miroslav_Kure
>>
>> This is an example of an extra file that, on its surface, seems
>>
ing on PPC.
I assume you mean stable here? Testing hasn't been 12.4 for a long time.
Yeah, the gnubg that's in stable is pretty broken in a lot of ways.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
he script look like this, and it should not stop in any runlevel, and
> only be used in runlevel S, and thus do not need any required-stop
> values either:
Yeah, sorry about that. It's already fixed in Subversion.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyr
ess
you depend on it directly there's a possible lurking RC bug there should
debhelper ever change. (Not to mention that it makes automated analysis
easier.)
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: puppet
Version: 0.18.4-1
Severity: wishlist
We have a special local configuration where we'd like to set some
environment variables for the puppetd process and may also need to change
its command-line flags. Could you add something like:
[ -r /etc/default/puppet ] && . /etc/default/pupp
Package: wnpp
Severity: wishlist
Owner: Russ Allbery <[EMAIL PROTECTED]>
* Package name: opensaml
Version : 1.1a
Upstream Author : Internet2
* URL : http://shibboleth.internet2.edu/downloads/
* License : Apache 2.0
Programming Lang: C++
Description
ort of command-line option that overrode a selected tag from the
command line. Would that work for the use cases that you have in mind?
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tes that
symlink but the name of the package being built is libcfitsio3-dev. Just
renaming that file should solve the problem.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubs
d
anywhere that I could see. I've added explicit documentation to the man
page.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
Package: postfix
Version: 2.3.3-1
Severity: minor
debian/templates in the postfix source package marks the default value
for postfix/root_address translatable, and some of the localizations have
translated "NONE" to the appropriate string in that language. However,
the postfix postinstall script
bers and file paths that shouldn't ever be translated.
So I think this is the right thing to do, although we'll see if we get any
pushback after the next lintian release.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
to confirm, this syntax works for type string as well, right? Not
just select and multiselect?
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
also does that, but there may well be some reason why that
wasn't done.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
be addressed by fc4 that I'm about to upload. I'll check
upstream to see about the rest.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Looks like this is indeed fixed in fc4, so we should be okay. I'm
rebuilding and testing on AMD64 (with 2.6.17 -- I don't have a system
running 2.6.18 yet) and then uploading, after which if you could give it
another try, I'd greatly appreciate it.
Thank you for the report!
-
hat should be all you need -- it's fine to run newer modules with an
older openafs-client.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
e new packages are now in the NEW queue.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
libpam-krb5
module from source and trying it out? I've almost finished a new 2.0
upstream release that fixes a bunch of issues, and I'd rather fix this
there than patch the old module.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
7;d much prefer to continue to check for exactly what
the devref says, since that way it's a lot easier to remain consistent.
So if this is wrong, the devref should really change.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: wnpp
Severity: normal
I don't actually use GTimer myself any more, so while I'm happy to continue
doing basic maintenance (the package isn't very much work, although see
below about oustanding bugs) and I wouldn't want to see it removed from
the archive, I'm happy to hand the package over
g of the idle, subtracting off time as appropriate, but gtimer
internally doesn't have the data structures that let one easily do that.
I'm happy to apply patches, but I'm afraid that I'm not likely to have
time to implement this myself in the near future.
--
Russ Allbery (
, this is fixed in the 1.4.2 release candidates, and I've been hoping
1.4.2 will be released soon so that I don't have to try to backport the
fix.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
Bleh, that was a stupid mistake. Thank you very much for the bug report.
I could have sworn I installed the package locally, too, to double-check
those dependencies.
New upload coming shortly.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCR
#x27;s a good approximation.)
In the future, this behavior will hopefully be configurable.
I'll leave the bug open until I get a chance to update the documentation
somewhere to explain this.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To U
security
vulnerabilities, but it's possible to find bugs in just about anything.
Updating numerous copies of that code is not appealing.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
Package: pkg-config
Version: 0.26-1
Severity: minor
In Autoconf output from PKG_CHECK_MODULES in pkg.m4, the "checking for"
message refers to the first argument of PKG_CHECK_MODULES, the variable
prefix, instead of the second argument, the module being checked for.
I've seen this result in strang
Package: systemd
Version: 204-5
Severity: minor
(Wow, the thousands of lines of systemd dump included in bug reports
by default seems a little excessive.)
systemctl status truncates log messages from the journal to
80 columns by default. Some experimentation revealed that --full will
prevent th
se SIGSTOP) should be rare.
Good point. Anything that's using socket activation probably doesn't
really need additional synchronization.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debia
Zbigniew Jędrzejewski-Szmek writes:
> http://cgit.freedesktop.org/systemd/systemd/commit/?id=e213d1a3c3
> http://cgit.freedesktop.org/systemd/systemd/commit/?id=69d918b
Thank you! That's great.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
perience
required to compare the implementations directly yet. I'm hoping to get a
chance to look at it once I finish converting my first service to upstart
and systemd support. I have a package now (kstart) that would benefit
greatly from this for one of its common use cases (running daemons t
a wishlist bug against dpkg perhaps?
I would hold off until we decide which init system we're going with, and
I'm not sure where this belongs. It may make more sense to put it into
dh-systemd and/or dh_installinit.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.o
Tollef Fog Heen writes:
> ]] Russ Allbery
>> It looks like both upstart and systemd don't provide direct mechanisms
>> to manage all instances. The upstart cookbook recommends getting a
>> list of all active services and extracting the list of instances of a
>&
nfiguration (which is quite nice
to do, since it isolates Java applications that may require different
override JARs), you want to restart all of them when you upgrade the
packaged Tomcat.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, ema
and think that's the superior option, but I understand why people don't
always want to do that. Some packages have a history of not cleanly
rebuilding with later versions of Autoconf and Automake.)
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
will work, I believe. I don't think there's an easy way to do that with
split. You'd have to do some complex thing with look-behind assertions.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
which point you
run into the problem that negative look-behind assertions have to be
fixed-length.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: devscripts
Version: 2.13.8
Severity: normal
In order to support file names that contain whitespace, uscan's parsing
of Files-Excluded needs to handle the character escaping protocol. The
following code should correctly handle foo\ bar, as well as the other
more pathological cases such as
ne. (Well, sort of; I was lazy and didn't turn it into a full patch.)
> Kind regards - and it is really fun to have "another technical family"
> so I wish you a merry Christmas as well
*grin*. Yes. Merry Christmas!
--
Russ Allbery (r...@debian.org) <http
Package: valgrind
Version: 1:3.9.0-4
Severity: minor
When valgrind is run with --trace-fds=yes, it reports AF_INET6
sockets open at exit as "pf-10" sockets instead of AF_INET6
sockets, as in this output excerpt:
==1369== FILE DESCRIPTORS: 6 open at exit.
==1369== Open AF_INET socket 5: 127.0.0.1:
suggestion is slightly wrong, and the places where it
has [ ] for a space should actually be \s for any whitespace.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
\
> ])+)/g);
my @excluded = ($filesexcluded =~ /(?:\A|\G\s+)((?:\\.|[^\\\s])+)/g);
and then you can drop the replacement of newlines with spaces, and tabs
should also be handled correctly.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To U
s using tiny enums for this purpose. So:
enum mangle_type {
MANGLE_NOGLOB = 0,
MANGLE_GLOB = 1
};
and then at the call site:
n = unit_name_mangle(e, MANGLE_NOGLOB);
which makes the meaning of that argument immediately obvious.
--
Russ Allbery (r...@debian.org)
Alessandro Ghedini writes:
> On mer, dic 25, 2013 at 02:52:32 -0800, Russ Allbery wrote:
>> Package: valgrind
>> Version: 1:3.9.0-4
>> Severity: minor
>> When valgrind is run with --trace-fds=yes, it reports AF_INET6
>> sockets open at exit as "pf-10&q
doing and how
it's forcing automake-1.13 (and whether that's really needed or automake
1.14 would work fine).
I don't think the solution is to package Automake 1.13, which we just
recently managed to get rid of.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~e
libraries from Automake 1.14? I suspect
something went wrong with updating the alternative for aclocal. I would
try a dpkg-reconfigure automake and see if that fixes it, or at least
produces some interesting output.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle
Package: pan
Version: pan/0.139-2
Severity: minor
I noticed, while looking at something else, that all lines of the
package long description for pan after the first have an extra leading
space. The specification for the package description says that this
makes those lines unwrappable, which leads
Package: upstart
Version: upstart/1.10-2
Severity: minor
While attempting to support an /etc/default file for backward
compatibility, I struggled with finding the right way to import
the environment settings into the upstart job and use them
appropriately. I'm not sure if there's a piece of docum
Package: sysv-rc
Version: 2.88dsf-44
Severity: normal
I have a package with an /etc/default file that implemented the
ill-conceived idea of disabling the service by changing a setting
in that file. I want to migrate away from that approach by
converting that setting into a proper update-rc.d disa
eed significant work
before it could be realistically used in any useful way for network
services in Debian. systemd's support looks ready for widespread
production use right now. I intend to configure my package in the next
upload to use socket activation with systemd if available.
--
Russ
Package: qa.debian.org
Severity: wishlist
Now that the backports archive has been integrated more completely
into the regular Debian archive, it would be great to see uploads
to backports show up in the news section of the PTS.
-- System Information:
Debian Release: jessie/sid
APT prefers testi
ant.
Agreed, with the caveat that I don't think we should discourage upstreams
from adding support for one or both of the synchronization protocols.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
thing that required documentation beyond a note
that it was supported.
Both of these are effectively trivial, and my current intention is to add
support for both protocols to the daemons that I maintain.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUB
he bit of
necessary supporting glue for upstart ended up in lsb-base instead of
init-system-helpers.
It's worth noting that the systemd support in update-rc.d is substantially
better than the upstart support. (There's more about this in my other
message that's being temporarily
Russ Allbery writes:
> For comparison purposes, the *total* burden, from my upstream
> perspective, of the two options was:
> * systemd: 14 lines (8 lines of code, 6 lines of build system)
> * upstart: 12 lines (6 lines of code, 6 lines of documentation)
> Since upstart
lbcd service, specify a command to run for the
# weight and interval, or do round-robin (-R), set the desired flags
# in DAEMON_OPTS in /etc/default/lbcd.
exec /usr/sbin/lbcd -f -l -Z $DAEMON_OPTS
This seems to work and is what I will be uploading.
--
Russ Allbery (r...@debian.org)
temd:/system/lbcd.service
└─3465 /usr/sbin/lbcd -f -l
Dec 28 17:18:11 wanderer systemd[1]: Starting responder for load balancing...
Dec 28 17:18:11 wanderer lbcd[3465]: ready to accept requests
Dec 28 17:18:11 wanderer lbcd[3465]: request from ::1 (version 3)
Dec 28 17:18:11 wan
Russ Allbery writes:
> I have now uploaded lbcd 3.5.0-1 to the archive.
And now lbcd 3.5.0-2, because I completely forgot to add the stanzas to
the systemd unit and upstart configuration file to run lbcd as a non-root
user. Whoops. (And, of course, I noticed one more problem after that
upl
emd package is not necessarily installed. If
we standardized on systemd as the required init system, much of that
complexity could be removed; it's there to be a good Debian citizen and
interoperate with the rest of the archive, including switching back and
forth between different init system
501 - 600 of 6091 matches
Mail list logo
