tuxpaint-devel Mailing List for Tux Paint (Page 159)
An award-winning drawing program for children of all ages
Brought to you by:
wkendrick
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
(15) |
Apr
(5) |
May
(12) |
Jun
(15) |
Jul
(21) |
Aug
(2) |
Sep
(14) |
Oct
(32) |
Nov
(47) |
Dec
(39) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
(33) |
Feb
(59) |
Mar
(17) |
Apr
(5) |
May
|
Jun
(6) |
Jul
(7) |
Aug
(19) |
Sep
(64) |
Oct
(161) |
Nov
(9) |
Dec
(23) |
| 2007 |
Jan
(6) |
Feb
(46) |
Mar
(55) |
Apr
(41) |
May
(43) |
Jun
(44) |
Jul
(46) |
Aug
(25) |
Sep
(16) |
Oct
(29) |
Nov
(50) |
Dec
(64) |
| 2008 |
Jan
(11) |
Feb
(18) |
Mar
(52) |
Apr
(37) |
May
(40) |
Jun
(78) |
Jul
(85) |
Aug
(31) |
Sep
(23) |
Oct
(13) |
Nov
(19) |
Dec
(37) |
| 2009 |
Jan
(36) |
Feb
(24) |
Mar
(86) |
Apr
(43) |
May
(36) |
Jun
(151) |
Jul
(23) |
Aug
(40) |
Sep
(11) |
Oct
(91) |
Nov
(68) |
Dec
(27) |
| 2010 |
Jan
|
Feb
(11) |
Mar
(79) |
Apr
(50) |
May
(26) |
Jun
(44) |
Jul
(31) |
Aug
(6) |
Sep
(2) |
Oct
(16) |
Nov
(11) |
Dec
(4) |
| 2011 |
Jan
(14) |
Feb
(5) |
Mar
(22) |
Apr
(1) |
May
(5) |
Jun
(5) |
Jul
(13) |
Aug
(1) |
Sep
(3) |
Oct
(18) |
Nov
(15) |
Dec
(25) |
| 2012 |
Jan
(1) |
Feb
(9) |
Mar
(41) |
Apr
(32) |
May
|
Jun
(2) |
Jul
(5) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
| 2013 |
Jan
|
Feb
(5) |
Mar
(16) |
Apr
(21) |
May
(3) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
(13) |
Nov
(1) |
Dec
(3) |
| 2014 |
Jan
|
Feb
(12) |
Mar
(6) |
Apr
(35) |
May
|
Jun
(12) |
Jul
(35) |
Aug
(98) |
Sep
(3) |
Oct
(8) |
Nov
(4) |
Dec
(1) |
| 2015 |
Jan
(4) |
Feb
(9) |
Mar
(58) |
Apr
(9) |
May
(15) |
Jun
(23) |
Jul
|
Aug
(32) |
Sep
(12) |
Oct
(21) |
Nov
(5) |
Dec
(14) |
| 2016 |
Jan
(6) |
Feb
(3) |
Mar
(37) |
Apr
(18) |
May
(5) |
Jun
(8) |
Jul
|
Aug
(21) |
Sep
(5) |
Oct
(20) |
Nov
(4) |
Dec
(6) |
| 2017 |
Jan
(2) |
Feb
|
Mar
|
Apr
(19) |
May
(8) |
Jun
(3) |
Jul
(3) |
Aug
(5) |
Sep
|
Oct
(4) |
Nov
(4) |
Dec
(6) |
| 2018 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(4) |
Sep
(4) |
Oct
|
Nov
|
Dec
(3) |
| 2019 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
(2) |
Jul
(1) |
Aug
(3) |
Sep
(14) |
Oct
(2) |
Nov
(1) |
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
(1) |
Apr
(1) |
May
(2) |
Jun
|
Jul
|
Aug
(3) |
Sep
(15) |
Oct
(9) |
Nov
(11) |
Dec
(7) |
| 2021 |
Jan
(12) |
Feb
(2) |
Mar
(16) |
Apr
|
May
|
Jun
(11) |
Jul
|
Aug
(4) |
Sep
(24) |
Oct
(68) |
Nov
(61) |
Dec
|
| 2022 |
Jan
(42) |
Feb
(17) |
Mar
(20) |
Apr
(2) |
May
(23) |
Jun
(4) |
Jul
(6) |
Aug
|
Sep
(27) |
Oct
(4) |
Nov
(10) |
Dec
(31) |
| 2023 |
Jan
(4) |
Feb
(18) |
Mar
(8) |
Apr
(11) |
May
(18) |
Jun
(47) |
Jul
(1) |
Aug
(1) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(2) |
| 2024 |
Jan
(10) |
Feb
|
Mar
|
Apr
(3) |
May
(4) |
Jun
(3) |
Jul
(6) |
Aug
|
Sep
(2) |
Oct
(1) |
Nov
|
Dec
(3) |
| 2025 |
Jan
(2) |
Feb
(11) |
Mar
(3) |
Apr
(1) |
May
(22) |
Jun
(5) |
Jul
(15) |
Aug
(5) |
Sep
|
Oct
(3) |
Nov
|
Dec
|
|
From: Ben A. <sy...@sa...> - 2005-03-22 23:47:16
|
I believe we added header detection because it was a common problem for users to forget to install the dependencies. But this has caused tuxpaint in Debian to break, which is a release critical bug right on the verge of Sarge releasing. I have to ask at this point if it is really worth it, or if we shouldn't put moving tuxpaint to a proper autotools-based build system as a higher priority. I'll hack my way around it now (probably just by disabling the checks) so I can remove this RC bug against tuxpaint as soon as possible, but I'd like to know what you guys think our permanent fix should be. Ben -------- Forwarded Message -------- > From: Kurt Roeckx <ku...@ro...> > Reply-To: Kurt Roeckx <ku...@ro...>, 30...@bu... > To: su...@bu... > Subject: Bug#300632: tuxpaint: FTBFS: Changed header files. > Date: Sun, 20 Mar 2005 22:33:55 +0100 > Package: tuxpaint > Version: 1:0.9.14-1 > Severity: serious > > Hi, > > Your package is no longer building problem. I get the following error: > > ...Compiling Tux Paint from source... > src/tuxpaint.c:176:2: #error "---------------------------------------------------" > src/tuxpaint.c:177:2: #error "If you installed SDL_image from a package, be sure" > src/tuxpaint.c:178:2: #error "to get the development package, as well!" > src/tuxpaint.c:179:2: #error "(e.g., 'libsdl-image1.2-devel.rpm')" > src/tuxpaint.c:180:2: #error "---------------------------------------------------" > src/tuxpaint.c:195:2: #error "---------------------------------------------------" > src/tuxpaint.c:196:2: #error "If you installed SDL_mixer from a package, be sure" > src/tuxpaint.c:197:2: #error "to get the development package, as well!" > src/tuxpaint.c:198:2: #error "(e.g., 'libsdl-mixer1.2-devel.rpm')" > src/tuxpaint.c:199:2: #error "---------------------------------------------------" > make[1]: *** [obj/tuxpaint.o] Error 1 > > You do seem to have both mentioned required build dependencies. > > The code looks like this: > #include "SDL_image.h" > #ifndef _IMG_h > #error > > #include "SDL_mixer.h" > #ifndef _MIXER_H_ > #error > > > The first seems to be using _SDL_IMAGE_H (now?) and the > second _SDL_MIXER_H. > > I find detection of presense of a header file like that a stupid > way. It should not rely on those defines. > > The proper way to do this would be to have a configure script > that could then give an error message. > > > Kurt > > -- |
|
From: Bill K. <nb...@so...> - 2005-03-22 20:13:50
|
On Tue, Mar 22, 2005 at 02:39:30PM -0500, Sam Hart wrote: > I actually wasn't aware that the list was switched to lists.sf.net... > Bill, was there a technical reason for the switch? Heh, yeah! :^) The Tux4Kids.net ones just stopped working. The admin system still works, and I made sure I wasn't "nomail"'d again, then I emailed you to ask what's up, but didn't get a response, so I figured you were super-busy. Shin-Ichi ended up sending me a personal email with some comments he had tried to send to tuxpaint-dev as well, so I figured it wasn't me. I didn't want to harass you about it (though I did consider whois'ing and calling you on the phone again ;^) ), and figured moving them would just take one more thing (4 more things?) off of your plate. It's kind of what SF.net is there for, anyway ;^) Also, one thing I missed recently was integrated archives, so that was another reason I decided to just go ahead and switch. :^) > Personally, I have never been a fan of the sf.net mailing lists as they > do all manner of stuff that I don't like (I am a big fan of reply-to > munging, for example, even if certain vocal opponents try to besmirch > it). I've got this list set up as 'reply-to', so maybe they changed something since you last looked? :) Note: For me, it's simple enough to set my Mutt up so that [R]eply does [L]ist-reply by default for these lists, so if we're in the minority, I'd be willing to consider changing the list settings to no-munging. (I do NOT want a big flamewar over it, though... I see those almost monthly on one or another list I'm on! :^) ) So, hopefully, no hard feelings Sam! :^) -bill! |
|
From: Sam H. <sa...@pr...> - 2005-03-22 19:41:30
|
I actually wasn't aware that the list was switched to lists.sf.net... Bill, was there a technical reason for the switch? Personally, I have never been a fan of the sf.net mailing lists as they do all manner of stuff that I don't like (I am a big fan of reply-to munging, for example, even if certain vocal opponents try to besmirch it). On Tue, 2005-03-22 at 14:02 -0500, Albert Cahalan wrote: > On Tue, 2005-03-22 at 10:30 -0800, Bill Kendrick wrote: > > Hello all! Welcome to the new Tux Paint Developers mailing list > > (tux...@li...) > > This is still a pretty strange list. I have to manually change > the address if I want to respond off list. This is awkward > enough that I sometimes won't bother when I'd normally send a > quick note to someone. Lots of unimportant stuff ends up on > the list too. > > Also, people don't get distinct personal replies. I guess this > isn't terribly important on a low-volume list, but things get > rough if traffic ever gets to be a few hundred posts per day. > Then, you really want people using reply-to-all so that people > can filter the personal copy as high-priority. > > > I'm also considering creating a moderated "tuxpaint-announce" list, > > simply for announcing new releases, when they come out. > > tuxpaint-news would be shorter -- ''''''''''''''''''''''''' .O. Sam Hart, sa...@pr... ..O Progeny Linux Systems, Inc OOO <http://www.progeny.com/> |
|
From: Albert C. <al...@us...> - 2005-03-22 19:18:59
|
On Tue, 2005-03-22 at 10:30 -0800, Bill Kendrick wrote: > Hello all! Welcome to the new Tux Paint Developers mailing list > (tux...@li...) This is still a pretty strange list. I have to manually change the address if I want to respond off list. This is awkward enough that I sometimes won't bother when I'd normally send a quick note to someone. Lots of unimportant stuff ends up on the list too. Also, people don't get distinct personal replies. I guess this isn't terribly important on a low-volume list, but things get rough if traffic ever gets to be a few hundred posts per day. Then, you really want people using reply-to-all so that people can filter the personal copy as high-priority. > I'm also considering creating a moderated "tuxpaint-announce" list, > simply for announcing new releases, when they come out. tuxpaint-news would be shorter |
|
From: Bill K. <nb...@so...> - 2005-03-22 18:30:57
|
Hello all! Welcome to the new Tux Paint Developers mailing list (tux...@li...) The Tux4Kids lists recently stopped delivering, so I decided to take some work off of Sam Hart's hands by simply recreating the lists over here at SourceForge.net. (This also has the benefit of having centralized archives.) I've resubscribed everyone who was on 'tuxpaint-dev' onto this new 'tuxpaint-devel' list. However, I didn't have time to go and adjust users' settings (e.g., "nodups", "digest", etc.), so if you changed anything from the defaults, please go in and change them (or send me a note, and when I have time, I'll adjust your subscription options... just remember: tell me your subscribed address if it's different from your normal one!) Later today, as I have time, I'll be resubscribing folks to the new tuxpaint-commits, tuxpaint-i18n and tuxpaint-stamps lists. (Or feel free to do so yourself, over at SourceForge.) Also, I've created a new list, "tuxpaint-users", which will be geared towards 'end-users' of Tux Paint. Rather... the teachers and parents of those end users, who have questions about Tux Paint, or have specific features they'd like to see implemented. I'm also considering creating a moderated "tuxpaint-announce" list, simply for announcing new releases, when they come out. Thanks, and enjoy! -- -bill! bi...@ne... http://www.newbreedsoftware.com/ |
|
From: Bill K. <nb...@so...> - 2005-03-22 18:10:23
|
Just a test! -bill! |