Bug#533652: status - package obsolete
FTF3k3 a écrit : Alexis Sukrieh is not the packager? Not anymore, I have resigned from Debian. http://lists.debian.org/debian-devel/2009/07/msg00175.html -- Alexis Sukrieh -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#453487: [Webapps-common-packages] Bug#453487: Severity of should this package be orphaned/removed bugs
* Moritz Muehlenhoff ([EMAIL PROTECTED]) : I have no special opinion about the general case, but in this specific case we have a high-profile app with regular security issues, which will soon no longer be supported upstream, while we will need to support it until 2011. Bugzilla is a pretty heavy package to maintain, because of this: upstream deprectates quickly major releases while Debian provides a long-time support. This is one of the major reason why I orphaned Bugzilla in the first place: that needs a big amount of non-stopping work. I do think this must be handled by a team rather by a one-person maintainer. That's why I frist tried to set up a Webapps Team to maintain the package but there was no volunteers to join the maintenance. Good luck with it. Tell me if I can help anyways. Regards, -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#439392: Updates for etch and sarge?
Thijs Kinkhorst wrote: Hi, Thanks for fixing this promptly. Do you intend to supply fixed packages for etch and sarge, or are they not vulnerable? Hi, The stable package has been submitted to the Security Team. It's wqaiting for approval. Regards, -- Alexis Sukrieh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#439392: Security Update for Etch?
Micha Lenk wrote: Hi Alexis, when will there be a security update available for Debian Etch? Thanks for your support Hi, I've submitted a patch for the etch package to the security team. It's in their hands and is waiting for approval. I'm waiting to see it going into the security updates as well ;) Regards, -- Alexis Sukrieh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#439392: [backup-manager] Fix proposed upstream
Hello, A fix has been proposed and is waiting for approval by the development team upstream. We welcome very much the Debian's point of view of the solution submited here. patch: http://bugzilla.backup-manager.org/cgi-bin/attachment.cgi?id=64 use private temp file for passing the password to b-m-u This way we hide the password in a file which is readable only by the user who launched backup-manager, and saved in his home directory. backup-manager-upload is passed the path to that file instead of the password itself. Feel free to comment on. Regards, -- Alexis Sukrieh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#439392: [backup-manager] Fix proposed upstream
Alexis Sukrieh wrote:
Hello,
A fix has been proposed and is waiting for approval by the development
team upstream. We welcome very much the Debian's point of view of the
solution submited here.
Please, ignore that patch. There is cleaner solution which is using the
environement variable already exported by the first script.
Sorry for the noise.
The patch that will be procvided upstream will be about reading
$ENV{BM_UPLOAD_FTP_PASSWORD} instead of taking it from the command line.
Regards.
--
Alexis Sukrieh
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407406:
After looking at the patch submitted upstream, it looks like I'm not
facing the exactly same bug, as the sources of mysql-server in etch
include the correct version:
MySQL patch:
http://lists.mysql.com/commits/12694
etch mysql-server sources:
if (!_mi_get_last_key(info,keyinfo,anc_buff,lastkey,keypos,length))
{
goto err;
}
Anyway, I'm facing the same symptom:
Incorrect key file for table after a fresh dump load in the database.
Regards,
Alexis
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407406: mysql-server: DELETE FROM table causes Incorrect key file for table
Christian Hammers wrote: That bug is supposed to be fixed since 5.0.26 if I read it correctly. Yep, but I'm facing a symptom very near to the upstream bug reported. That's why I thought in the first place it was the same bug. Could you mail me a copy of the mysqldump output you tried to insert? Having something reproducible vastly increases the chance to fix the bug. I can mail you the dump but only privately (and GPG encrypted) as it's some private data, used for a project I'm working on for a company. I ask you not to distribute the dump even if that's development stuff. Thanks a lot for paying attention to that issue. Here is how to reproduce the bug: $ echo create database test_database | mysql $ mysql test_database db/create.sql $ mysql test_database db/data.sql $ mysql test_database [...] mysql select words.id, words.value, sum(count) as count from sitetags, words where words.id = word_id group by word_id order by count desc limit 100;ERROR 126 (HY000): Incorrect key file for table '/tmp/#sql_7b82_0.MYI'; try to repair it mysql I'm mailing you the dump (it's quite big). Regards, Alexis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407406: mysql-server: DELETE FROM table causes Incorrect key file for table
Hi again, I also have another bug (certainly related) with the same dump: mysql SHOW FIELDS FROM users; ERROR 1030 (HY000): Got error 28 from storage engine mysql -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407406: mysql-server: DELETE FROM table causes Incorrect key file for table
Package: mysql-server Version: 5.0.30-3 Severity: grave Justification: causes serious data loss Hello, I use a Debian etch server for development purposes, and I use there a mysql database. Now that I've upgraded my development server from sarge to etch, I face a grave bug: when importing data from a dump made by mysqldump to a new database, a key corruption appears. Here is the error message: Mysql::Error: #HY000Incorrect key file for table '/tmp/#sql_7b82_0.MYI'; try to repair it: query ... After Googling a bit, I found that bug on the MySQL's bug tracking system: http://bugs.mysql.com/bug.php?id=22384 So it sounds to be fixed upstream (the report speaks about a patch). IMHO, That bug should definitely not be shipped with etch, it renders any impacted database unusable. Regards, -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-vserver-k7 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8) Versions of packages mysql-server depends on: ii mysql-server-5.0 5.0.30-3 mysql database server binaries mysql-server recommends no packages. -- debconf information: mysql-server/nis_warning: mysql-server/really_downgrade_from_41: false mysql-server/mysql_update_hints1: mysql-server/start_on_boot: true mysql-server/postrm_remove_databases: false * mysql-server/mysql_install_db_notes: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#395094: CVE-2006-545[3-5]: Multiple security issues in bugzilla
* Ben Hutchings ([EMAIL PROTECTED]) : Based on the advisory at http://www.bugzilla.org/security/2.18.5/ I would say that: [...] Ben, thanks a lot for your work regarding that issue. If you have an alioth account, feel free to ask Sean Finney to add you to the webapps-common team, so you can commit to the bugzilla SVN repo. I'm going to review and apply your patches as soon as possible. Thanks again, your help is pretty welcome, as bugzilla really needs attention, time and work. Regards, -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#395094: CVE-2006-545[3-5]: Multiple security issues in bugzilla
tags 395094 + confirmed thanks * Ben Hutchings ([EMAIL PROTECTED]) : Upstream security advisory: http://www.bugzilla.org/security/2.18.5/ These are fixed in 2.22.1 which would be suitable for sid. I'm working on the packaging of that new upstream release. -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#395094: [bugzilla #395094] bug only affects sarge now
tags 395094 + sarge thanks I've just uploaded bugzilla 2.22.1 to sid, urgency set to high. That bug is now closed in sid. We can focus on the sarge patches now. -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#393459: Bugzilla 2.22-5 postinst dies with status 10
reassign 393459 dbconfig-common severity 393459 serious retitle 393459 Empty postgres section seems to break dbconfig postinst thanks Tim Van Holder wrote: This looks like dbconfig-related - that parameter is fetched in /usr/share/dbconfig-common/dpkg/common, not directly in any Bugzilla stuff (in fact, checksetup.pl passes just fine). Indeed, when bugzilla 2.22-5 was uploaded to sid it used to work just fine, and there wasn't any dbconfig-common issues. That's why that bug must be coming from dbconfig-common, hence I'm reassigning it to that package. I'm also raising the severity to serious as it renders packages that use dbconfig-commin uninstalable. Sean, feel free to contact me if you need more details/help. Regards, -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34[EMAIL PROTECTED] The real glory of maintainership isn't making the big and important decisions. The real glory lies in all the small stuff that doesn't really matter, and that people will just argue forever. -- Linus Torvalds -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#391181: NMU (delayed-7) for closing #391181
tags 391181 + patch thanks Hi, I've just uploaded a fix for that bug to the delayed queue (7 days). Here is attached the patch I applied for closing the bug and enhancing a bit the package shape. Basically, it's about fixing lintian errors (#DEBHELPER# tags were missing in maintainer scripts) and making sure the cron.d script behaves correctly. I also added a postrm script that takes care manually of the purge phase. Regards, -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34[EMAIL PROTECTED] The real glory of maintainership isn't making the big and important decisions. The real glory lies in all the small stuff that doesn't really matter, and that people will just argue forever. -- Linus Torvalds diff -uNbBr pdbv-2.0.10.1/configure pdbv-2.0.10.1.1/configure --- pdbv-2.0.10.1/configure 2005-02-23 11:43:07.0 +0100 +++ pdbv-2.0.10.1.1/configure 2006-10-08 11:34:37.0 +0200 @@ -203,17 +203,17 @@ # see http://savannah.nongnu.org/bugs/?func=detailbugbug_id=2691group_id=2348 echo -n creating $CRONFILE... echo # May run on a daily basis (prefered for pdbv 1.x.x). $CRONFILE -echo 20 15 * * * nobody $PREFIX/bin/pdbv --cron=daily $CRONFILE +echo 20 15 * * * nobody [ -x $PREFIX/bin/pdbv ] $PREFIX/bin/pdbv --cron=daily $CRONFILE echo$CRONFILE echo # May run on a hourly basis (prefered for pdbv 2.x.x). $CRONFILE -echo 32 * * * * nobody $PREFIX/bin/pdbv --cron=hourly $CRONFILE +echo 32 * * * * nobody [ -x $PREFIX/bin/pdbv ] $PREFIX/bin/pdbv --cron=hourly $CRONFILE echo$CRONFILE echo # Once per week, regenerate the whole output without tests. $CRONFILE echo # Can be useful in regard of pop-con results, or because $CRONFILE echo # it happens that a package is replaced by a package of the $CRONFILE echo # exact same version. $CRONFILE -echo 05 18 * * 1 nobody $PREFIX/bin/pdbv --cron=daily --force $CRONFILE -echo 05 18 * * 1 nobody $PREFIX/bin/pdbv --cron=hourly --force $CRONFILE +echo 05 18 * * 1 nobody [ -x $PREFIX/bin/pdbv ] $PREFIX/bin/pdbv --cron=daily --force $CRONFILE +echo 05 18 * * 1 nobody [ -x $PREFIX/bin/pdbv ] $PREFIX/bin/pdbv --cron=hourly --force $CRONFILE echo$CRONFILE echo done diff -uNbBr pdbv-2.0.10.1/debian/changelog pdbv-2.0.10.1.1/debian/changelog --- pdbv-2.0.10.1/debian/changelog 2005-03-06 15:34:01.0 +0100 +++ pdbv-2.0.10.1.1/debian/changelog2006-10-08 12:05:08.0 +0200 @@ -1,3 +1,16 @@ +pdbv (2.0.10.1.1) unstable; urgency=low + + * Non-maintainer upload. + * Added the #DEBHELPER# tag in maintainer scripts (fixes lintian warnings). + * Moved the Build-Depends-Indep for debhelper to Build-Depends to fix a +lintian error. + * Make sure the cron.d/pdbv script is removed when the packaged is purged. + * Patched cron.d/pdbv in order to check that /usr/bin/pdbv is present at +runtime. +(closes: #391181) + + -- Alexis Sukrieh [EMAIL PROTECTED] Sun, 8 Oct 2006 12:04:31 +0200 + pdbv (2.0.10.1) unstable; urgency=low * New upstream release. diff -uNbBr pdbv-2.0.10.1/debian/control pdbv-2.0.10.1.1/debian/control --- pdbv-2.0.10.1/debian/control2005-03-06 15:28:40.0 +0100 +++ pdbv-2.0.10.1.1/debian/control 2006-10-08 11:47:20.0 +0200 @@ -3,7 +3,8 @@ Priority: optional Maintainer: Mathieu Roy [EMAIL PROTECTED] Uploaders: Jerome Marant [EMAIL PROTECTED] -Build-Depends-Indep: gettext, debhelper (= 4.1.16) +Build-Depends-Indep: gettext +Build-Depends: debhelper (= 4.1.16) Standards-Version: 3.6.1.0 Package: pdbv diff -uNbBr pdbv-2.0.10.1/debian/postinst pdbv-2.0.10.1.1/debian/postinst --- pdbv-2.0.10.1/debian/postinst 2004-06-05 15:38:57.0 +0200 +++ pdbv-2.0.10.1.1/debian/postinst 2006-10-08 12:04:19.0 +0200 @@ -43,4 +43,8 @@ `chown nobody $output_dir`; +# dh_installdeb will replace this with shell code automatically +# generated by other debhelper scripts. +#DEBHELPER# + exit; diff -uNbBr pdbv-2.0.10.1/debian/postrm pdbv-2.0.10.1.1/debian/postrm --- pdbv-2.0.10.1/debian/postrm 1970-01-01 01:00:00.0 +0100 +++ pdbv-2.0.10.1.1/debian/postrm 2006-10-08 11:45:44.0 +0200 @@ -0,0 +1,35 @@ +#! /bin/sh +# postrm script for pdbv +set -e + +# summary of how this script can be called: +#* postrm `remove' +#* postrm `purge' +#* old-postrm `upgrade' new-version +#* new-postrm `failed-upgrade' old-version +#* new-postrm `abort-install' +#* new-postrm `abort-install' old-version +#* new-postrm `abort-upgrade' old-version +#* disappearer's-postrm `disappear' roverwritr new-version +# for details, see /usr/share/doc/packaging-manual/ +case $1 in + +purge) +# Remove possible conffiles +if [ -e /etc/cron.d/pdbv
Bug#390902: electricsheep dies: X Error of failed request: BadMatch (invalid parameter attributes)
tags 390902 + help tags 390902 + moreinfo thanks * Tom Parker ([EMAIL PROTECTED]) : [EMAIL PROTECTED]:[~] electricsheep X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 141 (XVideo) Minor opcode of failed request: 19 () Serial number of failed request: 159 Current serial number in output stream: 159 zsh: terminated electricsheep Looks like that does happens when the Composite extension is enabled, but not with all graphic cards / devices... Could you precise which X driver you are using (radeon, ati, fglrx, ...)? Thanks. PS: the previous report I got privately was about the same bug on ppc with the driver radeon. -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34[EMAIL PROTECTED] The real glory of maintainership isn't making the big and important decisions. The real glory lies in all the small stuff that doesn't really matter, and that people will just argue forever. -- Linus Torvalds -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#374813: supertuxkart 0.2 is suitable for testing
Gonéri Le Bouder wrote: supertuxkart 0.2 is suitable for testing Great! One more RC bug closed ;-) Cheers, -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34[EMAIL PROTECTED] The real glory of maintainership isn't making the big and important decisions. The real glory lies in all the small stuff that doesn't really matter, and that people will just argue forever. -- Linus Torvalds
Bug#390902: electricsheep dies: X Error of failed request: BadMatch (invalid parameter attributes)
tags 390902 + confirmed retitle 390902 Fails to start when Composite is enabled thanks Tom Parker wrote: Running electricsheep from command line gets the following [EMAIL PROTECTED]:[~] electricsheep X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 141 (XVideo) Minor opcode of failed request: 19 () Serial number of failed request: 159 Current serial number in output stream: 159 zsh: terminated electricsheep I've already been told about that issue, but it is only appearing when the Composite extension is enabled. If you disable that extension is your X configuration, it should work. Regards, -- Alexis Sukrieh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386673: patch
Hi, The patched 2.6.8 version has hit debian unstable yesterday. It did build fine on ppc, great. Though, a user reported that when launching electricsheep (on ppc), he got the following error: $ electricsheep X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 141 (XVideo) Minor opcode of failed request: 19 () Serial number of failed request: 91 Current serial number in output stream: 91 [1]5535 terminated electricsheep But when he launches electricsheep with `--mplayer 1' it did work. As I don't have a sid ppc box, I cannot test that issue, thus I welcome very much ideas and tests. Cheers, -- Alexis Sukrieh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386673: patch
[ I CC Spot, the upstream author ] Steinar H. Gunderson wrote: On Mon, Sep 18, 2006 at 09:05:44AM +0200, Alexis Sukrieh wrote: Hmm, after applying your patch to the sources, I've built the package on my ppc (which is sarge actually) and I got the following assembly error messages: It builds fine in bruckner's sid dchroot, so I assume this is a problem with sarge, not the patch. Great news, I'll apply the patch as soon as I can then. Thanks! -- Alexis Sukrieh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386673: patch
tags 386673 + moreinfo thanks [EMAIL PROTECTED] wrote: Hi, The attached patch works around the problem. Hmm, after applying your patch to the sources, I've built the package on my ppc (which is sarge actually) and I got the following assembly error messages: Making all in libmpeg2 make[4]: Entering directory `/tmp/electricsheep-2.6.8/mpeg2dec/libmpeg2' powerpc-linux-gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I../include-Wall -g -O2 -c decode.c powerpc-linux-gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I../include-Wall -g -O2 -c header.c powerpc-linux-gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I../include-Wall -g -O2 -c stats.c powerpc-linux-gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I../include-Wall -g -O2 -c cpu_state.c /tmp/cchbUeuW.s: Assembler messages: /tmp/cchbUeuW.s:47: Error: Unrecognized opcode: `stvx' /tmp/cchbUeuW.s:49: Error: Unrecognized opcode: `stvx' /tmp/cchbUeuW.s:51: Error: Unrecognized opcode: `stvx' /tmp/cchbUeuW.s:53: Error: Unrecognized opcode: `stvx' /tmp/cchbUeuW.s:55: Error: Unrecognized opcode: `stvx' /tmp/cchbUeuW.s:57: Error: Unrecognized opcode: `stvx' /tmp/cchbUeuW.s:59: Error: Unrecognized opcode: `stvx' /tmp/cchbUeuW.s:61: Error: Unrecognized opcode: `stvx' /tmp/cchbUeuW.s:63: Error: Unrecognized opcode: `stvx' /tmp/cchbUeuW.s:65: Error: Unrecognized opcode: `stvx' /tmp/cchbUeuW.s:67: Error: Unrecognized opcode: `stvx' /tmp/cchbUeuW.s:68: Error: Unrecognized opcode: `stvx' /tmp/cchbUeuW.s:83: Error: Unrecognized opcode: `lvx' /tmp/cchbUeuW.s:85: Error: Unrecognized opcode: `lvx' /tmp/cchbUeuW.s:87: Error: Unrecognized opcode: `lvx' /tmp/cchbUeuW.s:89: Error: Unrecognized opcode: `lvx' /tmp/cchbUeuW.s:91: Error: Unrecognized opcode: `lvx' /tmp/cchbUeuW.s:93: Error: Unrecognized opcode: `lvx' /tmp/cchbUeuW.s:95: Error: Unrecognized opcode: `lvx' /tmp/cchbUeuW.s:97: Error: Unrecognized opcode: `lvx' /tmp/cchbUeuW.s:99: Error: Unrecognized opcode: `lvx' /tmp/cchbUeuW.s:101: Error: Unrecognized opcode: `lvx' /tmp/cchbUeuW.s:103: Error: Unrecognized opcode: `lvx' /tmp/cchbUeuW.s:104: Error: Unrecognized opcode: `lvx' make[4]: *** [cpu_state.o] Error 1 make[4]: Leaving directory `/tmp/electricsheep-2.6.8/mpeg2dec/libmpeg2' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/tmp/electricsheep-2.6.8/mpeg2dec' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/electricsheep-2.6.8' make[1]: *** [all] Error 2 make[1]: Leaving directory `/tmp/electricsheep-2.6.8' make: *** [build-stamp] Error 2 It looks like the patch introduced some unknown opcode. Do you manage to build the package on a ppc architecture? Regards, -- Alexis Sukrieh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386673: confirmed
tags 386673 + confirmed thanks Indeed, seems like electricsheep does not build on ppc since a couple of weeks... I've to investigate that issue. Thanks for the report. Alexis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#329387: [bugzilla #329387] new sarge package that fixes CVE-2005-4534
tags 329387 + pending thanks Hello, I've packaged a new version of bugzilla for closing a security issue reported on sarge: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=329387 This package is 2.16.7-7sarge2 and is available here: http://www.sukria.net/debian/source/bugzilla_2.16.7-7sarge2_i386.changes http://www.sukria.net/debian/source/bugzilla_2.16.7-7sarge2.diff.gz http://www.sukria.net/debian/source/bugzilla_2.16.7-7sarge2.dsc http://www.sukria.net/debian/source/bugzilla_2.16.7.orig.tar.gz It only provides the upstream patch (backported from 2.16.11) that closes that security issue : CVE-2005-4534 If an upload is possible to the security archive, that would be great. Thanks. -- Alexis Sukrieh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#318719: Patch - plays with sound now
Le vendredi 16 juin 2006 à 10:45 +0200, Sam Hocevar a écrit : This patch was in tecnoballz 0.91cvs20060501-1.3 but for some reason it disappeared from 0.91cvs20060612-1. This is my fault, I'm going to commit that patch upstream and then repackage tecnoballz with the reuslting new CVS snapshot. Thanks for the help. Regards, -- Alexis Sukrieh
Bug#318719: Patch - plays with sound now
tags 318719 + pending thanks Hi, I've just applied Sam's last patch (provided in debian package version 0.91cvs20060501-1.3) in the upstream CVS repository. I've packaged the resulting export as version 0.91cvs20060616-1. This bug will then be closed as soon as that package is uploaded to the Debian archive. I guess that now, for real, tecnoballz does run on AMD 64 archs ;-) Thanks for anyone who gave a hand for closing that issue. Best regards, -- Alexis Sukrieh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#318719: Patch - plays with sound now
Le jeudi 15 juin 2006 à 18:32 +0200, Helge Kreutzmann a écrit : tags 318719 + patch thanks robot Looking at the sources and poking around a little. I can always briefly here the sound, and then the crash (backtrace above) and the bug is the same (no two bugs as outlined above), i.e., it crashes at the same spot, same reason all the time. It works, if you apply the attached patch (I played the first two levels with sound with no previous config file in my home dirctory, i.e. it was created automatically with sound). I derived the patch by finding this ugly hack and knowing that assumptions about sizeof(int) are often problems on 64bit architectures. So I don't know if this patch actually is the right way to fix this; please check on a 32bit architecture. Thanks a lot for the patch, I'm going to test it on a 32bit arch very soon. Regards, -- Alexis Sukrieh
Bug#373166: merging #373168 and #373166
merge 373168 373166 tags 373168 + confirmed tags 373166 + confirmed tags 373166 + pending tags 373168 + pending thanks Thos two bugs come from the same problem: a bad presint. The new package is on the way for fixing this. Regards, -- Alexis Sukrieh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366961: bugzilla: Upgrade erases db information from localconfig.
* Steve Langasek ([EMAIL PROTECTED]) disait : Hi Alexis, Any progress on this RC bug? Hi Steve, I'm packaging bugzilla 2.22-1 and have rewrote the postinst script in order to fix that bug. Sadly I really don't have free time currently, my work is requesting a lot of my time ; that's why I lag so much. Anyway, I'll try to prepare and finalize 2.22-1 soon (hopefully this weekend). The package is almost ready but there are still some upgrade issues (from 2.20.1 - 2.22) to solve. Best regards, -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366961: Bugzilla 2.22-1
Hi Frankie, As said on IRC, a new package is abvailble for bugzilla 2.22: http://www.sukria.net/debian/source/bugzilla_2.22.orig.tar.gz http://www.sukria.net/debian/source/bugzilla_2.22-1.diff.gz http://www.sukria.net/debian/source/bugzilla_2.22-1.dsc http://www.sukria.net/debian/source/bugzilla_2.22-1_i386.changes It closes 3 bugs, one of them is RC. Thanks. Alexis. -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org signature.asc Description: Digital signature
Bug#365110: [electricsheep #365110] downgrading severity
severity 365110 important thanks As I cannot reproduce the bug on an etch system, and as I suspect this bug to be closed in 2.6.6-1, I downgrade the severity of this bug in order to let the package entering etch (which is actually the best way to close it). Thanks. -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#365110: [electricsheep #365110] bug closed in 2.6.6-1
tags 365110 + moreinfo tags 365110 + unreproducible thanks Hello, sorry for being so long to answer that report, I really had a lot to do in real life recently... I just installed a fresh new etch system (in a vserver) and installed xscreensaver and electricsheep. I'm surprised, I cannot reproduce that bug. Everything goes fine on my etch system. Anyway, I know that 2.6.5 (the version in etch) is affected by an upstream bug about memory handling, which has been closed in version 2.6.6. I installed 2.6.6-1 (the package is going to be uploaded soon, hopefully) and checked that evrything is ok on etch with this version. So I suppose that the bug your are experiencing will disappear with 2.6.6-1. I welcome a report though, if you can grab the source package from my repo, build it on your etch system and then test it: deb-src http://www.sukria.net/debian ./ apt-get source electricsheep cd electricsheep-2.6.6 dpkg-buildpackage -rfakeroot Thanks for your report. Regards, Alexis. -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org signature.asc Description: Digital signature
Bug#348014: bug seems to be still there
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) disait : I'm just trying to install version 2.20.1-2 on a debian testing and i'm having the same problem reported in this bug. Again the problem has been solved by manually copying params file: cp /usr/share/bugzilla/debian/params.new /etc/bugzilla/params This bugs is going to be closed with the upcoming package version 2.20.1-3 -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366961: bugzilla: Upgrade erases db information from localconfig.
tags 366961 + confirmed thanks * Daniel Kobras ([EMAIL PROTECTED]) disait : When denying to use dbconfig-common on upgrade, the postinst script erases the values of $db_port, $db_name, $db_user, and $db_pass from /etc/bugzilla/localconfig. The values need to be filled in by hand from /etc/bugzilla/localconfig.dpkg.old before the installation is usable again. This bug can be reproduced with dpkg-reconfigure bugzilla as well, denying the first question. The wording of the dbconfig-common question indicates that 'No' is the proper answer on upgrades, ie. when the database for bugzilla has already been set up. Maybe I misunderstood, but in any case postinst must not erase essential local configuration. I'm sorry for this issue, I'm working on fixinf this properly. Thanks for the report. -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337377: Regression regarding the debian-sys-maint user?
* Christian Hammers ([EMAIL PROTECTED]) disait : You might be successfull if you modify your statement to explicitly say GRANT read,write TO ... but although I try not to change the debian-sys-maint user (and IMHO did not during the last months) it's not encouraged to use him and Sean's proposal of using the dbconfig-common would be much better. The last package in sid (2.20.1-2) uses dbconfig-common. Thanks for your comments. -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#364877: bugzilla: Too many arguments for main::fix_pl_scripts_perm
merge 348014 364877 thanks * Jérôme Schneider ([EMAIL PROTECTED]) disait : Package: bugzilla Version: 2.20.1-1 Severity: grave Justification: renders package unusable The installation failed after the configuration : This bug has already been reported and is closed with the last package: 2.20.1-2. This new package has been uploaded yesterday. -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org
Bug#337377: Regression regarding the debian-sys-maint user?
* Christian Hammers ([EMAIL PROTECTED]) disait : You might be successfull if you modify your statement to explicitly say GRANT read,write TO ... but although I try not to change the debian-sys-maint user (and IMHO did not during the last months) it's not encouraged to use him and Sean's proposal of using the dbconfig-common would be much better. Thanks for your comments. I've changed my postinst in order to use dbconfig-common, that works great. Thanks. -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#348014: bugzilla: Installation fails due to broken checksetup.pl script and missing params
tags 348014 + confirmed thanks * Neil Williams ([EMAIL PROTECTED]) disait : Automatic installation fails. Manual configuration after dpkg-reconfigure also fails. [snip] This is a bad hack of a workaround - the package desperately needs these things fixed properly. I'm sorry for this big mistake in the packaging. I'm working on this and prepare a new package for solving this issue. Thanks for the report. Regards. -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337377: (no subject)
tags 337377 - unreproducible tags 337377 - moreinfo tags 337377 + sid tags 337377 + confirmed severity 337377 grave thanks This bugs is reproducible on sid now. After investigating, this really sounds like the mysql-server package changed the rights of the user debian-sys-maint, take a look at the following: $ mysql -uroot -p Password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 22 to server version: 5.0.20-Debian_1-log Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql create database mydbtest; Query OK, 1 row affected (0.00 sec) mysql grant all privileges on mydbtest.* to [EMAIL PROTECTED] identified by 'pass'; Query OK, 0 rows affected (0.00 sec) Now the same commands with the user debian-sys-maint (which is used for granting privileges in the postinst phase of our package). $ mysql -udebian-sys-maint -p Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 21 to server version: 5.0.20-Debian_1-log Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql create database mydbtest2; Query OK, 1 row affected (0.00 sec) mysql grant all privileges on mydbtest.* to [EMAIL PROTECTED] identified by 'pass'; ERROR 1044 (42000): Access denied for user 'debian-sys-maint'@'localhost' to database 'mydbtest' To conclude: the last version of mysql-server in sid does not allow debian-sys-maint to grant privileges. This sounds like a bug as when you look at the rights in the table mysql.user, this user as Grant rights... I'm going to contact the mysql-server(s maintainer Maybe this bug should be reassigned to them. -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org signature.asc Description: Digital signature
Bug#360617: unable to install DBD::mysql::db do failed: Access denied for user 'debian-sys-maint'@'localhost' to database 'bugzilla' at /usr/share/bugzilla/debian/postinst-db.pl line 357, STDIN line
severity 360617 normal tags 360617 + unreproducible tags 360617 + moreinfo thanks * annonygmouse ([EMAIL PROTECTED]) disait : I tried to install, and chose automatic, but afterwards I tried to go back or cancel the configuration with no luck, so I killed all dpkg-preconfigure and tried to start over... with no luck. This looks like your debian-sys-maint user has benn altered since the installation of mysql-server. debian-sys-maint should be able to grant privileges... -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#349812: tagging sarge
tags 349812 + sarge thanks This bug affects only sarge. -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#349812: backup-manager: security update overwrote conffile
tags 349812 + confirmed thanks * Christoph Martin ([EMAIL PROTECTED]) disait : Because /etc/backup-manager.conf is not marked as a conffile, the last security update overwrote my configuration of /etc/backup-manager.conf. I configured an upload via ftp and also MB_POST_BACKUP_COMMAND. The complete configuration is lost, so that no backup to the ftp site was made. This bug was closed in later versions of the package a while ago. Sadly sarge's version is pretty old (0.5.7-1) regarding to sid's one (0.6-1). In later versions of tha pckage, ucf is used in order to prevent such bad things. I would suggest to use the backport in the meantime. -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344653: electricsheep - FTBFS: cannot find -lX11
tags 344653 + pending thanks * Stephen Gran ([EMAIL PROTECTED]) disait : The addition of libx11-dev, libxext-dev and x-dev are because the package #includes headers from those packages. I only did a simplistic grep test, so it may be over generous in my dependency (for instance, if a chunk of source is not actually built or used, my test would miss that completely). The addition of libxt-dev is for the configure test for X (it looks for X11/Intrinsic.h from the libxt-dev package) and then fills in the autoconf macro X_LIBS=' -L/usr/X11R6/lib'. Without this bit, linking fails. With it, it succeeds. The fact that /usr/X11R6/lib is in /etc/ld.so.conf and the linker still doesn't look there is a bit mystifying (as I thought that's, er, exactly what that file is for) but that's a seperate problem. Thanks a lot. Your patch fixes that issue. I applied it and built a 2.6.4-2 package successfully in my pbuilder. My sponsor will upload the new package as soon as he has the time. Best wishes and merry christmas! -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#329387: bugzilla security update for sarge (2.16.7-7sarge2)
* Martin Schulze ([EMAIL PROTECTED]) disait : Do you happen to know about the package in woody? Well, I don't know. Where can I grab woody's source packages? a) what about woody As soon as I know where to fetch woody's sources, I will tell you. b) what about sid Sid is not affected, the vulnerable script does not exist in the sid version. -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344653: electricsheep - FTBFS: cannot find -lX11
tags 344653 + help tags 344653 + confirmed thanks * Bastian Blank ([EMAIL PROTECTED]) disait : There was an error while trying to autobuild your package: /usr/bin/ld: cannot find -lX11 collect2: ld returned 1 exit status Indeed, I reproduced that with my pbuilder... I'm a bit confused, because even if I add libx11-6 in my build-dependencies (which provides libX11.so.6) I still get the error. I don't know how to solve that build issue, if someone can give me a hand, that's very welcome... -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344653: electricsheep - FTBFS: cannot find -lX11
* Steve Langasek ([EMAIL PROTECTED]) disait : I'm a bit confused, because even if I add libx11-6 in my build-dependencies (which provides libX11.so.6) I still get the error. Er, you need the package that provides *libX11.so*, not libX11.so.6. You should be build-depending on libx11-dev, not on libx11-6: you should *never* need to build-depend on runtime lib packages. My package *did* build-depend on libx11-dev, and I got the FTBS even with that build-dependcy. As I was puzzled, I tried to add libx11-6 in my build dependcy, in order to try. But whatever I did, I get a FTBS in my pbuilder... -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#338743: [bluez-utils #338743] More info
tags 338743 + patch
thanks
* Marco d'Itri ([EMAIL PROTECTED]) disait :
cd /dev ./MAKEDEV bluetooth
less /sbin/MAKEDEV
Thanks, here is attached a patch for the postinst script.
I plan to make a sponsored NMU for closing this RC bug in bluez-utils'
maintainer does not apply it.
Best regards,
--
Alexis Sukrieh [EMAIL PROTECTED]
0x1EE5DD34
Debian http://www.debian.org
Backup Manager http://www.backup-manager.org
diff -ubBr bluez-utils-2.19/debian/bluez-utils.postinst
bluez-utils-2.19.orig/debian/bluez-utils.postinst
--- bluez-utils-2.19/debian/bluez-utils.postinst2005-12-23
09:36:11.0 +0100
+++ bluez-utils-2.19.orig/debian/bluez-utils.postinst 2005-12-23
09:35:40.0 +0100
@@ -24,36 +24,9 @@
# Amended by Edd Dumbill [EMAIL PROTECTED] for
# the Debian distribution and to support devfs
- VHCI_MAJOR=10
- VHCI_MINOR=250
-
- RFCOMM_MAJOR=216
-
- # if devfs isn't mounted on /dev/ or we're not
- # using udev, then we need to create the device names
-
- if [ ! -e /dev/.devfsd -a ! -e /dev/.udevdb ]; then
- echo Checking and creating device nodes ...
- #
- # Create device for VHCI
- #
- if [ ! -c /dev/vhci ]; then
- mknod /dev/vhci c ${VHCI_MAJOR} ${VHCI_MINOR}
- chmod 660 /dev/vhci
- fi
-
- #
- # Create devices for RFCOMM
- #
- C=0;
- while [ $C -lt 256 ]; do
- if [ ! -c /dev/rfcomm$C ]; then
- mknod -m 660 /dev/rfcomm$C c
${RFCOMM_MAJOR} $C
- chgrp dialout /dev/rfcomm$C
- fi
- C=`expr $C + 1`
- done
- fi
+# Policy says we must not use mknod in maintainer scripts,
+# using MAKEDEV instead.
+cd /dev ./MAKEDEV bluetooth
# handle the devfs case
if [ -e /dev/.devfsd ]; then
Bug#318719: [tecnoballz #318719] Bug still open?
tags 318719 + moreinfo thanks Hello, I'd like to know if the last package closed this bug. Indeed, there is a patch applied in the last version for AMD 64 support. Could you tell me if you can reproduce the bug with the package version 0.91cvs2005082? Thanks. -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#329387: bugzilla security update for sarge (2.16.7-7sarge2)
Hi, I'm the maintainer of the backup manager package. There are currently one security issue in our sarge package (0.5.7-7sarge1). I made a package with the patch submitted against the bug #329387 which closes the issue. Can we plan to upload that package to security updates? The package is available on my repository: deb-src http://www.sukria.net/debian ./ Changes: http://www.sukria.net/debian/source/bugzilla_2.16.7-7sarge2_i386.changes Diff.gz: http://www.sukria.net/debian/source/bugzilla_2.16.7-7sarge2.diff.gz Dsc: http://www.sukria.net/debian/source/bugzilla_2.16.7-7sarge2.dsc Regards, -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org signature.asc Description: Digital signature
Bug#318719: [tecnoballz #318719] Bug still open?
* Andreas Jochens ([EMAIL PROTECTED]) disait : Could you tell me if you can reproduce the bug with the package version 0.91cvs2005082? I can not reproduce the bug with the latest version. So this seems indeed to be fixed, thanks! Great! Thanks, I'm closing the bug. -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#329387: bugzilla security update for sarge (2.16.7-7sarge2)
* Alexis Sukrieh ([EMAIL PROTECTED]) disait : I'm the maintainer of the backup manager package. ^^ Of course I was speaking about bugzilla, not backup-manager, sorry! (Hopefully I'm on holydays this evening ;) -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#251159: Bug still open?
Hello, I was looking for some RC bugs to close and found that one. When I look to the debian/control file, I don't see any build-dependency against libssl0.9.7, but a one against libssl-dev which is good. Moreover, looking to the binary package in sid, I find that the dependency is good: Depends: libc6 (= 2.3.5-1), libssl0.9.8, common-lisp-controller (= 3.37), cl-split-sequence, cl-uffi So I guess that bug can be closed by hand, can't it? Regards, -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#237156: Bug should be closed
Hello, I was looking for some RC bugs and found that one. I think we can safely close that bug as it was affecting woody and is not still valid in sid. -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#251159: Bug still open?
* Christoph Martin ([EMAIL PROTECTED]) disait : So I guess that bug can be closed by hand, can't it? I think you have to wait some more time. It looks like someone did a non maintainer binary only upload: Well, ok, but I think NMU'ing the source package is welcome, isn't it? -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#338743: [bluez-utils #338743] More info
Hello, I was looking for some RC bugs and found that one. I'd like to help if I can and I started investigating. The problem is that bluez-utils' postinst script creates two devices nodes: - /dev/vhci (major 10, minor 250) - /dev/rfcomm (major 216, minor 0-255) I looked at the MAKEDEV manpage but didn't find any information about how to create those nodes. Where can I find more information about that? Thanks. Regards, -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#251159: Bug still open?
* Christoph Martin ([EMAIL PROTECTED]) disait : If I understand this correct the packages has only to be rebuild and no changes have to be make in the sources. What do you want to change in the sources for the NMU? Well, I thought the source should have been sync with the binary. Forget my mail if that's useless. I was also thinking that a changelog entry would have been cleaner than a binary-only NMU. But I must be wrong, sorry for the noise. -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#326362: [fuzz #326362] Is a NMU welcome?
Hello, While in the NM process, I'm looking for some RC bugs to close and I found that one. I try to build fuzz with a build-dependency against libreadline5-dev in my sid pbuilder environement and it worked. If needed, I can ask my sponsor for NMU'ing the package, is that welcome? Regards, -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#251159: [Pkg-openssl-devel] Re: Bug#251159: Bug still open?
Hi Christoph, * Christoph Martin ([EMAIL PROTECTED]) disait : But I must be wrong, sorry for the noise. No. Thanks for your work. If you think a real NMU would make the case clearer and speed up the inclusion in testing, go ahead. The maintainer of cl-tclink is really not responsive. Ok, then I'll contact my sponsor for NMU'ing this package. Thanks for your responses. I do think it's cleaner to have a changelog entry whenever something changes in the Debian archive. Regards, -- Alexis Sukrieh [EMAIL PROTECTED] 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#303156: tecnoballz: FTBFS (amd64/gcc-4.0): cast from 'ecran_hard*' to 'Sint32' loses precision
close 303156 thanks Le mercredi 19 octobre 2005 à 21:00 +1000, Rob Weir a écrit : Hi Alexis, this bug seems to be fixed in your recent uploads to sid; perhaps it should be closed? -rob -- Alexis Sukrieh [EMAIL PROTECTED]
Bug#335519: Bug affects only sarge
tags 335519 + sarge tags 335519 + confirmed severity 335519 important thanks This bug affects only sarge, packages in testing/unstable are not affected. Moreover, it onnly affects people who use the upload system with FTP, which is not the default case. That's why I reduce the severity of the bug to important (a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone). Regards. -- Alexis Sukrieh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#303156: tecnoballz: FTBFS (amd64/gcc-4.0): cast from 'ecran_hard*' to 'Sint32' loses precision
Le mercredi 19 octobre 2005 à 21:00 +1000, Rob Weir a écrit : On Wed, Apr 06, 2005 at 08:36:21AM +0200, Alexis Sukrieh said * Alexis Sukrieh ([EMAIL PROTECTED]) disait : I have sent a mail to upstream author, forwarding him the patch and asking for a new upstream release when possible. Upstream author just confirmed that he will apply your patch in the sources. Then, I'm waiting for a new upstream version of TecnoballZ to close that bug. Hi Alexis, this bug seems to be fixed in your recent uploads to sid; perhaps it should be closed? Ok, as I do't have any amd64 at home, I was not able to close it by my self. Could you look if the other AMD64 bug is closed? http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=318719 If so, I'll close the two bugs in our BTS and will infomr upstream developer that the current cvs source tree is AMD 64 compliant ;) Alexis. -rob -- Alexis Sukrieh
Bug#331206: bugzilla: Two information disclosure vulnerabilities in Bugzilla
tags 331206 + confirmed thanks * Moritz Muehlenhoff ([EMAIL PROTECTED]) disait : [...] Please see http://www.bugzilla.org/security/2.18.4/ for the full advisory. 2.18.4 fixes these issue. Ok, I'll then package 2.18.4 as soon as possible for closing those issues. Thanks for the report. -- Alexis Sukrieh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#331206: (no subject)
tags 331206 + pending thanks This bug is closed in the svn package `bugzilla 2.18.4-1'. It will be uploaded soon. Thanks for the report. -- Alexis Sukrieh
Bug#321567: Bugzilla bugs closed in SVN, pending upload
tags 321567 + pending tags 252076 + pending tags 305360 + pending tags 320004 + pending tags 327063 + pending tags 312925 + pending thanks This bug has been closed in the SVN repository of bugzilla. You can grab the latest version with the following command line: svn co svn://svn.debian.org/svn/pkg-bugzilla/bugzilla/trunk This bug will be closed as soon as the new package is uploaded (2.18.3-2). Regards. -- - Alexis Sukrieh signature.asc Description: Digital signature
Bug#321567: bug 321567 confirmed
tags 321567 + confirmed thanks Thanks for the report, I'm going to apply this patch for the next upload. Regards. -- - Alexis Sukrieh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#315582: [backup-manager] Pending security upload
tags 308897 + pending tags 315582 + pending thanks This two bugs are fixed in the new pending sarge package (0.5.7-1sarge1), which will be uploaded hopefully to the security archive soon. Regards. -- - Alexis Sukrieh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#318003: (forw) [EMAIL PROTECTED]: Bug#318003: electricsheep: segfaults on powerpc]
Hello. I started building mpeg2dec_onroot against the actual libmpeg2-4-dev we have in debian. As expected, there are changes to be made. The first one is to use mpeg2_tag_picture() instead of mpeg2_pts() which has been droped. Second, we should use a pointer to mpeg2dec: - static mpeg2dec_t mpeg2dec; + static mpeg2dec_t *mpeg2dec; The last change to made is the most difficult one: the function mpeg2dec_decode_data does not exist anymore, and no other function has the same prototype. It seems that we should use mpeg2dec_buffer() which takes the same args but return a stat einstead of a frame number. Moreover, data has to be parsed by mpeg2dec_parse(). I cannot manage currently to have it working well, any help is welcome :) Spot, if you can take a look at this migration ,I would be glad :-) -- - Alexis Sukrieh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#318719: It's a 64bit issue
* Helge Kreutzmann ([EMAIL PROTECTED]) disait : severity 318719 grave thanks dude Hello, I just got the confirmation on debian-alpha, that indeed tecnoballz segfaults there as well. I expect ia64 to follow suit (given the reasoning in my above mail). Since alpha is released, this bug is hence RC. Thanks for all your comments, and sorry for the crappy build rules, that's my first package using autoconf, and I agree, it's really in a bad shape. I would suggest to apply the patch submitted for #303156, wich should fix the 64bit related issues, and see if that stop the segfault. Moreover, I cannot upload a new package now, because tecnoballz *does not* build with gcc 4.0, there is a lot of work behind... Thanks. -- - Alexis Sukrieh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#318003: (forw) [EMAIL PROTECTED]: Bug#318003: electricsheep: segfaults on powerpc]
* Paul Brossier ([EMAIL PROTECTED]) disait : Alexis, i noticed another issue: a copy of the mpeg2 library is included in the source and compiled. spot, i see parts of the mpeg2 code were modified, but it would be much better if mpeg2dec_onroot could be linked against debian's libmpeg2-4. I tried to build a package depending on mpeg2dec and libmpeg2-4, but unfortunately, electrichseep's customized version of mpeg2dec has special switches (-w and -f) that don't exist in the official mepg2dec. Moreover, if I disable those switch in electricsheep, I got the following error: ./electricsheep mpeg2dec-0.4.0 - by Michel Lespinasse [EMAIL PROTECTED] and Aaron Holtzman Unaligned buffers. Anyone know how to fix this ? Then, it doesn't seem to be an easy game to switch to the official mpeg2dec binary, electricsheep is deeply bound to its own version. -- - Alexis Sukrieh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#315582: Bugs closed in etch and sid
tags 308897 - etch tags 315582 - etch thanks The 0.5.8-2 package is in testing now and closes those bugs. -- - Alexis Sukrieh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#315582: [backup-manager #315582] Bug still open in sarge
reopen 315582 thanks This bug is closed in sid, but still opened in sarge. It will will be closed in etch as soon as the package propagate (I'll then remove the etch tag). Regards. -- - Alexis Sukrieh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#312569: [electricsheep #312569] Fixed?
I could not reproduce this bug with the last version. Thanks for upgrading :) Thanks, I close the bug. -- - Alexis Sukrieh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#315582: unmerging
unmerge 315582 thanks That's not the same problem as the one in #308897. -- Alexis Sukrieh [EMAIL PROTECTED] http://www.sukria.net « Quidquid latine dictum sit, altum sonatur. » Whatever is said in Latin sounds profound.
Bug#308897: backup-manager security fixes, pending upload.
tags 315582 + pending tags 315582 + pending thanks Those two security issues are pending upload. The security team has been contacted for uploading a fixed package to stable. Thanks for the report and the patches. For testers, pending packages are available here: For sarge: http://www.sukria.net/debian/binary/backup-manager_0.5.7-2sarge1_all.deb For sid/etch: http://www.sukria.net/debian/binary/backup-manager_0.5.8-2_all.deb You'll can find the sources of those packages here: http://www.sukria.net/debian/source/ Regards. -- Alexis Sukrieh [EMAIL PROTECTED] http://www.sukria.net « Quidquid latine dictum sit, altum sonatur. » Whatever is said in Latin sounds profound.
Bug#312569: [electricsheep #312569] Fixed?
tags 312569 + moreinfo thanks Please could you reproduce that bug with the new package we uploaded? Unstable now provides 2.6.2. I'm looking forward to your comments, in order to close that bug if it's not reproducible with the new upstream release. -- Alexis Sukrieh [EMAIL PROTECTED] http://www.sukria.net « Quidquid latine dictum sit, altum sonatur. » Whatever is said in Latin sounds profound.
Bug#284835: [electricsheep #284835] Woody bugs are closed
This bug is closed now, woody is dropped. -- Alexis Sukrieh [EMAIL PROTECTED] http://www.sukria.net Quidquid latine dictum sit, altum sonatur. Whatever is said in Latin sounds profound.
Bug#308232: Pending upload
tags 308232 + pending tags 308789 + pending tags 309227 + pending tags 309475 + pending tags 311169 + pending tags 311980 + pending thanks Those bugs are pending upload. Fixed in the SVN repository, release: 2.18-7. Cheers. -- Alexis Sukrieh [EMAIL PROTECTED] http://www.sukria.net « Quidquid latine dictum sit, altum sonatur. » Whatever is said in Latin sounds profound.
Bug#308897: backup-manager: insecure default configuration
tags 308897 + pending thanks * Paul Brossier ([EMAIL PROTECTED]) disait : please correct me if this is over inflated severity. justification: introduces a security hole on systems where you install the packages in its default configuration, backup-manager stores a .tar.gz of /etc in /var/backups. this file is world readable, so that any local user is able to read /etc/shadow, /etc/ppp/chap-scripts and other interesting bits from it. You're absolutely right. This bug is closed in the upcoming new upstream version 0.5.8 I'll ask my sponsor to upload the new package as soon as the upstream release is ready. a solution to this problem is to have backup-manager create files with perms 0700. I chose the solution to add two new configuration keys: BM_USER and BM_GROUP. The archives repository will be chowned to $BM_USER:$BM_GROUP and will be chmoded 660 -- Alexis Sukrieh [EMAIL PROTECTED] http://www.sukria.net « Quidquid latine dictum sit, altum sonatur. » Whatever is said in Latin sounds profound.
Bug#308232: [bugzilla #308232] confirmed
tags 308232 + confirmed thanks Indeed, I confirm this is only a 2.18 issue. The 2.18 package did not entered sarge. I'll certainly come back to the /var/lib/bugzilla directory for $datadir, as it was done for the 2.16 package. Thanks for the report. -- Alexis Sukrieh [EMAIL PROTECTED] http://www.sukria.net « Quidquid latine dictum sit, altum sonatur. » Whatever is said in Latin sounds profound.
Bug#308232: bugzilla: [FHS] Creates tempfiles on /usr/share.
tags 308232 + pending thanks Bug closed in the SVN repository: http://svn.debian.org/wsvn/pkg-bugzilla/trunk/bugzilla-2.18/debian/changelog?op=filerev=0sc=0 I now use /var/lib/bugzilla for the root dir of every data files, which is FHS compliant. Thanks for the report. Regards. -- Alexis Sukrieh [EMAIL PROTECTED] http://www.sukria.net « Quidquid latine dictum sit, altum sonatur. » Whatever is said in Latin sounds profound.
Bug#84368: [debget] all RC bugs closed with this patch
tags 278675 + patch
tags 84368 + patch
tags 306924 + patch
thanks
Hello, I know debget is not in testing and is supposed to be removed
soon, anyway, the patch here will fix all of those RC bugs against it.
If that can help...
--
Alexis Sukrieh [EMAIL PROTECTED]
http://www.sukria.net
« Quidquid latine dictum sit, altum sonatur. »
Whatever is said in Latin sounds profound.
--- /usr/bin/debget 2005-05-06 16:26:11.038703952 +0200
+++ debget 2005-05-06 17:17:45.119332200 +0200
@@ -251,7 +251,7 @@
# Getopt::Long has some really awful defaults. This function loads it
# then configures it to use more sane settings.
-sub getopt;
+sub getopt(@);
sub configure_getopt {
Getopt::Long-import(2.11);
*getopt = \Getopt::Long::GetOptions;
@@ -302,21 +302,37 @@
# (source/binary) for the given DISTRIBUTION, SECTION1 and SECTION2.
sub file_dir {
-my ($type, $dist, $sec1, $sec2) = @_;
+my ($type, $dist, $sec1, $sec2, $package) = @_;
+
+# first generate the prefix
+my $initial = $package;
+$initial =~ s/^(.).*$/$1/ if $package !~ /^lib/;
+$initial =~ s/^(.{4}).*$/$1/ if $package =~ /^lib/;
$sec2 = /$sec2 if $sec2 ne '';
+my $prefix = ;
+# experimental is the simple case
if ($dist eq 'experimental') {
return 'project/experimental';
}
-if ($type eq 'source') {
- return dists/$dist/$sec1/source$sec2;
+# for unstable and testing, look to the pool
+# debian/pool/$section/$initial/$sourcepackage/
+elsif ($dist eq 'testing' or $dist eq 'unstable') {
+ $prefix = pool/$sec1/$initial;
+ return $prefix/$package;
}
+# Here, we manage the stable stuff
+$prefix = dists/$dist/$sec1;
+
if ($type eq 'binary') {
my $arch = arch;
- return dists/$dist/$sec1/binary-$arch$sec2;
+ return $prefix/binary-$arch$sec2;
+}
+elsif ($type eq 'source') {
+ return $prefix/source$sec2;
}
xdie invalid type `$type';
@@ -507,13 +523,13 @@
my ($s1, $s2, $p) = package_section package_source($package),
$orig_package;
push @ret, [host_dir($s1),
- file_dir('source', $O{'dist'}, $s1, $s2),
+ file_dir('source', $O{'dist'}, $s1, $s2, $package),
^\Q$p\E_.*\\.(dsc|tar\\.gz|diff\\.gz)\$];
}
if ($O{'binary'}) {
my $arch = arch;
push @ret, [host_dir($sec1),
- file_dir('binary', $O{'dist'}, $sec1, $sec2),
+ file_dir('binary', $O{'dist'}, $sec1, $sec2, $package),
^\Q$package\E_[^_]+(_(\Q$arch\E|all))?\\.deb\$];
}
return @ret;
Bug#303454: (no subject)
severity 303454 minor thanks I'm afraid but a bug which is not related to the Official Debian Archive could not be flaged grave. -- Alexis Sukrieh [EMAIL PROTECTED] http://www.sukria.net « Quidquid latine dictum sit, altum sonatur. » Whatever is said in Latin sounds profound.
