e than it's worth, and since this library won't add any new library
dependencies to your package, it's really just aesthetic.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@li
fused about version numbers containing more than one dash.)
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.o
cious and internalized.
xsublim uses
instead, I think.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.d
(because
> Policy says all files in /etc are conffiles).
This is only true if you're using debhelper, and from previous messages I
believe the original poster is learning packaging by taking a more manual
approach.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eag
he conffiles in the package.
> OR is there a debhelper command (dh_..) that will trigger that prior to
> calling dpkg-deb
dh_installdeb handles creating of conffiles if you're using debhelper
(compatibility level v3 or higher).
--
Russ Allbery (r...@debian.org) <h
probably unenforcable.
I believe Debian and Fedora use essentially the same policy: we don't
include software with a patent that we think is likely to be enforced on
either Debian or our users. Where that line gets drawn tends to vary a
lot depending on a wide variety of factors, including leg
gt; over the package.
I don't agree. The new version is not eligible for squeeze regardless,
and it seems to me like there's some time to ask Matthias what his
intentions are concerning the package, whether he is interested in
transferring it to a new maintainer, etc.
--
Russ Allbe
chats.)
Is this work targetted at squeeze?
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Arch
romising and it seems like things are now on the
right track.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas
can manually import
the public key into each client using apt-key add. How you obtain the
public key is up to you in that case. Any trusted path works.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mento
Jonathan Wiltshire writes:
> On Tue, Sep 14, 2010 at 08:42:08PM -0700, Russ Allbery wrote:
>> The conventional way to handle this is to build a Debian package that
>> installs the keyring and runs apt-key add, based off of packages like
>> debian-archive-keyring, and
practice it doesn't work. So I
agree with Christoph.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87ocbyu1as@windlord.stanford.edu
g-agent with a five minute timeout, which is long enough to let me
sign a bunch of packages while I'm actively working (plus git tags and so
forth) but short enough that I'm not too worried about an attacker taking
advantage of the cached password.
--
Russ Allbery (r...@debian.org)
ng rewrite into DocBook that I need to commit, so you may
want to hold off doing significant work until I have a chance to deal with
that. I haven't had a chance for some months now, but I have a vacation
starting this weekend and hope to get somewhat caught up on Debian work
during that vac
it should be. Such libraries without SONAMEs can't be represented in
shlibs, which is causing both of the errors that you're getting.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ..
Jordi Gutiérrez Hermoso writes:
> Does it have to be this way? Why do fixes to testing have to go
> through unstable, even during freeze time?
Because otherwise there isn't any good way to test them with a reasonably
large user base, which is even *more* important during the freeze
ibs section because the shlibs
file syntax requires a version number in the SONAME (see Policy 8.6.3).
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscr
are you trying to fix other than that you don't like the name?
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listma
thing actually looks at. All the other things, like the symlinks and
the shlibs entries, then have to match the SONAME that's recorded in the
library.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ..
ntal because you're concerned that it may really be broken and
non-functioning?
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe".
like to have new software in
unstable during the freeze period since they're not very interested in the
stable release, and that's come up before (such as in the CUT
discussions), but as with your note above, this seems most often to be an
argument made theoretically by peop
tall the right kernel headers, ensure that they're always
upgraded when the kernel is upgraded, etc.), so it may be helpful to have
it be fairly obvious that the package is a DKMS package.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE
e at this point, since updates
have broken the buildability of the package in the past five months.)
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscrib
getting it to work with the fglrx and the free versions of the libraries
as well. But not for the next Debian release at this stage, of course.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.
rm drawback that we've accumulated some 3GB
of tarballs in Subversion and the overall Subversion repository is
therefore ginormous.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a s
sible to have
some sort of automagic here. Maybe someone else will know more.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact lis
e 2.6.6-6~bpo50+1 version.
> how can i bypass this error
I suspect you will need to either backport dpkg or remove the (optional)
qualifier that doesn't appear to be supported by stable dpkg (or remove
the symbols file entirely).
--
Russ Allbery (r...@debian.org) <ht
gue that "keeping intact" doesn't require
duplicating in debian/copyright but just not removing the notice from the
source code, but it's easy enough to copy the GPL notice, and I think
better safe than sorry.
--
Russ Allbery (r...@debian.org) <http://www.e
installed the package before, I'm fairly sure you
wouldn't get that message.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe"
ould easily
deal with via /etc/default. I think the current behavior is correct,
particularly given the *substantial* simplicity gain from being able to
treat everything in /etc as a conffile.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUB
roblems of init scripts being configuration files while still
providing the same features).
The effort that would be put into plastering over further problems with
System V init scripts could, I think, be better put into working out the
details of an optional transition to a better init system.
--
ches for fixes, which makes it complex to separate the changes easily
| into individual patches. They are therefore all included in a single
| Debian patch.
|
| For full commit history and separated commits, see the packaging Git
| repository.
--
Russ Allbery (r...@debian.org) <htt
kage
and bump your local version. It's a big pain in the ass, and I
wouldn't do this.
5. Give up on using Debian packages to do this and instead use a separate
configuration management system that doesn't do its work with packages
(something like Puppet or Cfengine). Th
x27;s just strongly
preferred for security support. In this case, it sounds like what was
originally one library has forked thoroughly enough to be four separate
libraries. It's not an ideal situation, but I don't think this should
block adding the software to Debian.
That said, it woul
t fixing this for manual invocations of
debian/rules, you need to instead hook into binary-arch and binary-indep
and stop building the package in the build rule.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-re
packages as
well as the NVIDIA graphics drivers and libraries, and while I don't have
any time to work on NVIDIA packaging myself, I'm happy to do uploads for
others and some package review. Other people on the team may also be
willing to help.
--
Russ Allbery (r...@debian.org)
27;s just a pointer to where you can find the
complete license.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...
e
appropriate packages. If your package follows that model, just omit the
*.la files from all the *.install files, and they won't be part of any
package.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ
according to the GPL itself: "any version ever published."
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contac
ug from people who do
>> not think it belongs in Debian, but I think arguments for having it in
>> Debian are a bit stronger. I have gone ahead and changed the bug to an
>> ITP.
> Great! Thanks for working on this, Nathan.
Yes, thank you. I've been wanting this for
Tanguy Ortolo writes:
> debian/clean
> What is that? I have never seen such a file, is it for a dh command
> I do not know yet? I may be interested for my own packages. :-)
It lists additional files deleted by dh_clean.
--
Russ Allbery (r...@debian.org)
rd to fix,
since the only benefit is some minor cleanliness that users will never
notice.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87lixycw1h@windlord.stanford.edu
format hammered out), so I can quickly find the information I need and
don't have to parse and understand hundreds of different ways of conveying
the same information.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mento
do I have to handle this in debian/libxyz.install?
On Debian, you should always install into lib and never use lib64.
(Eventually, you may want to use the multiarch directory, but it will
still not be lib64.)
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
happen if you run it interactively. If you don't run it
interactively, then it should realize that it can't prompt and just abort.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists
David Bremner writes:
> On Thu, 09 Jun 2011 13:40:54 -0700, Russ Allbery wrote:
>> On Debian, you should always install into lib and never use lib64.
>> (Eventually, you may want to use the multiarch directory, but it will
>> still not be lib64.)
> That was my first
em².
So we should absolutely forbid this in Policy instead of just removing the
requirement. I'll open a bug against debian-policy for this.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
convention for changelog entries for cherry-picks:
* Apply upstream deltas:
- []
- ...
where is the first eight characters of the upstream commit
hash and is the first line of the upstream commit message,
edited as necessary to keep the length of the change
Wolodja Wentland writes:
> On Wed, Jul 06, 2011 at 12:53 -0700, Russ Allbery wrote:
> [ ... ]
>> but for some other packages I want to use some of the files that are
>> generated as part of the upstream tarball release but aren't checked in.
> Ok, this is not necessar
I like
being able to pull down the repository from anywhere and build a new
Debian revision of the package without having to hunt down or download the
original upstream tarball separately. With Subversion, I ended up
checking the upstream tarballs into the repository to accomplish the same
end, b
Policy process, but it's an
*optional* policy. No package will be required to use DEP-5. It won't
even be at the should level. That was part of the original DEP-5
discussion; it's there for people who want to use it, but it's not
something the project wants to stand
e latest config.{guess, sub},
> or is it enough to set the --build and --host options of configure
> with dpkg-architecture?
If you don't use config.guess and config.sub, there's no reason to copy
them into the package.
--
Russ Allbery (r...@debian.org) <http://ww
ate common package
just isn't worth it, and that way the desktop file is only installed when
the command is available.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
wit
rking tricks in battle against APT, but i will
> leave that up to decide for others as IANAD{D,M}.
You can't use disappearing packages with Policy-compliant packages so far
as I can tell, since it would require both packages provide the same
/usr/share/doc directory and changelog file, which is
David Kalnischkies writes:
> On Fri, Aug 19, 2011 at 00:58, Russ Allbery wrote:
>> You can't use disappearing packages with Policy-compliant packages so
>> far as I can tell, since it would require both packages provide the
>> same /usr/share/doc directory and changel
gt; * License : GPL
>Section : net
I think you need to use a bit less generic of a name than that. (Like,
for instance, news-rss-ticker, which would be a fine name).
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSU
C headers.) But there's no obvious reason why that
shouldn't be required given the current Policy wording.
I think this should probably be raised as a Policy bug so that we can
clarify this one way or the other.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/&g
"Bernhard R. Link" writes:
> * Russ Allbery [110822 19:59]:
>> That's a fascinating point. I have never done that with any -dev
>> package, since essentially every -dev package would require that, which
>> seems rather silly. (There are almost no non-trivi
Sune Vuorela writes:
> On 2011-08-22, Russ Allbery wrote:
>> There are not, so far as I know, any exceptions for -dev packages from the
>> normal requirements for Depends, which say simply:
>> The Depends field should be used if the depended-on package is
>>
be to write an explicit exception into
Policy saying that C -dev packages do not have to declare dependencies on
any package that's part of build-essential.)
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors
seems like it could pose any problem, and it's going to be pretty
rare for that to be any sort of issue since C -dev packages aren't likely
to care about dpkg-dev one way or the other.
Note that I explicitly said, and meant, "part of build-essential," not "in
the
"Bernhard R. Link" writes:
> * Russ Allbery [110824 19:34]:
>> -data packages *should* depend on the non-data package in an ideal
>> world, and the only reason why they don't is because circular
>> dependencies are a bigger problem. But -data packages a
mdall/)
That's an unfortunate upstream name, given the conflict with the existing
Heimdal package (which is a long-standing implementation of Kerberos).
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@li
ill happen,
at least in the near future. Job control in portable Bourne shell isn't
up to it.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscr
t as soon as
possible.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87ehy8ayoj@windlord.stanford.edu
some things, too (although with it
merging is sufficiently painful that I really don't want to use it for a
problem involving merges).
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
w
wkward, and once one
invests in the one-time tool configuration effort required to separate the
two release flows, generally unnecessary.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
the VCS and
> the Debian archive of binary packages.
There are very good reasons to favor some sort of 3.0 (VCS) source
format. But using 3.0 (native) as a stand-in for that causes problems
because it breaks various assumptions about the meaning of a native
package.
--
Russ Allbery (r...@deb
rect solutions
to technical problems. If we want to use a source package format similar
to 3.0 (native) for non-native packages, we should define such a format,
not abuse the native package format for that purpose and lose the
meaningful distinction between a native and a non-native package.
--
Russ Al
of the reasonable and non-extortive ones, this
certainly should be (in part) up to the BTS admins. Any black list that
Debian uses I'm sure Debian has the local ability to override.
Starting upstream is probably the right move, but contacting the BTS
admins about it isn't unreasonable.
history without changing what the previous maintainer
> did?
Lintian will ignore all changelog entries below the line:
Old Changelog:
with no leading whitespace in the changelog file. This is intended to
allow preservation of historic entries that are not formatted correctly
for the current s
is documented in the section for
> syntax-error-in-debian-changelog perhaps it only works for syntax errors?
> Is this a bug or a feature?
I think it's a bug. Could you open a bug on Lintian about that? Thanks!
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/
r more than just normal static or global
variables).
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@list
ioned URL currently available
that takes you straight to the current text of the document. However, I
may have missed something.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
wi
forces of wishful thinking and forward progress
Looking at the history, it's probably referring to the ongoing problem
that one can't really use Build-Depends-Indep without a lot of trouble
because the buildds run build, not build-arch.
--
Russ Allbery (r...@debian.org)
ols file (symbol tag optional), and then the symbols generation won't
care if it appears and disappears.
You have to do that for some things with C++, since there are places where
C++ just doesn't give you control over what symbols are exported.
--
Russ Allbery (r...@debian.org)
Thomas Weber writes:
> On Fri, Jan 06, 2012 at 05:14:32PM -0800, Russ Allbery wrote:
>> If it's a private symbol not intended to be used by clients and that
>> wouldn't naturally be used by clients, you can mark it optional in the
>> symbols file (symbol tag
g the ViewVC URI, which I didn't realize
would work but which does seem to be versioned (even though Lintian
doesn't know about it).
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.or
Marco (the package maintainer) specifically said that he wanted to handle
the update in:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690128#95
That's why I didn't offer to sponsor this upload. Admittedly, he's not
gotten a chance yet, and it's been a little b
and to upload with a changelog
entry that starts with:
* Upload to unstable.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Troubl
comes from
shlibs/symbols, which won't take into account restrictions on the build
dependency.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsu
should use at least trivial symbol
versioning that assigns all symbols a version that changes with the
SONAME.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsub
ture. The
> dual-repository approach remains relevant if upstream is on CVS or SVN
> and the Debian packages are to be maintained with git.
Indeed, that's part of why I haven't revised my notes yet. Both methods
really need to be explained.
--
Russ Allbery (r...@debian.org)
e the upstream VCS history
> in your Debian repo.
You can, but I've not found it particularly useful. Mileage may vary, of
course, but when upstream isn't using Git, the annoyance of dealing with
the translation layer and the various weird conventions used in other
VCSes has rarely se
pristine-tar and let it do its thing for subsequent uploads.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lis
Andreas Rütten writes:
> schrieb Russ Allbery :
>> Yeah, I agree. That's partly what I was trying to do with my notes,
>> but they need more revision, and I wouldn't at all mind the content
>> being copied somewhere that's more generally editable so that oth
ers in this directory
> but I never heard of this strategy on the Debian wiki.
That's mostly because multiarch for -dev packages isn't really
well-documented yet. But I believe this is the right approach.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~e
Thomas Moulard writes:
> On Tue, May 14, 2013 at 9:56 AM, Russ Allbery wrote:
>> Thomas Moulard writes:
>>> A package I maintain contains a configuration header (vpConfig.h)
>>> which differ depending on the architecture we are (here the
>>> dependencies
d therefore won't be able to use the
upstream distribution verbatim.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
Felix Natter writes:
> So I add a download rule:
> get-orig-source:
> uscan --force-download --repack
> and use the result as input to git-import-orig and everything should be
> ok?
Yup, that's what I'd do.
--
Russ Allbery (r...@debian.org) <
ate as needed
% cd ..
% debsign *.changes
# the previous step requires you have a GnuPG key set up
They're now ready to upload, which you probably want to do with dput. If
you're uploading it to mentors, see the mentors documentation for the
correct dput configuration and tar
ey are
particularly obscure, if they are only useful for very specific purposes
(such as all debugging symbol packages), or if they conflict with packages
with a higher priority (such as alternative implementations of the same
functionality).
--
Russ Allbery (r...@debian.org) <http
ication in README.Debian; it's not entirely satisfactory, but
sometimes there isn't another good option.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscri
T o n g writes:
> On Tue, 25 Jun 2013 20:45:15 -0700, Russ Allbery wrote:
>> The typical thing to do in this sort of situation is to document the
>> required modification in README.Debian; it's not entirely satisfactory,
>> but sometimes there isn't another good
ogram or
configuration file and includes such things as architecture-independent
libraries").
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". T
ase, you can safely consider it legal boilerplate and ignore it.
I suspect the problem in this case is the lack of some accompanying clear
license statement.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-r
.org/type1nondfsg
Seems weird to have it in a favicon, though.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@
rt version for most packages is "use dh_apache2".
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.
nk thats true. As long as you care about
> backporting your package to stable, 2.2 should still be considered.
You pretty much have to branch to support both. The packaging is
substantially different.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
T
Alexander Wirt writes:
> On Tue, 23 Jul 2013, Russ Allbery wrote:
>> You pretty much have to branch to support both. The packaging is
>> substantially different.
> I have several packages working well for 2.2 and 2.4. At least for
> webapps, it is possible.
Hm, how do you
501 - 600 of 707 matches
Mail list logo
