Re: chromium not in Squeeze: a bit of communication needed?
On Wed, Sep 8, 2010 at 5:55 PM, Sven Joachim wrote: > On 2010-09-08 16:10 +0200, Michael Gilbert wrote: >> I think that this need is justification to declare backports "officially >> supported by the debian project". Thus when asked this question, you >> can point to the fact that chromium is indeed supported on stable, just >> via a different model than folks are used to. That is of course >> assuming someone is willing to support the backport. > > It also means that users need to be taught how to change the apt pinning > priority for backports, because in the default configuration backported > packages are never updated automatically. Which is very bad from a > security point of view. Yes, but it is not the best solution. Someone already proposed in another thread (about 'backports') to change the default archive pin from '1' to '200' (in fact any value >=100 and <500, 200 is just my favorite) so that packages from backports will still have a lower priority over the packages from stable/security/volatile but also to be able to install them without pinning all the involved packages if the package only exists on backports. Thanks -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimwyzvxrtt1esbs2pkutct7nkyxx1pdybozt...@mail.gmail.com
Bug#608744: unblock: mercurial-server/1.1-1
2011/1/3 Mehdi Dogguy : > On 01/03/2011 11:31 AM, Teodor wrote: >> >> Please unblock package mercurial-server. The two RC bugs for this >> package were fixed so it should get back for inclussion in Debian 6.0 >> (squeeze). >> > > I think it's too late to get it back in Squeeze. I guess this would be the last chance to have mercurial-server in Debian 6.0. It is 26 days old [1] since the RC bugs were fixed and no more issues reported. Please accept it. Thanks -- [1] http://qa.debian.org/excuses.php?package=mercurial-server -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTi=FspLfTR=jnnyuhpybiu66_r2skseqjoydb...@mail.gmail.com
Bug#608744: unblock: mercurial-server/1.1-1
2011/1/24 Neil McGovern : > By the looks of things, Mehdi has already replied to your bug saying > that we can't accept the package at this stage. Yes, I know. But I thought that it could also be a good candidate for a "second thought" as it has been for other packages too. I mean, the package is in a good shape and we use it in production. > Apologies for the disappointment. My personal opinion is that the release policy should include allowing any leaf package back if there are no RC critical bugs. Maybe this will be changed for the next release, it is up to you (by you I mean the release team)! Thanks -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktim-kimixqbia2+mgf10zko0t9hj2mypxs3km...@mail.gmail.com
Re: Volatile Going Away?
Hi, 2011/1/27 Philipp Kern : > possibly. The only value I see in this is the transparent "we upgrade to the > next stable version when it's released" way of upgrading.[1] Apart from that > we're not entirely unhappy with only using codenames instead of suite > aliases. Of course, I only use codenames too. I just mentioned it just because it was provided in the past and will probably remain for those who prefer to use "stable" instead of the current code name for stable (lenny or soon to be squeeze). Also, I didn't do any fresh install recently but is this entry added automatically in sources.list the same way the "squeeze main" entry is added? | deb http://ftp.de.debian.org/debian squeeze-updates main Thanks -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTi�YRhnzKHCn2DXtFEbhf7RsqDnwOPvyPMu7=g...@mail.gmail.com
Re: New clamav upstream version: Should it go into squeeze?
Hi, On Wed, Oct 27, 2010 at 1:10 PM, Julien Cristau wrote: > On Tue, Oct 26, 2010 at 23:18:47 +0200, Moritz Muehlenhoff wrote: > >> Since the planned way to keep clamav updated in Squeeze will be by >> updating to the latest current clamav stable release, the same should >> naturally apply during the freeze? >> > Yes. Please unblock 'libclamunrar' to have it in sync with current 'clamav'. Thanks -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktinc6c4jhep=b6daduy1qgoy5q1gzea4zs7xc...@mail.gmail.com
Re: Please create volatile indices for squeeze
[added debian-live as requested by Daniel] Hi, 2010/11/13 Philipp Kern : > Please wait until this is formally communicated. The name might as well > still change. (Or the contents of the Release file, for pinning etc.) > > (I.e. the uncoordinated export from ftp-master wasn't our "wish".) Of course we'll wait until Debian 6.0 is released anyway (there are no packages yet in volatile or backports). However, I don't see why having squeeze-volatile on the master debian/ repository (and thus on all mirrors) is an issue?! IMO this is a step forward and backports will probably follow for wheezy. Probably there wasn't enough man power to do it for squeeze, at least this is how I see the situation with backports -- which is exactly in the same situation as volatile archive was for lenny with the difference that the backports archive has less restrictions (also a good thing). The only issue that I can see with the current implementation regarding stable/security/volatile/backports is report on bug #602390 [1]. Thanks [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602390 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikfwmnyrk8hdnvtenv6v5awy3p5j7cs531jg...@mail.gmail.com
Bug#604855: unblock: shibboleth-sp2/2.3.1+dfsg-3
Hi, 2010/11/25 Russ Allbery : > Ah, hm, that's a good point. I hadn't thought about that, since the old > Shibboleth modules depended on Apache. But the current packages only > recommend. > > I'm not sure the best way to do this. Check for whether apache2.2-common > is installed, since it contains the init script? (Checking for the > existence of the init script may be a lurking bug later for upstart > systems, file-rc, systemd, etc.) Alternately, we could just ignore > failures on the invoke-rc.d command to restart Apache. > > Does anyone have any suggestions about the best approach? The intended behavior is to restart Apache only if is running. It must not be started if it is stopped or not even available. It does matter if the module is enabled, but only if Apache is also running. I see at least two possible implementations: 1) use the 'status_of_proc' LSB function (there are many init scripts doing this for the status command); 2) check if there is any Apache process running: # pidof apache2 > /dev/null && invoke-rc.d apache2 restart Thanks -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimdv77a+otrmdyh0re-8gnru6u3reanovko1...@mail.gmail.com
Bug#606651: unblock: iceweasel/3.5.16-1
Hi, Just a note, iceweasel's migration is blocked by sqlite3 [1]. I've seen this today on my systems where the packages where kept back on a dist-upgrade (manually added a PIN for the version in unstable until the release). So, this probably means an unblock for sqlite3 or a t-p-u upload. This should be confirmed by the Release Team, I'm just guessing here. Thanks [1] http://qa.debian.org/excuses.php?package=iceweasel -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (600, 'testing'), (500, 'squeeze-updates'), (200, 'unstable'), (100, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktinno_vbyuyl+-17ulk7-4h+zyo2gagzkk-sm...@mail.gmail.com
Bug#608744: unblock: mercurial-server/1.1-1
Hi, 2011/1/3 Mehdi Dogguy : > > I think it's too late to get it back in Squeeze. What would be the risk of including this package with no release critical bugs into 6.0? There are packages with RC bugs that are ignored and still allowed to be released with 6.0, but a package with no RC bugs is not a candidate? Something is not right here. If we would have an alternative HG server but I couldn't find one!? Please reconsider this decision. Thanks -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktike5e8pvqjwrskuu9vra+oum+ogwbozr8yia...@mail.gmail.com
Bug#663541: error: alternative path /usr/share/java/swt-gtk-3.7.jar doesn't exist
Hi Debian Release team, The reported problem here appears to be for amd64 only because I was able to install the package libswt-gtk-3-java on i386. Also, looking at the build status page [1] I see that the amd64 package was uploaded directly by the maintainer. Is there any chance that scheduling a rebuild will fix this problem? Thanks [1]: https://buildd.debian.org/status/package.php?p=swt-gtk Selecting previously unselected package libswt-gtk-3-jni. (Reading database ... 284321 files and directories currently installed.) Unpacking libswt-gtk-3-jni (from .../libswt-gtk-3-jni_3.7.2-1_i386.deb) ... Selecting previously unselected package libswt-gtk-3-java. Unpacking libswt-gtk-3-java (from .../libswt-gtk-3-java_3.7.2-1_i386.deb) ... Setting up libswt-gtk-3-jni (3.7.2-1) ... Setting up libswt-gtk-3-java (3.7.2-1) ... update-alternatives: using /usr/share/java/swt-gtk-3.7.jar to provide /usr/share/java/swt.jar (swt.jar) in auto mode. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cag2wgfdxxzanebn9ybsoqairhiz90ry5rygqwi8vt5zjz7q...@mail.gmail.com
Re: php-mdb2: fix for bug#571702 in squeeze?
2012/5/8 Thomas Goirand : > Yes. As I wrote, this was fixed upstream, and the diff is only a > backport of upstream fix for the issue which I believe Teodor did (I'm > not sure who's the author, but it looked correct to me). I'm the author of the patch. I tried to find how it was fixed in testing/unstable but I saw a new upstream version with too many changes so I gave up. Thus I don't know if in the latest version you have the same fix or something more complex. Thanks -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cag2wgfe9iyvhprgqxvtaaxg0gtjs_og1cdqoxqnjpzm-q6e...@mail.gmail.com
Re: php-mdb2: fix for bug#571702 in squeeze?
2012/5/8 Cyril Brulebois : > As far as I'm concerned, I can't judge the impact of that PHP thingy. > [..] > So, unless somebody feels fancy and wants to take it from here, that's > a “no” for me. I don't think this decision should be based on feelings, but rather on technical analyse of the patch. I'm no PHP expert myself but this is what I can say: - it changes the only two lines of code that do "var =& new something" which were the reason of all warnings in the logs; - $result -> $result_resource only in function &_wrapResult() to cope with the first change. If there are no PHP experts on the Release Team, please contact other PHP teams for evaluation. I, too, would like to avoid any regressions introduced in stable. > Even if you think this change is totally harmless, I'd rather not see > the behaviour of a given library in stable change, at all. I'd rather > stick to considering targeted fixes for the callers, on a case by case > basis. I don't see the behaviour changed, but again this should be analysed especially by those who use the library (rdepends?). Thanks for considering. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAG2Wgfd=ueudgzktg1rfmgckhfecwqtvf5v6jbf65jzo0hc...@mail.gmail.com
Re: php-mdb2: fix for bug#571702 in squeeze?
2012/5/8 Adam D. Barratt : > I'll add looking at this to my to-do list. > > In any case, the window for getting fixes into the upcoming point release > closed a couple of days ago, so the package won't get approved (or > otherwise) until the point release has happened (scheduled for the coming > weekend). I don't think anyone involved had considered to push this patch in 6.0r5. The next point release is a reasonable target. 2012/5/9 Philipp Kern : > The patch must be minimal. I don't think it could be made more minimal that this. I tried and the result was not good. Thanks -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cag2wgfdkuw7qwn23cd+am8ose7jjdybl8-la53-kn9cu4ol...@mail.gmail.com
Bug#707550: opu: package php-mdb2/2.5.0b2-1
Hi, 2014/1/21 intrigeri : > Hi, > > Teodor, ping? I don't have the necessary experience to make this source debdiff. Thomas, are you still interested in uploading this (simple) patch for squeeze? Cheers -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cag2wgffe_+rsxec84qv0tjpbjdr3ux0nouj5msp4utrcgu_...@mail.gmail.com
