Bug#35955: Fehler in Ihrer E-Mail!
In Ihrer E-Mail mit dem Betreff Breathtaking image for your company NOW an den/die Empfänger [EMAIL PROTECTED] ist ein Fehler aufgetreten. Die Nachricht konnte nicht geprüft werden und wurde deshalb in Quarantäne gestellt. Sollen wir Ihre E-Mail ungeprüft weiterleiten, senden Sie uns diese Benachrichtigung an [EMAIL PROTECTED] Diese Nachricht enthält für uns alle wichtigen Angaben [EMAIL PROTECTED]; Sun, 29 Oct 2006 19:27:33 +], um eine rasche Weiterleitung ihrer E-Mail zu ermöglichen.
Bug#394084: pycentral breaks if python-all is not available
Package: python-central Version: 0.5.6 pycentral calls apt-cache to obtain the dependencies of the python-all package. If apt-cache returns nothing, pycentral ends up traversing an empty list (the python None value) which causes it to abort. As pycentral is called from the postinstall scripts of many packages, this causes a problem. I'm not sure if it is ok to expect python-all to be available at all times, but at the very least pycentral must deal with this problem a bit more gracefully. Perhaps, if python-all is not available, it could call python -V instead and do the work for the default python? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#748345: nslcd: Missing space in ldapns.ldif
Package: nslcd Version: 0.8.10-4 Severity: normal Tags: patch Dear Maintainer, * What exactly did you do (or not do) that was effective (or ineffective)? Add white space between 'top' and 'AUXILIARY' -- System Information: Debian Release: 7.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- old/ldapns.ldif 2014-05-16 13:18:18.592903549 +0200 +++ new/ldapns.ldif 2014-05-16 13:18:34.852895126 +0200 @@ -9,7 +9,7 @@ 'IANA GSS-API authorized service name' EQUALITY caseIgnoreMatch SYNTAX 1.3.6. 1.4.1.1466.115.121.1.15{256} ) olcObjectClasses: {0}( 1.3.6.1.4.1.5322.17.1.1 NAME 'authorizedServiceObject' - DESC 'Auxiliary object class for adding authorizedService attribute' SUP top + DESC 'Auxiliary object class for adding authorizedService attribute' SUP top AUXILIARY MAY authorizedService ) olcObjectClasses: {1}( 1.3.6.1.4.1.5322.17.1.2 NAME 'hostObject' DESC 'Auxilia ry object class for adding host attribute' SUP top AUXILIARY MAY host )
Bug#667641: mailfront: hangs unexpectedly
Package: mailfront Version: 1.16-1 Severity: important We have experienced several cases in which mailfront has hung unexpectedly. qmaild 14431 0.0 0.0 2000 796 ?SApr03 0:00 /usr/sbin/mailfront smtp qmail check-fqdn counters mailrules relayclient cvm-validate qmail-validate add-received patterns accept-sender It appears to be hung in the middle of a write: # strace -p 14431 Process 14431 attached - interrupt to quit write(6, "q3T7JU+Z8WimlbpoIn3eT+2R2H5L1Bht"..., 4096^C Process 14431 detached Most mailfront invocations go through smoothly, but we get a few of these a week. -- System Information: Debian Release: 6.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages mailfront depends on: ii libbg11.106-1BG Libraries Collection ii libc6 2.11.3-2 Embedded GNU C Library: Shared lib ii libcvm1 0.96-1 Credential Validation Modules (sha Versions of packages mailfront recommends: pn ipsvd (no description available) pn runit (no description available) mailfront suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#757242: pdns-server: PowerDNS not transfer primary-level zones
Hi, i solved this problem! If create record aaa.bbb.mydomain.net on PowerAdmin, PowerAdmin same create record bbb.mydomain.net with NULL in content, and if `content` == NULL, zone not transfering. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#531546: Acknowledgement (cacti in lenny can no longer graph)
Hello, I have made some more test on this and it is now clear that the problem is with the old rra files. What is puzzling is that they use the same database level as the previous version of rrdtool (1.2 in etch). So I am at a loss to understand what is happening but the test I verified is fairly simple : On a Lenny installation, if you start with fresh rra files, cacti graphs, if you import rra files from a previous installation (etch), no graphing occurs anymore. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#600182: ntp: NTP switching from kernel time sync status change 4001 to 0001 caused server to stop responding
Package: ntp Version: 1:4.2.4p4+dfsg-8lenny3 Severity: critical Justification: breaks the whole system Hi There, We've just had an issue were a server became unresponsive after NTP started switching status as per the daemon log below: Oct 13 19:15:44 mb ntpd[1966]: kernel time sync status change 4001 Oct 13 20:06:59 mb ntpd[1966]: kernel time sync status change 0001 Oct 13 20:41:09 mb ntpd[1966]: kernel time sync status change 4001 Oct 13 20:58:14 mb ntpd[1966]: kernel time sync status change 0001 Oct 13 21:43:43 mb afpd[5409]: afp_alarm: child timed out Oct 13 21:43:43 mb afpd[5409]: 44.10KB read, 650.20KB written Oct 13 21:43:43 mb afpd[5409]: Connection terminated Oct 13 21:43:43 mb afpd[2052]: server_child[1] 5409 exited 1 Oct 13 21:49:26 mb ntpd[1966]: kernel time sync status change 4001 Oct 13 22:06:30 mb ntpd[1966]: kernel time sync status change 0001 Oct 14 00:06:00 mb ntpd[1966]: kernel time sync status change 4001 Oct 14 00:23:06 mb ntpd[1966]: kernel time sync status change 0001 Oct 14 00:57:16 mb ntpd[1966]: kernel time sync status change 4001 Oct 14 01:48:31 mb ntpd[1966]: kernel time sync status change 0001 Oct 14 02:56:49 mb ntpd[1966]: kernel time sync status change 4001 Oct 14 03:48:02 mb ntpd[1966]: kernel time sync status change 0001 Oct 14 06:38:45 mb ntpd[1966]: kernel time sync status change 4001 Oct 14 08:21:13 mb ntpd[1966]: kernel time sync status change 0001 Oct 14 09:46:37 mb ntpd[1966]: kernel time sync status change 4001 Oct 14 10:03:40 mb ntpd[1966]: kernel time sync status change 0001 Once the server was rebooted, netatalk (afpd) clients could reconnect again. and SSH connections once again worked. I'm not 100% sure that NTP caused the issue, as the status changes have been reported previously without causing unresponsiveness. However there is no other logs indicating any other failures. Regards, Mark -- System Information: Debian Release: 5.0.6 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ntp depends on: ii adduser 3.110add and remove users and groups ii libc6 2.7-18lenny4 GNU C Library: Shared libraries ii libcap1 1:1.10-14support for getting/setting POSIX. ii libedit22.11~20080614-1 BSD editline and history libraries ii libncurses5 5.7+20081213-1 shared libraries for terminal hand ii libssl0.9.8 0.9.8g-15+lenny8 SSL shared libraries ii lsb-base3.2-20 Linux Standard Base 3.2 init scrip ii netbase 4.34 Basic TCP/IP networking system Versions of packages ntp recommends: ii perl 5.10.0-19lenny2 Larry Wall's Practical Extraction Versions of packages ntp suggests: pn ntp-doc(no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#884964: using "su - " in postinst causing some installs to fail
Package: debconf-doc Version: 1.5.61 The use of "su - " in postinst is breaking package installs/upgrades only when there are file(s) in /etc/profile.d. Details are in the two bug reports: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884955 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875958 I do not know what other packages may use "su - " but would suggest that this issue be documented in debconf-doc so maintainers/devs can avoid this. If I should file this some place else, please let me know. Thank you. -- Terry LinuxChix System Admins
Bug#884964: using "su - " in postinst causing some installs to fail
Simon, Thank you for your comments. > Arguably the bug here is that there was a file in /etc/profile.d that > assumed bash syntax, rather than guarding bashisms with a check for > $BASH_VERSION or similar. I would recommend changing those profile > snippets so the problematic parts only run on shells that are known to > support them (bash and maybe zsh). > > For many uses of profile snippets, it would make sense to wrap them in > a guard against non-interactive shells, which also dodges any issues > that those snippets might cause in non-interactive shells. > > smcv > I've done quite a bit more testing on this. I've had three packages with this issue - spamassassin, sa-compile and tuptime. The user for spamassassin and sa-compile is debian-spamd whose shell is set to /bin/sh. The user for tuptime is tuptime whose shell is also set to /bin/sh. Changing the shell to /bin/bash for tuptime for example, eliminates the error with using 'su -'. I did note that the package postgresql-common calls the Bourne shell in postinst but without a login and this poses no problem during installation: su -s /bin/sh postgres -c "test -O /var/lib/postgresql && test -G /var/lib/postgresql" || \ chown postgres:postgres /var/lib/postgresql The postgres user's shell is /bin/bash but I don't think this matters because login isn't being used so /etc/profile.d files aren't being read. Aliases present no problem. Functions, depending on how they are written, do. function somefunction () {} causes a problem. function somefunction {} causes a problem. somefunction () {} does not. So there's the bashism - using the reserved word 'function'. Interestingly, when using the reserved word function, the presence of () changes the error message. With the use of (): -sh: 5: /etc/profile.d/test.sh: Syntax error: "(" unexpected (expecting "fi") Without the use of (): -sh: 5: /etc/profile.d/test.sh: function: not found Definitely would have been much easier to spot the error had we not used (). Wrapping the function with this worked. if [ "${BASH-}" ] && [ "$BASH" != "/bin/sh" ]; then function testfunction { echo 'Function from test.sh in /etc/profile.d' } fi Doing the same thing but with the () included did not work. That has me scratching my head. It should have bypassed those lines entirely. I'll update the bug reports I've filed in the packages with this information. I'm not sure there's a good solution for this. It seems to be such a specific issue. Had I not created a user with a /bin/sh shell and tried to recreate the function for that user, I'm not sure I would have twigged that the reserved word function was causing the problem since the error kept coming back as the ( causing the issue. Anyway, thanks again for your comments. It spurred me to investigate further. -- Terry
Bug#884964: Bug#875958: sa-compile: The package fails to run sa-compile
An update. We experienced the same problem with the package tuptime and I filed a bug report there[1]. I had some comments from the other bug reports which led me to do some more testing. Here's what I found. Three packages have had this issue - spamassassin, sa-compile and tuptime. The user for spamassassin and sa-compile is debian-spamd whose shell is set to /bin/sh. The user for tuptime is tuptime whose shell is also set to /bin/sh. No other users on my system use /bin/sh. Changing the shell to /bin/bash for tuptime for example, eliminates the error with using 'su -'. The aliases in the /etc/profile.d files present no problem. Functions, depending on how they are written, do. function somefunction () {} causes a problem. function somefunction {} causes a problem. somefunction () {} does not. Using the reserved word 'function' causes /bin/sh to throw an error. Interestingly, when using the reserved word function, the presence of () changes the error message. With the use of (): -sh: 5: /etc/profile.d/test.sh: Syntax error: "(" unexpected (expecting "fi") Without the use of (): -sh: 5: /etc/profile.d/test.sh: function: not found Definitely would have been much easier to spot the error had we not used (). So while calling a login shell caused a problem, ultimately, it's because /bin/sh does not recognise the reserved word 'function'. I'm not sure there's a good solution for this. It seems to be such a specific issue. Had I not created a user with a /bin/sh shell and tried to recreate the function for that user, I'm not sure I would have twigged that the reserved word function was causing the problem since the error kept coming back as the "(" causing the issue. At least you're aware if this is ever reported again. I hope this provides some clarification and allows you to reproduce the issue. In testing, four things fixed the issue: 1. Setting a user's shell to /bin/bash. 2. Using su without "-" 3. removing the reserved word function from the function 4. Wrapping the function with a test for bash but it behaved strangely. It worked if no "()" was present but if it was present, we had an error. Unexpected. We're still testing. We've chosen to remove the reserved word function so now our functions are simply somefunction () which solves the issue for us. Thank you. -- Terry LinuxChix System Admins [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884955
Bug#884964: using "su - " in postinst causing some installs to fail
Thank you again, Simon, for your concise explanations. We do have a policy on shell usage and the snippets were tested against those shells, but not against /bin/sh. My fault, I'm afraid, since I hadn't considered system users. We'll be adding that to our policy. I've sent the info to the two packages I filed bug reports for. Hopefully, the next time someone runs into the issue, they'll be able to come across these discussions and resolve it quickly. -- Terry
Bug#875958: sa-compile: The package fails to run sa-compile
The problem seems to occur only if you have script(s) in /etc/profile.d. On the last upgrade to 9.3 Stretch, we experienced this issue. Also, see comment by Vagnerr at https://askubuntu.com/questions/422264/how-to-debug-dpkg-configure-error-in-subprocess-post-installation describing this problem from May 2015. "I had a similar issue to you. With the installer just flat failing. Mine turned out to be an issue with installing the latest version from debian-backports for wheezy. It turned out that they changed the post install script to have a 'su - $OWNER -c "sa-update ...' call which did a full login shell exec to /bin/sh which was incompatible with our /etc/profile and /etc/profile.d files. removing the '-' making it "su $OWNER -c " fixed it for me – Vagnerr May 16 '15 at 14:43" I can confirm that removal of the file in /etc/profile.d fixed the problem. The file in question is /var/lib/dpkg/info/sa-compile.postinst, line 10, which reads: su - $OWNER -c "sa-compile --quiet" Here is the relevant portion of the transcript from our upgrade highlighting the issue with /etc/profile.d. Setting up spamassassin (3.4.1-6+deb9u1) ... Installing new version of config file /etc/cron.daily/spamassassin ... Installing new version of config file /etc/spamassassin/65_debian.cf ... -su: 19: /etc/profile.d/lcx_all_users_aliases.sh: Syntax error: "(" unexpected dpkg: error processing package spamassassin (--configure): subprocess installed post-installation script returned error exit status 2 Setting up zsh (5.3.1-4+b2) ... Setting up libicu57:amd64 (57.1-6+deb9u1) ... Setting up iproute2 (4.9.0-1+deb9u1) ... Setting up linux-image-4.9.0-4-amd64 (4.9.65-3) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.9.0-4-amd64 W: initramfs-tools configuration sets RESUME=UUID=e4df7c74-843d-4e43-a7de-8c97d1469f24 W: but no matching swap device is available. I: The initramfs will attempt to resume from /dev/vda2 I: (UUID=bf035740-4836-4088-835d-84bd43a5cd05) I: Set the RESUME variable to override this. /etc/kernel/postinst.d/zz-update-grub: Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.9.0-4-amd64 Found initrd image: /boot/initrd.img-4.9.0-4-amd64 Found linux image: /boot/vmlinuz-4.9.0-3-amd64 Found initrd image: /boot/initrd.img-4.9.0-3-amd64 done Processing triggers for libc-bin (2.24-11+deb9u1) ... dpkg: dependency problems prevent configuration of sa-compile: sa-compile depends on spamassassin; however: Package spamassassin is not configured yet. dpkg: error processing package sa-compile (--configure): dependency problems - leaving unconfigured Processing triggers for systemd (232-25+deb9u1) ... Setting up libsqlite3-0:amd64 (3.16.2-5+deb9u1) ... Processing triggers for man-db (2.7.6.1-2) ... Setting up libpython2.7-minimal:amd64 (2.7.13-2+deb9u2) ... Setting up openssh-client (1:7.4p1-10+deb9u2) ... Setting up spamc (3.4.1-6+deb9u1) ... Setting up libpython2.7-stdlib:amd64 (2.7.13-2+deb9u2) ... Setting up libdbus-1-3:amd64 (1.10.24-0+deb9u1) ... Setting up python2.7-minimal (2.7.13-2+deb9u2) ... Setting up iproute (1:4.9.0-1+deb9u1) ... Setting up python2.7 (2.7.13-2+deb9u2) ... Setting up openssh-sftp-server (1:7.4p1-10+deb9u2) ... Setting up libpython2.7:amd64 (2.7.13-2+deb9u2) ... Setting up libpython2.7-dev:amd64 (2.7.13-2+deb9u2) ... Setting up dbus (1.10.24-0+deb9u1) ... A reboot is required to replace the running dbus-daemon. Please reboot the system when convenient. Setting up python2.7-dev (2.7.13-2+deb9u2) ... Setting up openssh-server (1:7.4p1-10+deb9u2) ... Processing triggers for libc-bin (2.24-11+deb9u1) ... Errors were encountered while processing: spamassassin sa-compile -- Terry LinuxChix System Admins
Bug#986837: aoe: kernel crash on blk_update_request: I/O error, BUG: scheduling while atomic
Hi, I finally managed to identify the root cause of this issue and do have a patch and a more detailed description of the issue attched to the kernel bugtracker. The attached patch is applicable to stable (5.10.92) and experimental (5.17-rc4) kernels. As I did not receive any response to the original upstream report, I fear that this might be the same for the proposed patch as well. Do you have any suggestions on what to do? I would now follow up with a mail to the maintainers, the linux-block list and the lkml but I don't know anything more I could try. Regards, ValentinIndex: linux-5.10.92/drivers/block/aoe/aoedev.c === --- linux-5.10.92.orig/drivers/block/aoe/aoedev.c +++ linux-5.10.92/drivers/block/aoe/aoedev.c @@ -198,6 +198,7 @@ aoedev_downdev(struct aoedev *d) { struct aoetgt *t, **tt, **te; struct list_head *head, *pos, *nx; + struct request *rq; int i; d->flags &= ~DEVFL_UP; @@ -225,11 +226,13 @@ aoedev_downdev(struct aoedev *d) /* fast fail all pending I/O */ if (d->blkq) { - /* UP is cleared, freeze+quiesce to insure all are errored */ - blk_mq_freeze_queue(d->blkq); - blk_mq_quiesce_queue(d->blkq); - blk_mq_unquiesce_queue(d->blkq); - blk_mq_unfreeze_queue(d->blkq); + /* UP is cleared, error all requests without sleeping */ + while ((rq = list_first_entry_or_null(&d->rq_list, struct request, +queuelist))) { + list_del_init(&rq->queuelist); + blk_mq_start_request(rq); + aoe_end_request(d, rq, 1); + } } if (d->gd)
Bug#738286: Fix autologin to use getty
Ok, I had a system crash but I was able to find the configs I used for this. It only applies to sysvinit in the form I did it. I modifed the file lib/live/config/0170-sysvinit so that it has the following: In function Configure_sysvinit: # Configure autologin sed -i -e "s|^\([^:]*:[^:]*[^:]*\):\(.*getty\) \(.*getty\) \(.*\)$|\1:\2 ${LIVE_USERNAME:+-a $LIVE_USERNAME }\3|" /etc/inittab Sorry, for taking so long, in part I thought I had at least already posted this part of the details, but apparently not. I'm unlikely to actually have the chance to make a patch anytime soon though. Regards, Daniel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#566225: mirror listing update for ftp.th.debian.org
Package: mirrors Severity: minor Submission-Type: update Site: ftp.th.debian.org Aliases: ftp.coe.psu.ac.th Aliases: debian.coe.psu.ac.th Type: leaf Archive-architecture: ALL alpha amd64 arm armel hppa hurd-i386 i386 ia64 kfreebsd-amd64 kfreebsd-i386 m68k mips mipsel powerpc s390 sparc Archive-ftp: /debian/ Archive-http: /debian/ Archive-rsync: debian/ CDImage-ftp: /debian-cd/ CDImage-http: /debian-cd/ CDImage-rsync: debian-cd/ Volatile-ftp: /debian-volatile/ Volatile-http: /debian-volatile/ Volatile-rsync: debian-volatile/ IPv6: no Archive-upstream: ftp.tw.debian.org Volatile-upstream: ftp.tw.debian.org CDImage-upstream: cdimage.debian.org Updates: push Maintainer: CoE Sysadmin Team Country: TH Thailand Location: Songkhla, Thailand Sponsor: Computer Engineering Department, Prince of Songkla University, Thailand http://www.coe.psu.ac.th -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#989375: courier-pop: CVE-2011-0411 equivalent vulnerability - fix not implemented
Package: courier-pop Severity: important Dear Maintainer, Uni Münster did a vulnerability scan on the Internet and reported a Debian server running courier-pop to be vulnerable to the equivalent of CVE-2011-0411. The system information is from another system, but the issue exists in the upstream source, so it doesn't matter. The suggested fixes from www.postfix.org/CVE-2011-0411.html have never been implemented in courier-pop (according to the researchers only in the IMAP implementation). There has been a very old bug report for Ubuntu (Debian security team asked me to open a ticket in Debian BTS for this): https://bugs.launchpad.net/ubuntu/+source/courier/+bug/1194892 In the meanwhile I got the information from a courier developer that while courier-pop is vulnerable to the same issue as the other programs (where fixes have been implemented) according to him there has never been an practically exploit given the limitations of the POP3 protocol. The only possibility for an attacker would be to cause the server to send back errors or failures to the login request and as the attacker is already MITM he/she could do that anyway. As a measure of defense in depth and to prevent Internet scans to cause "noise", it might be still a good idea to implement the suggested fixes in the POP3 implementation too. Or someone could declare STARTTLS as anyway broken (then it should be disabled in config and documented there) and users should use the TLS-only ports as researchers recommended as workaround. -- System Information: Debian Release: 10.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-16-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages courier-pop depends on: pn courier-authlib pn courier-base ii debconf [debconf-2.0] 1.5.71 pn default-mta | mail-transport-agent ii libc6 2.28-10 pn libcourier-unicode4 ii libidn111.33-2.2 ii sysvinit-utils 2.93-8 courier-pop recommends no packages. Versions of packages courier-pop suggests: pn courier-doc pn mail-reader
Bug#301275: data corruption solved by proper lock/unlock of mod_delay file
Could 1.2.10-20 be copied into sarge's security updates? Thanks for your work on this package Frankie, much appreciated :) Cheers, -- James Wakefield Systems Administrator +61 03 5227 6888 We have now moved head office to 8-12 Pakington Street, Geelong West. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#524889: [rt.debian.org #1327] AutoReply: Debian RT: Bug#524889: mirrors: ftp.us.d.: ike.egr.msu.edu one day behind (was: ftp.us is using Etch key?)
Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Debian RT: Bug#524889: mirrors: ftp.us.d.: ike.egr.msu.edu one day behind (was: ftp.us is using Etch key?)", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.debian.org #1327]. Please include the string: [rt.debian.org #1327] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, - Hi Marc, DSA, and ike.egr.msu.edu admins On Mon, Apr 20, 2009 at 05:46:32PM +0200, Marc Fargas wrote: > Package: mirrors > Severity: normal > > My apt has been saying this for some time now: > W: GPG error: http://ftp.us.debian.org testing Release: The following > signatures were invalid: BADSIG A70DAF536070D3A1 Debian Archive Automatic > Signing Key (4.0/etch) > [..] > I moved to ftp.uk and I'm running fine now, not sure if that's an > error on my side or ftp.us is out-of-sync. @Marc: Thanks for your notice, one mirror out of the ftp.us.d.o round robin is one day behind : http://ike.egr.msu.edu/debian/project/trace/ftp-master.debian.org 2009-Apr-19 17:00:01 If it happens your pc download the Release file from one mirror and the signature from an other one, then inconsistency will appear. 64.50.238.52 : ftp-atl.osuosl.org. ab76dcf7f2f4674f2fbcf58acc7c5a46 128.30.2.36 : rocky-mountain.csail.mit.edu. ab76dcf7f2f4674f2fbcf58acc7c5a46 35.9.37.225 : ike.egr.msu.edu. 2561030a5b38bc239ae3311567455a53 << bad !! 64.50.236.52 : ftp-chi.osuosl.org. ab76dcf7f2f4674f2fbcf58acc7c5a46 @DSA: Could you please remove temporarly 35.9.37.225 from the round robin ? @msu.edu people: Could you please check the sync processes ? Best regards. -- Simon Paillard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#272335: [rt.debian.org #1298] AutoReply: Debian RT: Bug#272335: www.debian.org do not support mod_gzip
Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Debian RT: Bug#272335: www.debian.org do not support mod_gzip", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.debian.org #1298]. Please include the string: [rt.debian.org #1298] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, - On Sat, Sep 25, 2004 at 03:24:36AM +0200, Frank Lichtenheld wrote: > On Sun, Sep 19, 2004 at 03:11:16PM +0300, Juhapekka Tolvanen wrote: > > Why WWW-pages of Debian do not use mod_gzip? > > I guess because we do not want to require more configuration from > all the mirror admins than necessary. So it is their own responsibilty > if they want to use this or not. Sure, however we may encourage them to enable mod_gzip on http://debian.org/mirror/webmirror#ref Such a question is more in the scope of DSA, so let's forward it to them. Regards. -- Simon Paillard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org