Josip Rodin:
> You can upload the sources only nowadays...
There are autobuilders for all platforms that handle the compilations
for me, then?
--
\\//
peter - http://www.softwolves.pp.se/
Statement concerning unsolicited e-mail according to Swedish law:
http://www.softwolves.pp.se/peter/r
I'm trying to do a source only upload, but I'm failing to get
dpkg-source not to overwrite my tarfile (I would like to use the exact
same tarfile as my official distribution of the program, not re-pack it
for Debian).
I'm running "dpkg-source -ss -sn -b ", but it is still
overwriting the tarfile.
Josip Rodin:
> Yes, build daemons for i386, m68k, sparc, powerpc should be active.
All right. If I only could figure out how to do a source only upload
that won't overwrite my original tarfile, I'd be all set.
--
\\//
peter - http://www.softwolves.pp.se/
Statement concerning unsolicited e-m
Hi!
So, am I supposed to move over my packages from using suidmanager to
use the new dpkg-statoverride? If so, is there a HOWTO describing how
to do it somewhere?
--
\\//
peter - http://www.softwolves.pp.se/
Statement concerning unsolicited e-mail according to Swedish law:
http://www.softw
Jeremy Higgs:
> I cannot see anything wrong...?? but I still get a 'missing separator' error!
It's a standard Makefile, so you need to have tabs before the commands
that defines the target. You've removed the initial tabs from the dh_
lines.
--
\\//
peter - http://www.softwolves.pp.se/
Stat
Hi!
I have a tarfile for a debian-original program (i.e no .orig or
maintainer version), and I also have it uncompressed. When I run
dpkg-buildpackage -rfakeroot from the uncompressed directory, it
overwrites my tarfile.
How do I stop it from doing that? I want to have the "original" tarfile
th
Joey Hess:
> There is one wrinkle: If your package previously used suidmanager, and
> you convert it to not, you should make it Conflicts: suidmanager (<< 0.50).
> (The details of why are a little messy; see earlier discussion on
> debian-devel.)
A program I packaged (jwhois, I am taking over ma
Hi!
I can't really figure out how testing works, since one of my packages
(turqstat) currently has the very obsolete version 1.2 (same as in
potato) in testing, whereas it after that has been releases 1.3, 1.4,
2.0 and 2.0.1. 2.0 is from November last year, and should be good
enough to have gone
Tollef Fog Heen:
> So, unless it's dependant on other buggy packages, or you get any RC
> bugs, it will go into testing.
Well, what I'm curious about is why only 1.2 is in testing, 1.4 was in
woody since a couple of months before testing was introduced.
Does this stuff require that the package
Joey Hess:
> Hmm. If you run chrmod in the postinst, you will clobber any different
> permissions that the user has set with statoverride.
Well, I remove the statoverride (previously suidmanager stuff) in the postrm
as well, so I need to re-instate them there.
> I think it may work to examine d
Chris Danis:
> I'm in the NM queue, currently packaging tclbabel, a piece of
> software I have written myself. Because I am both upstream and
> possibly Debian maintainer, should this be such a native package?
It could be, but it does not need to. I have made the programs I write
myself native p
Tollef Fog Heen:
> I've ITP'ed and packaged mboxgrep. If somebody could sponsor the
> upload for me, I'd appreciate.
I'll sponsor you, Tollef.
--
\\//
peter - http://www.softwolves.pp.se/
Statement concerning unsolicited e-mail according to Swedish law:
http://www.softwolves.pp.se/peter/
Hi!
I'm in the process of adopting the Siag Office suite of packages, and
I'm currently wrestling a bit with lintian vs. the way it has been
packages. Lintian gives me an error on two of the packages that
"usr-doc-symlink-points-outside-of-usr-doc". The thing with that is
that there is two versio
[EMAIL PROTECTED]:
> Yes, just copy the commands you need into your postinst file from
> /usr/share/debhelper/autoscripts/postinst-doc
Is there any way to force debhelper to insert these, rather than to insert
them manually?
--
\\//
peter - http://www.softwolves.pp.se/
Statement concerning
Julian Gilbey:
> But in cases where the only meaningful installation was suid or sgid (for
> example, /bin/su), the deb always held a suid or sgid binary.
Hmmm, so my use of suidregister/dpkg-statoverride in the jwhois package
isn't really a correct implementation? I am creating a group when the
Julian Gilbey:
> If the binary must be setgid, then you should just chown/chmod the
> binary. If it could be used not-setgid, then use statoverride.
It can be used non-setgid if the sysadmin is paranoid, yes (then the
cache functions will be non-operative).
JP Sugarbroad:
> Packages should al
2.0.1 (currently 1.2-1) (low)
Maintainer: peter karlsson <[EMAIL PROTECTED]>
turqstat uploaded 26 days ago, out of date by 16 days!
out of date on alpha: turqstat (from 1.4)
out of date on arm: turqstat (from 1.4)
out of date on m68k: turqsta
Christopher C. Chimelis:
> Alpha has serious gcc/g++ problems with Qt 2.2, so don't expect an alpha
> upload for quite some timejust fyi :-)
So basically, I should change "Architecture: any" to specifically not
list alpha (and other platforms lacking Qt)?
--
\\//
peter - http://www.softwol
Christopher C. Chimelis:
> If it were something like GNAT, where we cannot build it on Alpha at
> all without pre-existing binaries (which don't exist for
> alpha-linux), then I would say omit Alpha.
Well, also there is the endian problem. I don't know how 1.4 debs ended
up on these machines, be
Hi!
I have CVS access to a upstream program I am the Debian maintainer for
(jwhois), and since I have learnt the lesson of moving the debian
directory in the CVS, I'm planning to add them as a separate module.
My question, however, is how to handle differences between the Debian
version and the
Chad C. Walstrom:
> The easiest way is to maintain a vendor branch in a local repository.
I would prefer not to make unnecessary copies...
> You can use the cvs-inject script provided by cvs-buildpackage to
> automate much of this. (Do an 'apt-cache show cvs-buildpackage'.)
Ah. cvs-buildpacka
Jaldhar H. Vyas:
> I hope this helps anyone who has faced the problem themselves. I have a
> question too, is there anyway to use the unmangled name?
Did you specify AC_LANG_CPLUSPLUS in your configure.in?
--
\\//
peter - http://www.softwolves.pp.se/
Statement concerning unsolicited e-mail
Hi!
If the testing scripts says that an architecture is out of date, and that
architecture is not listed as one of the target architectures for the
program in question, where do I ask to get it corrected?
--
\\// Live Long and Prosper
Peter Karlsson
Developer / Utvecklare / Utvikler
Christian T. Steigies:
> And you will note m68k is not the fastest arch on the world
> (allthough the nicest ;-)
Hmm, perhaps I should dust off the Amiga 1200 that is lying in a
desktop drawer¹ doing nothing. Wonder how much I extra stuff I need to
equip it with to get it running Debian and conn
Hi!
For the various auto-builders, is it possible to get logs of any failed
builds sent via e-mail, or do one have to go hunt around to try to find
them using the various web interfaces?
--
\\//
peter - http://www.softwolves.pp.se/
Statement concerning unsolicited e-mail according to Swedish
Hi!
I notice that the BTS pages say that the bugs I have tagged as "fixed" are
"fixed in NMU", even though I tagged them manually. I have understood the
"fixed" tag as something I can use when the bug is fixed locally/upstream,
but has not yet found its way into Debian (for instance, for wishlist
Hi!
I just noticed that a package I submitted was built on the wrong
machine here at home, and is linked against wrong libraries. Can I, as
the maintainer, do a binary "NMU" where I only recompile the package
against the correct libraries? How do I go about and do that?
--
\\//
peter - http://w
Manuel Estrada Sainz:
> The first problem is that I generate the changelog automaticly from CVS
> which seams too big and verbose for a debian changelog but I am not
> suposed to have an upstream changelog in a pure debian package.
Well, I "cheat" myself, with both a standard changelog and a Deb
Tollef Fog Heen:
> Increase the version number by 0.01, recompile and upload. See the
> developers reference 8.2, third paragraph.
So, how do I change the version number without touching the changelog?
Invoking the way the reference says will keep the current version, and
there does not seem to
Mike Markley:
> The best way to go is simply to increment the debian revision by 0.1 or so,
> with a changelog entry describing why you did it (binary-only build for arch
> xxx)...
But the reference says that I should not touch the changelog, even when
updating the version by 0.1 for a binary-on
Colin Watson:
> Why couldn't you use 'dh_installchangelogs ChangeLog' to achieve the
> same effect?
Because it is a native Debian package, and the manual page for
dh_installchangelogs says
NOTES
It is an error to specify an upstream changelog file for a
debian native package.
--
Julian Gilbey:
> Which is impossible to do.
That's about what I figured, but it still says that :-)
--
\\//
peter - http://www.softwolves.pp.se/
Statement concerning unsolicited e-mail according to Swedish law:
http://www.softwolves.pp.se/peter/reklampost.html
--
To UNSUBSCRIBE, email
quot;update excuses":
turqstat 2.0.2 (currently 1.2-1) (optional) (low)
Maintainer: peter karlsson <[EMAIL PROTECTED]>
turqstat uploaded 52 days ago, out of date by 42 days!
> out of date on i386: xturqstat (from 2.0.2.0.1)
> th
Steve M. Robbins:
> The undocumented page provides no more information than "No manual
> entry for foo" (but the former is much longer to read). What is the
> point?
Personally, I reason that if I get "No manual entry", it is a program
that probably shouldn't have entered myself, but if I get un
Hi!
What's the thought about software which is only available in a
non-English language? I am thinking about packaging a client for the
LysKOM server, which is only available in Swedish (there's some support
for gettext, but no-one has bother translating the program into any
other languages yet).
What does this error message mean?
"No `START-INFO-DIR-ENTRY' and no `This file documents'.
install-info: unable to determine description for `dir' entry - giving up"
I get it when trying to install my program, which has an info file. I
have not done anything special about it more than let debh
Josip Rodin:
> Your info file should have something like this near the top:
It hasn't. It starts like this:
===[ cut ]===
This is lyskom.info, produced by makeinfo version 4.0 from
/home/peter/tmp/sgmltmp.lyskom32294.info.2.
\input texinfo
^_
File: lyskom.info, Node: Top, Next: Inledning
Hi!
Lintian warns me about that I should add --section to install-info and
points me to check for a good section in /usr/share/info/dir, but that
directory doesn't exist on my system... The install-info doesn't
recomment any valid sections either... Is there any canonical list?
--
\\//
peter -
Hi!
Can a single binary package have a different name than the source package it
comes from?
I am packaging the LysKOM tty-client, which has the upstream name
tty-client, but I have received requests for renaming the Debian package to
lyskom-tty-client. Can I do that without changing the name of
e character sets used in
Fidonet and Usenet today.
-- peter karlsson <[EMAIL PROTECTED]> Tue, 17 Jul 2001 22:45:00 +0200
===[ cut ]===
It complains about line 6, which is part of the comment. This is really
weird, does anyone have any ideas?
--
\\//
peter - http://www.softwolves.pp
Eric Van Buggenhaut:
> > .
> ^^^
> You sure about that period ?
It's just in the parsed output, not in the original, and I think is
supposed to look like that.
--
\\//
peter - http://www.softwolves.pp.se/
Statement concerning unsolicited e-mail according to Swedish law:
http://www.so
peter karlsson:
> I'm getting a weird error from debhelper; it says that it cannot
> parse the changelog:
D'uh! I forgot I split the changelog into one per each binary package
generated from the sources. The error message was for the *other*
changelog file...
--
\
Steve Langasek:
> Do you ever intend to release this software as a tarball for use outside
> of Debian?
Yes, the tarball that I create for Debian is also distributed from my
homepage (together with Debian packages compiled for potato, for those that
do not use unstable), along with a RAR package
Steve Langasek:
> Since this is the Debian changelog rather than an upstream changelog, the
> majority of changes noted are specific to the shared debian directory, of
> which there is precisely one for any set of binary packages that are built
> from a single source package.
Well, first of all,
Hi!
What does this mean?
dpkg-gencontrol: error: source package has two conflicting values - turqstat and
xturqstat
My source package "turqstat" generates two binary packages, "turqstat"
and "xturqstat". They each have their own changelogs (debian/changelog
and debian/xturqstat.changelog), and
Wichert Akkerman:
> You can't do that, changelogs have to be shared.
Why? The changelog lists what was changed between the versions, and that
differens between the two binary packages I created (there was a feature
only added to the command line version, not the GUI version), and I want
that ref
Steve Langasek:
> I regularly do my own builds on two architectures before uploading, just
> to get that extra bit of testing into it.
Is there a way to upload two architectures at once, and include them in the
same .changes file?
--
\\//
peter - http://www.softwolves.pp.se/
Statement conce
Hi!
How do I get dpkg-buildpackage not to re-build the source tarball when
building a native package? No matter what I do, it rebuilds it, which
prevents me from keeping the tarball I created from my CVS tree, which
also is what I distribute elsewhere.
--
\\//
peter - http://www.softwolves.pp.s
Mike Markley:
> You probably don't want to do this... since a native package has no
> .diff.gz, the source tarball must contain everything used to generate the
> set of binary packages you're uploading.
It does, I just untarred it to a directory and ran dpkg-buildpackage there.
I don't wnat dpkg
Santiago Vila:
> I would first create the Debian source and binary packages for upload,
> and then distribute the resulting tar.gz elsewhere, in that order.
The problem is that I am generating the tar from my CVS (not all of the CVS
is exported, there are some MSWIN and OS/2 specific stuff there
Santiago Vila:
> Oops! I understand. My suggestion is that you arrange things so that
> dpkg-buildpackage creates the one and only source tarball, instead of
> creating it in advance by hand.
I *could* do that, but that would still not solve the problem of the files
in the tarball being owned by
Santiago Vila:
> Including MSWIN and OS/2 specific stuff in a Debian source tarball
> should not be a problem.
Well, the packages structure are different on the different platforms, and
also my MSWIN/OS2 source packages also contain binaries, plus that the
source is CRLF formatted there, and tha
Colin Watson:
> If you can't build the Debian package as part of the process of
> generating the tarball from CVS, I suppose you could use -b and hack the
> .changes by hand to include the source, although that's rather ugly.
I tried hacking the changes file by hand, but my upload got rejected t
Julian Gilbey:
> For what reason was it rejected?
Wrong syntax or wrong checksum. I couldn't manage to get the files 100%
correct, so in the end I gave up...
--
\\//
peter - http://www.softwolves.pp.se/
Statement concerning unsolicited e-mail according to Swedish law:
http://www.softwolve
Santiago Vila:
> If you insist that the tarball must be created first, follow Julian's
> suggestion and make your package non-native by creating an .orig.tar.gz
> tarball (in this case the .diff.gz is typically the debian/* files).
I don't want to make it non-native, since that means I would hav
Hi!
An NMU upload for a package that I am adopting was uplodad as if it was
a Debian native package, with a name-x.y-1.1.tar.gz with the sources,
with no diffs or orig.tar.gz. I wish to upload a new version, correct
with a diff against the orig.tar.gz. Can I somehow re-upload the
orig.tar.gz for
Hi!
I am thinking of removing the upstream source level changelog from the
binary package for jwhois, and instead use its NEWS file, which
contains a history in human readable format. Is this wise? Is there any
policy on what should be considered the upstream changelog? Must the
source level chan
Sean 'Shaleh' Perry:
> without seeing the files, why is changelog not "human readable"?
Well, because it has a lot of noise, with minor changes to files that
are not interesting for those that do not download the source package.
The NEWS file, on the other hand, just lists the actual compound
ch
Francesco P. Lovergine:
Hmmm, doesn't
> here is a blessing:
> **May you do good and not evil.
break the "No Discrimination Against Fields of Endeavor" part of DFSG?
> **May you share freely, never taking more than you give.
Not to speak of "License Must Not Contaminate Other Software"
Hi!
Is it possible to have different default values to a question in
different language setups?
I am trying to package a piece of software that can be installed with
two different sets of initial data, one in English and one in Swedish,
and I wish to have the English version default when asking
Hi!
Where's the best place to put a conferencing system's database files?
I have currently put them in /var/spool/packagename/, but I'm not sure
if that's a good idea, as FHS states that spool should be for more
temporary data (this database file will be kept all time when the
conferencing syste
Joey Hess:
> Yes, you can localize the Default field. Default-se or whatever.
Should I write the translated default choice in the translated language
or in English? I can't get it to work, but that's probably because I've
already saved a setting to the debconf database and can't get rid of
it.
Robert Bihlmeyer:
> I'd guess English, at least the templates I look at use English in
> 'Default' even if 'Choices' was translated.
Okay. I'll try again.
> Shouldn't purging the package (i.e. debconf's PURGE command) remove
> all settings?
I ran the config script manually, so debconf said tha
Hi!
I am planning to package a Python script that will aid another package
I already have in Debian. Since I don't really know much about Python I
wonder what packages I need to depend on. Is it enough to depend on
python-base?
The script starts with these lines:
import sys
import nntplib
impor
Sean 'Shaleh' Perry:
> Gregor just posted his draft of the python packaging policy. Give it a peak.
And... where do I find that?
--
\\//
peter - http://www.softwolves.pp.se/
Statement concerning unsolicited e-mail according to Swedish law:
http://www.softwolves.pp.se/peter/reklampost.htm
Hi!
I am trying to add icons to the menu entries for the Siag suite, but I
am having problems getting the icons to be recognized. I have this in
the menu file:
?package(xsiag): needs="X11" section="Apps/Math" \
title="Siag" longtitle="Siag Office Scheme-in-a-Grid" \
command="/usr/bin/siag" i
Sean 'Shaleh' Perry:
> looks like every other icon entry:
Exactly. That is why I am confused.
--
\\//
peter - http://www.softwolves.pp.se/
Statement concerning unsolicited e-mail according to Swedish law:
http://www.softwolves.pp.se/peter/reklampost.html
--
To UNSUBSCRIBE, email to [EM
While sifting through the policy upgrade checklist for one of my
packages, I came to the information about changing mail access from
/var/spool/mail to /var/mail. That's not hard. Also, the
upgrade-checklist states that I should "[...] include a suitable
Depends field; details in [12.6]". What Dep
Hi!
I have created a package of the LysKOM server (ITP bug #114231). Since this
is the first server I have packaged, I would appreciate if someone would
test and see that it works well on other systems than my own... :)
The package can be found at http://www.softwolves.pp.se/deb/
It only has on
Peter S Galbraith:
> The problem is not really with hppa, but with g++-3.0.
> Here's what I do to test build (another package) using g++-3.0 :
Is it possible to get g++ 3 for i386 somewhere? That would make it a
lot easier to test if things work... :)
--
\\//
peter - http://www.softwolves.pp.s
Peter S Galbraith:
> Sure, install the package 'g++-3.0'.
Hmm, interesting. It doesn't show up when I do dpkg -l, but obviously
apt knows about it.
--
\\//
peter - http://www.softwolves.pp.se/
Statement concerning unsolicited e-mail according to Swedish law:
http://www.softwolves.pp.se/pe
David Given:
> E: vbcc: FSSTND-dir-in-usr usr/man/
> - --- what's this?
E: vbcc: FSSTND-dir-in-usr usr/man/
N:
N: As of policy version 3.0.0.0, Debian no longer follows the FSSTND.
N:
N: Instead, the Filesystem Hierarchy Standard (FHS), version 2.1, is
N: used. You can find it in /usr/shar
Hi!
When upgrading Siag Office to its latest version I found that parts of
the code had been broken out into a library. Since I have never before
packaged a library I would appreciate some help to check whether I am
doing things correctly or not.
Could someone please have a look at the files tha
Junichi Uekawa:
> Without too much looking at, my first question is: why do you have
> mowitz-config in diff.gz?
It seems that it is not removed properly when doing a make distclean.
I'll fix that.
> Binary package names are incorrect, name them "lib"mowitz0 and
> "lib"mowitz-dev
Okay. I was a
Junichi Uekawa:
> Are you sure of the soname version number?
It is at least the version used in the files:
$ ls -l /usr/lib/libMowitz.*
-rw-r--r--1 root root 400490 13 mar 18.42 /usr/lib/libMowitz.a
-rw-r--r--1 root root 717 13 mar 18.41 /usr/lib/libMowitz.la
lrwx
Junichi Uekawa:
> That doesn't tell much.
> objdump -p /usr/lib/libMowitz.so | grep SONAME
er$ objdump -p /usr/lib/libMowitz.so | grep SONAME
SONAME libMowitz.so.0
> That sounds like a bad news, a potential sign of upstream changing
> binary interface between 0.1.0 and 0.2.0
I don't kno
Hi!
According to the docs I an update my key on the Debian keyring by giving the
command
gpg --keyserver keyring.debian.org --send-keys 0x6394265E
but I cannot get it to work. Everytime I try (from different machines) I get
the error message
gpg: error sending to `keyring.debian.org': eof
Me:
> Did I misunderstand something, or is the keyring server down?
D'uh! GnuPG doesn't like my proxy. If I disable the proxy, it works just
fine.
--
\\//
peter - http://www.softwolves.pp.se/
Statement concerning unsolicited e-mail according to Swedish law:
http://www.softwolves.pp.se/pete
Hi!
I just got serious bugs filed against two of my packages about
dependencies on packages with lower priorities. In one case it is
correct (a package with "optional" depending on one with "extra"), but
in one case all the packages are set to "extra" in my control files, so
I can't really unders
Magnus Ekdahl:
> "...Note, however, that the postrm cannot rely on any non-essential packages
> to be present during the purge phase" (deluser isn't essential).
> If there aren't any way, is this script safe enough?
Why not just run the regular account deletion, and post an error
message if
Hi!
I have a question about a program that I am thinking about packaging:
It is a transfer program¹ licened according to GPL, but comes with some
program code that you download to the remote computer. That code is
also GPL, but the program used to compile those sources is not DFSG
free. The remot
Matt Zimmerman:
> If the program cannot be compiled using free tools, then it is not very
> free.
Well, that's a matter of definition.
I'll have a look at using another cross-assembler. Fortunately, there
seems to be a GPL'ed 6502 cross-assembler, so I'll have a look into
using that one instead
Jordi S. Bunster:
> Maybe someone else can help this guy with this one, maybe someone
> that knows more about how CD vendors can contribute back to debian,
> and make the difference between "Official CD" and the other stuff
> clear.
http://www.debian.org/CD/vendors/info contains all the informati
Mattia Dongili:
> any suggestion?
For jwhois, where I act as upstream "release manager" and Debian
developer, I usually put the debian directory in the upstream tarball,
and then build it for Debian. I call the version -1, though, but the
diff is empty for the -1 version (it is nonempty -2). It i
Hi!
A new version of a package that I maintain has changed the name of the
default configuration file. I want to propagate this name change, but
how do I handle it properly? AFAICT, I'm not allowed to touch conffiles
in the maintainer scripts, but this would mean that the old
configuration would j
Andreas Metzler:
> You could conditionally move the existing configuration file in the
> preinst to the new location.
Thanks. I'm doing something similar with a non-conffile for another of
my packages, so I'll just copy the working code from that. I was just
unsure whether I was allowed to do it
Steve Langasek:
> I regularly do my own builds on two architectures before uploading, just
> to get that extra bit of testing into it.
Is there a way to upload two architectures at once, and include them in the
same .changes file?
--
\\//
peter - http://www.softwolves.pp.se/
Statement concer
Hi!
How do I get dpkg-buildpackage not to re-build the source tarball when
building a native package? No matter what I do, it rebuilds it, which
prevents me from keeping the tarball I created from my CVS tree, which
also is what I distribute elsewhere.
--
\\//
peter - http://www.softwolves.pp.se
Mike Markley:
> You probably don't want to do this... since a native package has no
> .diff.gz, the source tarball must contain everything used to generate the
> set of binary packages you're uploading.
It does, I just untarred it to a directory and ran dpkg-buildpackage there.
I don't wnat dpkg-
Santiago Vila:
> I would first create the Debian source and binary packages for upload,
> and then distribute the resulting tar.gz elsewhere, in that order.
The problem is that I am generating the tar from my CVS (not all of the CVS
is exported, there are some MSWIN and OS/2 specific stuff there
Santiago Vila:
> Oops! I understand. My suggestion is that you arrange things so that
> dpkg-buildpackage creates the one and only source tarball, instead of
> creating it in advance by hand.
I *could* do that, but that would still not solve the problem of the files
in the tarball being owned by
Santiago Vila:
> Including MSWIN and OS/2 specific stuff in a Debian source tarball
> should not be a problem.
Well, the packages structure are different on the different platforms, and
also my MSWIN/OS2 source packages also contain binaries, plus that the
source is CRLF formatted there, and that
Colin Watson:
> If you can't build the Debian package as part of the process of
> generating the tarball from CVS, I suppose you could use -b and hack the
> .changes by hand to include the source, although that's rather ugly.
I tried hacking the changes file by hand, but my upload got rejected th
Julian Gilbey:
> For what reason was it rejected?
Wrong syntax or wrong checksum. I couldn't manage to get the files 100%
correct, so in the end I gave up...
--
\\//
peter - http://www.softwolves.pp.se/
Statement concerning unsolicited e-mail according to Swedish law:
http://www.softwolves
Santiago Vila:
> If you insist that the tarball must be created first, follow Julian's
> suggestion and make your package non-native by creating an .orig.tar.gz
> tarball (in this case the .diff.gz is typically the debian/* files).
I don't want to make it non-native, since that means I would have
Hi!
An NMU upload for a package that I am adopting was uplodad as if it was
a Debian native package, with a name-x.y-1.1.tar.gz with the sources,
with no diffs or orig.tar.gz. I wish to upload a new version, correct
with a diff against the orig.tar.gz. Can I somehow re-upload the
orig.tar.gz for x
Hi!
I am thinking of removing the upstream source level changelog from the
binary package for jwhois, and instead use its NEWS file, which
contains a history in human readable format. Is this wise? Is there any
policy on what should be considered the upstream changelog? Must the
source level chang
Sean 'Shaleh' Perry:
> without seeing the files, why is changelog not "human readable"?
Well, because it has a lot of noise, with minor changes to files that
are not interesting for those that do not download the source package.
The NEWS file, on the other hand, just lists the actual compound
cha
Francesco P. Lovergine:
Hmmm, doesn't
> here is a blessing:
> **May you do good and not evil.
break the "No Discrimination Against Fields of Endeavor" part of DFSG?
> **May you share freely, never taking more than you give.
Not to speak of "License Must Not Contaminate Other Software".
Hi!
Is it possible to have different default values to a question in
different language setups?
I am trying to package a piece of software that can be installed with
two different sets of initial data, one in English and one in Swedish,
and I wish to have the English version default when asking i
101 - 200 of 224 matches
Mail list logo
