libcurl3-dev's reverse Build-Depends
Since libcurl3-dev was removed from unstable, suddenly a lot of packages are now FTBFS because their Build-Depends on libcurl3-dev cannot be satisfied. Would you consider providing a transition libcurl3-dev package for now, or making libcurl3-openssl-dev provide libcurl3-dev? -- Unless it's your intention to force all maintainers to choose explicitly between the openssl and gnutls versions immediately, in which case there should be a mass bug filing. -- Daniel Schepler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: adept for Debian?
On Tue, Oct 18, 2005 at 02:26:39PM +0200, Christoph Haas wrote: > A coworker just showed me his Ubuntu/Breezy installation featuring their > package management tool "adept" [1]. It looks pretty nifty. Are there plans > already to offer the same package in Debian? It's not listed in the wnpp > yet. I'm just curious if anyone has talked to Ubuntu maintainers about > making it available in Debian. It'll come: it can't currently go in because it needs a newer version of konsole. This means it can't be uploaded until kde 3.5 is in. adept is a package manager for KDE developed by Peter Rockai on top of the libapt-front library[1]. It supports debtags natively, it's the first application based on libapt-front, and since I'm involved in both debtags and libapt-front, I really want it in as well :) Ciao, Enrico [1] apt-get install libapt-front-dev http://libapt-front.alioth.debian.org -- GPG key: 1024D/797EBFAB 2000-12-05 Enrico Zini <[EMAIL PROTECTED]> signature.asc Description: Digital signature
Re: libcurl3-dev's reverse Build-Depends
On Wed, Oct 19, 2005 at 09:24:42AM +0200, Daniel Schepler wrote: > Since libcurl3-dev was removed from unstable, suddenly a lot of packages are > now FTBFS because their Build-Depends on libcurl3-dev cannot be satisfied. > Would you consider providing a transition libcurl3-dev package for now, or > making libcurl3-openssl-dev provide libcurl3-dev? -- Unless it's your > intention to force all maintainers to choose explicitly between the openssl > and gnutls versions immediately, in which case there should be a mass bug > filing. i'd like to force rdepends packagers to choose the right libcurl3-*-dev for them. anyway i agree with you about the wrong time to enforce this. i'll re-introduce libcurl3-dev as a transition package depending on libcurl3-openssl-dev. anyway i don't consider this urgent and it will be solved with the next upload, which is not too far away. regards domenico -[ Domenico Andreoli, aka cavok --[ http://people.debian.org/~cavok/gpgkey.asc ---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: a few tips on proper use of version tracking in the Debian BTS
> "Joey" == Joey Hess <[EMAIL PROTECTED]> writes: Joey> 2. If you forget a changelog entry, or find out about a Joey> fix (such as a fix for a security hole) after your upload, Joey> send mail to [EMAIL PROTECTED] as before, but Joey> include a "Version:" pseudo-header[2]. What is the preferred way of closing bugs that are not bugs (e.g. mistake by the submitter)? -- Brian May <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tiffani now on ftp.debian.org / people.d.o/~aba/ turned off
Hi, as some of you already know, Anthony turned on tiffani on ftp-master. As the tiffani on people is now longer needed (and also broken by this change), I disabled the cronjob. Please just use your normal debian mirror for support of partial lists. Thanks for all your help, support, debugging etc. Cheers, Andi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: a few tips on proper use of version tracking in the Debian BTS
On Wed, Oct 19, 2005 at 05:56:47PM +1000, Brian May wrote: > > "Joey" == Joey Hess <[EMAIL PROTECTED]> writes: > Joey> 2. If you forget a changelog entry, or find out about a > Joey> fix (such as a fix for a security hole) after your upload, > Joey> send mail to [EMAIL PROTECTED] as before, but > Joey> include a "Version:" pseudo-header[2]. > What is the preferred way of closing bugs that are not bugs > (e.g. mistake by the submitter)? Closing without a version header retains the traditional semantics of marking the bug closed in all versions. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Re: adept for Debian?
Enrico Zini <[EMAIL PROTECTED]> writes: > adept is a package manager for KDE developed by Peter Rockai on top of > the libapt-front library[1]. It supports debtags natively, it's the > first application based on libapt-front, and since I'm involved in both > debtags and libapt-front, I really want it in as well :) So do any of these things support aptitude's "auto" mechanism (which allows dependencies to be automatically deleted when nothing requires them)? -miles -- Next to fried food, the South has suffered most from oratory. -- Walter Hines Page -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: a few tips on proper use of version tracking in the Debian BTS
On Wed, Oct 19, 2005 at 01:44:38AM -0700, Steve Langasek wrote: > Closing without a version header retains the traditional semantics of > marking the bug closed in all versions. Two questions: 1) once a bug as been closed - erroneously I would say - mailing [EMAIL PROTECTED] without the "Version:" pseudo header, is there a way to push the version information to the bts? 2) AFAICT the bts parses changelog to understand in which version a given bug has been closed. Assume that the version of package p in unstable is x and that I upload version x+2, with two entries in the changelog one for x+1 and for for x+2. Entry x+1 has a closes:#nnn entry. Is this enough for the bts or do I need to mail it as well? Many TIA, Cheers. -- Stefano Zacchiroli -*- Computer Science PhD student @ Uny Bologna, Italy [EMAIL PROTECTED],debian.org,bononia.it} -%- http://www.bononia.it/zack/ If there's any real truth it's that the entire multidimensional infinity of the Universe is almost certainly being run by a bunch of maniacs. -!- signature.asc Description: Digital signature
Re: libcurl3-dev's reverse Build-Depends
On Wed, Oct 19, 2005 at 10:03:14AM +0200, Domenico Andreoli wrote: > On Wed, Oct 19, 2005 at 09:24:42AM +0200, Daniel Schepler wrote: > > Since libcurl3-dev was removed from unstable, suddenly a lot of packages > > are > > now FTBFS because their Build-Depends on libcurl3-dev cannot be satisfied. > > Would you consider providing a transition libcurl3-dev package for now, or > > making libcurl3-openssl-dev provide libcurl3-dev? -- Unless it's your > > intention to force all maintainers to choose explicitly between the openssl > > and gnutls versions immediately, in which case there should be a mass bug > > filing. > i'd like to force rdepends packagers to choose the right libcurl3-*-dev > for them. anyway i agree with you about the wrong time to enforce this. > i'll re-introduce libcurl3-dev as a transition package depending on > libcurl3-openssl-dev. anyway i don't consider this urgent and it will > be solved with the next upload, which is not too far away. This kind of uncoordinated change is in fact *very* disruptive when we're in the middle of a pile of transitions for testing; you've left all packages that build-depend on libcurl3-dev in an unbuildable state in unstable (38 of them, it appears), and some of these currently *need* to be built in order to get the KDE transition through without breaking packages in the process. Specifically, php4 and php5 are tied into the mess, and are missing builds on various architectures which can't be done now without a libcurl3-dev fix, or a sourceful upload of php4/5 that requires a rebuild on all archs. So depending on when you think you'll upload curl again, I need to decide whether it's quicker to do a new sourceful upload of php4 and php5, or wait for this transition package. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Re: Finding out in postinst whether some other package is configured
Frank Küster <[EMAIL PROTECTED]> writes: > Goswin von Brederlow <[EMAIL PROTECTED]> wrote: > >> Frank Küster <[EMAIL PROTECTED]> writes: >> >>> Goswin von Brederlow <[EMAIL PROTECTED]> wrote: >>> Also how would a package inset such a Post-Invoke line into the conffig? Modifying the conffile would be a policy violation. >>> >>> The package that provides the hook to run provides the config entry; the >>> packages that need to run the hook touch a file in /var/ or >>> append a line to such a file. >> >> That means that every such case has to reinvent the wheel. >> >> Also you still haven't gotten the hook into the Post-Invoke apt >> option. > > I don't remember how zope does it, but apparently it has found a way. > Probably it just drops a file into apt/conf.d, not caring about other > files specifying a Post-Invoke option (which works because there are > none...) Yes, that is usualy done. But it won't work the first time around. Only subsequent apt calls would work. And dpkg -i foo.deb also ignores those. So not realy an option. > Regards, Frank > -- > Frank Küster > Inst. f. Biochemie der Univ. Zürich > Debian Developer MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: libcurl3-dev's reverse Build-Depends
On Wed, Oct 19, 2005 at 03:24:15AM -0700, Steve Langasek wrote: > On Wed, Oct 19, 2005 at 10:03:14AM +0200, Domenico Andreoli wrote: > > On Wed, Oct 19, 2005 at 09:24:42AM +0200, Daniel Schepler wrote: > > > Since libcurl3-dev was removed from unstable, suddenly a lot of packages > > > are > > > now FTBFS because their Build-Depends on libcurl3-dev cannot be > > > satisfied. > > > Would you consider providing a transition libcurl3-dev package for now, > > > or > > > making libcurl3-openssl-dev provide libcurl3-dev? -- Unless it's your > > > intention to force all maintainers to choose explicitly between the > > > openssl > > > and gnutls versions immediately, in which case there should be a mass bug > > > filing. > > > i'd like to force rdepends packagers to choose the right libcurl3-*-dev > > for them. anyway i agree with you about the wrong time to enforce this. > > > i'll re-introduce libcurl3-dev as a transition package depending on > > libcurl3-openssl-dev. anyway i don't consider this urgent and it will > > be solved with the next upload, which is not too far away. > > This kind of uncoordinated change is in fact *very* disruptive when > we're in the middle of a pile of transitions for testing; you've left all > packages that build-depend on libcurl3-dev in an unbuildable state in > unstable (38 of them, it appears), and some of these currently *need* to be > built in order to get the KDE transition through without breaking packages > in the process. Specifically, php4 and php5 are tied into the mess, and are > missing builds on various architectures which can't be done now without a > libcurl3-dev fix, or a sourceful upload of php4/5 that requires a rebuild on > all archs. > > So depending on when you think you'll upload curl again, I need to decide > whether it's quicker to do a new sourceful upload of php4 and php5, or wait > for this transition package. this is enough for me to consider such upload urgent. i'm building and uploading within minutes. thank you domenico -[ Domenico Andreoli, aka cavok --[ http://people.debian.org/~cavok/gpgkey.asc ---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: a few tips on proper use of version tracking in the Debian BTS
On Wed, Oct 19, 2005 at 11:06:14 +0200, Stefano Zacchiroli wrote: > On Wed, Oct 19, 2005 at 01:44:38AM -0700, Steve Langasek wrote: > > Closing without a version header retains the traditional semantics of > > marking the bug closed in all versions. > > Two questions: > 1) once a bug as been closed - erroneously I would say - mailing >[EMAIL PROTECTED] without the "Version:" pseudo header, is >there a way to push the version information to the bts? If the bug is still open in some version of your package, I guess "found nnn version" would give this information to the bts. You could probably also use "reopen nnn" together with "close nnn version" if the bug is only closed in that version of your package. > 2) AFAICT the bts parses changelog to understand in which version a >given bug has been closed. Assume that the version of package p in >unstable is x and that I upload version x+2, with two entries in the >changelog one for x+1 and for for x+2. Entry x+1 has a closes:#nnn >entry. Is this enough for the bts or do I need to mail it as well? > The bugs closed in your upload are determined by the changes file, so you can use the -vversion switch with dpkg-buildpackage or dpkg-genchanges to use changelog information for versions version+1 and version+2. Cheers, Julien Cristau -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sid is/was crazy
On Wed, 19 Oct 2005, Bernd Eckenfels wrote: > In article <[EMAIL PROTECTED]> you wrote: > > /var/cache/apt/archives/partial/yelp_2.10.0-3_i386.deb - open (30 > > Read-only file system) [IP: 204.152.191.7 80] > > debian:~# screen > > mkfifo /var/run/screen/S-root/5922.pts-0.debian failed > > your /var is mounted read only mode because your kernel had an hardware IO > error. > > >Additional sense: Scsi parity error > > this could be a failing device electronics, broken wiring, thermal or power > problems - less likely is a failing drive but also possible. > > Backup your data as long as you can. And, considering the type of problem you had and that you were unable to figure it out immediately, I'd strongly suggest that you switch to Etch or Sarge, instead of Sid. You will have a happier Debian experience, then. Eventually one of the real badass sid breakages would hit you, and cause you quite a lot of grief. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#334741: ITP: aspell-ku -- Kurdish aspell dictionary
Package: wnpp Severity: wishlist Owner: Christoph Berg <[EMAIL PROTECTED]> * Package name: aspell-ku Version : 0.20 Upstream Author : Erdal Ronahi <[EMAIL PROTECTED]> and others * URL : https://sourceforge.net/projects/myspellkurdish/ * License : GPL Description : Kurdish aspell dictionary Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: New versions of teTeX and libkpathsea: please test your packages
Re: Frank Küster in <[EMAIL PROTECTED]>
> teTeX-3.0 has been in experimental for a while and will be uploaded to
> unstable as soon as library transitions are allowed again[1].
tetex-bin and -base 3.0-9 are now in unstable, for those wanting to
rebuild their packages.
> - your package Build-Depends on tetex-{bin,base, or extra}:
> - your package Depends on teTeX:
> - your package provides additional fonts for use with TeX
> - your package depends on libkpathsea:
Christoph
--
[EMAIL PROTECTED] | http://www.df7cb.de/
signature.asc
Description: Digital signature
Do not use libkpathsea4! (was: New versions of teTeX and libkpathsea: please test your packages)
Christoph Berg <[EMAIL PROTECTED]> wrote: > Re: Frank Küster in <[EMAIL PROTECTED]> >> teTeX-3.0 has been in experimental for a while and will be uploaded to >> unstable as soon as library transitions are allowed again[1]. > > tetex-bin and -base 3.0-9 are now in unstable, for those wanting to > rebuild their packages. But, please, please follow the mail that you got if you are the maintainer of a package that depends on libkpathsea: Do not upload packages linked again the new libkpathsea4! The release team still does not allow library transitions, and while this is the case, tetex-bin_3.0-* should be the only package that depends on soversion 4 of that library! Please, please, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
Re: adept for Debian?
"Miles Bader" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] Enrico Zini <[EMAIL PROTECTED]> writes: adept is a package manager for KDE developed by Peter Rockai on top of the libapt-front library[1]. It supports debtags natively, it's the first application based on libapt-front, and since I'm involved in both debtags and libapt-front, I really want it in as well :) So do any of these things support aptitude's "auto" mechanism (which allows dependencies to be automatically deleted when nothing requires them)? That is the main reason why i use aptitude, and insist that all programs use aptitude. If even one program tries to install without going through aptitude i loose that information. I personally feel that auto should be pudhed up to apt (the library). Thus all front ends would generate the data, although they can ignore the data, if so desired, and not do the automatic removal. Later when aptitude is run it will clean up. The other two reasons that i use aptitude is the better dependency handleling (including reccomends) and the interface. The better depenedency handling should be moved up to apt (the library). The logic for handling reccomends should be optional, allowing a front-end (such as the minimalisic apt-get) to ignore reccomends. The result of moving these things up means that the various fron ends will avoid stepping on each others toes. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
OT: Please vote for EU recognition of those who oppose software patents
I know it's off-topic for the list but I feel it is sufficiently important that it deserves the widest possible publication. I'm not sure if the list has already received this notification. The vote *is* open to non-EU residents. Feel free to adapt any part of it if you'd like to send it on to other user group mailing lists etc. --- Dear Supporters of NoSoftwarePatents.com, On 6 July 2005, the European Parliament rejected a proposal to legalise software patents in Europe. However, our fight continues. There is now a public Internet poll in which you can vote against software patents. Everyone can participate in the vote of the "Europeans of the Year". That is the most important award in the European Union, and Florian Mueller, the founder of the NoSoftwarePatents.com campaign, has a realistic chance to win. If Florian wins, then the big news in the media will be: "Opponent of software patents is elected as European of the Year". The importance of our cause would be clearer than ever before, to politicians, the press, and the public. Florian would also have the chance to make a speech against software patents in front of some of Europe's most powerful politicians. Please click here to read more about this opportunity to vote (on the Internet) against software patents: http://www.nosoftwarepatents.com/en/m/ev50/index.html Thank you very much in advance for your support. This is really a unique opportunity for you and your friends to show to politicians that software patents are a major problem to people all over the world. Everyone may participate in the vote, including non-Europeans, and if we win, then the victory will belong to all of us together. Best regards, The NoSoftwarePatents.com Team --- My two-cents: The vote works like this: 1. You must vote once for each of the ten categories, not just Florian. The link above at nosoftwarepatents.com links on to a page that explains who on the list of nominees did the most to support the fight against software patents. There are some categories where the vote is entirely neutral - make your own mind up on those. (I would personally recommend against voting for Tony Blair - no matter what your political persuasion - as the UK government was firmly behind the UKPO. If Lord Sainsbury was on the list, maybe I would change that but although he listens, it is still unclear how much he acts on the reports.) 2. Enter your real name and a genuine email address at the end. You will receive a confirmation email that activates your vote by providing a link. This is an attempt to block repeat voting - not sure how it works for those of us with multiple email addresses! However, do NOT deliberately attempt to skew the vote - your votes may be disqualified if abuse is found. 3. This is a real poll with real results - it's not the usual Slashdot type poll that has no effect beyond the stats. There are real awards that will get the attention of the worldwide media. 4. Florian was and is the most persistent anti-software-patent voice in Brussels, his support of FFII, his endless campaigning and unflinching support for the fight against software patents does deserve wider recognition. From the nosoftwarepatents.com site: This is a campaign for a cause, not for a person. A respected jury has nominated Florian Mueller as a figurehead of our movement, and he has made it clear that we will all be winners if he becomes elected. By voting for Florian in a public Internet poll, you and your friends - no matter where in the world you live - can send out a strong signal that politicians must act against software patents. If we succeed with this campaign, the issue of software patents will be elevated to the level of awareness that other major political topics enjoy. Our opponents try to portray it as a concern of geeks. With the power of the Internet, we can prove them wrong once again. We face strong competition from such prominent people as Bono (U2), Bob Geldof, J.K. Rowling and 46 other candidates. However, we have a realistic chance to win because a public Internet poll should be a home game for us. Imagine what it will mean if our candidate receives a highly prestigious award that Microsoft has co-sponsored, at a gala event that is moderated by a pro-patent lobbyist (Pat Cox), and if he can then make an acceptance speech in front of many EU commissioners and the heads of governments of several EU member countries. Europe's political leaders would have to listen to us like never before, and the news would go around the world. Florian has promised that he will give the prize money to the FFII if he wins. -- Neil Williams = http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/ pgpfoge2jNwFI.pgp Description: PGP signature
Bug#334779: ITP: pngnq -- tool for optimizing PNG (Portable Network Graphics) images
Package: wnpp Severity: wishlist Owner: "Nelson A. de Oliveira" <[EMAIL PROTECTED]> * Package name: pngnq Version : 0.3 Upstream Author : Stuart Coyle <[EMAIL PROTECTED]> * URL : http://www.cybertherial.com/pngnq/pngnq.html * License : BSD like(?) Description : tool for optimizing PNG (Portable Network Graphics) images Pngnq is a tool for quantizing 32-bit RGBA PNG images to 8-bit RGBA pallete PNG. It's is an adaptation by Stuart Coyle of Greg Roelf's pnqquant. While pngquant uses a median cut algorithm, Pngnq uses Anthony Dekker's neuquant algorithm (http://members.ozemail.com.au/~dekker/NEUQUANT.HTML), generally resulting in better looking results than pngquant. . Optimizers (like pngcrush and optipng) optimize the compression, usually losslessly. pngnq quantizes colors down to 256 (or fewer) distinct RGBA combinations, which is quite lossy. Optimized PNGs are usually two to four times smaller than the 32-bit versions. . Homepage: http://www.cybertherial.com/pngnq/pngnq.html -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.13-rc5-mm1 Locale: LANG=pt_BR, LC_CTYPE=pt_BR (charmap=ISO-8859-1) (ignored: LC_ALL set to pt_BR) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#334785: ITP: mpich2 -- An implementation of the MPI2 message-passing interface
Package: wnpp Severity: wishlist Owner: Zach Lowry <[EMAIL PROTECTED]> * Package name: mpich2 Version : 1.0.2p1 Upstream Author : The MPICH2 team * URL : http://www.example.org/ * License : (GPL, LGPL, BSD, MIT/X, etc.) Description : An implementation of the MPI2 message-passing interface This is an implementation of the Message-Passing Interface (MPI). The goals of MPICH2 are to provide an MPI implementation for important platforms, including clusters, SMPs, and massively parallel processors. It also provides a vehicle for MPI implementation research and for developing new and better parallel programming environments. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.8-2-686-smp Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: NMU policies for etch
On Tue, 18 Oct 2005, Frank Küster wrote: > > - send mail to the bug with a full diff *before* uploading your package to > > incoming; two minutes before, two hours before, two days before, it > > doesn't matter > > And make sure that the mail has actually left your system... (real life > experience). Actually, make certain it appears in the bug. Spohr has processisng delays, in addition to whatever other mail systemms it travels thru.
Bug#334809: ITP: psemu-drive-cdrmooby -- ISO plugin for PSX emulators
Package: wnpp Owner: Ryan Schultz <[EMAIL PROTECTED]> Severity: wishlist * Package name: ISO plugin for PSX emulators Version : 2.8 Upstream Author : Mooby * URL : http://mooby.psxfanatics.com * License : GPL Description : ISO plugin for PSX emulators This plugin provides ISO support for PSX emulators. With it, you can rip a PlayStation CD directly to your hard drive or play a CDROM image from disk. Images can be automatically decompressed or compressed as needed. The version I am packaging has been modified to remove non-DFSG compliant RAR code. This plugin is for PCSX, see bug #137355 for more on that. There are a number of other psemu plugins. Please ignore invalid ITP numbers in the changelogs for now, if any are reported. I'll upload fixed versions shortly after I get all of the ITPs filed. Potential sponsors: lintian/pbuilder clean packages available from: deb http://rschultz.ath.cx/debian unstable/i386/ deb-src http://rschultz.ath.cx/debian unstable/source/ -- Ryan Schultz "Pleased to meet you, e^x," says the Differential Operator. "I'm d/dt." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
gcc 4.1 with stack smashing protection in etch?
Hi, now that Steve Langasek has published July 30th as the toolchain freeze, do you already know if you will include gcc 4.1 instead of 4.0 as the standard gcc in etch? If yes, etch could profit from the ProPolice-like stack smashing protection in gcc 4.1. If it will be 4.1, will every debian package automatically be compiled with the SSP in etch? Or is a certain compile-flag needed to be activated, which won't be the default in etch? It seems that Redhat will release RHEL 5 in the end of 2006 with a gcc 4.1 compiler. cheers, mike. ___ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
uploading to stable and unstable at once
Hello dear developers, to fix a critical bug on scsitools package (0.8-1), I'm willing to upload a new revision of my package to stable but it was rejected by dinstall merely because I targeted it only to stable but no newer release is available in testing/unstable. Although I'm working on a new release of scsitools for unstable to fix more bugs, I'd rather want to upload a simple fix to address the critical bug first. This is why I tried to upload to stable, with no success. So is there a chance to get it accepted if I target it both to stable and unstable at once ? Is autobuilder so nice to build all architectures under a stable chroot then ? Or do I need to upload to unstable first (0.8-2 for instance) then try again an upload targeted only to stable (named 0.8-1sarge for example) ? Here is the message sent back to me by dinstall: Mapping stable to proposed-updates. Rejected: scsitools_0.8-1sarge_i386.deb: old version (0.8-1) in unstable <= new version (0.8-1sarge) targeted at proposed-updates. Rejected: scsitools_0.8-1sarge_i386.deb: old version (0.8-1) in testing <= new version (0.8-1sarge) targeted at proposed-updates. Rejected: scsitools_0.8-1sarge.dsc: old version (0.8-1) in unstable <= new version (0.8-1sarge) targeted at proposed-updates. Rejected: scsitools_0.8-1sarge.dsc: old version (0.8-1) in testing <= new version (0.8-1sarge) targeted at proposed-updates. Regards. E.D. PS: please cc: me as I'm not reading debian-devel every days. -- Eric Delaunay | Il vaut mieux pomper même s'il ne se passe [EMAIL PROTECTED] | rien que risquer qu'il se passe quelque chose | de pire en ne pompant pas. Devise Shadok. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: NMU policies for etch
On Tue, Oct 18, 2005 at 10:28:55AM +0200, Frank Küster wrote: > Steve Langasek <[EMAIL PROTECTED]> wrote: > > - don't NMU for feature requests (i.e., wishlist bugs) without the > > maintainer's prior approval > Shouldn't NMU's without the maintainers approval be restricted to RC and > maybe important bugs? Isn't that my question? :) -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Re: [Fwd: major problem with gnome-games dependency]
Hi, Kevin: El Jueves, 13 Octubre 2005 09:03, Kevin Mark escribió: [...] > Hi Thijs and fellow DDs, > something just sprang into my brain as you mentioned the 'm$ office > thingy'. gnome is a meta-package and someone wondered how he could > install 'his' gnome. here is a scenerio: > > apt-get install gnome > (gnome installs as usuall, but creates a configuration file--blank at > first?) > > dpkg-reconfigure gnome > (this presents a debconf-like screen that displays the basic gnome > packages and also displays optional gnome packages with select/unselect > boxes. after the optional packages are selected, the choices are noted > in a configuration file, and the unselected apps would than be > a)marked for removal in the status file so that the next upgrade cycle > would remove them > or > b)removed by 'apt-get remove' > not sure if I need "a AND b" or "a OR b". > > apt-get install gnome > (now the apt front-end would read the meta-package configuration file to > determine what to install/upgrade. Thus you get to have 'your' gnome and > upgradeing gnome would only install what you want thus saving time and > effort) Yeah! It remmembers quite a lot the localepurge package behaviour. When you install it it asks you if you want to be informed about new locales and when new locales do appear a menu gives you the chance to check in which man/info/etc pages do you want installed in your system. Something like this could go for metapackages: apt-get install gnome (...) [debconf menu] Gnome is a metapackage made up of these bunch of packages. Choose the ones your really want (with all packages starting as checked; maybe submenus for different categories and these submenus depending on the debconf "chatting" level chosen -critical, high, low...). Then the first poster would check-out all gnome-games, then [ok] Do you want to be informed about new [Gnome] packages added [Yes/no]. This way, when on next release new Gnome is made out of new packages, he will have again the choice to tell which ones he wants. -- SALUD, Jesús
Re: uploading to stable and unstable at once
Eric <[EMAIL PROTECTED]> writes: > Mapping stable to proposed-updates. > Rejected: scsitools_0.8-1sarge_i386.deb: old version (0.8-1) in unstable <= > new version (0.8-1sarge) targeted at proposed-updates. > Rejected: scsitools_0.8-1sarge_i386.deb: old version (0.8-1) in testing <= > new version (0.8-1sarge) targeted at proposed-updates. > Rejected: scsitools_0.8-1sarge.dsc: old version (0.8-1) in unstable <= new > version (0.8-1sarge) targeted at proposed-updates. > Rejected: scsitools_0.8-1sarge.dsc: old version (0.8-1) in testing <= new > version (0.8-1sarge) targeted at proposed-updates. I think you'll need to wait until you finish your 'unstable' package and then upload the 'stable' one later. Or then, upload this too to unstable with -2 and then prepare a -3 with your other fixes later. Looks faster and better to me. -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://www.freedom.ind.br/otavio - "Microsoft gives you Windows ... Linux gives you the whole house." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Unidentified subject!
£¬ÄúºÃ£¡ -- ŽËÖ£¬ ŸŽÀñ£¡ zhouke mailto:[EMAIL PROTECTED]
Re: NMU policies for etch
On Wed, 19 Oct 2005, Steve Langasek wrote: > On Tue, Oct 18, 2005 at 10:28:55AM +0200, Frank Küster wrote: > > Steve Langasek <[EMAIL PROTECTED]> wrote: > > > > - don't NMU for feature requests (i.e., wishlist bugs) without the > > > maintainer's prior approval > > > Shouldn't NMU's without the maintainers approval be restricted to RC and > > maybe important bugs? > > Isn't that my question? :) Well, IMHO only if we want to increase the hostile takeovers. What could be easily solved with a few NMUs will get much uglier. Note that I am all for going postal over anyone that breaks an essential package or does something equally stupid in an NMU. There is one thing that should be mandatory on all NMUs, though. It must be built inside a *CLEAN* pbuilder chroot for whichever distro the NMU is going to be uploaded to. low-disk-IO autobuilder-style chroots where packages are installed and removed and sometimes leave breakage behind do NOT count. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
Re: I will personally give 50 dollars to anyone who can figure out whoexactly st
It was probably you to smart for your on good
Re: I will personally give 50 dollars to anyone who can figure out whoexactly st
probably you to smart for you on good
