their
> config files after an upgrade -- man-db
man-db only ever altered its configuration file in the postinst when it
wasn't a conffile. I only decided some months ago that it would be
better off managed by dpkg.
--
Colin Watson [EMAIL PROTECTED]
On Mon, Feb 18, 2002 at 09:20:31PM +0100, Andreas Rottmann wrote:
> tclsh ./www/index.tcl `cat ./VERSION` >index.html
> make[1]: *** [index.html] Error 139
[...]
> Has anyone got an idea what 'Error 139' means?
The child process (tclsh) segfaulted (139 = 128 + 11 = signal
On Mon, Feb 25, 2002 at 10:50:09AM -0800, Yves Arrouye wrote:
> But... Wouldn't it be nice to have dpkg understand "alpha/beta" in version
> numbers?
It'll be in dpkg 1.10, although it's not clear whether it'll be valid to
use it until that makes it into
> > in debian directory?
> > Or am I to modify it by hand every time?
>
> I don't know debian/my_package.files, but dpkg-gencontrol
> (or dh_gencontrol) will create debian/files.
That's completely different, sorry. debian/*.files is used by
dh_movefiles.
--
Colin Watson [EMAIL PROTECTED]
uns once a day (just before 8pm GMT)
to install accepted packages into the pool, and the mirrors update
shortly after that.
--
Colin Watson [EMAIL PROTECTED]
#x27;re
building multiple programs, in which case you'll have to find out
exactly how #123741 was fixed.
--
Colin Watson [EMAIL PROTECTED]
target
yourself.
The examples that show $(MAKE) being called in the build target are just
that - examples. It's not mandatory.
--
Colin Watson [EMAIL PROTECTED]
; /usr/share/applets/Clocks/alarm_applet.desktop
Policy section 11.7 says "Any configuration files created or used by
your package must reside in /etc." If you need the file to be accessible
from its current location as well, make a symlink.
--
Colin Watson [EMAIL PROTECTED]
On Mon, Mar 18, 2002 at 01:14:41AM -0500, Chris AtLee wrote:
> On Sun, 2002-03-17 at 19:30, Colin Watson wrote:
> > On Sun, Mar 17, 2002 at 11:41:07AM -0500, Chris AtLee wrote:
> > > E: alarm-applet: file-in-usr-marked-as-conffile
> > > /usr/share/applets/
sion of that check, I think
you can safely ignore that error. Please try applying the patch I sent
to bug #122742 to your /usr/share/lintian directory and see if that
quietens lintian's complaints.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE,
ill be just as good as everyone else's.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
oesn't sound like you have any shared library dependencies to
be substituted there - programs not written in C/C++ generally don't -
so it's also more correct to remove it in your case.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, ema
s containing strings of letters which the package
management system cannot interpret (such as ALPHA or pre-), or with
silly orderings (the author of this manual has heard of a package
whose versions went 1.1, 1.2, 1.3, 1, 2.1, 2.2, 2 and so forth).
(policy chapter 4)
--
Colin Watson
glimpse&archive=yes
(all archived bugs against glimpse; the ones closed by Jose Carlos
Garcia Sogo are the ones that were still open when the package was
removed)
Regards,
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [E
to use the
--force-confmiss option to dpkg to reinstall it, although you probably
don't want to use that option indiscriminately (it's marked as dangerous
in 'dpkg --force-help').
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, em
master (a.k.a. lintian.debian.org) is upgraded to woody
post-release.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
r the archive maintenance software to install it - there's no
way around that.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tually adds to
misc:Depends ('grep misc:Depends /usr/bin/dh_*'). It doesn't cause a
real problem besides the unsightly warning if you aren't, though.
(Not a Python person, sorry.)
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [
hc
> GHCVERSION := $(shell ghc --version | tr -d "a-zA-Z ,")
> GHCDSTLIB = debian/tmp/lib/ghc-${GHCVERSION}/Fudgets
>
> The question then is this a good form for a Debian package?
Provided that you build-depend on ghc (versioning the build-dependency
if appropriate?
01' or should I just keep the version
> as 'h13u'?
Depends, really. What would other examples of this versioning scheme be?
The main thing you should consider is whether 'dpkg --compare-versions
lt ' will always be true.
--
Colin Watson
a
> portion, they should be distributed separately)
The original poster was talking about one source package generating
multiple binary packages, so I don't think that's really relevant.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
forwards any connection to a remote host.
By the way, if you haven't got it already in your local copy, do
remember to upgrade the Standards-Version: to something more current
(such as at least the first version where build-dependencies were
defined). :)
--
Colin Watson
le upstream? Is this a "deal breaking
> condition" for debian compliancy?
Well, you definitely have to compile without those optimizations, as,
for instance, not all Debian i386 systems have MMX.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Mon, Jun 17, 2002 at 12:55:25PM +0200, Marc Leeman wrote:
> Colin Watson wrote:
> > What about autobuilders, or anyone who might have to do a non-maintainer
> > upload of the package at some point in the future?
>
> Autobuilders will have a package that is tailored to thei
wanted to remove one of his _uid_'s. And that is *not* possible.
Here's the effect of revoking the self-signature on one of my uids (this
is an old key, but the point remains) - output from 'gpg --list-sigs':
pub 1024D/4917A514 1999-12-31 Colin Watson <[EMAIL PROTECTED]>
archive in order to show it to your AM.
I'd normally expect people to be looking for sponsorship at around the
same time as they're entering the NM queue.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ore then".
The process doesn't have to be linear. You can find someone who's
prepared to sponsor you in the future and advocate you now without them
necessarily having to actively sponsor you (upload your packages) right
now.
> Colin Watson <[EMAIL PROTECTED]> wrote:
> >
y if you have INSTALL in debian/docs or debian/.docs.
dh_make may have added this for you. Remove it and all will be well.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
wx root/root 0 2002-06-21 16:15:17 ./usr/X11R6/lib/libXm.so.3
-> libXm.so.3.0.1
The package name must be changed to libmotif3. I'll file a bug about
this in a moment.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL P
the environment in which it is
built, because of the way dynamic linking works.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
hefrenchiesteam.tuxfamily.org/download/debian/openmotif-2.2.2-1_i386.deb
Er, openmotif is already in Debian ...
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Fri, Jul 12, 2002 at 03:37:29PM +0200, Michael Koch wrote:
> Can someone give me an example how to achieve this ? dpkg/debhelper always
> seems to reset my permissions.
Do the chmod after calling dh_fixperms.
--
Colin Watson [EMAIL PROTECTED]
ls-imap4d: package-has-a-duplicate-relation libmailutils0,
> > libmailutils0 (= 20020713-1)
>
> This is referred to as a bug in lintian. See the bts for more info (-:
Is it? It does look like a duplicate relation to me (the second implies
the first) ...
--
Colin Watson
luding it in /etc in the .deb (perhaps /usr/share/,
or autogenerated) and managing it in your maintainer scripts. Any file
that actually goes in /etc in a .deb will be blithely overwritten by
dpkg on each upgrade, which isn't allowed.
Cheers,
--
Colin Watson [E
ich appears
to be obsolete because oo2c conflicts with it. I think voberon-dev
should depend on libooc-x11-dev instead, but I don't know anything about
Oberon. Any comments?
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
conffiles and so aren't in the .deb and aren't
listed in 'dpkg -S' output, so long as they follow the rules for how
configuration files must be handled.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Tue, Jul 16, 2002 at 02:36:32PM +0200, Alexandre wrote:
> I agree. My question was more on the lines of 'is the configure target
> mandatory in debian/rules?'
Not at all - it's just a convention (popularized by dh_make, I suspect).
--
Colin Watson
ex 2.6.1-5
>
> And I tried the following packages uploads which were all rejected (< or >):
> weex 2.6.1-0woody1
> weex 2.6.1-5woody1
> weex 2.6.1-6woody1
Try -4woody1.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
t, perhaps. The .changes file does have to be signed
after gpg has written the .dsc file, since it contains the md5sum of the
signed .dsc.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscrib
his means the old source packages can't stay around in the
archive, since libglut-dev is generated by both old and new. This makes
transitions more difficult: libglut3 and libglut4 could still coexist on
users' systems, but they could not both be in a distribution at the same
time
package with no content,
>
> I am not sure but isn't it better to use 'Provides: glutg3' instead of
> providing a package glutg3 with no content.
Most dependencies on glutg3 are versioned, and a Provides: can't satisfy
versioned dependencies.
--
Colin Watson
x27;s known to be widely deployed.
Use whatever version you think is appropriate (say, db3) and let
dependencies do the rest of the work for you.
--
Colin Watson [EMAIL PROTECTED]
sixth may also be
a problem depending on how you're interacting with other init script
subsystems - I haven't looked at the details.
--
Colin Watson [EMAIL PROTECTED]
y between a IPv4-only browser and the rest
> of the
^
"Its" "as a stub proxy"
Cheers,
--
Colin Watson [EMAIL PROTECTED]
2]: 550 5.7.1 <[EMAIL PROTECTED]>...
> Relaying denied
For what it's worth, my mails to Indra at that address have been
delivered fine. (Well, I used <[EMAIL PROTECTED]>; is it possible that
some MTA is being brain-dead about case?)
--
Colin Watson [EMAIL PROTECTED]
On Thu, Aug 08, 2002 at 04:03:36PM +0100, Steve Kemp wrote:
> I'm not using them, hence the question. I believe that it's no longer
> necessary to create the links nowadays.
Yep. No need to create the links yourself unless you're building
packages targetted at woo
On Thu, Aug 08, 2002 at 06:39:11PM +0200, Holger Kubiak wrote:
> Why is there no link from /usr/doc to /usr/share/doc ?
There probably will be.
--
Colin Watson [EMAIL PROTECTED]
ut, so don't worry about it. It's better to use
the pristine source tarball provided by upstream where possible and not
needlessly repack it, since this has nice properties like allowing
people to compare md5sums easily.
--
Colin Watson [EMAIL PROTECTED]
On Fri, Aug 16, 2002 at 04:28:53PM -0700, Ian Zimmerman wrote:
> Hi, how can I easily determine the host architecture string in a
> maintainer script?
'dpkg --print-installation-architecture' should do it.
--
Colin Watson [EMAIL PROTECTED]
o problem.
Personally I might be inclined to make the package Architecture: any in
this case, though.
--
Colin Watson [EMAIL PROTECTED]
depend on a conf file
> >which is obsolete as well (it is still there, because it is a conffile, but
> >not supported by debconf).
[...]
> Installing your package will break the PCMCIA stuff,
> at least you are messing with files of other packages.
I read him as saying they
hough.
>
> I assume by this you mean you'd select and copy the correct file at
> binary-package creation time, rather than installation time?
Yeah. It depends heavily on context though - how big the package is, how
well symlinks to conffiles work, etc.
--
Colin Watson [EMAIL PROTECTED]
ful as examples).
Ship 'em in /usr/share/doc//examples then? That's fine, just
keep the configuration file handling as simple as you can.
--
Colin Watson [EMAIL PROTECTED]
and failing.
You'd have to acquire real root privileges from inside the fakeroot,
since the faked filesystem permissions go away as soon as that fakeroot
process dies ...
--
Colin Watson [EMAIL PROTECTED]
love to know how you
keep track of this under the current system.
--
Colin Watson [EMAIL PROTECTED]
en running lintian
in an unstable chroot on my woody system. I don't believe it has
anything to do with the packages (which are processed fine on my
laptop), but I haven't got round to tracking it down further yet.
--
Colin Watson [EMAIL PROTECTED]
ib
>
> Compiling process went without error msgs. 'hello' file has been
> produced. But this "hello" file is not executable. The message is:
> "bash: hello: command not found".
Sounds like you want './hello', not 'hello'.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
On Mon, Sep 02, 2002 at 02:05:48AM +0200, Peter Palfrader wrote:
> On Sun, 01 Sep 2002, Kristis Makris wrote:
> > On Tue, 2002-08-27 at 04:15, Peter Palfrader wrote:
> > > Colin Watson wrote:
> > > > Currently I see no way at all to find out whose requests for
sible to easily distinguish between a first time
> install and an upgrade.
Sections 6.4 and 6.6 of policy describe what arguments will be passed to
the postinst in these cases.
--
Colin Watson [EMAIL PROTECTED]
ave to use
something like a high epoch instead.
--
Colin Watson [EMAIL PROTECTED]
On Mon, Sep 09, 2002 at 07:02:34PM +0200, Matus fantomas Uhlar wrote:
> Colin Watson wrote:
> -> That would require versioned dependencies on virtual packages (versioned
> -> Provides:) to work, but they don't. You'll probably have to use
> -> something like a high e
e below)?
It's been a known bug/feature-request in the packaging system for a long
time.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
On Mon, Sep 09, 2002 at 08:39:09PM +0200, Ryszard Lach wrote:
> Can you remind me where should I upload a non-us package?
non-us.debian.org. By scp, upload to /org/non-us.debian.org/incoming/.
--
Colin Watson [EMAIL PROTECTED]
?
Not usually. The autobuilders ensure that it compiles; for the rest, we
rely on bug reports from users and the occasional blitz by porters to
fix common classes of problems.
--
Colin Watson [EMAIL PROTECTED]
uild and sign in one step, then you'll need to
use debuild rather than dpkg-buildpackage: debsign is in devscripts and
so not called by programs in dpkg-dev.
> Looks like a bug to me.
Nothing I can find documents either DEBEMAIL or DEBFULLNAME for use by
either dpkg-buildpackage or
On Mon, Sep 23, 2002 at 11:38:02AM +0200, Remi VANICAT wrote:
> Of course this mean that you need to have your gnupg secret key there,
> and this may be unwanted.
No, build it unsigned on the remote machine, then copy the .dsc and
.changes back for signing on a local trusted machine.
--
On Mon, Sep 23, 2002 at 12:06:29PM +0200, Dagfinn Ilmari Manns?ker wrote:
> Colin Watson <[EMAIL PROTECTED]> writes:
> > On Mon, Sep 23, 2002 at 11:38:02AM +0200, Remi VANICAT wrote:
> >> Of course this mean that you need to have your gnupg secret key there,
>
o report it in a
> minute)
I think it's been fixed already:
lintian (1.20.18) unstable; urgency=low
[...]
* added python version 1.5, 2.{1,2,3} to checks/scripts, closes: #114164
[...]
-- Sean 'Shaleh' Perry <[EMAIL PROTECTED]> Fri, 13 Sep 2002 09:49:24 -0700
--
> fully python on python and nothing more.
Please still use at least 'python (>= 2.2)' (I don't know the details of
the Python policy, but something with that kind of effect), to help
people trying to work out how to backport packages to stable.
--
Colin Watson [EMAIL PROTECTED]
tom, it's maintained by a team who can be
contacted at [EMAIL PROTECTED]
Cheers,
--
Colin Watson [EMAIL PROTECTED]
ns on.
Well, that depends. Is the compiler hitting an internal compiler error
or something? If so then you do care about the host architecture.
--
Colin Watson [EMAIL PROTECTED]
on, but requires
quite substantially more work than just a quick hack to the name of the
.deb.
--
Colin Watson [EMAIL PROTECTED]
.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
people might disagree. I don't know if changing this in an NMU is
> neccessary but I would do it.
I don't think this is a bug. Some people might even consider it a
feature to be able to set CFLAGS from their environment when building
the package locally.
At any rate I would avoid changing t
ystem(),
> which is, well, yuk).
libapt-pkg-perl gives you AptPkg::Version, which has a compare() method.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
n $package.conffiles start with "/" but one
> conffile contains filename without leading "/"
If that does what I think it does and renders the conffiles entry
ineffective, it's probably a serious bug.
--
Colin Watson [EMAIL PROTECTED]
#x27;s a problem, although hurd-i386 can sometimes turn up
Linux-specific build-dependencies.
sh is SuperH, the Dreamcast chip. Ignore it for now - it doesn't even
have libc6 in the archive, so your build-dependencies are rather
unlikely to be satisfiable there.
rop the dependency.
If you really need a specific version then you'd probably be best off
using a substvar and special-casing for each architecture, but avoid
that if you can as it involves a lot of maintenance.
--
Colin Watson [EMAIL PROTECTED]
treated as an NMU, which is why I use
-k instead of either -m or -e to dpkg-buildpackage, but it's not a
disaster.
--
Colin Watson [EMAIL PROTECTED]
t's
> correct
> now.
The right way to fix this is to make sure that
packagename_upstreamversion.orig.tar.gz is in the parent directory when
you do the build (so in this case fortunes-it_1.51.orig.tar.gz). There's
no need to unpack the .orig.tar.gz yourself.
--
Colin Watson
s way and making Debian-specific changes, I'd
go for having the upstream version as 1.6-, where is the
date on which you constructed the tarball (or some other similar
strictly increasing scheme). Then you keep the upstream version and
still get to make Debian-specific changes with reasonable e
e thing upstream is.
> it lets you unpack the file as is without having to worry about
> overwriting the debianized version.
Use a temporary directory. You should get into the habit of doing this
when unpacking random tarballs anyway.
--
Colin Watson [EMAIL PROTECTED]
27; -
fakeroot because orig tends to depend on clean.
--
Colin Watson [EMAIL PROTECTED]
On Tue, Oct 29, 2002 at 08:24:16AM +0100, Sven Luther wrote:
> On Tue, Oct 29, 2002 at 12:54:28AM +0000, Colin Watson wrote:
> > On Mon, Oct 28, 2002 at 11:46:51PM +0100, martin f krafft wrote:
> > > okay. and i still believe that it even makes sense to have .orig
> > >
's willing? Certainly, an advocate should be somebody who's
worked with you and is familiar with your work.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
On Thu, Oct 31, 2002 at 12:49:20PM +0100, Christian Surchi wrote:
> On Wed, Oct 30, 2002 at 09:37:47PM -0600, Steve Langasek wrote:
> > ldapsearch -P2 -x -h db.debian.org -b ou=Users,dc=debian,dc=org l= > string>
>
> without a d.o login?
Yes. Try
d.
> >
> > That said, the PTS seems to have frozen on november 2/3 or something
> > such, so you would need to look at the build logs directly.
>
> Grmbl. I can't.
Yes you can, see <http://buildd.debian.org/>.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
On Thu, Nov 07, 2002 at 07:18:07PM +, Colin Watson wrote:
> On Thu, Nov 07, 2002 at 07:15:06PM +0100, Oliver Kurth wrote:
> > On Thu, Nov 07, 2002 at 06:51:01PM +0100, Sven Luther wrote:
> > > I also had the problem, but then after a time the package built
> > >
t; notifications, and I can now use [EMAIL PROTECTED] to merge/manipulate bugs
> etc.
A minor nit: you can, technically speaking, use [EMAIL PROTECTED] whether
you're the maintainer or not. Etiquette is the access control there.
--
Colin Watson [EMAIL PROTECTED]
On Wed, Nov 20, 2002 at 01:58:45PM +0100, Sven Luther wrote:
> BTW, i have tried to install the J2sdk1.4 packages, but they complain
> about a missing j2se-common.
Add main to sources.list along with non-free.
--
Colin Watson [EMAIL PROTECTED]
hanks, i've seen that there is ITP of ImageJ in 2000 but the author is
> unreachable, so i posted another ITP.
You should generally just post your intentions to the existing ITP bug
instead. Filing duplicates tends to produce weird results in various web
pages an
ver, or ssh.
What version of lintian? This looks like bug #122742, which has been
fixed.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
n it there.
>
> dpkg-deb mplayer...deb
>
> ..says that /etc/mplayer/codecs.conf exists.
>
> BUT it's not installed in /etc/mplayer/ at all.
If you remove a conffile manually, dpkg won't reinstall it unless you
use the --force-confmiss flag or do a purge/reinstall cycle.
cy in
> order to pass dh_testroot?
You could use DPkg::Build-Options to get apt-get to pass -rfakeroot.
--
Colin Watson [EMAIL PROTECTED]
e" mean in the build target? I'd expect the
build target to build everything appropriate.
--
Colin Watson [EMAIL PROTECTED]
On Thu, Dec 19, 2002 at 02:58:11PM +0100, pp wrote:
> if $mysqlcmd -D mysql -e 'use midgard;' >/dev/null 2>&1 ; then
>
> db_input "high" midgard/error
db_input can return with exit code 30 if the question is skipped. In
that case, you
On Thu, Dec 19, 2002 at 03:45:14PM +0100, pp wrote:
> Colin Watson <[EMAIL PROTECTED]> wrote:
> > On Thu, Dec 19, 2002 at 02:58:11PM +0100, pp wrote:
> > > if $mysqlcmd -D mysql -e 'use midgard;' >/dev/null 2>&1 ; then
> > >
> > &g
nto a whole different style of debconf
programming involving the 'seen' flag. Be very careful when you use this
that the question is not displayed twice to people upgrading with apt
(once when preconfiguring and once when configuring).
--
Colin Watson [EMAIL PROTECTED]
nfig, it's likely to be actively bad. When
preconfiguration is in use, the admin will see the question twice.
--
Colin Watson [EMAIL PROTECTED]
worry about that warning. Accept it as a bug in
dpkg, tell anybody who complains about it that it's a bug in dpkg, and
make your package behave in the simplest possible way.
--
Colin Watson [EMAIL PROTECTED]
801 - 900 of 1012 matches
Mail list logo
