t
anyway.
I think we should recommend (but not require) that AM_MAINTAINER_MODE
not be used, and perhaps work to specify an optional debian/rules target
that regenerates the build system in an appropriate way. That seems to
provide the necessary benefits for users who need to change these files
the case then the end user is going to lose out anyway when
trying to modify the package. I'm not arguing that such bugs shouldn't
be fixed, merely that it's a mistake to turn them into showstoppers that
could potentially block more urgent upload requirements.
Cheers,
--
Colin
debbugs to handle PGP signatures years ago. If it's
broken now then something has gone wrong since then.
Thanks,
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Fri, Feb 22, 2008 at 03:41:17PM -0500, Justin Pryzby wrote:
> Colin watson wrote about a scenario where he apparently needed to do
> this:
> http://lists.debian.org/debian-devel/2006/12/msg00647.html
Yes, if you need to use the contents of the package's files in the
preinst then
#x27;m too thick to have my automatic reply software distinguish
> incoming list mail from personal mail, so please remove me from
> the list permanently.
It's more likely a spam forging debian-mentors@lists.debian.org as its
From: address.
--
Colin Watson
ler source package, that's really just the
d-i build system. For actual content you really need to know which
package is responsible for the particular bit of the installation you're
interested in, which can be something of a bootstrapping problem for
those new to the code. Section 6
can't figure out if the fix is
> still in the package or maybe dropped from the unstable upload due to
> cause other problems.
To clarify, it still has to appear in debian/changelog, but it doesn't
have to be in the most recent version; leaving i
ed; that's fine and in that event I'll supersede it with another
proposal and go straight to the transition plan which allows people to
start using UTF-8 manual pages properly. I issued a pre-release version
recently. It's probably best to check it out using bzr:
http://www.chiark.greenen
[Quotes reordered slightly to suit the flow of my reply from argument to
constructive suggestion. :-)]
On Mon, Sep 10, 2007 at 09:56:50PM +0200, Adam Borowski wrote:
> On Mon, Sep 10, 2007 at 07:03:57PM +0100, Colin Watson wrote:
> > On Wed, Aug 15, 2007 at 12:50:53AM +0200, Adam Borow
On Wed, Sep 12, 2007 at 02:25:26AM +0200, Adam Borowski wrote:
> On Tue, Sep 11, 2007 at 09:55:44AM +0100, Colin Watson wrote:
> > > > I do need to find the stomach to look at upgrading groff again, but it's
> > > > not *necessary* (or indeed sufficient)
On Fri, Sep 14, 2007 at 10:39:10AM +0100, Colin Watson wrote:
> On Wed, Sep 12, 2007 at 02:25:26AM +0200, Adam Borowski wrote:
> > On Tue, Sep 11, 2007 at 09:55:44AM +0100, Colin Watson wrote:
> > > Is this what your "hack" pipeline implements? If so, I'd love to s
nt word was "than", so the sentence should read:
>
> "Really, it may have sounded more rude to you, than it was meant to be."
And, to nitpick further, you also ought to leave out the comma before
"than". (With "then", the comma is correct.)
Cheers,
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
not originally made by you.
I hope this will avoid such mistakes in the future.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
s
> more appropriate for my level of expertise...
This is a list for people starting out on the path to becoming Debian
developers. You're probably looking for the debian-user list.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE,
On Thu, Jan 16, 2014 at 04:52:40PM +0100, Marco Balmer wrote:
> On Thu, Jan 16, 2014 at 03:48:41PM +0000, Colin Watson wrote:
> > The package on mentors.d.n has an .orig.tar.bz2, but the version
> > currently in the Debian archive has an .orig.tar.gz. Was this change
> > int
On Thu, Jan 16, 2014 at 03:45:45PM +, Colin Watson wrote:
> On Thu, Jan 16, 2014 at 04:30:52PM +0100, Marco Balmer wrote:
> > For your information:
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735565
>
> Sorry for the delay. I'm building it now. I think
anything special. Moves between sections are
treated as new packages, meaning that an ftpmaster needs to look at them
before they're accepted. Just wait.
--
Colin Watson [EMAIL PROTECTED]
pkg-buildpackage (namely -sa, and possibly
-v if you want to excerpt more of the changelog) than it does to have to
mess about with version numbering just for the benefit of an upload.
Those flags are provided for exactly this purpose.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
nybody
> who is not the maintainer (not even a DD in my case) is not allowed to
> do officially tag it "upstream" and send the mail to [EMAIL PROTECTED]
I would suggest asking the maintainers what they prefer. As far as I
know Debian's tetex maintainers are
nting
versions and so on. What do 'file' and 'objdump -p' say about that file?
--
Colin Watson [EMAIL PROTECTED]
On Fri, Jul 25, 2003 at 12:49:55AM +0200, Andreas Barth wrote:
> there is a RC-bug against xserver-rage128; this package is neither in
> stable, testing nor unstable. So, what to do with this bug?
> http://bugs.debian.org/163631
I think it should be closed. See bug #120460.
Cheers,
nd out *why* that error's being thrown.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
ng libcurl2. Is there a solution for this?
No, Build-Depends are primarily there to make sure the build daemons do
something consistent for unstable, so they should force your package to
always build one way. Just ignore the build-deps for woody instead.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
ut:
$ lftp ftp://ftp.ceplovi.cz/data/www/ceplovi/matej/progs/debian/
cd: Access failed: 550 /data/www/ceplovi/matej/progs/debian: No such file or
directory
Cheers,
--
Colin Watson [EMAIL PROTECTED]
g of the previous versions anyway. A 'closes
> #nn' in the changes list of a previous version won't be considered.
... unless you use the -v option to dpkg-buildpackage, which is often
useful anyway on an initial upload.
--
Colin Watson [EMAIL PROTECTED]
On Thu, Jul 31, 2003 at 10:28:17AM -0400, John Belmonte wrote:
> I'm wondering if the control mailserver can tolerate a PGP/MIME message.
> The case is when you want to combine control commands and a bug
> follow-up, and have your message signed.
Yes, it can.
Cheers,
--
be fully utf-8, but my name has a
> "strange character" that gets converted
>
> So when the uploader checks the name of the Maintainer in the control
> file (not utf-8) with the name in the changelog says that are different,
> and results in a NMU
Why not convert y
7;t easily tell which are which.
Switching to UTF-8 throughout would solve that problem.
So, to summarize, please either use plain ASCII (if you think that the
lack of recoding is a problem) or UTF-8 (if you don't mind); using other
legacy encodings is just storing up trouble.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
me of that directory doesn't matter (much). It's the presence of
the .orig.tar.gz and the version number at the head of debian/changelog
that are important.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
> the rest i wish make automatic.
I think Geert's point is that you've asked for testers and a sponsor but
haven't told anyone where the source is!
Cheers,
--
Colin Watson [EMAIL PROTECTED]
between ISO-8859-1 and UTF-8,
and you needn't worry. The procedure you just described demonstrates
that the file is indeed plain ASCII.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
necessary to name the binary packages, dependencies, and
> the rest.
debian/changelog must also be present.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
On Fri, Aug 08, 2003 at 10:12:52PM +1000, Matthew Palmer wrote:
> On Fri, Aug 08, 2003 at 11:24:13AM +0100, Colin Watson wrote:
> > On Fri, Aug 08, 2003 at 07:38:11PM +1000, Matthew Palmer wrote:
> > > The things which absolutely have to be in a package in order to be
> >
etc. Is there a single spot where one can look? Or is this knowledge I
> will only gain when I use the force?
I found it easiest (years ago) to read the sources.list(5) man page and
learn how those lines map into URLs, so I can then just go off with a
web browser or a
On Tue, Aug 12, 2003 at 11:53:27AM -0700, Eric Winger wrote:
> Colin Watson wrote:
> >That's correct except that you want "non-free" there, not "free".
> >(Ever think you'd hear a Debian developer say that?)
>
> would it be sacreligious to ask w
x file, but my commands aren't being
> executed.
You must rename that to postinst. Your completed source package
shouldn't have any of those example *.ex files in it.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
ight to
> > queue/unchecked (f.k.a Incoming).
>
> Does uploading to Incoming still work?
Yes. (What have you been doing instead?)
--
Colin Watson [EMAIL PROTECTED]
r mechanism
is partly implemented and will be completed in the near future; see the
archives of debian-debbugs for details.
> the bts docs say as soon as a fixed version is in the archive, but there
> are a lot of open bugs tagged "fixed".
The fixed tag is for something differe
should be a control message like everything
else, not a button on the web pages.
--
Colin Watson [EMAIL PROTECTED]
On Sun, Aug 24, 2003 at 05:26:32PM +0200, Goswin von Brederlow wrote:
[Please don't send me private copies of list mail.]
> Colin Watson <[EMAIL PROTECTED]> writes:
> > On Sun, Aug 24, 2003 at 03:28:00PM +0200, Goswin von Brederlow wrote:
> > > I would need a parser
buildd logs [1] say that attempts have been
> made to build the package on other archs. I event got a FTBFS bug
> report. I'm not sure of how I should handle this bug, btw.
You need to get a buildd admin to add your package to the
centrally-maintained Packages-arch-specific list.
e no installed packages own them any
more.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
uiltin echo parses "\n" in bash as well as
> dash.
That isn't mandated by POSIX, though, and there are shells in Debian
that don't do that. I agree with Andreas: use printf instead.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
On Thu, Aug 28, 2003 at 01:24:50PM +0200, Chris Niekel wrote:
> On Thu, Aug 28, 2003 at 10:43:34AM +0100, Colin Watson wrote:
> > That isn't mandated by POSIX, though, and there are shells in Debian
> > that don't do that. I agree with Andreas: use printf instead.
>
tell us more.
> Where are all changelog parsed?
/usr/lib/dpkg/parsechangelog/debian
--
Colin Watson [EMAIL PROTECTED]
xt stage anyway due to increasing the
uninstallability count. There's probably a glitch in the binary-NMU
case.
--
Colin Watson [EMAIL PROTECTED]
non-us rather
than messing around with upload queues (which seem to be a frequent
cause of problems from my impression of the number of people asking
questions about them). In the case of an upload queue, you may have to
upload a .commands file to delete the extra files; there's documentation
of th
If you want a real-life example, I can unashamedly plug the groff
package, although I've just noticed that the DH_EXCLUDE := -Ngroff-x11
stuff is now obsolete.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
make the
whole dependency chain deadlock. Please don't try it. :)
--
Colin Watson [EMAIL PROTECTED]
On Mon, Sep 08, 2003 at 07:36:45PM +0200, Bruno Rodrigues wrote:
> I need a sponsor to update two packages and close some bugs:
>
> mantis (0.17.5-7+1) unstable; urgency=low
[...]
> php4-imagick (0.9.7-0+2) unstable; urgency=low
I'm looking at these now.
Version 3.6.1
>* Better detection of wrong mysql's root user/pass parameters
I've uploaded this (I'd prefer not to get into regular sponsorship of
this as I don't know PHP, but these changes were easy enough to check
without that knowledge). Steve Langasek tell
VARIABLE
SUBSTITUTION".
> and give some examples for package which are made from a
> single source package and automate using the description in
> sub-packages?
Not sure about that, I'm afraid. Using substvars is reasonably common
though (if nothing else, dpkg-shlibdeps uses them)
sing "lintian -i" - it will tell you more about the errors and
> warnings that it finds.
You can also pipe the output from lintian through lintian-info if you
don't want to spend time running lintian again.
--
Colin Watson [EMAIL PROTECTED]
not setuid/setgid no, but I still think it's best to not trust
> the PATH - sure it's not critical, but it's a good think "just in
> case".
Just in case somebody decides to move the programs in question? Witness
grep.
--
Colin Watson [EMAIL PROTECTED]
ou use the -v option to dpkg-buildpackage to include the
changelog entries from all the NMUs, which I personally think should be
best practice.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
when a security
update to xfree86 is released. For people running testing, xfree86 and
LTSP won't propagate into testing at the same time, and so on. You need
to plan for these kinds of things.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
tion. Sponsors are the best candidates for this.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
ept binaries from
elsewhere.
> Does the acknoledgements actually go to the uploder, i.e. the person
> signing the changes, or just to the Maintainer and Changed-By persons?
They go to the Maintainer: in the .changes file.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
On Wed, Oct 22, 2003 at 09:53:45AM +1000, Martin Michlmayr wrote:
> * Colin Watson <[EMAIL PROTECTED]> [2003-10-21 19:15]:
> > Boggle. Your sponsor just signed something you'd built? Sponsors are
> > supposed to build packages themselves, not accept binaries from
> >
days for the maintainer to respond is adequate, IMHO.
Needless to say, though, be doubly careful to get the second NMU right.
:-) You may find debdiff useful (in general, not just in this case).
--
Colin Watson [EMAIL PROTECTED]
ally each
time it becomes necessary; that way you might also remember to tell
upstream that they should update their copies, which is something a good
Debian maintainer should be doing.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
uestions, while *your package* is managing the file. As
a result, lots of people blame debconf for bugs that are the fault of
individual packages, which gives debconf a bad name.)
Cheers,
--
Colin Watson [EMAIL PROTECTED]
have time to
review and deploy it, though.
--
Colin Watson [EMAIL PROTECTED]
hat case dh_make is just being stupid. You can delete those lines
from debian/rules.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
ax, and ignore the warning.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
nt unstable libc.
That's been in unstable for a while; try updating.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
ig.tar.gz.
The packaging tools never create .orig.tar.gz. You're supposed to put it
there yourself, and it should usually be an exact copy of the upstream
tarball.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
e says "Architecture: all", not "Architecture: any".
Cheers,
--
Colin Watson [EMAIL PROTECTED]
nf prompting).
Sometimes you have to prompt in the postinst, namely when you need your
package to be unpacked before being able to figure out what the question
should be. I don't know whether that applies in this case, but it does
happen.
--
Colin Watson [EMAIL PROTECTED]
ort UTF-8 really quite well, though, with a tiny bit
of locales configuration. Even woody systems support them with only a
few unpleasant bugs.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
?) unavailable.
packages.debian.org is just a search engine, not the archive itself.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
e
warning if there's some serious practical problem.
--
Colin Watson [EMAIL PROTECTED]
his into a man vs. info war! Anyway, proper UTF-8
support often involves a significant amount of upstream design work and
development, which contrasts somewhat with things that have been release
goals in the past.
Something with the force of a "should" is probably
On Tue, Dec 16, 2003 at 04:38:23PM +0100, Sven Luther wrote:
> On Tue, Dec 16, 2003 at 02:48:01PM +0000, Colin Watson wrote:
> > Depends how practical that is, I guess. For example, it's still unknown
> > when groff will support it properly (as in UTF-8 input; UTF-8 output is
On Tue, Dec 16, 2003 at 07:00:26PM +0100, Sven Luther wrote:
> On Tue, Dec 16, 2003 at 05:22:36PM +0000, Colin Watson wrote:
> > On Tue, Dec 16, 2003 at 04:38:23PM +0100, Sven Luther wrote:
> > > Yep, noticed that also, man simply removes the - from manpages,
> > > w
On Tue, Dec 16, 2003 at 09:23:01PM +0100, Sven Luther wrote:
> On Tue, Dec 16, 2003 at 07:44:35PM +0000, Colin Watson wrote:
> > On Tue, Dec 16, 2003 at 07:00:26PM +0100, Sven Luther wrote:
> > > Well, i most definitively cannot see it, and i am using a UTF-8 aware
> > >
ariables such as LANG across the ssh connection. If
anyone knows of a not-too-hacky way to do this, I'd be interested.
--
Colin Watson [EMAIL PROTECTED]
installed
as part of the binary package? That way you can write your documents as
you suggested originally but you don't have to worry about where to put
additional.1.
--
Colin Watson [EMAIL PROTECTED]
On Tue, Dec 23, 2003 at 02:43:42AM +0100, Matthias Urlichs wrote:
> Hi, Colin Watson wrote:
> > Does your package contain any architecture-dependent code, i.e. XS
> > modules (look for .so, .bs)? If so, you probably want to put the
> > modules in /usr/lib/perl5 and ignore
hen you
notice them. The bug tracking system has a few bugs meaning that it
doesn't react very well to running out of disk space (although it does
at least keep all the data *somewhere*), and this was a casualty. I've
fixed up the bug log and marked the affected message for reprocessing.
C
if I find that I have some
spare time.
--
Colin Watson [EMAIL PROTECTED]
ring security
> > scrutiny).
>
> Just upload a new, fixed version.
Note that you need to upload a new version anyway, as components (main,
contrib, non-free) are not overridden by the archive administrators.
--
Colin Watson [EMAIL PROTECTED]
urate description of debmake, as should be clear from
its package description. The debmake package contains debstd, which is a
monolithic program occupying roughly the same space as debhelper, and
deb-make, which is analogous to dh_make.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
On Sun, Oct 17, 2004 at 09:35:32PM +0200, martin f krafft wrote:
> also sprach Colin Watson <[EMAIL PROTECTED]> [2004.10.17.2031 +0200]:
> > That isn't an accurate description of debmake, as should be clear
> > from its package description. The debmake package conta
nce when the day ends.
debian/rules files don't need to have a complete debhelper usage manual
embedded in them. Use the documentation.
--
Colin Watson [EMAIL PROTECTED]
ill include previous changelog
entries.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
u confirmed with
him that he's OK with you taking them?
That said, the ITA was several months ago ...
Cheers,
--
Colin Watson [EMAIL PROTECTED]
(CURDIR), but I should probably take that up with
dh-make-perl ...
Cheers,
--
Colin Watson [EMAIL PROTECTED]
e control
fields to the current locale for output by 'dpkg -s' and the like.
(Likewise 'apt-cache show'.) This might make it a stretch for policy to
recommend it, but I see no reason why packages can't start using UTF-8
for things like maintainer names before then.
--
Colin Watson [EMAIL PROTECTED]
're using debian/hatari.manpages, which is fine, then make sure
you put debian/hatari.1 there and not just hatari.1.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
ose lists aren't being updated. Don't worry about
it.
By the way, why did you create a new bug rather than retitling the
existing one? You shouldn't do that.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
to be specified, in this example "2.3.0". All four
components may still be used if someone wishes to do so.
--
Colin Watson [EMAIL PROTECTED]
debian
> revision.
Debian revisions x.1, x.2, etc. are generally used for non-maintainer
uploads.
--
Colin Watson [EMAIL PROTECTED]
> Why are you surprised? If it's because you prefer info, you can just
> > provide a minimal manpage and refer to the info documentation in it.
>
> I am surprised because i saw programs with an automatic created debian
> manpage or without a manpage.
It's a bug not to have a man page. Sadly, we have bugs ...
--
Colin Watson [EMAIL PROTECTED]
ent, so for now I'd say just
wait.
--
Colin Watson [EMAIL PROTECTED]
looked at this, but why would one generate a new
.orig.tar.gz that isn't original? .diff.gz bloat is to be lived with.
--
Colin Watson [EMAIL PROTECTED]
On Tue, Feb 17, 2004 at 02:42:20AM -0800, Joshua Kwan wrote:
> On Tue, Feb 17, 2004 at 10:16:17AM +0000, Colin Watson wrote:
> > Huh? I haven't looked at this, but why would one generate a new
> > .orig.tar.gz that isn't original? .diff.gz bloat is to be lived with.
>
s naming everything after women -
> nobody else has the slightest idea of what does what...
In case you haven't seen it:
http://cvs.debian.org/dak/docs/README.names?cvsroot=dak
--
Colin Watson [EMAIL PROTECTED]
ld be easier since you can
reuse the old packaging, though (grab it from snapshot.debian.net if
nothing else). Do check for bugs against it that were closed by the
removal, though.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
ful because it adds extra complexity to the unpack order: this is
why policy recommends against it.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
1 - 100 of 1012 matches
Mail list logo
