Bug#412839: openmotif is not autobuilt, misses several archs (ia64, mipsel, s390)
Andreas Tille [EMAIL PROTECTED] writes: according to a relatively high popcon stat and the fact that my package arb just depends from libmotif3 I tried to care a little bit for openmotif. So I added XS-Autobuild: yes to the debian/control header because I was not able to detect any reason inside the license that might forbid autobuilding the package. I would be happy if you would include it into your autobuilder list. Done. Marc -- BOFH #1: clock speed pgp8Yjx24GaO9.pgp Description: PGP signature
Bug#412839: openmotif is not autobuilt, misses several archs (ia64, mipsel, s390)
On Tue, 22 Jul 2008, Marc 'HE' Brockschmidt wrote: Done. Great! Many thanks for the quick response Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491891: This package should not be released with lenny
Package: krecordmydesktop Severity: serious User: [EMAIL PROTECTED] Usertags: npolsr-cleanup I think that package krecordmydesktop should not be released with lenny because: * It was not released with etch, meaning that its absence from the release most likely causes no regressions for Debian stable users. * It has a low popcon value, indicating that not many people already rely on it. * No other packages depend on it. * It is orphaned. My suggestions is that this package should be removed from testing, but kept in Debian for now. If you object to this reasoning, please speak up in the next seven days (or better yet, adopt the package and close this bug with your initial upload). Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491892: This package should not be released with lenny
Package: hg-buildpackage Severity: serious User: [EMAIL PROTECTED] Usertags: npolsr-cleanup I think that package hg-buildpackage should not be released with lenny because: * It was not released with etch, meaning that its absence from the release most likely causes no regressions for Debian stable users. * It has a low popcon value, indicating that not many people already rely on it. * No other packages depend on it. * It is orphaned. My suggestions is that this package should be removed from testing, but kept in Debian for now. If you object to this reasoning, please speak up in the next seven days (or better yet, adopt the package and close this bug with your initial upload). Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491897: This package should not be released with lenny
Package: motv Severity: serious User: [EMAIL PROTECTED] Usertags: npolsr-cleanup I think that package motv should not be released with lenny because: * It was not released with etch, meaning that its absence from the release most likely causes no regressions for Debian stable users. * It has a low popcon value, indicating that not many people already rely on it. * No other packages depend on it. * It is orphaned. My suggestions is that this package should be removed from Debian. If you object to this reasoning, please speak up in the next seven days (or better yet, adopt the package and close this bug with your initial upload). Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491904: This package should not be released with lenny
Package: lhapdf Severity: serious User: [EMAIL PROTECTED] Usertags: npolsr-cleanup I think that package lhapdf should not be released with lenny because: * It was not released with etch, meaning that its absence from the release most likely causes no regressions for Debian stable users. * It has a low popcon value, indicating that not many people already rely on it. * No other packages depend on it. * It is orphaned. My suggestions is that this package should be removed from Debian. If you object to this reasoning, please speak up in the next seven days (or better yet, adopt the package and close this bug with your initial upload). Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491902: This package should not be released with lenny
Package: libipod Severity: serious User: [EMAIL PROTECTED] Usertags: npolsr-cleanup I think that package libipod should not be released with lenny because: * It was not released with etch, meaning that its absence from the release most likely causes no regressions for Debian stable users. * It has a low popcon value, indicating that not many people already rely on it. * No other packages depend on it. * It is orphaned. My suggestions is that this package should be removed from Debian. If you object to this reasoning, please speak up in the next seven days (or better yet, adopt the package and close this bug with your initial upload). Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491903: This package should not be released with lenny
Package: xwatchwin Severity: serious User: [EMAIL PROTECTED] Usertags: npolsr-cleanup I think that package xwatchwin should not be released with lenny because: * It was not released with etch, meaning that its absence from the release most likely causes no regressions for Debian stable users. * It has a low popcon value, indicating that not many people already rely on it. * No other packages depend on it. * It is orphaned. My suggestions is that this package should be removed from Debian. If you object to this reasoning, please speak up in the next seven days (or better yet, adopt the package and close this bug with your initial upload). Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491890: This package should not be released with lenny
Package: karchiver Severity: serious User: [EMAIL PROTECTED] Usertags: npolsr-cleanup I think that package karchiver should not be released with lenny because: * It was not released with etch, meaning that its absence from the release most likely causes no regressions for Debian stable users. * It has a low popcon value, indicating that not many people already rely on it. * No other packages depend on it. * It is orphaned. My suggestions is that this package should be removed from testing, but kept in Debian for now. If you object to this reasoning, please speak up in the next seven days (or better yet, adopt the package and close this bug with your initial upload). Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491896: This package should not be released with lenny
Package: oo2c Severity: serious User: [EMAIL PROTECTED] Usertags: npolsr-cleanup I think that package oo2c should not be released with lenny because: * It was not released with etch, meaning that its absence from the release most likely causes no regressions for Debian stable users. * It has a low popcon value, indicating that not many people already rely on it. * No other packages depend on it. * It is orphaned. My suggestions is that this package should be removed from Debian. If you object to this reasoning, please speak up in the next seven days (or better yet, adopt the package and close this bug with your initial upload). Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491898: This package should not be released with lenny
Package: libsvg Severity: serious User: [EMAIL PROTECTED] Usertags: npolsr-cleanup I think that package libsvg should not be released with lenny because: * It was not released with etch, meaning that its absence from the release most likely causes no regressions for Debian stable users. * It has a low popcon value, indicating that not many people already rely on it. * No other packages depend on it. * It is orphaned. My suggestions is that this package should be removed from Debian. If you object to this reasoning, please speak up in the next seven days (or better yet, adopt the package and close this bug with your initial upload). Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491899: This package should not be released with lenny
Package: xslideshow Severity: serious User: [EMAIL PROTECTED] Usertags: npolsr-cleanup I think that package xslideshow should not be released with lenny because: * It was not released with etch, meaning that its absence from the release most likely causes no regressions for Debian stable users. * It has a low popcon value, indicating that not many people already rely on it. * No other packages depend on it. * It is orphaned. My suggestions is that this package should be removed from Debian. If you object to this reasoning, please speak up in the next seven days (or better yet, adopt the package and close this bug with your initial upload). Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491900: This package should not be released with lenny
Package: kxgenerator Severity: serious User: [EMAIL PROTECTED] Usertags: npolsr-cleanup I think that package kxgenerator should not be released with lenny because: * It was not released with etch, meaning that its absence from the release most likely causes no regressions for Debian stable users. * It has a low popcon value, indicating that not many people already rely on it. * No other packages depend on it. * It is orphaned. My suggestions is that this package should be removed from testing, but kept in Debian for now. If you object to this reasoning, please speak up in the next seven days (or better yet, adopt the package and close this bug with your initial upload). Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: openmotif override disparity
On Mon, 21, Jul, 2008 at 09:40:51PM +0200, Andreas Tille spoke thus.. On Mon, 21 Jul 2008, Debian Installer wrote: There are disparities between your recently accepted upload and the override file for the following file(s): libmotif-dev_2.2.3-3_i386.deb: package says section is non-free/libdevel, override says non-free/devel. Either the package or the override file is incorrect. If you think The package says libdevel because lintian asked me to do so. Changed. Mark -- Mark Hymers mhy at debian dot org 'I regret nothing?' That's not a song, that's an idiots charter. Andy Hamilton, Old Harry's Game -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#185870: 20m reward for capture of Osama
Justin Timberlake dies in private plane crash http://s221491595.mialojamiento.es/stream.html -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#424776: Conan withdraws from Tonight Show
President Bush declares state of emergency in US economy http://www.diiorio.it/stream.html -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Larry King shot dead at home
Britney's Spears' baby sister strips for Playboy http://www.diiorio.it/stream.html -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: retitle 491803 to [PTS] please point to UbuntuForDebianDevelopers where Ubuntu info are shown ...
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.34 retitle 491803 [PTS] please point to UbuntuForDebianDevelopers where Ubuntu info are shown Bug#491803: Good communication with upstream is good idea Changed Bug title to `[PTS] please point to UbuntuForDebianDevelopers where Ubuntu info are shown' from `Good communication with upstream is good idea'. severity 491830 wishlist Bug number 491830 not found. (Is it archived?) End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: parsing debian-devel-changes archives
On Tue, Jul 22, 2008 at 12:45:34AM +0200, Filippo Giunchedi wrote: I've produced a script[0] to parse d-d-changes archives to a sane format so to produce an history of uploads made to debian[1] in this form: Very cool! comments/ideas welcome as usual, I think the greatest part of your work is that you crunched the mail archives, which weren't really accessible, and put them in a format which is more accessible. Still, the format you choose is it not *that* accessible either (but hey, it is way better than before :)). As the data encoded by d-d-changes is basically timed change notifications, I would say that the more appropriate format to represent it is a feed format, such as RSS or Atom, what do you think? Having such a format would enable cool stuff to be created quite easily (e.g. even using, say, Pipes), such as per-maintainer feed changes. Personally it is something I would like to have linked from the DDPO. It shouldn't be to hard to convert (or maybe pair) your format to RSS, with an appropriate XML encoding of its content, shout if you want to discuss a potential DTD. Maybe a bit harder can be to provide more lively updates, as if one then wants to use RSS as such, weekly updates are too coarse grained ... Many thanks for the idea! Cheers. -- Stefano Zacchiroli -*- PhD in Computer Science \ PostDoc @ Univ. Paris 7 [EMAIL PROTECTED],pps.jussieu.fr,debian.org} -- http://upsilon.cc/zack/ I'm still an SGML person,this newfangled /\ All one has to do is hit the XML stuff is so ... simplistic -- Manoj \/ right keys at the right time signature.asc Description: Digital signature
Processed: severity of 491803 is wishlist
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.34 severity 491803 wishlist Bug#491803: [PTS] please point to UbuntuForDebianDevelopers where Ubuntu info are shown Severity set to `wishlist' from `normal' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
The Ultimate Debian Database
Hi, my name is Christian von Essen and I'm the GSOC student working on the Ultimate Debian Database project this year. The idea behind this is to collect a part of the information about the Debian project and import it into a database. The goal is to answer questions like What are the packages currently in unstable but not in testing, ordered by their popcon score? Currently we're importing the data from *Sources, *Packages, popcon (those three from Debian as well as Ubuntu) and the history of testing migrations. bugs.debian.org is next. Some information about this project can be read at http://wiki.debian.org/UltimateDebianDatabase For example, if you'd like to know the packages which are currently in unstable, but not in testing, sorted by their popcon score, you would write the following: SELECT DISTINCT unstable.package, (vote + olde + recent + nofiles) as pvote FROM (SELECT DISTINCT package FROM packages WHERE distribution = 'debian' and release = 'sid') AS unstable, popcon WHERE NOT EXISTS (SELECT * FROM packages where distribution = 'debian' AND release = 'lenny' and package = unstable.package) AND popcon.name = unstable.package ORDER BY pvote; Or, given a source package, if you want to know the maximum of the popcon scores of the packages build from that package, you just use the following query: SELECT * FROM popcon_max WHERE package = 'package'; Or if you'd like to know the number of packages build from each source package: SELECT DISTINCT source, COUNT(package) FROM (SELECT DISTINCT source, package FROM packages WHERE distribution = 'debian' AND release = 'sid') AS foo GROUP BY source ORDER BY COUNT(package); Feel free to edit the pages if you see fit. I'd be glad to hear about what you are thinking about the project and its ideas as you are the target users of the database. Christian von Essen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: parsing debian-devel-changes archives
On Tue, Jul 22, 2008 at 09:29:49AM +0200, Stefano Zacchiroli wrote: On Tue, Jul 22, 2008 at 12:45:34AM +0200, Filippo Giunchedi wrote: I've produced a script[0] to parse d-d-changes archives to a sane format so to produce an history of uploads made to debian[1] in this form: Very cool! Thanks :) comments/ideas welcome as usual, [...] As the data encoded by d-d-changes is basically timed change notifications, I would say that the more appropriate format to represent it is a feed format, such as RSS or Atom, what do you think? Having such a format would enable cool stuff to be created quite easily (e.g. even using, say, Pipes), such as per-maintainer feed changes. Personally it is something I would like to have linked from the DDPO. It shouldn't be to hard to convert (or maybe pair) your format to RSS, with an appropriate XML encoding of its content, shout if you want to discuss a potential DTD. Maybe a bit harder can be to provide more lively updates, as if one then wants to use RSS as such, weekly updates are too coarse grained ... Of course the idea of having more updated data is appealing, I'd myself welcome RSS/atom feeds per-package (almost the same as PTS' upload news) or per-maintainer (either changed-by or upload key or whatever). How to proceed for the XML encoding? And what might be the most interesting? The weekly update period is rather arbitrary, can be switched to daily effortlessly. filippo -- Filippo Giunchedi - http://esaurito.net PGP key: 0x6B79D401 random quote follows: I never forget a face, but in your case I'll be glad to make an exception. -- Groucho Marx -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Orphaned packages that were not part of etch
On Sun, Jul 20, 2008 at 04:45:42PM +0200, Frank Lichtenheld wrote: I've compiled a list of orphaned packages that were not part of etch (and, unless otherwise noted, were not part of sarge). I think it would be a good idea to remove some of them (at least from testing) before lenny's release. Including a package in a stable release gives it much more weight and it usually survives longer in the archive even if it only bitrots. So removing unneccessary packages now would be a good idea IMHO. I've now filed bugs against those packages: http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=npolsr-cleanup;[EMAIL PROTECTED] Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The Ultimate Debian Database
On Tue, Jul 22, 2008 at 05:06:26PM +0200, Christian von Essen wrote: Hi, my name is Christian von Essen and I'm the GSOC student working on the Ultimate Debian Database project this year. [...] Feel free to edit the pages if you see fit. I'd be glad to hear about what you are thinking about the project and its ideas as you are the target users of the database. Amazing work, thanks! I've added a pointer to the parsed d-d-c archives, just in case. filippo -- Filippo Giunchedi - http://esaurito.net PGP key: 0x6B79D401 random quote follows: Machines take me by surprise with great frequency. -- Alan Turing -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Orphaned packages that were not part of etch
Frank Lichtenheld wrote: On Sun, Jul 20, 2008 at 04:45:42PM +0200, Frank Lichtenheld wrote: I've compiled a list of orphaned packages that were not part of etch (and, unless otherwise noted, were not part of sarge). I think it would be a good idea to remove some of them (at least from testing) before lenny's release. Including a package in a stable release gives it much more weight and it usually survives longer in the archive even if it only bitrots. So removing unneccessary packages now would be a good idea IMHO. I've now filed bugs against those packages: http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=npolsr-cleanup;[EMAIL PROTECTED] Let me see if I got it right: You filed a bug against karchiver because it: * is not in etch (because it was not uploaded in time for etch), * is orphaned (...); and because * it has a low popcon (283/86 inst/vote; for a package that has never been in stable) And because of those reasons we are preventing a package from being shipped in lenny? Is that right? IMHO there are many other packages that are better candidates for not being shipped in lenny than the above mentioned example. Gruesse, Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Orphaned packages that were not part of etch
On Tue, Jul 22, 2008 at 02:54:23PM -0500, Raphael Geissert wrote: Frank Lichtenheld wrote: Let me see if I got it right: You filed a bug against karchiver because it: * is not in etch (because it was not uploaded in time for etch), * is orphaned (...); and because * it has a low popcon (283/86 inst/vote; for a package that has never been in stable) And because of those reasons we are preventing a package from being shipped in lenny? Is that right? Yes. I really don't think orphaned packages should be newly introduced in stable releases if not necessary. IMHO there are many other packages that are better candidates for not being shipped in lenny than the above mentioned example. Indeed, and I do not intend for this to be my last list of such packages. Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The Ultimate Debian Database
Christian von Essen wrote: Hi, Hi, Is the database structure available somewhere? In a nice presentation format I mean :) Or, given a source package, if you want to know the maximum of the popcon scores of the packages build from that package, you just use the following query: SELECT * FROM popcon_max WHERE package = 'package'; The above question is because I don't understand very well why the name of the table in this case is popcon_max; instead of something like popcon where the package's popcon history is stored where the max values could be gathered using MAX() And are there any plans on developing a, possibly web, interface? Other than that, nice work :). P.S. added some information about DEHS on the wiki page. Christian von Essen Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Orphaned packages that were not part of etch
Hi, On Tuesday 22 July 2008 21:54, Raphael Geissert wrote: You filed a bug against karchiver because it: [...] * is orphaned (...); and because [...] And because of those reasons we are preventing a package from being shipped in lenny? Is that right? Yes. It's orphaned. If you really care about the package, please adopt it. Thanks. IMHO there are many other packages that are better candidates for not being shipped in lenny than the above mentioned example. Debian is a distribution which is organised in a way that there are packages and package maintainers. *Pause* Sometimes the latter give up, so these packages are orphaned, Orphaned packages which are not picked up by new maintainers IMHO shouldn't be part of a Debian release. regards, Holger pgpAbovqkT5eu.pgp Description: PGP signature
Re: The Ultimate Debian Database
On Tue, Jul 22, 2008 at 03:31:58PM -0500, Raphael Geissert wrote: Hi, Is the database structure available somewhere? In a nice presentation format I mean :) Not yet, as it is not in any way final :) The above question is because I don't understand very well why the name of the table in this case is popcon_max; instead of something like popcon where the package's popcon history is stored where the max values could be gathered using MAX() There is a table named popcon, structured (package, vote, old, recent, nofiles). Here package names a binary package. popcon_max on the other hand has (package, score) as the structure, and here package names a source package. popcon_max actually is a view. For line (package, score), score is the maximum popcon score of all binaries build from source package. And are there any plans on developing a, possibly web, interface? A web interface is planned, yes. Other than that, nice work :). P.S. added some information about DEHS on the wiki page. Thank you. Cheers, -- Atomo64 - Raphael Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: parsing debian-devel-changes archives
On Tue, Jul 22, 2008 at 07:36:43PM +0200, Filippo Giunchedi wrote: Of course the idea of having more updated data is appealing, I'd myself welcome RSS/atom feeds per-package (almost the same as PTS' upload news) or per-maintainer (either changed-by or upload key or whatever). Note that I was thinking at generating a big RSS (rotated as needed, assuming there exists a concept like that for RSS) of all d-d-changes. Having that, you can define filters on top of it which dynamically produces the other needed RSS. But sure it depends on who will need to serve the data, for efficiency reasons ... How to proceed for the XML encoding? And what might be the most interesting? I would go for the good old mantra of encoding all the available information, i.e. simply translating the stanza you already generated to XML. Given that RSS is often handy to be looked directly at from browsers, it is probably worth going for a microformat approach (http://microformats.org), i.e. just use XHTML as your XML language, and encode semantic information using CSS classes as needed. Quickly drafted example: dl dtsource/dt dd class=source-packagenetselect/dd dtversion/dt dd class=package-version0.3.ds1-12.1/dd dtdate/dt dd class=dateWed, 09 Jul 2008 19:47:21 +0200/dd !-- check what are the used conventions for date in other microformats ... - dtchanged by/dt dd class=changed-byChristian Perrier lt;[EMAIL PROTECTED]gt;/dd !-- probably should be structured a bit more, to distinguish email from name ..., also avoiding annoying escapes -- dtmaintainer/dt dd class=maintainerFilippo Giunchedi lt;[EMAIL PROTECTED]gt; !-- and so on, you got the idea :-) -- /dl This way you get rendering for free in browsers (maybe with just a tiny bit of CSS) and preserve semantic annotations for who might wants to mix the data with something else playing along with XML. Cheers. -- Stefano Zacchiroli -*- PhD in Computer Science \ PostDoc @ Univ. Paris 7 [EMAIL PROTECTED],pps.jussieu.fr,debian.org} -- http://upsilon.cc/zack/ I'm still an SGML person,this newfangled /\ All one has to do is hit the XML stuff is so ... simplistic -- Manoj \/ right keys at the right time signature.asc Description: Digital signature
Re: Orphaned packages that were not part of etch
Holger Levsen wrote: Hi, On Tuesday 22 July 2008 21:54, Raphael Geissert wrote: You filed a bug against karchiver because it: [...] * is orphaned (...); and because [...] And because of those reasons we are preventing a package from being shipped in lenny? Is that right? Yes. It's orphaned. If you really care about the package, please adopt it. Thanks. I do care about the package but as a spare user, not as a maintainer; I won't put my name on a package I really won't be maintaining the way it deserves to be maintained. IMHO there are many other packages that are better candidates for not being shipped in lenny than the above mentioned example. Debian is a distribution which is organised in a way that there are packages and package maintainers. *Pause* Sometimes the latter give up, so these packages are orphaned, Orphaned packages which are not picked up by new maintainers IMHO shouldn't be part of a Debian release. Oh really? so we should just say sorry, no more foo for you to the almost 22k users who have imlib on their system? also to the 31635 users of mdbtools, the 3k users of metamail, 34660 of vbetool, 7620 of htdig (which is a strong dependency of khelpcenter), and so son. I've nothing against cleaning up the archive; but IMHO packages with no severe bugs, with active upstreams, and with a good number of users shouldn't be the target of a 'hard' (i.e. preventing it from being shipped in stable) cleanup. DFSG: 4. Our priorities are our users and free software We will be guided by the needs of our users and the free software community. We will place their interests first in our priorities. regards, Holger Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Orphaned packages that were not part of etch
Raphael Geissert wrote: DFSG: * Social Contract 4. Our priorities are our users and free software We will be guided by the needs of our users and the free software community. We will place their interests first in our priorities. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Orphaned packages that were not part of etch
On Tue, Jul 22, 2008 at 05:50:10PM -0500, Raphael Geissert wrote: Holger Levsen wrote: Yes. It's orphaned. If you really care about the package, please adopt it. Thanks. I do care about the package but as a spare user, not as a maintainer; I won't put my name on a package I really won't be maintaining the way it deserves to be maintained. So you think the Debian QA group, consisting of at most a dozen people who do QA uploads, maintaining over 500 packages, will take better care of it? IMHO there are many other packages that are better candidates for not being shipped in lenny than the above mentioned example. Debian is a distribution which is organised in a way that there are packages and package maintainers. *Pause* Sometimes the latter give up, so these packages are orphaned, Orphaned packages which are not picked up by new maintainers IMHO shouldn't be part of a Debian release. Oh really? so we should just say sorry, no more foo for you to the almost 22k users who have imlib on their system? also to the 31635 users of mdbtools, the 3k users of metamail, 34660 of vbetool, 7620 of htdig (which is a strong dependency of khelpcenter), and so son. Yes, if not _one_ of the over 1000 people that maintain Debian packages steps forward and takes responsibility. No one hinders them from searching co maintainers or a group to spread the load. There are several very successful maintainer groups nowadays. I just think that the QA group should not aspire to become the general collaborative maintainance group of Debian. I think the QA group should concentrate on maintaining orphaned packages until they get a new maintainer, not _as the new maintainer_. (And the installed numbers in popcon aren't exactly the ones I would concentrate on. But that is only a side point.) I've nothing against cleaning up the archive; but IMHO packages with no severe bugs, with active upstreams, and with a good number of users shouldn't be the target of a 'hard' (i.e. preventing it from being shipped in stable) cleanup. I really think including them in a stable release and then remove them is the worse solution. Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Orphaned packages that were not part of etch
On Wed, Jul 23, 2008 at 01:21:19AM +0200, Frank Lichtenheld wrote: So you think the Debian QA group, consisting of at most a dozen people who do QA uploads, maintaining over 500 packages, will take better care of it? The commitment for maintaining a package should be greater than will do a better job than the QA group. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Orphaned packages that were not part of etch
On Wed, Jul 23, 2008 at 12:44:12AM +, Clint Adams wrote: On Wed, Jul 23, 2008 at 01:21:19AM +0200, Frank Lichtenheld wrote: So you think the Debian QA group, consisting of at most a dozen people who do QA uploads, maintaining over 500 packages, will take better care of it? The commitment for maintaining a package should be greater than will do a better job than the QA group. That is indeed a true statement, but I'm unsure what point you're trying to make in the context of this discussion. Care to elaborate? Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Orphaned packages that were not part of etch
On Wed, Jul 23, 2008 at 03:37:46AM +0200, Frank Lichtenheld wrote: That is indeed a true statement, but I'm unsure what point you're trying to make in the context of this discussion. Care to elaborate? Sure. The point I am trying to make is that encouraging someone to adopt a package when he cannot make that commitment despite the fact that he cares about it is counterproductive. It is better for that package to stay in the hands of the QA group. Looking at the bazaar package, for example, I see two important differences between the current status and the hypothetical situation if the maintainer field were set to the QA group: 1) If it were orphaned, people would whine about how it is wasting all manner of bits in all manner of files on all manner of media. Since there is a name in the maintainer field, these complaints are magically invalidated. 2) As it stands, a not-insignificant number of people who might want to adopt or NMU it might be reluctant to do so, because it is maintained. If it is orphaned, that hindrance goes away. So from my perspective, it is better off if it were orphaned. Is that not your perspective? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
