Bug#609295: ITP: naev -- 2D space trading combat game
Package: wnpp Severity: wishlist Owner: Vincent Cheng * Package name: naev Version : 0.4.2 Upstream Author : Edgar Simo "bobbens" Nikola Whallon <6.satur...@gmail.com> Josiah Schwartfeger Deiz Bas Fournier "BTAxis" * URL : http://code.google.com/p/naev/ * License : code - GPL-3 ; data - public domain, GPLv2, GPLv3, CC-By (and -SA) 3.0 Programming Lang: C, Lua Description : 2D space trading combat game -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110108093413.25671.41534.report...@vincent-laptop.vc.shawcable.net
how to identify firmware packages
On Fri, Jan 07, 2011 at 10:04:33PM +0100, Petter Reinholdtsen wrote [edited]: > We should find a better way to identify firmware packages, allowing > hw-detect to find the correct ones without unpacking. Some options: an optional control field in binary packages or, perhaps better, a debtags facet. -S -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110108105229.gc9...@mobee
Re: squeeze will not have googleearth-package
On Thu, Jan 06, 2011 at 02:30:36PM +0100, Holger Levsen wrote [edited]: > so googleearth-package was removed from squeeze, because of a RC bug, which > was fixed on mentors.d.n for 4 days already when it was removed. The sponsorship request should have been CC'ed to the RC bug report. -S -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110108105501.gd9...@mobee
Benötige eine USB Start-Disk(3,5´´Floppy) zum Start für USB-Stick
hallo. ich habe mir einen bootfähigen USB-Stick "gebastelt" mit debian Lenny (5.0.7Live). ich habe ihn bei meinem freund ausprobiert und er funzt. "Toll" leider habe ich das problem das mein PC Compaq keinen Boot von USB unterstützt. Bei Damn Small Linux habe ich festgestellt das man a von 3,5´´ Diskette booten kann und man dann den bootfähigen USB-Stick starten kann. Leider ist diese Distri nicht so mein Fall Wie kann ich nun meinen USB-Stick mit debian 5.0.7 von kloppy aus starten. ich habe im internet schon nachgesehen, leider nichts brauchbares gefunden und wende mich nun auf diese art an sie. ich bedanke mich schon jetzt für die mühe! mfg matthias herbst -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/268450.23535...@web27108.mail.ukl.yahoo.com
Re: how to identify firmware packages
On Sat, 2011-01-08 at 11:52 +0100, Serafeim Zanikolas wrote: > On Fri, Jan 07, 2011 at 10:04:33PM +0100, Petter Reinholdtsen wrote [edited]: > > We should find a better way to identify firmware packages, allowing > > hw-detect to find the correct ones without unpacking. > > Some options: an optional control field in binary packages or, perhaps better, > a debtags facet. The script used to generate control information for firmware packages already lists each firmware blob in the package description. In fact those descriptions are almost pure apt-cache-SEO. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Re: Benötige eine USB Start-Disk(3,5´´F loppy) zum Start für USB-Stick
For the record: I answered Matthias in a private e-mail, just forgot to CC -devel, don't know why I didn't use the "answer list" function. Kind regards, Kai Wasserbäch -- Kai Wasserbäch (Kai Wasserbaech) E-Mail: deb...@carbon-project.org Jabber (debianforum.de): Drizzt URL: http://wiki.debian.org/C%C3%B9ran GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 (http://pgpkeys.pca.dfn.de/pks/lookup?search=0xE1DE59D2&fingerprint=on&hash=on&op=vindex) signature.asc Description: OpenPGP digital signature
Re: Bug#605912: runit: Upgrade failure lenny -> squeeze
# CC to debian-devel for squeeze blocker user release.debian@packages.debian.org usertag 605912 + squeeze-is-blocker thanks Hi, Thanks for looking at this bug. I think the patch you've suggested is the wrong solution, however. On Tue, 2011-01-04 at 01:14 +0900, Hideki Yamane wrote: > I guess it is due to lack of flag in debconf templates file. > Here's a proposal patch, it works in my chroot environment. [...] > +runit (2.1.1-6.2) unstable; urgency=low > + > + * Non-maintainer upload. > + * debian/control > +- add missing depenedency "debconf (>= 0.5) | debconf-2.0" > + * debian/runit.templates.in > +- add "runit-run/install" (Closes: #605912) The code in the config script which sets the runit-run/install flag as seen (which is where this bug comes from) is guarded by a check for upgrades from versions >= 2.0.0-1, which is the version in lenny. However, runit only ever suggested runit-run, so the code was always broken. As runit-run no longer exists after lenny, I think removing the entire block of code would be a better solution. In terms of the second part of the patch, the package's use of debconf looks a little odd. There is one template, which says "can I signal init to restart?". Previously, the signalling was performed without asking, which broke in environments where there was no such process, such as vservers (see #542593). The implemented solution asks this question at low priority if an init process is found, and high priority if not; in both cases the default is "yes", which does not seem to make much sense in the case where it has already been determined that there is no such process. It's possible that I simply need more coffee, but it may make more sense to simply rip the debconf use back out, and have the postinst signal init based simply on the existence of an init process. Comments welcome. Regards, Adam -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1294505796.2903.5925.ca...@hathi.jungle.funky-badger.org
runit package changes /etc/inittab ?
While we are on topic. Maintainer scripts of runit package modify /etc/inittab Although looks like /etc/inittab is not owned by any package, so policy is not violated, this IMO still looks strange in debian context. Is modifying /etc/inittab from postinst ok for random debian package these days? -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110108.20...@blacky.localdomain
Re: runit package changes /etc/inittab ?
[Nikita V. Youshchenko] > Is modifying /etc/inittab from postinst ok for random debian package > these days? It is unlikely to cause upgrade problems, at least. :) The file is copied in place by the sysvinit postinst only if it is missing. Vennlig hilsen, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2flsjx32nx7@login1.uio.no
Security implication of using force-reload instead of restart ?
Hi I've just noticed that on libapache2-mod-php5 package upgrade, apache server was not restartted (but only HUPed because of force-reload called from libapache2-mod-php5 postinst) Doesn't this mean that running apache has still old version of php module loaded, so it still is vulnerable to issues fixed in php update? Is this a severity serious bug? Perhaps same situation exists with other package combinations as well? signature.asc Description: This is a digitally signed message part.
