tream breaks that guarantee and the SONAMEs diverge.
--
Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
ices just want us to
preserve whatever notice upstream decided to write.
There's generally no useful purpose served in trying to improve upstream's
copyright notices or make them more accurate, and it arguably can be a
technical violation of some licenses that require preserving copyright
notices.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
Debian for working with non-free
software.
This sort of upstream repackager, if it itself is released under a free
software license, is in general acceptable for contrib if someone is
willing to sponsor it. (I haven't looked at the details of this specific
package.)
--
Russ Allbery (r...@debi
Andrius Merkys writes:
> On 09/06/2018 07:12 AM, Russ Allbery wrote:
>> As part of that transition, it looks like exactly what you said
>> ("adaptation and rebuilding of all packages depending on blacs-mpi")
>> was done for the packages in Debian.
>
ge too far from upstream in
trying to maintain backward compatibility. If upstream has decided not to
maintain that compatibility, trying to do it ourselves in Debian is rarely
a good use of scarce resources. That sometimes means package-breaking
transitions that require a bit of work for dependencies.
r tool, please use an empty override target.
Please note that the dh_installsystemd tool has a slightly
different behaviour in some cases (e.g. when using the
--name parameter).
You may want to read the dh_installsystemd(1) man page to see if any of
the changes affect your
t and then run man dgit-user, hopefully that should get
you started.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
/bugs.debian.org/cgi-bin/bugreport.cgi?bug=658333
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
ne).
We don't have great or consistent naming conventions for this stuff.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
he included package into the including binary
> package somewhere in /usr/share/doc/$package. While it will waste some
> space (and duplicate files), it will also make sure that we correctly
> follow any copyright changes without requiring the package maintainers
> to manually track them
Paul Wise <p...@debian.org> writes:
> Personally, I feel this change to policy is a mistake.
Alternative proposals that achieve the goal of not adding Built-Using
fields to the entire archive are welcome.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
o I need to somehow include the debian/copyright file from
> gnu-efi in the syslinux-efi binary package?
Yes, or at least the portions relevant to the code that's being statically
linked. The resulting binary is a derivative work of the syslinux-efi
package, so you need to follow its license.
--
if you *really* want to provide an HTML version for some reason,
multimarkdown < README.org > README.html does a pretty good job (probably
redirecting it to some path under the staging area for building the new
package).
BTW, are you sure that this is in Markdown? org-mode is something else
rate those stanzas (the notices are fairly
consistent and open for that sort of automation) rather than asking people
to do tedious and not very productive manual work.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
it probably wouldn't, by itself, trigger a new release.
So the update would wait for some other time zone change to be rolled into
a release.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
rely on
that.
The required timeliness depends a lot on what you're using leap seconds
for, and in particular if you need to know about them far in advance, or
if it's only necessary to have an updated table before the leap second
itself arrives.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
lowed
>> subdir of /usr/bin is /usr/bin/mh.
> So nmh is not following FHS either.
mh implementations have a special historical exception in the FHS.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
think gbp import-orig, under the hood, does something more complicated
using Git plumbing to create the merge commit directly.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
e paragraph, or at least
somewhere in debian/copyright (a Comment field or whatever).
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
so that you can
remove them. That should make it safer to add an override for a Lintian
bug, since when the bug is fixed, Lintian will tell you that you can
remove it.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
Jeffrey Walton <noloa...@gmail.com> writes:
> On Wed, Sep 30, 2015 at 3:55 AM, Russ Allbery <r...@debian.org> wrote:
>> Yeah, this is why I'd put a check into the Debian packaging to be sure
>> that the software was built this way and abort the build during the
hy I'd put a check into the Debian packaging to be sure
that the software was built this way and abort the build during the check
phase if it wasn't, with a big comment explaining the situation. Then
hopefully anyone else who picks up the package, if that happens, would be
aware.
--
Russ Allber
dividual build.
Also, I would question the assumption a bit: if this is important for
distributions, wouldn't it be important for all builds?
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
well as all those 'Provided' packages
>are held back.
I think you need Replaces. See:
https://www.debian.org/doc/debian-policy/ch-relationships.html#s7.6.2
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
"Thomas Schmitt" <scdbac...@gmx.net> writes:
> Russ Allbery wrote:
>> That intransitive form of allow is almost always used
>> in combination with the preposition "for".
> But why then isn't the lintian check called
> "allows to allows f
to allow for
a variety of uses, but it's not as common of phrasing for a package
description, and it's usually a pretty indirect and unusual way of
phrasing things.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
):
$ patchelf --remove-needed libraw1394.so.8 /path/to/binary
--
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
packages are not required to use Git, and QA
uploads for orphaned packages often don't.
You can import the changes from 1.10 into the repository using a tool such
as gbp import-dsc from the git-buildpackage package. That's what I'd do
at this point.
--
Russ Allbery (r...@debian.org
are installed. I think that you can work around this by
having your internal packages use Pre-Depends for the package that
provides your script library (instead of Depends).
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-mentors-requ
in the generated package.
--
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: https://lists.debian.org/8761cvfjx3
that takes
care of activating your systemd unit file. --parallel is up to you and
depends on whether your package supports parallel build. (It's unrelated
to systemd support.)
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian
welcome!).
--
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: https://lists.debian.org/87tx0xd40q@hope.eyrie.org
, and an upstart configuration, all of the same (simple)
daemon, so it's easy to compare them.
--
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
find this approach too complicated. I guess I'm just used
to it, but it works for me.
--
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
. If you're not, you
can leave it out.
--
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: https://lists.debian.org/87oarpju8v
progress.
+1.
I use help as a sort of variant of wontfix. It means that I'm not opposed
to a fix for that bug, but I'm not going to work on it, either because I
don't have the time or I don't have the necessary skills. Therefore,
unless someone else works on it, it's not going to get fixed.
--
Russ
situations
for my packages.
--
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: https://lists.debian.org/87k3374r2i
from the basename of the source file. So you need to
rename funopen.3 to FunOpen.3, and then it should install in the correct
location.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject
Ole Streicher oleb...@debian.org writes:
Russ Allbery r...@debian.org writes:
This is arguably a bug in te dh_installman documentation. It takes the
section component of the man page name from the .TH line, but the name
component is taken from the basename of the source file. So you need
with ftp.debian.org.
It's possible that Policy could stand some work to make this clearer.
--
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
debian-de...@liska.ath.cx (Оlе Ѕtrеісhеr) writes:
Russ Allbery r...@debian.org writes:
I'm pretty sure that default is applied before dak ever sees the binary
package priority. (In other words, it's expanded via the build process
before priorities are added to the *.changes file.)
So
want done, and they don't always regenerate everything.
--
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: https
is needed given that autoreconf
is recursive.
I don't think autoreconf can always figure out what to do when the files
are buried in some random subdirectory without anything at the top level.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE
are better treated as source, and the
generated files regenerated on every build. This ensures that the files
can still be generated from the source, which in turn ensures that anyone
wanting to make changes to the source package will be able to do so
easily.
--
Russ Allbery (r...@debian.org
Yavor Doganov ya...@gnu.org writes:
Russ Allbery wrote:
I would still use dh-autoreconf. It's not as critical, since it's
unlikely to be necessary for supporting new architectures, but I think
the Autoconf and Automake files are better treated as source, and the
generated files regenerated
believed that this
can be done for MIT-licensed software regardless of whether it's
dual-licensed, since there aren't any license terms that conflict.)
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
and instead provide some sort of Makefile
to install things, but it works great for quick internal packages.
--
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
about, as long as the packages in Debian do the right thing.
Is any of these Stanford-internal packages available to be looked at in
a public place?
It doesn't look like it, unfortunately.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email
fix (and similarly for the other patterns in other *.install files).
--
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
not sure why -- I think it shouldn't -- but that will
at least affect Apache and PHP modules.
I must be misremembering the Python situation.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
: it's
probably a plugin.
```
then.
Yes. The it's probably a plugin part is basically trying to tell you to
ignore this as long as the message is correct and it is a plugin.
Python, PHP, and Apache modules all generally get this warning.
--
Russ Allbery (r...@debian.org) http
these days for most
packagers to spend time on.
--
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: https
, and the Apache packaging for
wheezy is substantially different than Apache packaging for jessie and
newer releases.
--
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
then turn into a
UID via getpwnam)? Then you wouldn't have to modify the configuration
file.
If it doesn't support names now, could that be added? It might be a
fairly simple patch, a few lines at most.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle
users for running
particular applications normally should not have a valid shell, and
auditors will often require that they not have a valid shell. You don't
want that sort of change (possibly required by local audit policies) to
break the package.
--
Russ Allbery (r...@debian.org) http
by a older version than 1.4.12, it is
allowed to modify the old changelog entries, when the fix was actually
added.
Yup.
--
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
Dariusz Dwornikowski dariusz.dwornikow...@cs.put.poznan.pl writes:
On wto, lut 18, 2014 at 01:29:06 -0800, Russ Allbery wrote:
I think you were also saying this, but just to be very clear: please
also include the CVE numbers directly in debian/changelog in the entry
for whatever release
the previous
release.
--
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/87y524tya5
debhelper 9 or later, which means
stable or squeeze-backports (but not squeeze itself).
--
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
. If you want to rename things,
you'll need to do that separately, usually with an override and some code
that runs before dh_install.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject
Schwimmer
* Extensively modified by Russ Allbery ea...@eyrie.org
from one of my projects.
- I should inherit the BSD-licensed, right?
Yes, almost always.
- How to express that the new file was based on another old file from a
different author in the debian/copyright file?
Copyright: 2003
directory, use whatever variable upstream
is using; if they're just using usr/bin literally, then use:
install -d $(DESTDIR)/usr/bin
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject
Russ Allbery r...@debian.org writes:
First, dh_installdirs is not actually useful for solving this particular
problem since dh_installdirs creates directories in the package staging
area. Your problem is happening prior to that; make install of the
upstream source into debian/tmp is failing
Russ Allbery r...@debian.org writes:
I guess I should say, for the sake of completeness, that you *can* make
dh_installdirs do this with the -P flag. But I would find that
confusing; I think an explicit install -d is easier to understand. And,
regardless, dh_installdirs isn't normally run
this stuff by hand, but I also mostly don't support
long options. I keep meaning to find a more portable solution to that for
C programs than GNU getopt_long(3).
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-mentors-requ
.
What's currently done everywhere in the archive is that the targets run by
dpkg-buildpackage (either arch or arch-indep builds) must have their
dependencies listed, and dependencies for the other targets are not
listed.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle
on the exact situation.
--
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/87a9gdcpx7
have been known to start with the empty set and just keep building and
adding dependencies to fix each failure or each missing feature in
configure.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
means making a debian/glimpse/usr/lib/glimpse directory and moving
some of the files into 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 unsubscribe. Trouble? Contact listmas
Paul Wise p...@debian.org writes:
Send the lintian authors a patch to update the current
Standards-Version.
This is already in progress -- no need to send more patches.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-mentors
prefix. You can possibly
work around this by setting prefix to $(CURDIR)/debian/tmp, but this
really should be fixed upstream by adding support for DESTDIR.
http://www.gnu.org/prep/standards/html_node/DESTDIR.html
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle
years. I have
fix it myself, but I don't know how.
Generally it's as simple as adding $(DESTDIR) in front of the installation
paths for all install rules in the upstream Makefiles.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian
with. (The socket_* calls are, on Linux, just macros
that expand to write and close. They exist for compatibility with
Windows, where different functions have to be used when working with
sockets.)
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email
it approved by the normal IETF process. (I think this is quite reasonable
given how scarce such ports are.)
--
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
it that way. I've seen
upstreams just refuse to add the license exception on the grounds that
they think Debian's concern is silly and they refuse to cater to it.
*sigh*
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-mentors-requ
();
savescore_memory2file();
}
What would be the standard way to lock the scorefile?
fcntl(fd, F_SETLK). See fcntl(2).
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject
.
--
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/87zjqpluqh@windlord.stanford.edu
any further investigation.
--
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/87bo3hkh8s
#1 and #3. (It
would be okay for the separate non-free archive.)
--
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
forward.
Note that this only works if the only binaries linked with that shared
library are built from the same source package. If you have to link with
that shared library across source packages, you may want to consider a
different approach.
--
Russ Allbery (r...@debian.org) http
Russ Allbery r...@debian.org writes:
Beren Minor beren.minor+deb...@gmail.com writes:
I can either:
- exclude usr/lib/gemrb from dh_makeshlibs
I would do this. If the library is not a public API that should be used
by other projects, then having out it ouf /usr/lib is probably the right
Beren Minor beren.minor+deb...@gmail.com writes:
On Wed, Sep 4, 2013 at 12:49 AM, Russ Allbery r...@debian.org wrote:
Alternately (and in my opinion preferrably) just exclude the plugins
directory from dh_makeshlibs:
override_dh_makeshlibs:
dh_makeshlibs -Xusr/lib/gemrb
(This is really a (minor) upstream bug, since, as plugins, these objects
should not have SONAMEs.)
--
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
of multi-arch comes from just having
the libraries be multi-arch, and we've not yet made a push to multi-arch
the dev packages. The dev packages pose a variety of additional
challenges that we haven't completely sorted through.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org
. 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/
--
To UNSUBSCRIBE, email to debian
Alexander Wirt formo...@formorer.de 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 deal
Arno Töll a...@debian.org writes:
On 23.07.2013 20:08, Russ Allbery wrote:
Hm, how do you deal with the conf.d vs. conf-available change and the
completely different maintainer script actions?
there are several possibilities, but I suggest something like [1] which
I wrote for that purpose
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.debian.org
Archive: http://lists.debian.org
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-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
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...@lists.debian.org
Archive: http://lists.debian.org
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. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org
if they 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://www.eyrie.org
, 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 unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http
# 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 target.
--
Russ Allbery (r...@debian.org) http
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 listmas...@lists.debian.org
Archive: http
Felix Natter fnat...@gmx.net 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) http://www.eyrie.org
Thomas Moulard thomas.moul...@gmail.com writes:
On Tue, May 14, 2013 at 9:56 AM, Russ Allbery r...@debian.org wrote:
Thomas Moulard thomas.moul...@gmail.com writes:
A package I maintain contains a configuration header (vpConfig.h)
which differ depending on the architecture we are (here
putting headers 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/~eagle
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) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian
.
--
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/87sj362qhi@windlord.stanford.edu
1 - 100 of 690 matches
Mail list logo
