depend on it.
--
Neil Roeth
on any of the binary packages built by the jade source package.
--
Neil Roeth
ust ran into this. :-) What is the "mechanism used for etch
to lenny upgrade"? How does it resolve the issue?
--
Neil Roeth
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Aug 12, Josselin Mouette (j...@debian.org) wrote:
> Le mercredi 12 août 2009 à 11:06 -0400, Neil Roeth a écrit :
> > I've had some packages for years during which policy was changed and
> > required
> > corresponding changes in my packages. In that case, the
ery useful and hope we keep it.
>
> --
> .''`. Josselin Mouette
> : :' :
> `. `' âI recommend you to learn English in hope that you in
> `- future understand thingsâ -- Jörg Schilling
--
Neil Roeth
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Jun 24, Sune Vuorela (nos...@vuorela.dk) wrote:
> On 2009-06-24, Neil Roeth wrote:
> > I received the below email that my package, aplus-fsf, was removed from
> > testing. Apparently that is due to the removal of gtk 1.2, but aplus-fsf
> > has
> > no direct de
scue/0.8.2-10 gtalk/0.99.10-12
# Round 3:
remove xemacs21/21.4.22-1 gtk+1.2/1.2.10-18.1 toolbar-fancy/0.07-7.1
aplus-fsf/4.22.1-1
--
Neil Roeth
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Feb 10, Hendrik Sattler ([EMAIL PROTECTED]) wrote:
> Am Freitag, 10. Februar 2006 13:36 schrieb Neil Roeth:
> > On Feb 10, Hendrik Sattler ([EMAIL PROTECTED]) wrote:
> > > Hi,
> > >
> > > I about packaging a library that ships an API reference in docb
he package is
installed it would ask which subset of the three to install (defaulting to PDF
only), and later, when upgrading the package, it would install the same
subset with no further interaction?
--
Neil Roeth
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
; Should this be done via dh_installcatalogs? Or dh_installxmlcatalogs?
>
> Thanks a lot for any comments and all the best
>
> Norbert
This web page: http://debian-xml-sgml.alioth.debian.org/ has a link to the
"Latest XML Policy Draft" which has info on where files should go. Hav
.7.3.3.c or
> 0.7.3.3.final, but I was wondering what The Right Thing To Do would be.
In the future, if you modify upstream's name of 0.7.3.4.b1 to be 0.7.3.4b1
instead, then 0.7.3.4.0 will be treated as a later version. I think that is
pretty clean, and no need to wait for the ~ cap
other;
where should the fonts go? If they are already going to the proper place, am
I getting the warning because I forgot something else, or is it a lintian bug?
--
Neil Roeth
On Nov 7, Mark Johnson ([EMAIL PROTECTED]) wrote:
> I'm updating the docbook-simple package from V1.0cr2 to V1.0. Since
> 1.0cr2 > 1.0, I'm not sure how to handle the situation.
1.0.0 will do the trick, and I think that's cleaner than something like
1.0really.
--
Neil Roeth
icates a machine to tracking unstable for no other purpose than
> to build packages).
Building in a pbuilder chroot is what I do, for exactly the reason you stated.
I do all my work on the package in my regular environment, then create the
package for upload with pbuilder, then test the resulting package before
uploading it.
--
Neil Roeth
earch and dns-nameservers lines to the stanzas in
/etc/network/interfaces if you are using resolvconf, or add scripts to
if-up.d/ and if-down.d/ to muck about with resolv.conf, or whatever you like.
I've done both, though I just switched to resolvconf (thanks, Thomas!).
In addition, of course, you need to set up hotplug, i.e., compile your kernel
with the appropriate options and drivers, etc.
--
Neil Roeth
On Sep 5, Matt Chorman ([EMAIL PROTECTED]) wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Friday 05 September 2003 06:04 pm, Neil Roeth wrote:
> > You need to look in the package itself for the call to configure, not in
> > the apt source. Suppo
on
cd foo-1.2.3
vi debian/rules # find the call to configure, add "--with-mysql"
fakeroot dpkg-buildpackage -uc -us
This will result in a .deb in the directory from which you called apt-get
source, which you can install with dpkg.
--
Neil Roeth
I will just make sure they meet the relevant
criteria by October 15.
--
Neil Roeth
es rather than slightly
older, better tested, more stable versions.
--
Neil Roeth
permission
needs to remove the old version of sbcl completely to unblock all package
builds.
It seems simple to fix, yet it's been like this for days with no explanation.
--
Neil Roeth
What's the status of the sbcl/common-lisp-controller problems that were
blocking builds on sparc and other platforms?
--
Neil Roeth
;the bug you closed
is reoccurring". If the compiler I'm using to test my fixes is different than
the one used to build the package, that might be the reason.
--
Neil Roeth
On Jun 18, Manoj Srivastava ([EMAIL PROTECTED]) wrote:
> On Mon, 16 Jun 2003 22:55:53 -0400, Neil Roeth <[EMAIL PROTECTED]> said:
> > On Jun 13, Daniel Jacobowitz ([EMAIL PROTECTED]) wrote:
> >> Certainly you have not broken Debian; but I maintain that this
> >&
rm,
> portable development. Not useless, because of flex-old, but certainly
> more awkward; I will not be able to build Debian packages which require
> a recent flex in the same root in which I build cross-platform
> software.
>
> Certainly you have not broken Debian; but I maintain that this
> short-sightedness does damage Debian's usefulness as a development
> platform, for all those targets which many more practical developers
> must support in order to do their jobs.
I think this is an excellent point. I can think of many times when I've done
development work in Debian and ported the result to Solaris, IRIX or HPUX. It
is, of course, not a requirement for Debian that this be easy, but the easier
it is, the more convincing the argument for integrating Debian into a mixed
*nix environment, for everyone from developers to CIOs.
--
Neil Roeth
for those two a while ago and had no objections when I recently
expressed an interest in adopting them.
--
Neil Roeth
On Apr 30, Martin Schulze ([EMAIL PROTECTED]) wrote:
> Neil Roeth wrote:
> > On Apr 28, Martin Schulze ([EMAIL PROTECTED]) wrote:
> > > Hamish Moffatt wrote:
> > > > Many have chroots but don't tend to have the relevant build-deps
> > > > ins
nyone much). If nobody is willing
> then I'd say there just isn't enough support and 386 should be dropped
> outright.
I am in favor of dropping the 386 altogether, but this is acceptable as an
alternative. If people would rather work on keeping 386 software up to date
than just run woody forever, more power to them. It doesn't seem like it
would cost much on anyone else's part to enable this.
--
Neil Roeth
How about "obsolete" and "deprecated" tags? This information is not currently
captured for packages anywhere, so it is hard to tell if packages are
obsolete, or if there is a transition going on from an older one to a newer
one.
--
Neil Roeth
missing.
> You don't have to, but it's a common way to get things installed.
^
What's the alternative?
--
Neil Roeth
29 matches
Mail list logo
