On Tue, Apr 14, 1998 at 01:04:31AM +0200, Christian Hammers wrote:
> How long do programs (normally) have to wait in the Incoming queue ?
Depends on the packages and distribution
Distribution: unstable
Known package
==> one day
Distribution: unstable
Unknown package
==> several
Hi !
How long do programs (normally) have to wait in the Incoming queue ?
Are Joey & co. just too busy or are there other problems why the kde*
programs are starving there =;-)
It's not that the waiting bothers me - it's just... the Incoming queue
of master.debian.org is AFAIK not mirrored and
What's the procedure for moving something that's been uploaded into
unstable into frozen? Whom do I contact and what information do I
need to give them? Do I then send out a debian-*-changes message?
I uploaded something into unstable but have been convinced that it
belongs in frozen.
Should I
Turbo Fredriksson <[EMAIL PROTECTED]> writes:
> I've been trying for the last two days tried to
> build a new version of my package, tcpquota, but
> I'm encountering one problem after the other...
> The problem here is the lines:
>
> dpkg-genchanges: not including original source code in upload
>
Joey Hess <[EMAIL PROTECTED]> writes:
> Turbo Fredriksson wrote:
> > What have I missed? (This is _EXACLY_ as it says in the 'mktemp' manual
> > page!!!)
>
> Yes, that should be safe. Lintian probably just does a simple check. You
> should mail the maintainers and ask for a lintian "override" for
Hi,
I do not know why you think this is a bug; this is supposed to
be a feature! Since the upstream source is not supposed to be
changed for succesive debian revisions, there is no point uploading
it. Presumably you uploaded the sources for the -1 version of
the package, so there is n
On Thu, Apr 09, 1998 at 03:14:33PM +0200, Rainer Clasen wrote:
>
> Carey Evans ([EMAIL PROTECTED]):
> > I've gotten the impression that the best way to do it is to use
> > *pristine* uptream source, which means that the .orig.tar.gz is really
> > the tar file you downloaded. The changes should al
I've been trying for the last two days tried to
build a new version of my package, tcpquota, but
I'm encountering one problem after the other...
When I do a 'sudo build', it packs the source in
a tarball, creates the diffs etc, but when it is
doing the 'dpkg-genchanges' it says:
- s n i p p -
Hi,
__> dpkg --compare-versions 1.0-beta-5 lt 1.0-pre-1 && echo good
good
__> dpkg --compare-versions 1.0-pre-5 lt 1.0 && echo good
Hmm, no god there. Yes, an epoch needed there. Me, I would try
0.9-beta-5 and 0.9-pre-1.
manoj
--
Saints should always be judged guilty un
* APH => Adam P Harris
APH> Ok, here's another one for you DFSG gurus. This one should be easy:
APH>
APH>
APH>
APH>
APH>
APH>
APH>
APH>
APH>
APH>
Check if it allows modified DTD's to be made from it---with _different_
file names, I mean---in the suggested reading (Guidelines...).
Turbo Fredriksson wrote:
> This is the line in the postinst:
>
> - s n i p p -
> TMP_FILE=`mktemp -q /tmp/$0.XX`
> if [ $? -ne 0 ]; then
> echo "$0: Can't create temp file, exiting..."
> exit 1
> fi
> - s n i p p -
>
> What have I missed? (This is _EXACLY_ as it says i
I know I read this at one point, and I _think_ I remember most of it
correctly, but which doc. describes how dpkg compares version numbers?
I think that in the case of tkdesk I may have to use epochs (the
upstream authors have 1.0-beta-1 through 1.0-beta-5 coming before
1.0-pre-1, which comes befor
Hi... I'm just trying to build my latest version
of my TCPQuota, but lintian complains...
- s n i p p -
[papadoc]$ lintian -i tcpquota_1.6.13-3_all.deb
W: tcpquota: possibly-insecure-handling-of-tmp-files-in-maintainer-script
postinst:66
N:
N: The maintainer script seems to access a fil
13 matches
Mail list logo
