Re: question: bugfixes in experimental?
Hi, On Sun, 2005-07-31 at 08:11 +0200, Harald Dunkel wrote: > Shouldn't it be some kind of policy to mark a bug as fixed, > only if the fix is available on the same level as the previous > broken package? There's a semi-policy IMHO, you can tag[1] the bugs instead of closing them, so there's a fixed-in-experimental for example. You can also tag the bug as sarge, etch, whichever contains the bug. Say, if the bug exists in sarge _and_ etch, then you fix the bug for Etch, but instead of closing it, remove the etch tag. Then, fix the bug for Sarge, and say it is important enough that the volatile project accept it, so you close the bugreport. Otherwise you better close it anyway, as you don't have other way to make the fix into Sarge; well, maybe with the upcoming revisions as it happeded with Woody and earlier. Regards, Laszlo/GCS [1] http://www.debian.org/Bugs/Developer#tags -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: question: bugfixes in experimental?
On Sun, 31 Jul 2005, Harald Dunkel wrote: > I've got a problem with marking broken packages as fixed. Fixed generally means that the bug has been fixed in an NMU, IE, by someone not the maintainer; fixed-in-experimental is the tag that usually means that the bug in question has actually been fixed in experimental. The proper solution for this issue is versioning support in the bts which has already been implemented. [See #247066 and friends.] Don Armstrong -- Tell me something interesting about yourself. Lie if you have to. -- hugh macleod http://www.gapingvoid.com/archives/batch20.php http://www.donarmstrong.com http://rzlab.ucr.edu signature.asc Description: Digital signature
question: bugfixes in experimental?
Hi folks, I've got a problem with marking broken packages as fixed. If there is (lets say) a grave functionality bug for package "M" in unstable or testing, then a bugfix in experimental doesn't help me. (I made very bad experiences with experimental, e.g. broken version numbers, currupted apt system, etc., so this stuff won't be installed on my PC.) Shouldn't it be some kind of policy to mark a bug as fixed, only if the fix is available on the same level as the previous broken package? Regards Harri signature.asc Description: OpenPGP digital signature
bugs2ldap running on master (was: bugs2ldap gateway down - wnpp, bts.turmzimmer.net broken)
* Andreas Barth ([EMAIL PROTECTED]) [050728 22:39]: > on request of Ryan Murray I stopped the bugs2ldap-gateway on > bugs.debian.org. I'll move that gateway to some other host as soon as I > have time. At least the following services are broken by that: > - the wnpp bug list > - bts.turmzimmer.net The bts2ldap ldap daemon is running now again on master, port 10101. The bugs are available within the dn dc=current,dc=bugs,dc=debian,dc=org. bts.turmzimmer.net works again with this change. Cheers, Andi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Debian Science mailing list created
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Everyone, This is to let interested people know that the Debian Science mailing list [1] has been created. This list is aimed to encourage discussion about how best to use Debian as an operating system for science research and how to improve Debian to make it more useful to scientists and people working in related fields. Please tell friends and colleagues about the list, and encourage any interested people to use the list to discuss and/or request help for any issues they may encounter in using Debian software for their research. Helen 1. http://lists.debian.org/debian-science/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC7FV53eNc8VZTycQRAhiBAJ0RPPi+cRbvFGXd7Moh4RlRGNtiHwCfVXy6 O+9OV7IIifp6BXmHne3dU5w= =7cfc -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#320637: ITP: lltag -- Massive and magic command-line mp3/ogg file tagger
Brice Goglin wrote: > Package: wnpp > Severity: wishlist > Owner: Brice Goglin <[EMAIL PROTECTED]> > > > * Package name: lltag > Version : 0.6.1-1 > Upstream Author : Brice Goglin <[EMAIL PROTECTED]> > * URL : http://bgoglin.free.fr/lltag/ > * License : GPL > Description : Massive and magic command-line mp3/ogg file tagger I don't think "massive" is the right word here, unless this program is 300MB, in which case I question if it should be put in the archive. Also, "magic" is not a very useful description of the program. > > lltag is a command-line tool to set ID3 tags of mp3 files > and Ogg tags. It may be used to tag multiples files at > once by comparing their filename or pathname with > different formats. > Formats may be either passed on command-line or guess > by the program automagically. Strike the last sentence. Usage information doesn't belong here. Instead, put "by compare their ... against a configurable list of formats." in the sentence above. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFC, problem with g++4
Followups to #320630. --j -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#320637: ITP: lltag -- Massive and magic command-line mp3/ogg file tagger
Package: wnpp Severity: wishlist Owner: Brice Goglin <[EMAIL PROTECTED]> * Package name: lltag Version : 0.6.1-1 Upstream Author : Brice Goglin <[EMAIL PROTECTED]> * URL : http://bgoglin.free.fr/lltag/ * License : GPL Description : Massive and magic command-line mp3/ogg file tagger lltag is a command-line tool to set ID3 tags of mp3 files and Ogg tags. It may be used to tag multiples files at once by comparing their filename or pathname with different formats. Formats may be either passed on command-line or guess by the program automagically. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13-rc4=LoulousMobile Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#320623: ITP: monouml -- computer-aided software engineering (CASE) friendly tool
David Moreno Garza wrote: > Package: wnpp > Severity: wishlist > Owner: David Moreno Garza <[EMAIL PROTECTED]> > > > * Package name: monouml > Version : 0.1a > Upstream Author : Mario Carrión <[EMAIL PROTECTED]>, and others. > * URL : http://monouml.sf.net/ > * License : GPL and LGPL > Description : computer-aided software engineering (CASE) friendly tool > > CASE tool based on the mono Framework. CASE? It looks like you're trying to continue the short description in the extended description (you expanded the acronym there). Don't do that. See Policy 3.4 for why. > . > Designed for allowing to all UNIX/Linux developers faster computer > systems design using a friendly GUI application. This is awkward, to say the least. Consider asking debian-l10n-english@lists.debian.org for help phrasing this. > Not only a diagramming > tool but rather a complete CASE tool based on the OMG standars and > fully compatible with propietary tools. OMG standards? What are those? "The description field needs to make sense to anyone, even people who have no idea about any of the things the package deals with." from Policy 3.4.2. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Packages descriptions review
One more question: Was the question, should short descriptions be capitalized? ever decided? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Packages descriptions review
I've started reviewing the news section, and I'm noticing that I'm running across descriptions which are OK as-is, but could be better. So far, Iv'e put in a comment saying how I think it could be approved, but am clicking "OK". Is that right? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Packages descriptions review
On Sat, Jul 30, 2005 at 04:08:10PM +0200, Clément Stenac wrote: > > how will you handel changes in the description (from upstream, aka package > > maintainer)? > > By comparing all descriptions when we are done. For packages which have > a new descriptions, a manual review/merge will be needed. No, this will not work. We habe 10 and more changes in the description _per_day. Some are very stupid (like http://ddtp.debian.net/ddt.cgi?diff1=16963&diff2=953 ) other more complex (like http://ddtp.debian.net/ddt.cgi?diff1=16966&diff2=2177 ) If you need some weeks for the review of all descriptions (and you will need more time), you can check this all again. You must update unreviewed description daily. Checked reviewed descriptions again and show changes to the reviewer, if the review ist not finished. Gruss Grisu -- Michael Bramer -- http://www.feuerwehr.kreuzau.de/wiki/ PGP: finger [EMAIL PROTECTED] -- Linux Sysadmin -- Use Debian Linux Frage: Stammt der Begriff UNIX aus einem Dialog zwischen einem Deutschen und einem Engländer? - "This is for you nix." -- Andreas (Felix) Kalbitz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SUMMARY: Re: shared library -dev package naming proposal
On 29-Jul-05, 08:50 (CDT), GOMBAS Gabor <[EMAIL PROTECTED]> wrote: > On Thu, Jul 28, 2005 at 08:38:17AM -0500, Steve Greenland wrote: > Exercise: let's say I have an application that uses GSSAPI, and has to > be able to be built statically. Requirements: > > - It should build with Heimdal's libgssapi > - It should build with MIT's libgssapi > - It should build with Globus GSI > > All these cases require a completely different set of dependant static > libraries even though I'm only using the GSSAPI interface. > > With libtool, it's trivial, since all the information you need is > already expressed in the .la files. Unless they're borked, which seems to happen frequently. > Care to explain a method that is > > - better than libtool > - works already (the most important requirement being that Globus must > support it out-of-the-box) > - not Debian-specific (only a minor set of the target machines runs > Debian)? Makefile conditionals. Work on all platforms that support GNU make (i.e. pretty much any of current interest), explicit, trivial to debug and update. Of course, it requires you to actually *understand* what your software dependencies are, but I don't see that as a bad thing. > Well, I have used libtool on a couple of architectures and my opinion is > that using libtool is still way more effective than re-inventing it over > and over again. Yes, it has bugs (for example the AIX support is > notoriously buggy), but they can be fixed just like any other software. But apparently never are. Mostly because libtool is a horrendous, incomprehensilbe shell script. And since AIX is one of our major platforms, I spend *way* too much time fighting with it. Steve -- Steve Greenland The irony is that Bill Gates claims to be making a stable operating system and Linus Torvalds claims to be trying to take over the world. -- seen on the net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
New experimental shadow package 4.0.11.1-1, synced with upstream
The shadow package maintenance team is glad to announce the release of version 4.0.11-1 of the shadow package, in experimental. Shadow is the source package for passwd and login and is part of the base system. Both packages are "Priority: required". This package was highly desynchronized with upstream: up to now we had version 4.0.3 in Debian (including sarge and sid) while upstream was still moving on with many changes. Moreover, the 4.0.3 Debian version had accumulated a huge number of Debian-specific patches. Since May, the shadow package maintenance team has worked both on the current version in Debian (trying to deal with over 120 bug reports, some of them being over 5 years old), and the new version. While dealing with many issues in 4.0.3, the team also did its best to resynchronise with upstream. The huge number of Debian patches made this work very tedious and long, which explains the 3 months delay for a new version in Debian. However, thanks mostly to the work of Nicolas François, helped by Alexander Gattin, as well as the upstream author's (Tomasz Klockzko's) collaboration, we have managed to prepare a new release which uses the latest upstream code, namely version 4.0.11.1. We did our best to keep all features from 4.0.3 available with the goal of making the transition as smooth as possible. Of course, given the critical importance of some utilities provided by login and passwd (mostly su), we have decided to upload the new version in experimental. Please test it as much as possible by installing the new passwd and login packages. Package maintainers who use "su" in their maintainer scripts should test them with the new su as much as possible. We also recommend all package maintainers using useradd to give these packages a try and check them (DO NOT confuse useradd, which is a "low level" utility provided by passwd, and adduser which is a Debian specific utility, provided in a separate package). Hope you'll enjoy the new beast, The shadow package maintenance team, starring (ALPHABETICALLY) Nicolas François INTERNATIONALLY SUPER STARRING (ALPHABETICALLY) Alexander Gattin EXTRA-TERRESTRIALLY CO-SUPER (ALSO ALPHABETICALLY) STARRING Tomasz Klockzko SUPER-INTER- GALACTICALLY (A BIT ALPHABETICALLY) CO MEGA STARRING Christian Perrier SUPRA COSMICALLY INTER-UNIVERSALLY ULTRA ALPHABETICALLY HYPER-STARRING Martin Quinson AND Christine Spang AS THE WOMAN WITH THE BIGGEST CREDIT -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#320623: ITP: monouml -- computer-aided software engineering (CASE) friendly tool
Package: wnpp Severity: wishlist Owner: David Moreno Garza <[EMAIL PROTECTED]> * Package name: monouml Version : 0.1a Upstream Author : Mario Carrión <[EMAIL PROTECTED]>, and others. * URL : http://monouml.sf.net/ * License : GPL and LGPL Description : computer-aided software engineering (CASE) friendly tool CASE tool based on the mono Framework. . Designed for allowing to all UNIX/Linux developers faster computer systems design using a friendly GUI application. Not only a diagramming tool but rather a complete CASE tool based on the OMG standars and fully compatible with propietary tools. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-1-386 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Re: Public service announcement about Policy 10.4
Marco d'Itri wrote: > On Jul 29, Steve Langasek <[EMAIL PROTECTED]> wrote: > > > Well, please note that posh is not the only shell that lacks support for > > local. IIRC, it also breaks down under one or more of dash and busybox sh. > dash supports local, or at least supports it in the way it's used in > all the packages I maintain and use. AFAIR busybox sh doesn't (at least in the version used for the d-i udeb). Thiemo signature.asc Description: Digital signature
Re: Public service announcement about Policy 10.4
On Jul 29, Steve Langasek <[EMAIL PROTECTED]> wrote: > Well, please note that posh is not the only shell that lacks support for > local. IIRC, it also breaks down under one or more of dash and busybox sh. dash supports local, or at least supports it in the way it's used in all the packages I maintain and use. -- ciao, Marco signature.asc Description: Digital signature
Re: Public service announcement about Policy 10.4
On Jul 29, "Brian M. Carlson" <[EMAIL PROTECTED]> wrote: > I have found no less than four packages which break with /bin/posh > as /bin/sh, including one that refuses to be removed because of its > brokenness. I am expecting many more. Yes, like most of my packages. posh does not provide any benefit over dash, so I have no plan to cripple my scripts to support posh and I urge other maintainers to do the same. Hint: [EMAIL PROTECTED]:~$size /bin/bash /bin/dash /bin/posh textdata bss dec hex filename 643347 22456 19004 684807 a7307 /bin/bash 79407 896 10236 90539 161ab /bin/dash 978904524 0 102414 1900e /bin/posh [EMAIL PROTECTED]:~$ (Feel free to add more meaningful benchmarks.) -- ciao, Marco signature.asc Description: Digital signature
A quick favor...
Hi, I took a look at your site a couple of hours ago... and I want to tell you that I'd really love to trade links with you. I think your site has some really good stuff related to my site's topic of Packaging and would be a great resource for my visitors. In fact, I went ahead and added your site to my Packaging Resource Directory at http://www.packaging-hq.com under http://www.packaging-hq.com/ Is that OK with you? Can I ask a favor? Will you give me a link back on your site? I'd really appreciate you returning the favor. I have created a list of all the sites i've visited but if you have recieved this email in error then please let me know and i will remove you from my list and apologies for any inconvenience this has caused. Thanks and feel free to drop me an email if you'd like to chat more about this. Best wishes, Andy [EMAIL PROTECTED] P.S. When you do link back, there's some suggested code to use at http://www.packaging-hq.com/links/addlink.html//
Re: Packages descriptions review
Hello, > how will you handel changes in the description (from upstream, aka package > maintainer)? By comparing all descriptions when we are done. For packages which have a new descriptions, a manual review/merge will be needed. Regards, -- Clément Stenac -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Packages descriptions review
On Fri, Jul 29, 2005 at 11:32:18PM +0200, Clément Stenac wrote: > > Someone suggested an announcement should be sent to > > > d-d-a. What do you think ? > > > > Yes, go to it and find some reviewer. > > Will do... > > > Maybe you should add a 'get a random Description' link on your Page... > > I'm not sure it would be very good, because it's better to review > related packages together. It's however true that it could probably make > the whole stuff more attractive. how will you handel changes in the description (from upstream, aka package maintainer)? some changed description from this night: changed description from dvorak7min (dvorak7min) changed description from libnetclient-ocaml-dev (netclient) changed description from libocamlnet-ocaml (ocamlnet) changed description from libocamlnet-ocaml-dev (ocamlnet) Gruss Grisu -- Michael Bramer - a Debian Linux Developer http://www.debsupport.de PGP: finger [EMAIL PROTECTED] -- Linux Sysadmin -- Use Debian Linux »A train station is a station where trains stops. But what are workstations?« signature.asc Description: Digital signature
Re: congratulations to the X team!!
On 7/15/05, Miles Bader <[EMAIL PROTECTED]> wrote: > FWIW, I previously had xorg from Ubuntu installed, and upgrading from > that to Debian's xorg _didn't_ go smoothly: the file "/etc/X11/Xsession" > was created by two packages, x11-common [debian], and xorg-common > [ubuntu], and in upgrading tried to install x11-common before removing > xorg-common. > > I ended up downgrading to xfree86 from testing, and then upgraded back up > to xorg from unstable (and all that went smoothly). > > [I know none of that is supported, but just FYI... :-] > > -Miles > -- > ((lambda (x) (list x x)) (lambda (x) (list x x))) > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] Hello, I was also using ubuntu's xorg on Sid, but unlike you I am still unable to install xserver-xorg and xserver-common or even xserver-xfree86 from testing. This means I can't run GNOME. Can you help? malebo...
Re: ..last mirror update was a week ago, what's going on???
On 7/29/05, Steve Kemp <[EMAIL PROTECTED]> wrote: > On Fri, Jul 29, 2005 at 02:31:01AM +0200, Arnt Karlsen wrote: > > > ..last mirror update was a week ago, what's going on??? > > > ..and, yeah, gg:"Debian mirror update" "21-Jul-2005" etc > > finds _lotsa_ noise. > > > ..whether this mirror update lapse is planned or not, a wee > > mention here on d-m and and on d-announce would IMHO > > be warranted. > > It was announced. Two machines, including ftp-master, were > shut down so they could be physically moved. > > They took longer than the couple of days announced, but this > was the source of the delay. > > Original announcement: > >http://lists.debian.org/debian-devel-announce/2005/07/msg00013.html > > Followup when service was restored: > >http://lists.debian.org/debian-devel-announce/2005/07/msg00018.html So when will the unstable -> testing 'migrations' start again?
Re: SUMMARY: Re: shared library -dev package naming proposal
On Thu, Jul 28, 2005 at 02:18:29PM -0400, Jay Berkenbilt wrote: > > FWIW, detecting a fixed libtool would be rather difficult, since it's the > > libtool used by the depending application which does the recursion and > > therefore needs to be fixed. > I was thinking we'd be able to tell from the .la file what we needed > to do. If a new libtool still generated a .la file, perhaps it could > put some kind of version indicator or something similar. Yeah, that still doesn't do any good (and yes, libtool would still need to generate .la files, or else it's no longer serving its purpose), because upstream isn't going to stand for breaking backwards compatibility, and that's the only way you could have any control at all over the version of libtool that an application was trying to use when building -- and that's not really more control than you also have just by dropping the -dev dependencies and letting the applications fend for themselves. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: RFC, problem with g++4
* Goswin von Brederlow:
> The proper use of this construct seems to be:
>
> template
> struct Foo {
> static const unsigned N = T::N;
> char bar[N];
> };
>
> struct Bla {
> static const unsigned N;
> };
>
> const unsigned Bla::N = 10;
>
> int main() {
> Foo foo;
> }
This program is ill-formed.
Bla::N is not an integral constant expression (5.19/1) and thus does
not make Foo::N an integral constant expression, either (9.4.2/4).
I will file a couple of bug reports. Some of these things might
actually undocumented G++ extensions.
> Correct me if I'm wrong but doesn't that
>
> 1.) Only move the const declaration from the template into the
> template parameter?
>
> 2.) Cause the template to have static member N in every file that uses
> the template and for every type?
>
> 3.) Cause Bla to have a static member N in every file that uses
> the template and for every type?
I don't understand these questions.
If the definition of Bla::N appears in multiple translation units, the
one definition rule is violated and the program is ill-formed.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
