RFS: Scheme shell
In agreement with the current maintainer, I intend to take over the scsh Debian package. scsh is a Scheme implementation tuned for writing shell scripts. I have already prepared a package that closes most open bugs. Here's the changelog: scsh (0.6.4-1) unstable; urgency=low * New upstream release (closes: #202075) * New maintainer * Don't do any build-time work at install-time (closes: #187939) * Separate DOCDIR from LIBDIR (closes: #202072) * Remove empty documentation directories in /usr/lib/scsh/doc (closes: #202056) * Install ekko.scm executable, correct #! path (closes: #202080) * Add /usr/lib/scsh/modules to Library search-path (closes: #177331) * Apply GNU/Hurd support patch (closes: #202564) * Don't build on 64 bits ports (addresses: #110073) * Get in conformance with policy 3.6.0 * Tweak description * Refer to Debian's copy of the GPL Will you be my sponsor? Thanks in advance. I'm already in the NM queue, so I don't need an advocate, just someone that uploads the package (after having checked it is not a nasty trojan or RC-bug ridden obviously ;) ) P.S.: I'm still looking for a sponsor for: - gnotepad+, a simple GNOME text editor http://lists.debian.org/debian-mentors/2003/debian-mentors-200301/msg00118.html - uf-view, a web cartoon viewer http://lists.debian.org/debian-mentors/2003/debian-mentors-200301/msg00232.html -- Lionel pgpii9aC8i6DY.pgp Description: PGP signature
RFS: facturalux - ERP/CRM software for GNU/Linux (2nd try)
Hi, folks. I have a reworked version of facturalux package and I'd like you to upload it, because I'm not yet a Debian Developer (expecting since 1029337800). The upload is important because it fixes a pair of issues, one regarding to gcc-3.3 compiling and other correcting an usability bug. You can obtain the packages here [1]. [1] http://www.superiodico.net/debian/upload/facturalux/ As usual, the package info: dpkg --info -- Package: facturalux Version: 0.4-2 Section: misc Priority: optional Architecture: powerpc Depends: libc6 (>= 2.3.2-1), libgcc1 (>= 1:3.3.1-1), libpng12-0 (>= 1.2.5.0-4), libqt3c102-mt (>= 3:3.1.1), libstdc++5 (>= 1:3.3.1-1), xlibs (>> 4.1.0), zlib1g (>= 1:1.1.4), debconf, libqt3-mt-psql | libqt3c102-mt-psql (>= 3), postgresql, libpq3 (>= 7.3) Installed-Size: 3528 Maintainer: Juan Manuel Garcia Molina <[EMAIL PROTECTED]> Description: ERP/CRM software for GNU/Linux ERP/CRM (Enterprise Resource Planning/Customer Relationship Management) software on storage management and enterprise sales for GNU/Linux, using C++, Qt 3.x and PostGreSQL. . Please, be sure to read /usr/share/doc/facturalux/README.debian. It contains critical info to get facturalux working. . This package contains main program and libs. -- And the changelog says: -- facturalux (0.4-2) unstable; urgency=low . * Bumped Standards-Version: to 3.6.1 * Fix compile with gcc-3.3 * Review package description under debian/control * Install /usr/share/facturalux/actions.xml (Closes: #203540) * Add autotools-dev to Build-Depends: * Added facturalux icon -- I'd like to seek an sponsor to this package. Thanks and regards. -- Juan Manuel García Molina [EMAIL PROTECTED]
Re: creating your own debian package repository
Eric Winger <[EMAIL PROTECTED]> writes:
> So, two questions:
>
> * Is this a reasonable way to maintain our internal packages - ie a
> seperate archive? Or is there a better way.
Its realy easy for small repositories (say <100 packages so this
applies to you) but you need proper management scripts if you have a
lot of packages and multiple persons managing the archive/uploading
debs.
> * If this is the most reasonable way, where is the information on
> building/maintaining your own archive.
You already got told about dpkg-scan{packages,sources}, that should be
fine for you already.
But if you want to use the archive from outside a trusted network you
should also make "Release" files giving md5sums of the Packages and
Sources files and gpg sign those. I'm not sure where the Syntax of
Release files is descriped or if but its easy to make your own by
using Debians as templates.
You should also care to set the Origin to point at you and not Debian
for bug reporting purposes.
MfG
Goswin
debix still searches sponsor
Hi again, still no definit sponsor. I started a tiny webpage on alioth: http://debix.alioth.debian.org/ Enjoy. Mrvn > Hi, > > I'm looking for a sponsor for 2 packages (debix and debix-imager), who > would have guessed. :) > > Debix-imager > > > Debix-imager is a setuid binary that allows a user to create a > loopback file, format it with the filesystem of his choice and install > the contents of a tar file or a debian system via debootstrap on it. > > The intention is to make it flexible enough for boot-floppies, > debian-installer and debix to create their bootfloppies, ramdisks and > live filesystems without needing root themself. > > I'm looking for a sponsor that knows a bit about security. > boot-floppies and/or debian-installer experiences would be good too. > At the moment I'm use ocaml but a rewrite in C/C++ would be easy and > maybe cleaner. (Codesize 195 lines atm). > > ftp://mrvn.homeip.net/debix-imager/ > > Debix > = > > Debix is a collection of scripts to create live filesystems. Several > flavours are planed: > > - Make a live filesystem image from any existing linux system > Apart from a special initrd a plain image of the existing system is > made without changes. The image on CD is made semingly writeable via > LVM2 snaphots by the initrd and then the normal init is started. > > - Pure live filesystem like knoppix > Difference to Knoppix would be customizable size, being a pure > Debian system and the possibility to migrate the live filesystem to > harddisk on-the-fly to get a running Debian system (with the > drawback that the partitioning scheme is mostly fixed, using online > ext2/3 resize patches could solve that). > > - Make a live filesystem with boot-floppies or debian-installer > Console and X subflavours included. The advantage over the normal > CDs would be better autodetection and access to www, irc and local > docs during instalation (one could read the installation docs on > www.debian.org in galeon while running boot-loppies in an xterm). > A mixture of knoppix and installer. > > A sponsor should be versed in /bin/sh and intrested in creating live > filesystems. Having a CD-rw or DVD-rw burner would be a big plus but > bochs or vmware will do to test stuff. > > Sources aren't debianized yet but I have an example CD image made from > a normal woody system (flavour 1 from above) at > rsync://mrvn.homeip.net/images/ > > Anyone intrested? > > MfG > Goswin > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: creating your own debian package repository
Eric Winger (2003-08-20 16:05:33 -0700) : > So, two questions: > > * Is this a reasonable way to maintain our internal packages - ie a > seperate archive? Or is there a better way. It's the best way I've found. > * If this is the most reasonable way, where is the information on > building/maintaining your own archive. I'll suggest you install the mini-dinstall package, and read its documentation. It works wonderfully for me, and it's more powerful than the dpkg-scanpackages stuff I've seen mentioned in your other answers. I use it in combination with dput (with an appropriate upload method), and it works like a charm. Roland. -- Roland Mas [...] ou une dent pourrie [...] -- in Variations sur un thème imposé -- Signatures à collectionner, série n°2, partie 2/3.
Re: creating your own debian package repository
Christopher W. Curtis wrote: A quick google for "apt repository howto", besides pulling up a surprising number of links about RPMs, also brings up these two: http://www.debian.org/doc/manuals/repository-howto/repository-howto.html Thanks to everyone for their responses. This link has proved very helpful so far.
Re: creating your own debian package repository
On Thu, Aug 21, 2003 at 02:40:27PM +0200, Roland Mas wrote: > Eric Winger (2003-08-20 16:05:33 -0700) : > > > So, two questions: > > > > * Is this a reasonable way to maintain our internal packages - ie a > > seperate archive? Or is there a better way. > > It's the best way I've found. > > > * If this is the most reasonable way, where is the information on > > building/maintaining your own archive. > > I'll suggest you install the mini-dinstall package, and read its > documentation. It works wonderfully for me, and it's more powerful > than the dpkg-scanpackages stuff I've seen mentioned in your other > answers. I use it in combination with dput (with an appropriate > upload method), and it works like a charm. The primary archive management tools right now are mini-dinstall and debarchiver. Two more are currently ITP'ed, both of which handle things in a pool layout (rather than directory layout), and which may end up merged into one. (Disclaimer: I'm the author of one of the ITP'ed tools). However, I do strongly recommend using one of the management scripts. -- Joel Baker <[EMAIL PROTECTED]>,''`. Debian GNU NetBSD/i386 porter: :' : `. `' `- pgpINhVkhu6PB.pgp Description: PGP signature
when to close bugs
hi everyone, i have a simple question: when am i to close bugs? once the bug is fixed in *one* version in the debian archive (unstable) or once it is fixed in *all*? the bts docs say as soon as a fixed version is in the archive, but there are a lot of open bugs tagged "fixed". and imho it would make more sense to close the bug once the version in stable is fixed. confused robert -- Robert Lemmen http://www.semistable.com pgpEpcVV4zaUs.pgp Description: PGP signature
can't install from a local repository
Probably a simple question. But I've created a local repository. Figured out how dput moved packages into the archive. Worked through atp-ftparchive and created a Packages.gz file, got sources-list to point at my archive correctly. But when I do a apt-get install spinelli (spinelli is my package) I get this message. Reading Package Lists... Done Building Dependency Tree... Done Package spinelli has no available version, but exists in the database. This typically means that the package was mentioned in a dependency and never uploaded, has been obsoleted or is not available with the contents of sources.list E: Package spinelli has no installation candidate After pillaging the documentation, I've concluded that this error is a mystery to me. Is there something special I have to do to a package to make it apt-get install'able? thx Eric
Re: when to close bugs
On Thu, Aug 21, 2003 at 03:40:50PM +0200, Robert Lemmen wrote: > hi everyone, > i have a simple question: when am i to close bugs? once the bug is fixed > in *one* version in the debian archive (unstable) or once it is fixed in > *all*? > the bts docs say as soon as a fixed version is in the archive, but there > are a lot of open bugs tagged "fixed". and imho it would make more sense > to close the bug once the version in stable is fixed. Current best practice is to close the bug as soon as the fixed package hits unstable. This is what happens if you close the bug in your changelog, unless it's an NMU, in which case it gets tagged 'fixed' instead. There has been a lot of interest recently in associating bugs with specific versions of packages, and I think this interest is being translated into code. In the meantime, closing bugs as soon as there's a fixed version seems to be the most effective way to manage bugs in the BTS, generally speaking. -- Steve Langasek postmodern programmer pgpyhyskMM9ZY.pgp Description: PGP signature
Re: can't install from a local repository
Eric Winger wrote: But when I do a apt-get install spinelli (spinelli is my package) I get this message. E: Package spinelli has no installation candidate I assume the 'apt-get update' succeeded; Try apt-cache policy spinelli Also - look at your packages file and make sure the File: header points to the correct .deb on your server. This should be pretty easy to track down using just a web browser. Chris
Re: when to close bugs
On Thu, Aug 21, 2003 at 03:40:50PM +0200, Robert Lemmen wrote: > i have a simple question: when am i to close bugs? once the bug is fixed > in *one* version in the debian archive (unstable) or once it is fixed in > *all*? Right now, just close it when it's fixed in unstable. A better 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 different. Cheers, -- Colin Watson [EMAIL PROTECTED]
Re: can't install from a local repository
Forgot to mention that I got this after doing apt-get update: Ign file: binary/ Release Reading Package Lists... Done Building Dependency Tree... Done I thought that the first line might have been ok because I'm not doing any pinning. Maybe that was a bad assumption. apt-cache policy spinelli revealed: spinelli: Installed: (none) Candidate: (none) Version Table: I'm not sure why this is because doing a apt-ftppackage package results in this in the packages.gz Package: spinelli Priority: optional Section: unknown Installed-Size: 437 Maintainer: unknown <[EMAIL PROTECTED]> Architecture: i386 Version: 0.9 Filename: ./spinelli_0.9_i386.deb Size: 131164 MD5sum: 9ef6eb14c9b242b5c76dbcd739a1034b Description: which has version 0.9 Eric Christopher Curtis wrote: Eric Winger wrote: > But when I do a > apt-get install spinelli (spinelli is my package) > > I get this message. > E: Package spinelli has no installation candidate I assume the 'apt-get update' succeeded; Try apt-cache policy spinelli Also - look at your packages file and make sure the File: header points to the correct .deb on your server. This should be pretty easy to track down using just a web browser. Chris
Re: can't install from a local repository
Eric Winger <[EMAIL PROTECTED]> writes: > Probably a simple question. But I've created a local > repository. Figured out how dput moved packages into the > archive. Worked through atp-ftparchive and created a Packages.gz file, > got sources-list to point at my archive correctly. > > > But when I do a > apt-get install spinelli (spinelli is my package) > > I get this message. > > > Reading Package Lists... Done > Building Dependency Tree... Done > Package spinelli has no available version, but exists in the database. > This typically means that the package was mentioned in a dependency and > never uploaded, has been obsoleted or is not available with the contents > of sources.list > E: Package spinelli has no installation candidate That happens if you have a Sources.gz entry saing some source will build the package but you don't have any deb for it or if something depends on it and you don't have a deb for it. I think this also happen sif the package is already installed but no longer available. apt-get knows it should be there (or was there) but it currently has no url for it.
Re: can't install from a local repository
> Forgot to mention that I got this after doing apt-get update: > > Ign file: binary/ Release > Reading Package Lists... Done > Building Dependency Tree... Done > > I thought that the first line might have been ok because I'm not doing > any pinning. Maybe that was a bad assumption. > > apt-cache policy spinelli revealed: > > spinelli: > Installed: (none) > Candidate: (none) > Version Table: > > I'm not sure why this is because doing a apt-ftppackage package results > in this in the packages.gz > > > Package: spinelli > Priority: optional > Section: unknown > Installed-Size: 437 > Maintainer: unknown <[EMAIL PROTECTED]> > Architecture: i386 > Version: 0.9 > Filename: ./spinelli_0.9_i386.deb > Size: 131164 > MD5sum: 9ef6eb14c9b242b5c76dbcd739a1034b > Description: > > > > which has version 0.9 > > Eric > > > Christopher Curtis wrote: > >> Eric Winger wrote: >> > But when I do a >> > apt-get install spinelli (spinelli is my package) >> > >> > I get this message. >> > E: Package spinelli has no installation candidate >> >> I assume the 'apt-get update' succeeded; >> Try apt-cache policy spinelli >> >> Also - look at your packages file and make sure the File: header >> points to the correct .deb on your server. This should be pretty easy >> to track down using just a web browser. >> >> Chris >> > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] What does the tree structure of your repository look like (where are the packages , where is Packages.gz etc ) and where do you point to in /etc/apt/sources.list ?
RFS: facturalux - ERP/CRM software for GNU/Linux (2nd try)
Hi, folks. I have a reworked version of facturalux package and I'd like you to upload it, because I'm not yet a Debian Developer (expecting since 1029337800). The upload is important because it fixes a pair of issues, one regarding to gcc-3.3 compiling and other correcting an usability bug. You can obtain the packages here [1]. [1] http://www.superiodico.net/debian/upload/facturalux/ As usual, the package info: dpkg --info -- Package: facturalux Version: 0.4-2 Section: misc Priority: optional Architecture: powerpc Depends: libc6 (>= 2.3.2-1), libgcc1 (>= 1:3.3.1-1), libpng12-0 (>= 1.2.5.0-4), libqt3c102-mt (>= 3:3.1.1), libstdc++5 (>= 1:3.3.1-1), xlibs (>> 4.1.0), zlib1g (>= 1:1.1.4), debconf, libqt3-mt-psql | libqt3c102-mt-psql (>= 3), postgresql, libpq3 (>= 7.3) Installed-Size: 3528 Maintainer: Juan Manuel Garcia Molina <[EMAIL PROTECTED]> Description: ERP/CRM software for GNU/Linux ERP/CRM (Enterprise Resource Planning/Customer Relationship Management) software on storage management and enterprise sales for GNU/Linux, using C++, Qt 3.x and PostGreSQL. . Please, be sure to read /usr/share/doc/facturalux/README.debian. It contains critical info to get facturalux working. . This package contains main program and libs. -- And the changelog says: -- facturalux (0.4-2) unstable; urgency=low . * Bumped Standards-Version: to 3.6.1 * Fix compile with gcc-3.3 * Review package description under debian/control * Install /usr/share/facturalux/actions.xml (Closes: #203540) * Add autotools-dev to Build-Depends: * Added facturalux icon -- I'd like to seek an sponsor to this package. Thanks and regards. -- Juan Manuel García Molina [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: creating your own debian package repository
Eric Winger <[EMAIL PROTECTED]> writes:
> So, two questions:
>
> * Is this a reasonable way to maintain our internal packages - ie a
> seperate archive? Or is there a better way.
Its realy easy for small repositories (say <100 packages so this
applies to you) but you need proper management scripts if you have a
lot of packages and multiple persons managing the archive/uploading
debs.
> * If this is the most reasonable way, where is the information on
> building/maintaining your own archive.
You already got told about dpkg-scan{packages,sources}, that should be
fine for you already.
But if you want to use the archive from outside a trusted network you
should also make "Release" files giving md5sums of the Packages and
Sources files and gpg sign those. I'm not sure where the Syntax of
Release files is descriped or if but its easy to make your own by
using Debians as templates.
You should also care to set the Origin to point at you and not Debian
for bug reporting purposes.
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
debix still searches sponsor
Hi again, still no definit sponsor. I started a tiny webpage on alioth: http://debix.alioth.debian.org/ Enjoy. Mrvn > Hi, > > I'm looking for a sponsor for 2 packages (debix and debix-imager), who > would have guessed. :) > > Debix-imager > > > Debix-imager is a setuid binary that allows a user to create a > loopback file, format it with the filesystem of his choice and install > the contents of a tar file or a debian system via debootstrap on it. > > The intention is to make it flexible enough for boot-floppies, > debian-installer and debix to create their bootfloppies, ramdisks and > live filesystems without needing root themself. > > I'm looking for a sponsor that knows a bit about security. > boot-floppies and/or debian-installer experiences would be good too. > At the moment I'm use ocaml but a rewrite in C/C++ would be easy and > maybe cleaner. (Codesize 195 lines atm). > > ftp://mrvn.homeip.net/debix-imager/ > > Debix > = > > Debix is a collection of scripts to create live filesystems. Several > flavours are planed: > > - Make a live filesystem image from any existing linux system > Apart from a special initrd a plain image of the existing system is > made without changes. The image on CD is made semingly writeable via > LVM2 snaphots by the initrd and then the normal init is started. > > - Pure live filesystem like knoppix > Difference to Knoppix would be customizable size, being a pure > Debian system and the possibility to migrate the live filesystem to > harddisk on-the-fly to get a running Debian system (with the > drawback that the partitioning scheme is mostly fixed, using online > ext2/3 resize patches could solve that). > > - Make a live filesystem with boot-floppies or debian-installer > Console and X subflavours included. The advantage over the normal > CDs would be better autodetection and access to www, irc and local > docs during instalation (one could read the installation docs on > www.debian.org in galeon while running boot-loppies in an xterm). > A mixture of knoppix and installer. > > A sponsor should be versed in /bin/sh and intrested in creating live > filesystems. Having a CD-rw or DVD-rw burner would be a big plus but > bochs or vmware will do to test stuff. > > Sources aren't debianized yet but I have an example CD image made from > a normal woody system (flavour 1 from above) at > rsync://mrvn.homeip.net/images/ > > Anyone intrested? > > MfG > Goswin > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: creating your own debian package repository
Eric Winger (2003-08-20 16:05:33 -0700) : > So, two questions: > > * Is this a reasonable way to maintain our internal packages - ie a > seperate archive? Or is there a better way. It's the best way I've found. > * If this is the most reasonable way, where is the information on > building/maintaining your own archive. I'll suggest you install the mini-dinstall package, and read its documentation. It works wonderfully for me, and it's more powerful than the dpkg-scanpackages stuff I've seen mentioned in your other answers. I use it in combination with dput (with an appropriate upload method), and it works like a charm. Roland. -- Roland Mas [...] ou une dent pourrie [...] -- in Variations sur un thème imposé -- Signatures à collectionner, série n°2, partie 2/3. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: creating your own debian package repository
Christopher W. Curtis wrote: A quick google for "apt repository howto", besides pulling up a surprising number of links about RPMs, also brings up these two: http://www.debian.org/doc/manuals/repository-howto/repository-howto.html Thanks to everyone for their responses. This link has proved very helpful so far. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: creating your own debian package repository
On Thu, Aug 21, 2003 at 02:40:27PM +0200, Roland Mas wrote: > Eric Winger (2003-08-20 16:05:33 -0700) : > > > So, two questions: > > > > * Is this a reasonable way to maintain our internal packages - ie a > > seperate archive? Or is there a better way. > > It's the best way I've found. > > > * If this is the most reasonable way, where is the information on > > building/maintaining your own archive. > > I'll suggest you install the mini-dinstall package, and read its > documentation. It works wonderfully for me, and it's more powerful > than the dpkg-scanpackages stuff I've seen mentioned in your other > answers. I use it in combination with dput (with an appropriate > upload method), and it works like a charm. The primary archive management tools right now are mini-dinstall and debarchiver. Two more are currently ITP'ed, both of which handle things in a pool layout (rather than directory layout), and which may end up merged into one. (Disclaimer: I'm the author of one of the ITP'ed tools). However, I do strongly recommend using one of the management scripts. -- Joel Baker <[EMAIL PROTECTED]>,''`. Debian GNU NetBSD/i386 porter: :' : `. `' `- pgp0.pgp Description: PGP signature
when to close bugs
hi everyone, i have a simple question: when am i to close bugs? once the bug is fixed in *one* version in the debian archive (unstable) or once it is fixed in *all*? the bts docs say as soon as a fixed version is in the archive, but there are a lot of open bugs tagged "fixed". and imho it would make more sense to close the bug once the version in stable is fixed. confused robert -- Robert Lemmen http://www.semistable.com pgp0.pgp Description: PGP signature
can't install from a local repository
Probably a simple question. But I've created a local repository. Figured out how dput moved packages into the archive. Worked through atp-ftparchive and created a Packages.gz file, got sources-list to point at my archive correctly. But when I do a apt-get install spinelli (spinelli is my package) I get this message. Reading Package Lists... Done Building Dependency Tree... Done Package spinelli has no available version, but exists in the database. This typically means that the package was mentioned in a dependency and never uploaded, has been obsoleted or is not available with the contents of sources.list E: Package spinelli has no installation candidate After pillaging the documentation, I've concluded that this error is a mystery to me. Is there something special I have to do to a package to make it apt-get install'able? thx Eric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: when to close bugs
On Thu, Aug 21, 2003 at 03:40:50PM +0200, Robert Lemmen wrote: > hi everyone, > i have a simple question: when am i to close bugs? once the bug is fixed > in *one* version in the debian archive (unstable) or once it is fixed in > *all*? > the bts docs say as soon as a fixed version is in the archive, but there > are a lot of open bugs tagged "fixed". and imho it would make more sense > to close the bug once the version in stable is fixed. Current best practice is to close the bug as soon as the fixed package hits unstable. This is what happens if you close the bug in your changelog, unless it's an NMU, in which case it gets tagged 'fixed' instead. There has been a lot of interest recently in associating bugs with specific versions of packages, and I think this interest is being translated into code. In the meantime, closing bugs as soon as there's a fixed version seems to be the most effective way to manage bugs in the BTS, generally speaking. -- Steve Langasek postmodern programmer pgp0.pgp Description: PGP signature
Re: can't install from a local repository
Eric Winger wrote: But when I do a apt-get install spinelli (spinelli is my package) I get this message. E: Package spinelli has no installation candidate I assume the 'apt-get update' succeeded; Try apt-cache policy spinelli Also - look at your packages file and make sure the File: header points to the correct .deb on your server. This should be pretty easy to track down using just a web browser. Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: when to close bugs
On Thu, Aug 21, 2003 at 03:40:50PM +0200, Robert Lemmen wrote: > i have a simple question: when am i to close bugs? once the bug is fixed > in *one* version in the debian archive (unstable) or once it is fixed in > *all*? Right now, just close it when it's fixed in unstable. A better 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 different. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: can't install from a local repository
Forgot to mention that I got this after doing apt-get update: Ign file: binary/ Release Reading Package Lists... Done Building Dependency Tree... Done I thought that the first line might have been ok because I'm not doing any pinning. Maybe that was a bad assumption. apt-cache policy spinelli revealed: spinelli: Installed: (none) Candidate: (none) Version Table: I'm not sure why this is because doing a apt-ftppackage package results in this in the packages.gz Package: spinelli Priority: optional Section: unknown Installed-Size: 437 Maintainer: unknown <[EMAIL PROTECTED]> Architecture: i386 Version: 0.9 Filename: ./spinelli_0.9_i386.deb Size: 131164 MD5sum: 9ef6eb14c9b242b5c76dbcd739a1034b Description: which has version 0.9 Eric Christopher Curtis wrote: Eric Winger wrote: > But when I do a > apt-get install spinelli (spinelli is my package) > > I get this message. > E: Package spinelli has no installation candidate I assume the 'apt-get update' succeeded; Try apt-cache policy spinelli Also - look at your packages file and make sure the File: header points to the correct .deb on your server. This should be pretty easy to track down using just a web browser. Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: can't install from a local repository
Eric Winger <[EMAIL PROTECTED]> writes: > Probably a simple question. But I've created a local > repository. Figured out how dput moved packages into the > archive. Worked through atp-ftparchive and created a Packages.gz file, > got sources-list to point at my archive correctly. > > > But when I do a > apt-get install spinelli (spinelli is my package) > > I get this message. > > > Reading Package Lists... Done > Building Dependency Tree... Done > Package spinelli has no available version, but exists in the database. > This typically means that the package was mentioned in a dependency and > never uploaded, has been obsoleted or is not available with the contents > of sources.list > E: Package spinelli has no installation candidate That happens if you have a Sources.gz entry saing some source will build the package but you don't have any deb for it or if something depends on it and you don't have a deb for it. I think this also happen sif the package is already installed but no longer available. apt-get knows it should be there (or was there) but it currently has no url for it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: can't install from a local repository
> Forgot to mention that I got this after doing apt-get update: > > Ign file: binary/ Release > Reading Package Lists... Done > Building Dependency Tree... Done > > I thought that the first line might have been ok because I'm not doing > any pinning. Maybe that was a bad assumption. > > apt-cache policy spinelli revealed: > > spinelli: > Installed: (none) > Candidate: (none) > Version Table: > > I'm not sure why this is because doing a apt-ftppackage package results > in this in the packages.gz > > > Package: spinelli > Priority: optional > Section: unknown > Installed-Size: 437 > Maintainer: unknown <[EMAIL PROTECTED]> > Architecture: i386 > Version: 0.9 > Filename: ./spinelli_0.9_i386.deb > Size: 131164 > MD5sum: 9ef6eb14c9b242b5c76dbcd739a1034b > Description: > > > > which has version 0.9 > > Eric > > > Christopher Curtis wrote: > >> Eric Winger wrote: >> > But when I do a >> > apt-get install spinelli (spinelli is my package) >> > >> > I get this message. >> > E: Package spinelli has no installation candidate >> >> I assume the 'apt-get update' succeeded; >> Try apt-cache policy spinelli >> >> Also - look at your packages file and make sure the File: header >> points to the correct .deb on your server. This should be pretty easy >> to track down using just a web browser. >> >> Chris >> > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] What does the tree structure of your repository look like (where are the packages , where is Packages.gz etc ) and where do you point to in /etc/apt/sources.list ? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
