Processed: reassign 613007 to ftp.debian.org
Processing commands for cont...@bugs.debian.org: reassign 613007 ftp.debian.org Bug #613007 [release.debian.org] RM: debiandoc2dbxml/0.3 Bug reassigned from package 'release.debian.org' to 'ftp.debian.org'. thanks Stopping processing here. Please contact me if you need assistance. -- 613007: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613007 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.12974978345447.transcr...@bugs.debian.org
[SRM] Approval for deluge_1.2.3+git20110209.8c36830-0squeeze1
Dear RM, please consider the attached diff for deluge in Squeeze. The upload would fix #602613 (although the bug isn't easily reproducible on all systems). Code for the fix is a backport from the 1.3.x release made by upstream on explicit request (so the version in unstable isn't affected). The following diffstat also shows other minor changes from upstream 1.2-stable brach which don't affect the package. ChangeLog |1 + debian/changelog |8 deluge/ui/gtkui/mainwindow.py | 15 ++- deluge/ui/gtkui/menubar.py|5 + deluge/ui/gtkui/systemtray.py |6 +- docs/man/deluged.1|1 + get_libtorrent.sh | 16 setup.py | 33 ++--- 8 files changed, 60 insertions(+), 25 deletions(-) Thanks, -- Cristian Greco GPG key ID: 0xCF4D32E4 diff -Nru deluge-1.2.3+git20100712.0b609bf/ChangeLog deluge-1.2.3+git20110209.8c36830/ChangeLog --- deluge-1.2.3+git20100712.0b609bf/ChangeLog 2010-07-12 23:46:04.0 +0200 +++ deluge-1.2.3+git20110209.8c36830/ChangeLog 2011-02-09 18:07:32.0 +0100 @@ -4,6 +4,7 @@ of string. This fixes a problem where using lt 0.14.10 wouldn't allow Deluge to start. * Fix libtorrent 0.15 compatibility + * Fix hang on quit === Deluge 1.2.2 (19 March 2010) === Core diff -Nru deluge-1.2.3+git20100712.0b609bf/debian/changelog deluge-1.2.3+git20110209.8c36830/debian/changelog --- deluge-1.2.3+git20100712.0b609bf/debian/changelog 2010-07-13 19:12:30.0 +0200 +++ deluge-1.2.3+git20110209.8c36830/debian/changelog 2011-02-12 13:12:33.0 +0100 @@ -1,3 +1,11 @@ +deluge (1.2.3+git20110209.8c36830-0squeeze1) stable; urgency=low + + * Imported Upstream version 1.2.3+git20110209.8c36830 +- Upstream commit 8c36830 backported from the 1.3.x release: + fix hang on quit. (Closes: #602613) + + -- Cristian Greco crist...@regolo.cc Sat, 12 Feb 2011 13:00:41 +0100 + deluge (1.2.3+git20100712.0b609bf-1) unstable; urgency=low * Imported Upstream version 1.2.3+git20100712.0b609bf diff -Nru deluge-1.2.3+git20100712.0b609bf/deluge/ui/gtkui/mainwindow.py deluge-1.2.3+git20110209.8c36830/deluge/ui/gtkui/mainwindow.py --- deluge-1.2.3+git20100712.0b609bf/deluge/ui/gtkui/mainwindow.py 2010-07-12 23:46:04.0 +0200 +++ deluge-1.2.3+git20110209.8c36830/deluge/ui/gtkui/mainwindow.py 2011-02-09 18:07:32.0 +0100 @@ -152,11 +152,16 @@ Returns a reference to the main window glade object. return self.main_glade -def quit(self): -if client.is_classicmode(): -gtk.main_quit() -else: -reactor.stop() +def quit(self, shutdown=False): + +Quits the GtkUI + +:param shutdown: whether or not to shutdown the daemon as well +:type shutdown: boolean + +if shutdown: +client.daemon.shutdown() +reactor.stop() def load_window_state(self): x = self.config[window_x_pos] diff -Nru deluge-1.2.3+git20100712.0b609bf/deluge/ui/gtkui/menubar.py deluge-1.2.3+git20110209.8c36830/deluge/ui/gtkui/menubar.py --- deluge-1.2.3+git20100712.0b609bf/deluge/ui/gtkui/menubar.py 2010-07-12 23:46:04.0 +0200 +++ deluge-1.2.3+git20110209.8c36830/deluge/ui/gtkui/menubar.py 2011-02-09 18:07:32.0 +0100 @@ -253,10 +253,7 @@ def on_menuitem_quitdaemon_activate(self, data=None): log.debug(on_menuitem_quitdaemon_activate) -# Tell the core to shutdown -def on_shutdown(result): -self.window.quit() -client.daemon.shutdown().addCallback(on_shutdown) +self.window.quit(shutdown=True) def on_menuitem_quit_activate(self, data=None): log.debug(on_menuitem_quit_activate) diff -Nru deluge-1.2.3+git20100712.0b609bf/deluge/ui/gtkui/systemtray.py deluge-1.2.3+git20110209.8c36830/deluge/ui/gtkui/systemtray.py --- deluge-1.2.3+git20100712.0b609bf/deluge/ui/gtkui/systemtray.py 2010-07-12 23:46:04.0 +0200 +++ deluge-1.2.3+git20110209.8c36830/deluge/ui/gtkui/systemtray.py 2011-02-09 18:07:32.0 +0100 @@ -324,9 +324,6 @@ if self.config[lock_tray] and not self.window.visible(): self.unlock_tray() -if self.config[classic_mode]: -client.daemon.shutdown() - self.window.quit() def on_menuitem_quitdaemon_activate(self, menuitem): @@ -334,8 +331,7 @@ if self.config[lock_tray] and not self.window.visible(): self.unlock_tray() -client.daemon.shutdown() -self.window.quit() +self.window.quit(shutdown=True) def tray_setbwdown(self, widget, data=None): self.setbwlimit(widget, _(Set Maximum Download Speed), max_download_speed, diff -Nru deluge-1.2.3+git20100712.0b609bf/docs/man/deluged.1 deluge-1.2.3+git20110209.8c36830/docs/man/deluged.1 ---
Re: GMP transition: 4.3.2 to 5.0.1?
On Sun, 2011-02-06 at 12:39 -0600, Steve M. Robbins wrote:
Now that squeeze is out, I'd like to move from GMP 4 to GMP 5. The
latter was released upstream about a year ago and the gmp lists
aren't buzzing with outrageous bugs, so it appears stable enough.
Looking at the package names of the unstable and experimental versions,
it looks like the main change is libgmp3c2 to libgmp3? (There is also
lib{32,64}gmp3 - lib{32,64}gmp10, but those libraries appear to only be
used by gmp itself).
I know GMP is used in gcc itself, so I'd appreciate some guidance
from the gcc team as well, since this is a major version change.
I uploaded GMP 5 to experimental last year and it builds fine with two
exceptions: hppa is BD-Uninstallable (?) and ia64 fails to build with
an ICE. The underlying cause is already known [1] and from reading
the bug report I suspect I may be able to work around this by building
one file with -O2 rather than -O3. Other suggestions welcome.
hppa is in Needs-Build, not BD-Uninstallable; that's expected because
hppa doesn't have any autobuilders for experimental.
Have any of the reverse-dependencies been test-built against the new
version? Does the move to 5.0.1 imply any source changes being required
for reverse-dependencies, or just rebuilds? (I say just as there
appear to be around 350 r-dependencies, including at least five from the
GCC suite).
Main question: should I go ahead and upload the new version when
I get a free moment or do we need more investigation?
At the very least I'd first like to confirm that the suggested change
for ia64 works (rebuilding on the other architectures wouldn't hurt
either) and better understand the scope of the changes, particularly in
relation to e.g. gcc.
Regards,
Adam
--
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/1297517979.27877.2727.ca...@hathi.jungle.funky-badger.org
Re: [SRM] Approval for deluge_1.2.3+git20110209.8c36830-0squeeze1
On Sat, 2011-02-12 at 13:55 +0100, Cristian Greco wrote: please consider the attached diff for deluge in Squeeze. The upload would fix #602613 (although the bug isn't easily reproducible on all systems). Code for the fix is a backport from the 1.3.x release made by upstream on explicit request (so the version in unstable isn't affected). Thanks for working on this; a question on the changes: --- deluge-1.2.3+git20100712.0b609bf/deluge/ui/gtkui/systemtray.py 2010-07-12 23:46:04.0 +0200 +++ deluge-1.2.3+git20110209.8c36830/deluge/ui/gtkui/systemtray.py 2011-02-09 18:07:32.0 +0100 @@ -324,9 +324,6 @@ if self.config[lock_tray] and not self.window.visible(): self.unlock_tray() -if self.config[classic_mode]: -client.daemon.shutdown() - self.window.quit() This looks like the call to shutdown() gets lost under some circumstances (as self.window.quit() will be called with the default setting of shutdown=False); is that intentional? The following diffstat also shows other minor changes from upstream 1.2-stable brach which don't affect the package. I guess this refers to these changes? get_libtorrent.sh | 16 setup.py | 33 ++--- If they're not relevant to fixing the bug and don't resolve any other issues with the package, then they shouldn't really be included in a stable update. I appreciate that they're not large, but they are larger than the combination of the files which do address #602613. Regards, Adam -- 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/1297519489.27877.2796.ca...@hathi.jungle.funky-badger.org
Bug#612342: squeeze KDE updates (was Re: My last (hopefully) bits for KDE in Squeeze)
On Mon, 2011-02-07 at 23:45 +0200, Modestas Vainius wrote: so I'm turning this thread into a bug report. My requests are below. Three would have been better; one package per report is much easier to keep track of. (As would using X-Debbugs-CC so the mail on the list actually had the bug number). More detailed info can be found in the quoted text, individual bug reports and previous mails in the thread. 1) krunner #607974 src:kdebase-workspace. The upload is planned to be identical to the current 4:4.4.5-8 in unstable, just with squeeze-adjusted revision number. 4:4.4.5-8 fared well in unstable, I have never had a single krunner crash since upgrading. This would basically be http://websvn.kde.org/?view=revisionrevision=1098125 ? How close to the 4.5 fix is the 4.4.5 version? (There didn't appear to be a link to the backported diff in the upstream bug report). 2) src:krusader #604196. All info, including the patch, below and in the bug report. Package revision will be properly squeeze-adjusted. Please go ahead with this one. 3) kde4libs #588374. Squeeze upload will be based on kde4libs 4:4.4.5-3 currently in unstable. It solves a desktop defacing issues after upgrade from KDE 3 (lenny - squeeze). Quoting the changelog: * Add a kconf_update script (migrate_from_kde3_icon_theme) to migrate away from old KDE 3 icon themes which are KDE 4 incompatible (e.g. crystalsvg). (Closes: #588374) This appears not to have been included in the previous discussions, afaics? It's a shame this wasn't resolved until so close to the release, given the date of the original report. Are most themes targeted at either KDE3 or KDE4, or would they usually be expected to work with both? Regards, Adam -- 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/1297528078.27877.3104.ca...@hathi.jungle.funky-badger.org
Bug#612342: squeeze KDE updates (was Re: My last (hopefully) bits for KDE in Squeeze)
Hello,
On šeštadienis 12 Vasaris 2011 18:27:58 Adam D. Barratt wrote:
Three would have been better; one package per report is much easier to
keep track of. (As would using X-Debbugs-CC so the mail on the list
actually had the bug number).
Sorry, will try to do better next time.
More
detailed info can be found in the quoted text, individual bug reports and
previous mails in the thread.
1) krunner #607974 src:kdebase-workspace. The upload is planned to be
identical to the current 4:4.4.5-8 in unstable, just with
squeeze-adjusted revision number. 4:4.4.5-8 fared well in unstable, I
have never had a single krunner crash since upgrading.
This would basically be
http://websvn.kde.org/?view=revisionrevision=1098125 ? How close to
the 4.5 fix is the 4.4.5 version? (There didn't appear to be a link to
the backported diff in the upstream bug report).
Because it was not backported by upstream, I backported it myself. But my
backport is very close to the original patch. It's only an unfuzz of the
modified comment lines in KDE 4.5 (see below)
@@ -1,3 +1,16 @@
+From: Aaron J. Seigo ase...@kde.org
+Subject: Fix for krunner occasionally crashes (threading related)
+Origin: backport http://websvn.kde.org/?view=revisionrevision=1098125
+Bug: https://bugs.kde.org/show_bug.cgi?id=236496#c11
+Bug: https://bugs.kde.org/show_bug.cgi?id=224212
+Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607974
+Last-Update: 2011-01-18
+Forwarded: yes
+Applied-Upstream: 4.5.0
+
+move the kfileplaces usage to the main thread; really non-optimal, but KIO
+forces our hand. if this works out in trunk, i'll backport to the 4.4 branch.
+
--- a/plasma/generic/runners/places/placesrunner.cpp
+++ b/plasma/generic/runners/places/placesrunner.cpp
@@ -19,14 +19,20 @@
@@ -21,16 +34,16 @@
Q_UNUSED(args)
setObjectName(Places);
addSyntax(Plasma::RunnerSyntax(:q:, i18n(Finds file manager locations
that match :q:)));
-@@ -34,7 +40,7 @@
+@@ -34,7 +40,7 @@ PlacesRunner::PlacesRunner(QObject* pare
- // ensure the bookmarkmanager, etc. in the places model gets creates
created in the main thread
- // otherwise crashes ensue
+ // makes sure we have the bookmarks and what not that the places
+ // model uses set up in the main thread, otherwise crashes ensue
-KFilePlacesModel places;
+m_helper = new PlacesRunnerHelper(this);
}
PlacesRunner::~PlacesRunner()
-@@ -43,21 +49,48 @@
+@@ -43,21 +49,48 @@ PlacesRunner::~PlacesRunner()
void PlacesRunner::match(Plasma::RunnerContext context)
{
@@ -84,7 +97,7 @@
if ((all !text.isEmpty()) || text.compare(term,
Qt::CaseInsensitive) == 0) {
type = Plasma::QueryMatch::ExactMatch;
relevance = all ? 0.9 : 1.0;
-@@ -67,18 +100,18 @@
+@@ -67,18 +100,18 @@ void PlacesRunner::match(Plasma::RunnerC
}
if (type != Plasma::QueryMatch::NoMatch) {
@@ -133,7 +146,7 @@
class PlacesRunner : public Plasma::AbstractRunner
{
Q_OBJECT
-@@ -35,8 +51,14 @@
+@@ -35,8 +51,14 @@ public:
void match(Plasma::RunnerContext context);
void run(const Plasma::RunnerContext context, const Plasma::QueryMatch
action);
2) src:krusader #604196. All info, including the patch, below and in the
bug report. Package revision will be properly squeeze-adjusted.
Please go ahead with this one.
3) kde4libs #588374. Squeeze upload will be based on kde4libs 4:4.4.5-3
currently in unstable. It solves a desktop defacing issues after
upgrade from KDE 3 (lenny - squeeze). Quoting the changelog:
* Add a kconf_update script (migrate_from_kde3_icon_theme) to migrate
away
from old KDE 3 icon themes which are KDE 4 incompatible (e.g.
crystalsvg). (Closes: #588374)
This appears not to have been included in the previous discussions,
afaics? It's a shame this wasn't resolved until so close to the
release, given the date of the original report.
Well, I figured you would not accept non-RC fixes so I didn't even try asking.
Are most themes targeted at either KDE3 or KDE4, or would they usually
be expected to work with both?
KDE 3 themes do not work with KDE 4. Afaik, many icons were renamed to comply
with some XDG standard. So that's where defacing comes from. When KDE 4
does not find an icon in the old KDE 3 theme, it uses a default one
(probably the first from the list). So in place of all missing icons, user
gets the same icon all over the place (new, open, save, save as, shutdown,
restart etc... buttons look the same). The patch resets icon theme in the user
configuration if it does not find some KDE 4 compliant icons in the current
theme.
--
Modestas Vainius mo...@debian.org
signature.asc
Description: This is a digitally signed message part.
Bug#612342: squeeze KDE updates (was Re: My last (hopefully) bits for KDE in Squeeze)
On Sat, 2011-02-12 at 19:49 +0200, Modestas Vainius wrote: On šeštadienis 12 Vasaris 2011 18:27:58 Adam D. Barratt wrote: Three would have been better; one package per report is much easier to keep track of. (As would using X-Debbugs-CC so the mail on the list actually had the bug number). Sorry, will try to do better next time. Heh. :-) 1) krunner #607974 src:kdebase-workspace. The upload is planned to be identical to the current 4:4.4.5-8 in unstable, just with squeeze-adjusted revision number. 4:4.4.5-8 fared well in unstable, I have never had a single krunner crash since upgrading. This would basically be http://websvn.kde.org/?view=revisionrevision=1098125 ? How close to the 4.5 fix is the 4.4.5 version? (There didn't appear to be a link to the backported diff in the upstream bug report). Because it was not backported by upstream, I backported it myself. But my backport is very close to the original patch. It's only an unfuzz of the modified comment lines in KDE 4.5 (see below) Okay; thanks for the explanation. Please go ahead with this one. 3) kde4libs #588374. Squeeze upload will be based on kde4libs 4:4.4.5-3 currently in unstable. It solves a desktop defacing issues after upgrade from KDE 3 (lenny - squeeze). Quoting the changelog: [...] KDE 3 themes do not work with KDE 4. Afaik, many icons were renamed to comply with some XDG standard. So that's where defacing comes from. When KDE 4 does not find an icon in the old KDE 3 theme, it uses a default one (probably the first from the list). So in place of all missing icons, user gets the same icon all over the place (new, open, save, save as, shutdown, restart etc... buttons look the same). The patch resets icon theme in the user configuration if it does not find some KDE 4 compliant icons in the current theme. Please go ahead with this one too. It would be good to get some testing of the updated packages for each of the fixes addressed in this report once they're in proposed-updates, although I suspect there's a good chance that most of the people reporting the issues may still be using unstable or testing. Regards, Adam -- 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/1297533958.27877.3315.ca...@hathi.jungle.funky-badger.org
Bug#612342: squeeze KDE updates (was Re: My last (hopefully) bits for KDE in Squeeze)
On Sat, Feb 12, 2011 at 07:49:53PM +0200, Modestas Vainius wrote: Are most themes targeted at either KDE3 or KDE4, or would they usually be expected to work with both? KDE 3 themes do not work with KDE 4. Afaik, many icons were renamed to comply with some XDG standard. So that's where defacing comes from. When KDE 4 does not find an icon in the old KDE 3 theme, it uses a default one (probably the first from the list). So in place of all missing icons, user gets the same icon all over the place (new, open, save, save as, shutdown, restart etc... buttons look the same). The patch resets icon theme in the user configuration if it does not find some KDE 4 compliant icons in the current theme. Hrm, Gnome displays image-missing in this case... IIRC, that is. Kind regards Philipp Kern signature.asc Description: Digital signature
[SRM] Approval for partconf_1.36squeeze1
Dear stable release managers,
I would like to fix a bug in partconf, which prevent installing a MIPS
machine using preseeding, as it's not possible to change the default
values of two debconf questions.
Please consider the diff below for partconf in stable.
Aurelien
diff --git a/debian/changelog b/debian/changelog
index bf599d6..b283bf6 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+partconf (1.36squeeze1) stable-proposed-updates; urgency=low
+
+ [ Aurelien Jarno ]
+ * Don't set default debconf values, they are already set in the
+templates. This fixes preseeding.
+
+ -- Aurelien Jarno aure...@debian.org Sat, 12 Feb 2011 22:31:09 +0100
+
partconf (1.36) unstable; urgency=low
[ Updated translations ]
diff --git a/partconf.c b/partconf.c
index b7d290d..c4a3d31 100644
--- a/partconf.c
+++ b/partconf.c
@@ -266,7 +266,6 @@ sanity_checks(void)
// XXX something like Partitions 1, 3 and 7 on IDE3 master, but this
// XXX is probably hard, especially for i18n. :-( If multi-line
// XXX substitutions worked, we could just list the partitions.
-debconf_set(debconf, partconf/confirm, false);
debconf_input(debconf, critical, partconf/confirm);
if (debconf_go(debconf) == 30)
return 0;
@@ -602,7 +601,6 @@ main(void)
if (check_proc_mounts()) {
// Chicken out if /target is already mounted
-debconf_set(debconf,partconf/already-mounted, no);
debconf_input(debconf, critical, partconf/already-mounted);
debconf_go(debconf);
debconf_get(debconf,partconf/already-mounted);
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurel...@aurel32.net http://www.aurel32.net
--
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/20110212214029.ga7...@volta.aurel32.net
Proposed kernel fixes on sparc for 6.0.1
Hello, Late in the release cycle we found out that a kernel bug prevents sparc machines with ATI graphics adapters using atyfb driver from booting due to problems with console handover, causing it to hang early during the boot (http://bugs.debian.org/602853). I thought that this can be worked around by disabling framebuffer during boot, however there was at least one report that this was not effective. I would like to solicit kernel team's opinions on feasibility of including the patch posted to the bug (committed upstream) in 6.0.1. I've already built a patched kernel and made if available for testing as a part of unofficial Squeeze installation image, and haven't heard about any problems so far. Eventually we would need release team's blessing as well, I guess. Best regards, -- Jurij Smakov ju...@wooyd.org Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- 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/20110212214831.ga4...@droopy.oc.cox.net
Re: [SRM] Approval for partconf_1.36squeeze1
On Sat, Feb 12, 2011 at 22:40:29 +0100, Aurelien Jarno wrote: Dear stable release managers, I would like to fix a bug in partconf, which prevent installing a MIPS machine using preseeding, as it's not possible to change the default values of two debconf questions. Please consider the diff below for partconf in stable. Ack, please go ahead. Cheers, Julien -- 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/20110212215627.gn3...@radis.liafa.jussieu.fr
Preparation of fixes to 6.0.1
Hello folks, I have prepare some branches that has what I am intending to upload to stable-proposed-updates. The modules I have changed are the following: grub-installer linux-kernel-di-sparc-2.6 tasksel cdebconf debootstrap kernel-wedge Please take a look and comment on those. If you think anything is missing please say so. -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- 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/AANLkTinTbvVOnR0xcET=0GMbA3rHO6Hkg48JQJYK6a=8...@mail.gmail.com
Re: Preparation of fixes to 6.0.1
On Sat, Feb 12, 2011 at 10:46:07PM +, Otavio Salvador wrote: Hello folks, I have prepare some branches that has what I am intending to upload to stable-proposed-updates. The modules I have changed are the following: grub-installer linux-kernel-di-sparc-2.6 This should probably be uploaded once the update kernel for 6.0.1 is available? tasksel cdebconf debootstrap kernel-wedge Please include debian-installer as well, I've committed a patch targeting 6.0.1. Thanks for doing this. Please take a look and comment on those. If you think anything is missing please say so. -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- 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/AANLkTinTbvVOnR0xcET=0GMbA3rHO6Hkg48JQJYK6a=8...@mail.gmail.com -- Jurij Smakov ju...@wooyd.org Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- 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/20110212231312.ga5...@droopy.oc.cox.net
openssl for testing.
Hi, Could someone bump openssl's priority so it migrates to testing sooner? It fixes a security issue. Kurt -- 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/20110212232418.ga9...@roeckx.be
Openssl 1.0.0
Hi, I would like to upload version 1.0.0(d) to unstable soon. It changes soname, but as far as I know the API is still compatible with the old one, and you should be able to rebuild everything against the new version. I wonder if I need to upload an openssl098 source package at the same time to provide the current soname. I would really like to avoid having the old soname in wheezy, so I would like to get rid of it as soon as possible and don't plan to keep a -dev package for it in any case. Please let me know what I should do, and when you think it's a good time to do that. Kurt -- 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/20110212232751.gb9...@roeckx.be
Re: openssl for testing.
On Sun, Feb 13, 2011 at 00:24:18 +0100, Kurt Roeckx wrote: Hi, Could someone bump openssl's priority so it migrates to testing sooner? It fixes a security issue. done. Cheers, Julien signature.asc Description: Digital signature
Re: Preparation of fixes to 6.0.1
On Sat, 2011-02-12 at 23:13 +, Jurij Smakov wrote: I have prepare some branches that has what I am intending to upload to stable-proposed-updates. The modules I have changed are the following: The below shouldn't be assumed to be an ack or nack for the particular uploads at this point. grub-installer There doesn't appear to be a squeeze branch for this listed on gitweb; for a stable update, the hurd fixes wouldn't be appropriate for instance. linux-kernel-di-sparc-2.6 This should probably be uploaded once the update kernel for 6.0.1 is available? Yes; or at least it will need rebuilding once a final(ish) kernel for 6.0.1 is in place; Dann's often uploaded lkdi-* nearer to the point release to get it built against the kernel we're including. tasksel Would this include all of the changes between 2.88 and 2.89, or just some subset? As I think I've mentioned before, changes which might affect what ends up on CD1 for any given CD set worry me, particularly given the last minute problems we had for 6.0.0 with getting the release notes on to the CDs and trying to get all of the packages required for KDE CD1 to fit on a single CD for some architectures. cdebconf debootstrap kernel-wedge Please include debian-installer as well, I've committed a patch targeting 6.0.1. I'd imagine this would want to be uploaded closer to the point release, or at least we'll need to rebuild it later on to pick up any further builds of lkdi-* or other udebs. Regards, Adam -- 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/1297555390.27877.4029.ca...@hathi.jungle.funky-badger.org
Re: [SRM] Approval for deluge_1.2.3+git20110209.8c36830-0squeeze1
Hi, On Sat, 12 Feb 2011 14:04:49 + Adam D. Barratt a...@adam-barratt.org.uk wrote: On Sat, 2011-02-12 at 13:55 +0100, Cristian Greco wrote: please consider the attached diff for deluge in Squeeze. The upload would fix #602613 (although the bug isn't easily reproducible on all systems). Code for the fix is a backport from the 1.3.x release made by upstream on explicit request (so the version in unstable isn't affected). Thanks for working on this; a question on the changes: --- deluge-1.2.3+git20100712.0b609bf/deluge/ui/gtkui/systemtray.py 2010-07-12 23:46:04.0 +0200 +++ deluge-1.2.3+git20110209.8c36830/deluge/ui/gtkui/systemtray.py 2011-02-09 18:07:32.0 +0100 @@ -324,9 +324,6 @@ if self.config[lock_tray] and not self.window.visible(): self.unlock_tray() -if self.config[classic_mode]: -client.daemon.shutdown() - self.window.quit() This looks like the call to shutdown() gets lost under some circumstances (as self.window.quit() will be called with the default setting of shutdown=False); is that intentional? Yes, the change is intentional. It is a backport and is however well tested, as commented by the bug submitter. The following diffstat also shows other minor changes from upstream 1.2-stable brach which don't affect the package. I guess this refers to these changes? get_libtorrent.sh | 16 setup.py | 33 ++--- If they're not relevant to fixing the bug and don't resolve any other issues with the package, then they shouldn't really be included in a stable update. I appreciate that they're not large, but they are larger than the combination of the files which do address #602613. Well, I know the changes seem particularly large, but it is not program code. It just adds another if/else switch to the setup.py module in order to call the newly added get_libtorrent.sh script in case the user is building from git and needs to download the libtorrent library. Half of the changes in setup.py in just code indentation. In any case, this code is never executed during build as the libtorrent library is available system-wide. I understand these changes can be annoying for a stable update but, on the other hand it wouldn't make sense to cherry-pick the single fix when we are tracking the 1.2-stable branch (which already included a number of fixes from last release) with a specific debian version of 1.2.3+git. Please let me know if my complaints are totally pointless. ;-) Thanks, -- Cristian Greco GPG key ID: 0xCF4D32E4 signature.asc Description: PGP signature
