On Mon, Jun 14, 2010 at 12:25:07PM +0200, Jakub Wilk wrote:
>> Ansgar Burchardt writes:
>>> I think this is a very good method to communicate with other team
>>> members about the current state of packages.
> Leaving notes is a good communication method? Seriously?
> How about *talking* to eac
On Sat, Feb 21, 2009 at 06:12:15PM +0100, Michael Rasmussen wrote:
> The source package does not postfix the source folder with version
> number which will cause lintian to complain.
> Orig:
> foo\
> subdir1
> subdir2
> My suggestion:
> foo-x.y.z\
> subdir1
> subdir2
dpk
On Thu, Jan 29, 2009 at 07:13:59PM +0100, Thorsten Alteholz wrote:
> libctl.so.3 libtcl3 #MINVER#
>scm_list_...@base
>scm_object_prope...@base
>(...)
>lintian -I -E libctl3_3.0.3-2_i386.deb
>E: libctl3: symbols-file-contains-current-version-with-debian-revision on
> symbol
On Wed, Jan 28, 2009 at 10:12:00AM -0600, Jordi Guti??rrez Hermoso wrote:
> it? I've been reading the dpkg-gensymbols manpage and chapter 8 in
> Policy, but I still don't understand how to generate the symbol list
http://qa.debian.org/cgi-bin/mole/seedsymbols has some autogenerated
symbols files
On Fri, Jan 23, 2009 at 04:05:38PM +0100, Andreas Tille wrote:
> I'm probably blind for the problem but this exit status 128 without
> any debug information is quite less. What are the best strategies
> to track down the problematic line of code which causes the problem.
I've not looked at the p
On Mon, Jan 19, 2009 at 01:17:06PM +, Neil Williams wrote:
> On what basis are you misreading my email as Debian-wide? The original
> email clearly stated that I was changing my sponsoring requirements. Is
This wasn't quite so clear as it might have been - the subject line is
much broader and
On Sun, Jan 18, 2009 at 07:59:50PM +, Neil Williams wrote:
> Mark Brown wrote:
> > translations until translations are done. Another way is to allow the
> > translations to lag a bit but ensure that when they are available they
> > are included promptly.
> That doe
On Sun, Jan 18, 2009 at 05:24:05PM +, Neil Williams wrote:
> Olivier Berger wrote:
> > > using debconf that requires sponsorship, that debconf translations are
> > > requested and updated by the maintainer on an ongoing basis.
> > You mean "that requires [my] sponsorship" ?
...
> In most c
On Sat, May 31, 2008 at 03:19:02PM -0500, Paul Johnson wrote:
> I'm randomly downloading packages. If you can point me to one that
> has source code patches correctly applied, I'd really appreciate it. I
> want to get it right :-)
zlib uses patches. Looking for packages with build dependencies
On Tue, Feb 19, 2008 at 10:59:10AM +0100, Bas Wijnen wrote:
> If we build separate infrastructure to test it, it would likely also try
> to do this for every upload. And preferrably on different (or even all)
> architectures we support. So if we make this whole extra check work
> right, it isn't
On Mon, Feb 18, 2008 at 05:03:24PM +0100, Bas Wijnen wrote:
> On Mon, Feb 18, 2008 at 12:47:41PM +0000, Mark Brown wrote:
> > On Sun, Feb 17, 2008 at 11:55:03PM +0100, Bas Wijnen wrote:
> > > No, I don't want to force a version, I want the package to force it.
> >
On Sun, Feb 17, 2008 at 11:55:03PM +0100, Bas Wijnen wrote:
> On Sun, Feb 17, 2008 at 09:29:59PM +0000, Mark Brown wrote:
> > On Sun, Feb 17, 2008 at 08:08:47PM +0100, Bas Wijnen wrote:
> > OTOH if the standard Debian build process jumps through unusual hoops
> > like forcin
On Sun, Feb 17, 2008 at 08:08:47PM +0100, Bas Wijnen wrote:
> The fact that there exist packages which work properly without
> recompiling from source doesn't mean it's a good default. IMO the
> default should be to always compile from source. Yes, that means hassle
> for the packager; it's pret
On Wed, Jan 16, 2008 at 11:47:23AM -0800, Russ Allbery wrote:
> the symbols file. (My recommendation would be to drop the Debian revision
> on all the versions in the symbols file for zlib1g, on the grounds that
> the introduction of new symbols was an upstream change so any package of,
JFTR thi
On Wed, Jan 16, 2008 at 10:28:46AM +, Neil Williams wrote:
> On Tue, 2008-01-15 at 12:50 +0000, Mark Brown wrote:
> > On Tue, Jan 15, 2008 at 10:44:32AM +, Neil Williams wrote:
> > Right, as you say the problems here are nothing to do with symbols
> > files or symbol
On Tue, Jan 15, 2008 at 10:44:32AM +, Neil Williams wrote:
> On Tue, 2008-01-15 at 09:35 +0100, Stefano Zacchiroli wrote:
> > On Mon, Jan 14, 2008 at 06:56:18PM +, Neil Williams wrote:
> > > Quick summary: IMHO, symbols files are largely irrelevant if not
> > > supported upstream via versi
On Mon, Aug 27, 2007 at 10:44:20AM +0100, Neil Williams wrote:
> Kapil Hari Paranjape <[EMAIL PROTECTED]> wrote:
> > *Always* use the Debian version of the .orig.tar.gz by doing "apt-get -d
> > source pkg".
> > Do *not* get the upstream .tar.gz which may have changed for some
> > mysterious reas
On Fri, Jul 27, 2007 at 10:16:20PM +0200, Christoph Haas wrote:
> That's done already. If m.d.n detects that a package is uploaded (by
> monitoring the debian-devel-changes mailing list) then the
> maintainer/sponsoree gets an email and the package is removed. The only
> exception is when package
On Sat, Jun 02, 2007 at 12:26:22PM -0400, Simon wrote:
> screwing that up. I don't see why the build system isn't just
> extended to handle bz2 files, it's one of the things that bugs me
> about debian packaging.
That's happening - support for bzip2 compressed tarballs is in dpkg-dev
in etch so
On Sun, Jan 14, 2007 at 02:43:12PM -0500, Roberto C. Sanchez wrote:
> I agree. However, I think the issue concerns the "requirement" that
> someone's preferences be followed. For example, it is one thing to say,
> "I can't sponsor your package because you use cdbs and I don't know
> anything abo
On Tue, Jan 02, 2007 at 02:05:01PM +1100, Robert Collins wrote:
> The point of packaging is to let things work as well as possible by
> default. Its not true to say that kernels and libraries are identical in
> their constraints : and I haven't claimed that. What I have claimed is
> that in no cas
On Tue, Dec 19, 2006 at 02:31:32AM -0500, Joe Smith wrote:
> "Kevin Coyner" <[EMAIL PROTECTED]> wrote in message
> >f-spot (0.2.2-0ubuntu1) feisty; urgency=low
> >
> > * Update to 0.2.2 upstream
> That is interesting. If that is followed by annother ubuntu changlog entry
> it makes perfect sense
On Mon, Dec 11, 2006 at 10:58:27AM -0800, Russ Allbery wrote:
> Neil Williams <[EMAIL PROTECTED]> writes:
> > How does this compare with other helper scripts like debuild and
> > pdebuild?
> Those aren't used as part of the package build process; they're wrappers
> around it that one doesn't have
On Thu, Aug 24, 2006 at 07:54:59PM +0900, Charles Plessy wrote:
> But it does not explain the difference between the archived bugs which
> are not findable and the archived bugs which can be manipulated.
This started happening with the introduction of version tracking: bugs
aren't archived in the
On Sat, Jan 28, 2006 at 01:04:49PM -0500, [EMAIL PROTECTED] wrote:
> If they feel the need to do it themselves, make sure they have all 12
> architectures, for each of unstable, testing, stable, and oldstable,
> and file bugs when packages aren't kept up to date.
> :)
Restricting themselves to th
On Wed, Jan 25, 2006 at 11:17:09PM +0100, martin f krafft wrote:
> also sprach Mark Brown <[EMAIL PROTECTED]> [2006.01.24.2229 +0100]:
> > People sometimes do this so they can ship something targetted at stable
> > (one of my upstreams insists on doing this and also doesn&
On Tue, Jan 24, 2006 at 01:23:34PM -0800, Russ Allbery wrote:
> Yeah, I agree with your general argument, but I can also see where he's
> coming from. He's applying the RPM model where this is how people
> normally handle RPMs of software that Red Hat itself isn't maintaining.
> He probably doesn
On Sat, Dec 31, 2005 at 03:37:03AM +0100, Daniel Leidert wrote:
> Are there special things I need to care of? Does anyone know a package,
> where the configuration files moved? I already added a NEWS file. But
> not every user installed apt-listchanges, so I should also inform him
> during update.
On Mon, Aug 02, 2004 at 06:17:05PM +0200, Andreas Metzler wrote:
> Basically that is up to you as maintainer. Having open bugs in the BTS
> tagged woody that you are not going to fix only serves one purpose:
> documentation. If you do not think this is necessary close it.
The usual reason to keep
On Mon, Aug 02, 2004 at 06:17:05PM +0200, Andreas Metzler wrote:
> Basically that is up to you as maintainer. Having open bugs in the BTS
> tagged woody that you are not going to fix only serves one purpose:
> documentation. If you do not think this is necessary close it.
The usual reason to keep
On Tue, Dec 23, 2003 at 05:59:53PM +0100, Florent Rougon wrote:
> which I don't understand since the m68k build log (as well as those for
> all other architectures) looks OK :
Check the archive to see if the package has actually been uploaded for
m68k - the buildd web page reports the build when
On Tue, Dec 23, 2003 at 05:59:53PM +0100, Florent Rougon wrote:
> which I don't understand since the m68k build log (as well as those for
> all other architectures) looks OK :
Check the archive to see if the package has actually been uploaded for
m68k - the buildd web page reports the build when
On Mon, Oct 20, 2003 at 02:37:07PM +0200, Robert Lemmen wrote:
> - bump the version number a bit and add a respective changelog entry,
> then re-upload
This is what you should do. You might also want to version the build
depend on the library.
--
"You grabbed my hand and we fell into it, lik
On Mon, Oct 20, 2003 at 02:37:07PM +0200, Robert Lemmen wrote:
> - bump the version number a bit and add a respective changelog entry,
> then re-upload
This is what you should do. You might also want to version the build
depend on the library.
--
"You grabbed my hand and we fell into it, lik
On Tue, Sep 09, 2003 at 12:45:40AM +0100, Colin Watson wrote:
> 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 this somewhere ...
Or just sit there and watch the mails until they stop - the que
On Tue, Sep 09, 2003 at 12:45:40AM +0100, Colin Watson wrote:
> 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 this somewhere ...
Or just sit there and watch the mails until they stop - the que
on their own merits
but assesses other things like dependencies separately - if look at
something like powertweak this is explicitly stated:
powertweak (0.99.4-19 to 0.99.5-1)
Maintainer: Mark Brown
39 days old (needed 10 days)
Valid candidate
Invalidated by dependency
No
on their own merits
but assesses other things like dependencies separately - if look at
something like powertweak this is explicitly stated:
powertweak (0.99.4-19 to 0.99.5-1)
Maintainer: Mark Brown
39 days old (needed 10 days)
Valid candidate
Invalidated by dependency
No
On Mon, Aug 25, 2003 at 11:52:06AM +0200, Roland Mas wrote:
> For anyone interested: one month has passed. I've been away for
> holidays, but I found no email from Eray in my inbox when coming back.
Unsurprisingly enough he hasn't contacted me either.
--
"You grabbed my hand and we fell into i
On Mon, Aug 25, 2003 at 11:52:06AM +0200, Roland Mas wrote:
> For anyone interested: one month has passed. I've been away for
> holidays, but I found no email from Eray in my inbox when coming back.
Unsurprisingly enough he hasn't contacted me either.
--
"You grabbed my hand and we fell into i
On Tue, May 13, 2003 at 01:29:00AM +0100, Colin Watson wrote:
> On Mon, May 12, 2003 at 05:41:40PM -0600, Jack Moffitt wrote:
> > Perhaps an easy thing to do would just be to show whether or not a
> > pckage is signed by a key which is signed by a real debian developer.
> Surely getting that sign
On Tue, Apr 29, 2003 at 03:35:19PM +0200, Sebastian Henschel wrote:
> so my question is: shall i drop the support for the old nodes, too?
> personally, i am favoring that solution, but what do you think?
That seems to be the sensible solution.
--
"You grabbed my hand and we fell into it, like a
On Sat, Feb 08, 2003 at 11:42:39AM +1100, Iain wrote:
> I am having a problem using debconf in my postinst:
> ./configure --admin $ADMIN --domain $DOMAIN --bindir /usr/sbin
> --notify $NOTIFY --install
> The problem is that when it gets to the above configure line (which expects
> user
On Sat, Feb 08, 2003 at 11:42:39AM +1100, Iain wrote:
> I am having a problem using debconf in my postinst:
> ./configure --admin $ADMIN --domain $DOMAIN --bindir /usr/sbin --notify
>$NOTIFY --install
> The problem is that when it gets to the above configure line (which expects user
>i
On Saturday, September 14, 2002, at 09:22 AM, martin f krafft wrote:
dpkg wants:
gpg: skipped `martin f. krafft <[EMAIL PROTECTED]>': secret key not
available
But your key says
uidMartin F. Krafft (Debian)
<[EMAIL PROTECTED]>
which is not the same since it has
On Mon, Sep 09, 2002 at 08:13:13PM +0200, Matus fantomas Uhlar wrote:
> -> Look at how the atlas2 package does this.
> I did it - it seems it has multiple modules for multiple instruction sets.
> However, that would require me to recompile those packages which sems like
> no good idea (it will be
On Mon, Sep 09, 2002 at 08:13:13PM +0200, Matus fantomas Uhlar wrote:
> -> Look at how the atlas2 package does this.
> I did it - it seems it has multiple modules for multiple instruction sets.
> However, that would require me to recompile those packages which sems like
> no good idea (it will b
On Mon, Sep 09, 2002 at 06:19:08PM +0200, Matus fantomas Uhlar wrote:
> I'd like to do it that way that my package would not cause any conflicts,
> and would not be automatically replacedm therefore I think it would be best
> to name these packages like "$package-$cpu"
Look at how the atlas2 pack
On Mon, Sep 09, 2002 at 06:19:08PM +0200, Matus fantomas Uhlar wrote:
> I'd like to do it that way that my package would not cause any conflicts,
> and would not be automatically replacedm therefore I think it would be best
> to name these packages like "$package-$cpu"
Look at how the atlas2 pac
On Thu, Aug 29, 2002 at 03:05:52PM +0200, Raphael Hertzog wrote:
> It's not a real concern anyway, since the BTS is not meant to contact
> someone directly but more to keep a record of what's going on.
It bothers me that if you e-mail the bug report you won't reach a
responsible person (either or
On Thu, Aug 29, 2002 at 02:59:54PM +0200, Jérôme Marant wrote:
> On Thu, Aug 29, 2002 at 01:49:29PM +0100, Mark Brown wrote:
> > Remember that with a BTS based solution the e-mails aren't going to miss
> > either you or the person being sponsored by default and there's
On Thu, Aug 29, 2002 at 03:05:52PM +0200, Raphael Hertzog wrote:
> It's not a real concern anyway, since the BTS is not meant to contact
> someone directly but more to keep a record of what's going on.
It bothers me that if you e-mail the bug report you won't reach a
responsible person (either o
On Thu, Aug 29, 2002 at 02:59:54PM +0200, Jérôme Marant wrote:
> On Thu, Aug 29, 2002 at 01:49:29PM +0100, Mark Brown wrote:
> > Remember that with a BTS based solution the e-mails aren't going to miss
> > either you or the person being sponsored by default and there's
On Thu, Aug 29, 2002 at 02:11:20PM +0200, Jérôme Marant wrote:
> I have a recent case of someone who NMU'ed packages of someone
> I do sponsor but I wasn't aware of that.
For things like that the PTS is probably the way to go.
> I would like an entry point for communicating with the sponso
On Thu, Aug 29, 2002 at 02:11:20PM +0200, Jérôme Marant wrote:
> I have a recent case of someone who NMU'ed packages of someone
> I do sponsor but I wasn't aware of that.
For things like that the PTS is probably the way to go.
> I would like an entry point for communicating with the spons
On Mon, Aug 26, 2002 at 04:40:51PM +0200, Raphael Hertzog wrote:
> That's why I went away and requested what's necessary :
> http://bugs.debian.org/151949
> Unfortunately, Anthony Towns doesn't agree with me because some IRCers
> misinterpreted the last thread about it.
No, I'm pretty sure there
On Mon, Aug 26, 2002 at 04:40:51PM +0200, Raphael Hertzog wrote:
> That's why I went away and requested what's necessary :
> http://bugs.debian.org/151949
> Unfortunately, Anthony Towns doesn't agree with me because some IRCers
> misinterpreted the last thread about it.
No, I'm pretty sure ther
On Fri, Aug 16, 2002 at 01:28:07PM +0100, Will Newton wrote:
> Rather at a tangent, but it appears from reading the archives of
> debian-newmaint that no NM has been accepted as a developer since week ending
> 12 May. Is this correct?
It doesn't appear so - there appears to have been at least o
On Fri, Aug 16, 2002 at 01:28:07PM +0100, Will Newton wrote:
> Rather at a tangent, but it appears from reading the archives of
> debian-newmaint that no NM has been accepted as a developer since week ending
> 12 May. Is this correct?
It doesn't appear so - there appears to have been at least
On Wednesday, July 31, 2002, at 09:43 PM, Ryszard Lach wrote:
I'm just wondering why my #DEBHELPER# entries are being silently removed
instead of changed to /usr/doc/package symlinks creation/removal
sections. Any ideas ?
It's a deliberate change, part of completing the /usr/share/doc
transit
On Wednesday, July 31, 2002, at 09:43 PM, Ryszard Lach wrote:
> I'm just wondering why my #DEBHELPER# entries are being silently removed
> instead of changed to /usr/doc/package symlinks creation/removal
> sections. Any ideas ?
It's a deliberate change, part of completing the /usr/share/doc
tra
On Wed, Jul 31, 2002 at 08:52:01AM +0200, Eric Van Buggenhaut wrote:
> On Tue, Jul 30, 2002 at 12:24 -0500, Mark Brown wrote:
> > This is an error. *Nothing* outside of /etc should be a conffile. See
> > policy 11.7.2.
> We're talking about conffiles here. P
On Wed, Jul 31, 2002 at 08:52:01AM +0200, Eric Van Buggenhaut wrote:
> On Tue, Jul 30, 2002 at 12:24 -0500, Mark Brown wrote:
> > This is an error. *Nothing* outside of /etc should be a conffile. See
> > policy 11.7.2.
> We're talking about conffiles here. P
On Tuesday, July 30, 2002, at 09:34 PM, Ian Zimmerman wrote:
The implication might be that the best way is not to ship the dynamic
book files at all, and just assume they are in the user's home
directory or subdirectory thereof and document where to get them.
That's all well and good if you've
On Tuesday, July 30, 2002, at 09:34 PM, Ian Zimmerman wrote:
> The implication might be that the best way is not to ship the dynamic
> book files at all, and just assume they are in the user's home
> directory or subdirectory thereof and document where to get them.
That's all well and good if yo
On Tue, Jul 30, 2002 at 06:14:55PM +0200, Eric Van Buggenhaut wrote:
> I don't agree with you here. When you have games that use high scores
> files, these are placed in /var as per FHS 5.4
> (http://www.debian.org/doc/packaging-manuals/fhs/fhs-5.4.html) and
> obvioulsy tagged as conffiles (you do
On Tue, Jul 30, 2002 at 06:14:55PM +0200, Eric Van Buggenhaut wrote:
> I don't agree with you here. When you have games that use high scores
> files, these are placed in /var as per FHS 5.4
> (http://www.debian.org/doc/packaging-manuals/fhs/fhs-5.4.html) and
> obvioulsy tagged as conffiles (you d
On Tue, Jul 30, 2002 at 04:15:11PM +0200, Eric Van Buggenhaut wrote:
> When you install crafty for the first time, it installed compiled
> opening books in /var/lib/crafty. Then, as it plays against you, it
> 'learns' from the games and add the new moves to the opening books
> that live in /var/li
On Tue, Jul 30, 2002 at 04:15:11PM +0200, Eric Van Buggenhaut wrote:
> When you install crafty for the first time, it installed compiled
> opening books in /var/lib/crafty. Then, as it plays against you, it
> 'learns' from the games and add the new moves to the opening books
> that live in /var/l
On Wed, May 29, 2002 at 01:33:26PM +0100, Steve Kemp wrote:
> It was my understanding that this should mark the given file as an
> init file - but this doesn't appear to be the case; what is it I'm missing?
debian/conffiles. You need to mark it as a configuration file for
yourself.
--
"You
On Tue, May 28, 2002 at 01:12:38AM -0700, Sean 'Shaleh' Perry wrote:
> setting it to Potato shows that it has either been fixed or obsoleted in more
> recent versions.
Though the more common thing is just to close the bug unless it's
frequently reported.
--
"You grabbed my hand and we fell int
On Tue, Apr 30, 2002 at 10:01:23AM +0300, Antti-Juhani Kaijanaho wrote:
> Either the bug is a mistake or the ftpmasters have overridden your
> package's priority.
One common reason for this to happen is that the maintainer changes the
priority of the package in the control file - the archive soft
On Tue, Apr 30, 2002 at 10:01:23AM +0300, Antti-Juhani Kaijanaho wrote:
> Either the bug is a mistake or the ftpmasters have overridden your
> package's priority.
One common reason for this to happen is that the maintainer changes the
priority of the package in the control file - the archive sof
On Thu, Mar 28, 2002 at 05:06:13PM +0100, pp wrote:
> Is there any way to use dch , to increase only version number?
If you specify a changelog entry on the command line dch won't drop you
into an editor.
--
"You grabbed my hand and we fell into it, like a daydream - or a fever."
msg05847/p
On Thu, Mar 28, 2002 at 05:06:13PM +0100, pp wrote:
> Is there any way to use dch , to increase only version number?
If you specify a changelog entry on the command line dch won't drop you
into an editor.
--
"You grabbed my hand and we fell into it, like a daydream - or a fever."
pgpIEmfMCcEG
On Mon, Mar 18, 2002 at 12:33:40AM +1100, Jamie Wilkinson wrote:
> So, as I understand it, there's an _incompatible_ API change (and thus
> requiring a SONAME change) when:
> * function prototypes (incl names) that are exported are changed or obsoleted
> * structs change or are obsoleted
> I thi
On Mon, Mar 18, 2002 at 12:33:40AM +1100, Jamie Wilkinson wrote:
> So, as I understand it, there's an _incompatible_ API change (and thus
> requiring a SONAME change) when:
> * function prototypes (incl names) that are exported are changed or obsoleted
> * structs change or are obsoleted
> I th
it
won't be rebuilt automatically.
This means that your package should be built for m68k (or at least have
a build attempted) at some point since it is still uncompiled for m68k,
it's just a quesiton of when.
> On Wed, 2002-02-20 at 00:24, Mark Brown wrote:
> > On Tue, Feb 19, 2
it
won't be rebuilt automatically.
This means that your package should be built for m68k (or at least have
a build attempted) at some point since it is still uncompiled for m68k,
it's just a quesiton of when.
> On Wed, 2002-02-20 at 00:24, Mark Brown wrote:
> > On Tue, Feb 19, 2
On Tue, Feb 19, 2002 at 10:43:45PM +0200, Alwyn Schoeman wrote:
> It then made the status given-back and labeled it out-of-date.
> This was 30 January 2002. The sources are now available but
> it doesn't seem to be up for rebuilding?
It is up for rebuilding but nothing has decided to go back and
On Tue, Feb 19, 2002 at 10:43:45PM +0200, Alwyn Schoeman wrote:
> It then made the status given-back and labeled it out-of-date.
> This was 30 January 2002. The sources are now available but
> it doesn't seem to be up for rebuilding?
It is up for rebuilding but nothing has decided to go back an
On Tue, Jan 29, 2002 at 06:19:02PM +0100, Stefan Schwandter wrote:
> all...). so the woody tag is certainly not appropiate anymore. Should I
> close the bug, since it is fixed in the current package (actually it was
> fixed , or tag it potato instead (because the buggy version is in
> potato)?
G
On Tue, Jan 29, 2002 at 06:19:02PM +0100, Stefan Schwandter wrote:
> all...). so the woody tag is certainly not appropiate anymore. Should I
> close the bug, since it is fixed in the current package (actually it was
> fixed , or tag it potato instead (because the buggy version is in
> potato)?
On Mon, Jan 28, 2002 at 02:18:07PM +0100, Stefano Zacchiroli wrote:
> So I reupload the package _including .orig.tar.gz_ and I received some
> mails like the following, what I have to do?
You need to change the upstream version number in some manner that won't
conflict with whatever upstream do n
On Mon, Jan 28, 2002 at 02:18:07PM +0100, Stefano Zacchiroli wrote:
> So I reupload the package _including .orig.tar.gz_ and I received some
> mails like the following, what I have to do?
You need to change the upstream version number in some manner that won't
conflict with whatever upstream do
On Wed, Jan 23, 2002 at 01:54:05PM +0100, Stefan Schwandter wrote:
> Am I doing the right thing when I build the free package from one source
> (snd) and the other packages from another (snd-motif), or can I build
> all binary packages from one source? I don't think so, but I want to be
> sure...
On Fri, Jan 04, 2002 at 05:52:19PM -0500, Bob Hilliard wrote:
> I can't find anything in the debconf documentation or the command
> available in /usr/share/doc/debian-policy/debconf_specification.txt.gz
> that would permit this type of conditional display of a message. Is
> there something i
On Fri, Jan 04, 2002 at 05:52:19PM -0500, Bob Hilliard wrote:
> I can't find anything in the debconf documentation or the command
> available in /usr/share/doc/debian-policy/debconf_specification.txt.gz
> that would permit this type of conditional display of a message. Is
> there something
On Fri, Jan 04, 2002 at 10:07:52PM +0100, Magnus Ekdahl wrote:
> I could fix the problem by manually by adding a chmod +x ./configure
> somewhere in the rules section. But manually adding a diff seems somewhat
> clumsy.
Other ways to do it include changing the tarball or running autoconf at
bu
On Fri, Jan 04, 2002 at 10:07:52PM +0100, Magnus Ekdahl wrote:
> I could fix the problem by manually by adding a chmod +x ./configure
> somewhere in the rules section. But manually adding a diff seems somewhat
> clumsy.
Other ways to do it include changing the tarball or running autoconf at
b
On Fri, Dec 28, 2001 at 09:27:43AM -0500, Jaldhar H. Vyas wrote:
> webmin-status sets up a cro job for its user. However there seems to be
> no good wa in Debian to remove a users crontab. putting the cron jobs
> into /etc/cron.d seem like a possibility but then they would run as root
> not a pa
On Fri, Dec 28, 2001 at 09:27:43AM -0500, Jaldhar H. Vyas wrote:
> webmin-status sets up a cro job for its user. However there seems to be
> no good wa in Debian to remove a users crontab. putting the cron jobs
> into /etc/cron.d seem like a possibility but then they would run as root
> not a p
On Thu, Dec 20, 2001 at 01:20:21PM +0100, Robert Bihlmeyer wrote:
> Nope - if our X libs were built with DECnet support, their -dev
> should depend on the appropriate packages, not you. Anyway, there's no
> Debian GNU/Ultrix (yet).
Linux can support DECnet all by itself :-) .
--
"You grabbed my
On Thu, Dec 20, 2001 at 01:20:21PM +0100, Robert Bihlmeyer wrote:
> Nope - if our X libs were built with DECnet support, their -dev
> should depend on the appropriate packages, not you. Anyway, there's no
> Debian GNU/Ultrix (yet).
Linux can support DECnet all by itself :-) .
--
"You grabbed m
On Mon, Dec 17, 2001 at 02:57:52PM -0800, Grant Bowman wrote:
> Takuo asked me what to do, so he doesn't know. He's the maintainer. I
> have recently had interactions with Takuo over other items as well,
> especially as it relates to debian-qa. I think you are jumping to
> premature conclusions
On Mon, Dec 17, 2001 at 02:57:52PM -0800, Grant Bowman wrote:
> Takuo asked me what to do, so he doesn't know. He's the maintainer. I
> have recently had interactions with Takuo over other items as well,
> especially as it relates to debian-qa. I think you are jumping to
> premature conclusion
On Mon, Dec 10, 2001 at 01:52:15AM +0100, Christian Surchi wrote:
> On Mon, Dec 10, 2001 at 12:42:32AM +0000, Mark Brown wrote:
> > Effectively what you're doing is turning the old package into a virtual
> > package provided by the new one.
> I remember some messages abo
On Mon, Dec 10, 2001 at 01:11:19AM +0100, Christian Surchi wrote:
> Provide: is for virtual package. If you change name you should have a
> new package with Conflicts: and Replaces:.
Effectively what you're doing is turning the old package into a virtual
package provided by the new one.
--
"You
On Mon, Dec 10, 2001 at 01:52:15AM +0100, Christian Surchi wrote:
> On Mon, Dec 10, 2001 at 12:42:32AM +0000, Mark Brown wrote:
> > Effectively what you're doing is turning the old package into a virtual
> > package provided by the new one.
> I remember some messages abo
On Mon, Dec 10, 2001 at 01:11:19AM +0100, Christian Surchi wrote:
> Provide: is for virtual package. If you change name you should have a
> new package with Conflicts: and Replaces:.
Effectively what you're doing is turning the old package into a virtual
package provided by the new one.
--
"Yo
1 - 100 of 189 matches
Mail list logo
