Re: Bug#730258: please add arch-specific BTS tags
On Sat, 23 Nov 2013, Ivo De Decker wrote: During a discussion about architecture qualification, the release team concluded that it would be interesting to have a better way to track architecture-specific bugs. It would be nice to have BTS tags for each architecture that is currently in the archive. It might also make sense to have tags for the architectures on debian-ports, to be able to filter issues about these easily. This sounds reasonable; are only tags required, or do we need more infrastructure than that? These are the list of ports that I see: amd64 armel armhf hurd-i386 i386 ia64 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390x sparc avr32 sh What else am I missing? [I note that http://www.debian.org/ports/#portlist-released seems to have a reasonable list of ports, and http://anonscm.debian.org/viewvc/webwml/webwml/english/releases/sid/archive.data?view=markup has another; I'd like to reference a canonical location for ports (perhaps maintained by debian-ports or similar) so I don't have to figure out for myself which ports need a tag and what that tag should be, and which ports are just duplicates of other ports, and therefore don't need a tag. -- Don Armstrong http://www.donarmstrong.com There are two major products that come out of Berkeley: LSD and UNIX. We don't believe this to be a coincidence. -- Jeremy S. Anderson -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131123215315.gb7...@teltox.donarmstrong.com
Re: Bug#730258: please add arch-specific BTS tags
On Sun, 24 Nov 2013, Paul Wise wrote: On Sun, Nov 24, 2013 at 5:53 AM, Don Armstrong wrote: These are the list of ports that I see: I would strongly suggest not hardcoding this list and instead harvesting the Architecture fields of the Release files for oldstable - experimental on ftp.d.o, ftp.d-p.o and maybe archive.d.o. We have made this mistake and similar ones (usually hardcoding release codenames) in the QA infrastructure and it has bitten us hard in the past. Lets not make that mistake here. The list will be hardcoded, because it has to live in the Debbugs configuration file, and tags shouldn't disappear just because debian-ports or debian has dropped an architecture. That said, I was planning on setting it up so that I at least was notified when the set from cannonical location changed. The release files are the closest to a canonical list of ports. There are other ports out there not maintained on d-p.o (like the Interix or Solaris ones for example) but I don't think we need to bother about those until they move closer to Debian. OK. -- Don Armstrong http://www.donarmstrong.com There are two major products that come out of Berkeley: LSD and UNIX. We don't believe this to be a coincidence. -- Jeremy S. Anderson -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131124004708.gc7...@teltox.donarmstrong.com
BTS tags/pseudopackages for ports [Was: Re: Potential issues for most ports]
On Tue, 05 Nov 2013, Don Armstrong wrote: In any event, if a few active porters wouldn't mind creating a wishlist bug against bugs.debian.org for this with a suggested course of action, I'd appreciate it. Assuming there is no significant disagreement about that course of action, I'd like to implement it within a week or so. If someone has filed a wishlist bug, I've missed it. -- Don Armstrong http://www.donarmstrong.com I really wanted to talk to her. I just couldn't find an algorithm that fit. -- Peter Watts _Blindsight_ p294 -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2013181711.gv9...@rzlab.ucr.edu
Re: Potential issues for most ports (Was: Re: Bits from the Release Team (Jessie freeze info))
On Tue, 05 Nov 2013, Niels Thykier wrote: In this regard; I am guilty of filing some those bugs without tagging them. Honestly, adding the tags get a bit in the way right now. If a package FTBFS on 4 architectures, I have to dig up 3-4 different usertags (with different user) and associate it with the bug. This sounds like a case where we should turn these usertags into fully fledged tags. [Or alternatively, they should just be made usertags under the debian-po...@lists.debian.org user or similar.] I'm OK with assisting with either, but I need to know which solution porters would prefer. -- Don Armstrong http://www.donarmstrong.com For those who understand, no explanation is necessary. For those who do not, none is possible. -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131105183439.gy9...@rzlab.ucr.edu
Re: Potential issues for most ports (Was: Re: Bits from the Release Team (Jessie freeze info))
On Tue, 05 Nov 2013, Don Armstrong wrote: On Tue, 05 Nov 2013, Niels Thykier wrote: In this regard; I am guilty of filing some those bugs without tagging them. Honestly, adding the tags get a bit in the way right now. If a package FTBFS on 4 architectures, I have to dig up 3-4 different usertags (with different user) and associate it with the bug. This sounds like a case where we should turn these usertags into fully fledged tags. [Or alternatively, they should just be made usertags under the debian-po...@lists.debian.org user or similar.] I would also be OK with creating a pseudopackage as well as Ian suggested. [Or multiple pseudopackages.] Something like i386.ports.debian.org or similar would work, with each current port getting a pseudopackage, and the maintainer of the pseudopackage being the ports list. -- Don Armstrong http://www.donarmstrong.com America was far better suited to be the World's Movie Star. The world's tequila-addled pro-league bowler. The world's acerbic bi-polar stand-up comedian. Anything but a somber and tedious nation of socially responsible centurions. -- Bruce Sterling, _Distraction_ p122 -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131105185031.gz9...@rzlab.ucr.edu
Re: Potential issues for most ports (Was: Re: Bits from the Release Team (Jessie freeze info))
On Tue, 05 Nov 2013, Wouter Verhelst wrote: Well, I did ask for the creation of port-specific tags back at debconf8 (if I'm not mistaken), but you told me to go for usertags instead ;-) Sounds familiar. Usertags have the advantage of not requiring me to do any work. But presumably at the time I hadn't thought of the difficulties of coordinating all of the different usertags between porters. Yes, I think that's a good idea; it would avoid issues where maintainers are waiting on porters and vice versa, since the reassigning of a bug to a port pseudopackage would make it clear who's waiting for whom. Additionally, it would allow porters to have a todo list of things that need to be done for their port but aren't specific to any one package (or of which the root cause hasn't been found yet, e.g., recently compiled binaries segfault, but we don't know why yet) If you're going down this road, I would appreciate it if ports listed on debian-ports.org would also be getting pseudopackages. Since they would all be under the same ports.debian.org (or similar) namespace, I wouldn't have a problem with it. [My main concern about pseudopackages is polluting the package namespace; since I can't imagine anyone ever wanting to create a package called someport.ports.debian.org for a sane reason, that shouldn't be a big deal.] It would also be possible (in the meantime) for bugs to be assigned to both the port-specific pseudopackage, and the original package which spawned the bug. In any event, if a few active porters wouldn't mind creating a wishlist bug against bugs.debian.org for this with a suggested course of action, I'd appreciate it. Assuming there is no significant disagreement about that course of action, I'd like to implement it within a week or so. -- Don Armstrong http://www.donarmstrong.com PowerPoint is symptomatic of a certain type of bureaucratic environment: one typified by interminable presentations with lots of fussy little bullet-points and flashy dissolves and soundtracks masked into the background, to try to convince the audience that the goon behind the computer has something significant to say. -- Charles Stross _The Jennifer Morgue_ p33 -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131105201345.ga9...@rzlab.ucr.edu
Re: Please unban S. Luther from debian-powerpc@lists.debian.org
On Thu, 30 Aug 2007, Jimmy Johnson wrote: So if someone would let us understand why Sven was banned in the first place, then may be this whole sad affair can be brought to some kind of closure. http://lists.debian.org/debian-powerpc/2007/08/msg00115.html is the warning which was sent from listmaster to Sven; for failing to heed it the ban was reinstated. If you wish to complain about the ban, e-mailing [EMAIL PROTECTED] is the appropriate response, not mailing this list. Don Armstrong [Further responses off list] -- The question of whether computers can think is like the question of whether submarines can swim. -- Edsgar Dijkstra http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Sound support on Powerbook5,7 17 [layout ID 0x40]: snd-aoa?
It seems that sound-powermac as of 2.6.17.3 doesn't yet support the Powerbook5,7 17 sound card; it gives me an snd: Unknown layout ID 0x40 I know that when I last harassed Benjamin about this, I was told that it wasn't supported yet, but perhaps that has changed. Is the snd-aoa driver supposed to support this card? Don Armstrong [Not subscribed, so please obey MFT.] -- DIE! -- Maritza Campos http://www.crfh.net/d/20020601.html http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sound support on Powerbook5,7 17 [layout ID 0x40]: snd-aoa?
On Mon, 24 Jul 2006, Johannes Berg wrote: I know that when I last harassed Benjamin about this, I was told that it wasn't supported yet, but perhaps that has changed. Is the snd-aoa driver supposed to support this card? It indeed is. In fact, IIRC Børge Holen has verified that it does work, Right, I managed to get it working myself now. It being in 2.6.18-rc1 basically makes getting it to work painless (beyond blacklisting snd_powermac or not compiling it so udev doesn't freak out.) Don Armstrong -- If you find it impossible to believe that the universe didn't have a creator, why don't you find it impossible that your creator didn't have one either? -- Anonymous Coward http://slashdot.org/comments.pl?sid=167556cid=13970629 http://www.donarmstrong.com http://rzlab.ucr.edu
