Re: Forwarding bugs upstream
Hi After reading this thread, I've got a strange thought. So teams maintaining important projects in Debian can't handle the load caused by bug report stream. Large presentange of bugs actually as upstream bugs. If so, upstream should be interested in that information non less than in any other information about bugs in their software. Also, upstream should be interested in having their software in distributions in as good shape as possible - distributions are *the* channel how most users get upstream's software. Then, maybe explicitly request upstream - at appropriate forums and in appropriate polite wording - to help debian team(s) to handle the bug report stream? Sure this will cause requests to put bug report into upstream trackers. Situation with this has been described within this thread, and this information - in brief form - could be presented to upstreams. I think this method could attact additional resource into solving the problem being discussed in this thread. Just wanted to share my thought. Nikita signature.asc Description: This is a digitally signed message part.
Re: Equivalent packages between Linux distributions
On Wednesday 19 January 2011 00.54:44 Silvio Cesare wrote: > I have generated a list of roughly equivalent packages between Linux > distributions (currently Debian 5 and Fedora 13). The list is > automatically generated. Cool! Maybe I have missed a pointer or whatever: how did you compute this similarity? Number of identical files? Or filenames? I was just wondering: GSoC project: * run this after every release of a major distribution * add this info to aptitude/... : if I install a package that doesn't exist, add this to the search database (not sure what aptitude looks at right now, exactly, but it already has the infrastructure for proposing a package if the given name doesn't exist.) But please make this optional, on small systems apt already is only barely usable. cheers -- vbi -- to debug such lockups in the future you can do: ... NOTE: dont use the keyboard in this mode for too long, it can lock up. -- Ingo Molnar, lkml signature.asc Description: This is a digitally signed message part.
Re: Equivalent packages between Linux distributions
You might want to look at the PackageMap project started by a Debian/Gentoo contributor: http://blog.hartwork.org/?p=373 http://lists.freedesktop.org/mailman/listinfo/packagemap -- bye, pabs http://wiki.debian.org/PaulWise -- 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/AANLkTi=gsel56fde7eaz5nedeo5h_y1uh56j-3vly...@mail.gmail.com
Bug#610506: ITP: ardentryst -- Action/RPG sidescoller, focused on story and character development
Package: wnpp Severity: wishlist Owner: Vincent Cheng * Package name: ardentryst Version : 1.7.1 Upstream Author : Jordan Trudgett * URL : http://jordan.trudgett.com/ * License : game itself: GPL-3 ; game data/music: CC 3.0 Programming Lang: Python Description : Action/RPG sidescoller, focused on story and character development Ardentryst is an action/RPG sidescoller, focused not just on fighting, but on story, and character development. It features two playable characters and a variety of weapons, items, armour, monsters, and beautiful level scenery and graphics. -- 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/20110119090820.2188.25780.report...@vincent-laptop.vc.shawcable.net
Re: Why is help so hard to find?
Tollef Fog Heen wrote: > While I have no love for insserv, if you think the whole point of > dependency based boot (be it insserv, upstart, systemd) is boot speed, > I think you're mistaken. It's a part of the goal, but much more > important is actually correctness. Getting the dependencies between > init scripts correct is sometimes hard. Thanks, it had to be said. I also hate change, but as you say... > People have to test, test again and test more and people also have to > file bugs. Bugs suck, but they're part of life and complaining about > decision made a long ago is much less productive than just living with > them, making the best out of them and filing bugs when things break. +1 -- ยท''`. : :' : As Freud said, sometimes a cigar is just a cigar. `. `' `-Proudly running Debian GNU/Linux -- 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/20110119164108.GQ2380@aenima
security updates introducing breakage
Hello, What is policy when security updates for stable introduce new regressions in software that weren't there before? Can these get fixed in stable? e.g. I have had somebody complain to me that this bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587702 which was introduced into stable through a security update, has been fixed in unstable/testing, but doesn't seem to be fixed in stable? What is the recommended way of querying issues like this? The bug in question is archived and closed because it is fixed in unstable, but no attempt has been made to fix the package in stable. So users are forced to install the non-security updated version to work around this. Thanks. -- Brian May -- 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/AANLkTi=hbq4nzglm4ak_vtl_6tbpjo15zy5sg0rch...@mail.gmail.com
Re: security updates introducing breakage
On Thu, Jan 20, 2011 at 10:59 AM, Brian May wrote: > What is policy when security updates for stable introduce new > regressions in software that weren't there before? Can these get fixed > in stable? If a stable security update contained a regression, usually that is fixed with an update in the stable security archive. Please ping the maintainer and CC the security team about this. You will also want to unarchive the bug so that it can be closed again. I also wonder why the security team didn't pick this up, I guess they don't have any automatic tracking of bugs filed against versions they uploaded. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/AANLkTi=97ga+uvemkftee7unc5sx5ruwdu9-2h9qb...@mail.gmail.com
Re: memset(x,y,0) bug audit
Samuel Thibault wrote: > On Tue, Jan 18, 2011 at 09:11, Silvio Cesare > wrote: >> I performed an audit of Debian stable for memset(x,y,0) bugs. These >> should typically be corrected with memset(x,0,y). > > I guess that could be one of the candidates for DACA. Will be available once cppcheck 1.47 is released and the archive is checked with it: https://github.com/danmar/cppcheck/commit/6ec4497919363ca3a81b61ce8121a9b48e46fe63 Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- 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/ih8eum$v9c$1...@dough.gmane.org
