Bug#1059924: should we actually ship sudo_logsrvd
Hi! * Marc Haber [240103 19:12]: > (1) > remove sudo_logsrvd from the package with no replacement? Please no, I know at least one user: Me! > (2) > move sudo_logsrvd to its own package with proper systemd unit etc bla > foo That sounds like a good idea, given that it is not a very common use case. I can start to work on that solution. > An independent solution would be to continue shipping sudo.deb in a > minimal configuration, and having a new sudo-extended.deb that can > support plugins, SSL, bells and whistles, but just with supported sudo > => sudo-extended migration path and explicitly not providing a migration > path back from sudo-extended to plain sudo. But all this can only be > done after sudo-ldap is gone as this is a horrible mess to package that > we NEED to get rid of. I willing to help get sudo-logsrvd and sudo-extendended packaged. Looking at the package... My first instinct would be to extend sudo-ldap with openssl, and split sudo-logsrvd from that package, and then rename sudo-ldap to sudo-extended. However I'm not using sudo with ldap and never used that package. Would that be a valid approach? Or anything else I can help with helping with the getting rid of sudo-ldap? Best regards, Alexander
Bug#1059896: sudo: Please add openssl support for sudo and sudo_logsrvd for secure transfer of sudo log files
Hi Marc, * Marc Haber [240103 18:00]: > Would it be very unfriendly to indeed suggest using stunnel instead of > native SSL? Not at all, that's why I mentioned it in the first place ;) > What is a motivation to use sudo_logsrvd instead of normal > syslog? Well... Because sudo_logsrvd can do much more than regular syslog. With regular logs you get very basic informatio: Which user did run run which command as which other user. And if your user does stuff like "sudo /bin/bash" or "sudo su -" or so you will have trouble finding out what they did. If you are unlucky, you will even find an empty shell history. That's when sudo's input output logging comes in handy. If you set LOG_INPUT and LOG_OUTPUT, sudo will basically create a screen capture. You know the tool "script" to log the output of your console? It is similar. And for these io logs, the log_srvd comes in handy. Because if you want to store these logs at a central location, regular syslog won't do. That's why they came up with a dedicated server for sudo logs. And as these logs can contain confidential information, you want to transfer them via tls. Allthoug that is IMHO a pretty cool feature I grant you, that it is a limited use case, and is not a very common scenario. So if you don't want to add openssl to make me happy, I will happily provide configuration examples on how to archive the same thing via stunnel. With that in mind, coming back to: > I was not aware of sudo_logsrvd at all, since that's a daemon, it should > probably be in its own package (or disabled). Yes, it is the daemon responsible to receive and store log files from other hosts running sudo. As most people will need it, it makes sense to split it of. However, if you do so, that package should IMHO use ssl. Because I can't think of a scenario, were people would like to use the log deamon, without using ssl. And here I think simplicity of direct ssl usage wins over extra package stunnel. Best regards, Alexander
Bug#1059896: sudo: Please add openssl support for sudo and sudo_logsrvd for secure transfer of sudo log files
Package: sudo Version: 1.9.5p2-3+deb11u1 Severity: wishlist Tags: patch Dear Maintainer, sudo 1.9 introduced the functionality to directly send log files (especially input/output logs) to a log server. As these logs might contain private data, they should be transfered using ssl. Both sudo as well as sudo_logsrvd support this, when the feature is enabled at compile time. I send merge request on salsa to add this functionality, and verified, that it works for me. However, I should also point out, that an alternative approach would be to use stunnel. If you prefer that instead of adding additional complexity to an security critical package, would you consider adding a Readme file explaining how that's doen? I use it for sudo an other distribution anyway, and could write one for you, if you prefer it that way. Best regards, Alexander -- System Information: Debian Release: 11.8 APT prefers oldstable-security APT policy: (500, 'oldstable-security'), (500, 'oldoldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-26-cloud-amd64 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sudo depends on: ii libaudit1 1:3.0-2 ii libc6 2.31-13+deb11u7 ii libpam-modules 1.4.0-9+deb11u1 ii libpam0g1.4.0-9+deb11u1 ii libselinux1 3.1-3 ii lsb-base11.1.0 ii zlib1g 1:1.2.11.dfsg-2+deb11u2 sudo recommends no packages. sudo suggests no packages. -- Configuration Files: /etc/pam.d/sudo changed [not included] /etc/sudoers [Errno 13] Permission denied: '/etc/sudoers' /etc/sudoers.d/README [Errno 13] Permission denied: '/etc/sudoers.d/README' -- no debconf information
Bug#1023590: RFS: monitoring-plugins-check-logfiles/4.1.0.1-1 [ITP] -- Nagios plugin check_logfiles
Hi! Am 2022-11-16 21:17, schrieb Hilmar Preuße: Just two small remarks: * I think it would be relatively easy to add autopkgtest to the package, allowing automatic verification of the functionality. * Feel free to ping me for additinal pointers / examples. As you did an non-source only upload I probably have to do another upload anyway. Maybe I'm wrong here. Good question: But as your package has to pass NEW processing by the ftp-team, it has to be an upload including the binary packages. That's makes it easier for them to review the package. But you are right: You'll have to follow with a "real" source only upload, so that your package can propagate to testing. If it also contains autpkgtsts: Perfect, but it may also be a reupload. Best regards, Alexander
Bug#1023590: RFS: monitoring-plugins-check-logfiles/4.1.0.1-1 [ITP] -- Nagios plugin check_logfiles
Hi! * Hilmar Preuße [221108 18:42]: > > We are using that plugin at the company, so thanks for packaging! > > > > I'm willing to sponsor and will try to take a closer look at it in the > > evening. > > > Good. Thanks! I didn't noticed any showstoppers, so just uploaded. You should receive a mail about it soonish, and then your package will have to be accepted by the ftp-master, but I guess you know that part (if not feel free to ask for details). Just two small remarks: * I think it would be relatively easy to add autopkgtest to the package, allowing automatic verification of the functionality. * Feel free to ping me for additinal pointers / examples. * I know that there is a maintainers team for several icinga / monitoring related packages, but I don't know how they are organized. Please consider joining them; team maintainership is usually a very good idea for various reasons. Best regards, Alexander
Bug#1023590: RFS: monitoring-plugins-check-logfiles/4.1.0.1-1 [ITP] -- Nagios plugin check_logfiles
Hi! Am 2022-11-07 09:52, schrieb Hilmar Preuße: I am looking for a sponsor for my package "monitoring-plugins-check-logfiles": We are using that plugin at the company, so thanks for packaging! I'm willing to sponsor and will try to take a closer look at it in the evening. But just a first question: Mentors service says, that you didn't added a watch file to it. Is there a specific reason for it? Best regards, Alexander
Bug#618511: Xplanet generates unreadable text labels
Hi Timo! A couple of years ago you reported a bug against the xplanet package in Debian, and I just stumbled over that bug report. I tried to reproduce it with the xplanet package 1.3.0-5.1 - the version which is currently shipped in Debians stable release, but unfortunatly I was unable to reproduce it. Using https://upload.wikimedia.org/wikipedia/commons/e/e9/Location_map_Japan.png as a replacement for your japan.png and running the exakt command you gave with the configuration and markers file you provided with the bug report, I got a readable output. Could you please retry it, and if you still have a problem provide an example of the result? By now the link you provided in your original report doesn't work anymore :( Best regards, Alexander
Bug#618511: Xplanet generates unreadable text labels
tags 618511 + unreproducible moreinfo thanks Hi! Using the configration example from the submitter, I was unable to reproduce the bug with xplanet 1.3.0-5.1 package in stable (nor with the 1.3.1-1 I'm currently preparing). Using https://upload.wikimedia.org/wikipedia/commons/e/e9/Location_map_Japan.png as replacement for japan.png I got the attached result (cropped to the text). Best regards, Alexander
Bug#1003911: ITA: xplanet -- planetary body renderer
retitle 1003911 ITA: xplanet -- planetary body renderer owner 1003911 ! thanks I intent to addopt xplanet.
Bug#1003911: RFA: xplanet -- planetary body renderer
Hi Steve! I noticed you are searching someone to adopt xplanet. I'm still using it from time to time and am also looking for something to slowly getting back. Would you mind if I adtopt it? I think one of the first stept would be, to check (and upload) the 1.3.1 release. Best regards, Alexander
Bug#1016752: developers-reference: Chapter 3.2.6. "Returning after retirement" refers to alioth.debian.org
Package: developers-reference Version: 12.5 Severity: minor Dear Maintainers, In the bullet point list of chapter 3.2.6. "Returning after retirement" the old alioth system is referenced. Should probably now be a refernece to salsa.debian.org? See https://www.debian.org/doc/manuals/developers-reference/developer-duties.en.html#returning-after-retirement. Best regards, Alexander -- System Information: Debian Release: 10.12 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-18-amd64 (SMP w/2 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled developers-reference depends on no packages. Versions of packages developers-reference recommends: pn debian-policy Versions of packages developers-reference suggests: pn doc-base
Bug#1016594: RFS: anonip/1.1.0-1 [ITP] -- Anonymize IP-addresses in log-files
tags 1016594 +pending thanks * Alexander Reichle-Schmehl [220803 21:26]: > I am looking for a sponsor for my package "anonip": Uwe Kleine-König kinldy reviewed the package and sponsored the upload. Best regards, Alexander
Bug#1016694: packages.debian.org uses favicon with white shadow
Package: www.debian.org Severity: wishlist Dear Maintainer, * What led up to the situation? I switched my browser to use dark theme and access packages.debian.org with it. * What exactly did you do (or not do) that was effective (or ineffective)? I switched my browser to use dark theme and access packages.debian.org with it. * What was the outcome of this action? I saw that it uses a favicon with a white grop shadown looking really ugly. * What outcome did you expect instead? To see a just red favicon just like the one of www.debian.org or wiki.debian.org See the attached screenshot of my open tabs showing from left to right packages.debian.org (with an ugly favicon), www.debian.org and wiki.debian.org. Best regards, Alexander -- System Information: Debian Release: 10.12 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-18-amd64 (SMP w/2 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#930471: First package ready and uploaded to mentors.debian.net
Hi! Package is basically ready and uploaded to Debian mentors service at https://mentors.debian.net/package/anonip/. Currently looking for a sponsor at, see #1016594 -- RFS: anonip/1.1.0-1 [ITP] -- Anonymize IP-addresses in log-files. Best regards, Alexander
Bug#1016594: RFS: anonip/1.1.0-1 [ITP] -- Anonymize IP-addresses in log-files
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "anonip": * Package name: anonip Version : 1.1.0-1 Upstream Author : https://github.com/DigitaleGesellschaft/Anonip * URL : https://github.com/DigitaleGesellschaft/Anonip * License : BSD-3-Clause * Vcs : [fill in URL of packaging vcs] Section : admin The source builds the following binary packages: anonip - Anonymize IP-addresses in log-files To access further information about this package, please visit the following URL: https://mentors.debian.net/package/anonip/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/a/anonip/anonip_1.1.0-1.dsc Changes for the initial release: anonip (1.1.0-1) unstable; urgency=medium . * Initial release (Closes: #930471) Regards, -- Alexander Reichle-Schmehl
Bug#930471: ITP: anonip -- Anonymize IP-addresses in log-files
retitle 930471 ITP: anonip -- Anonymize IP-addresses in log-files owner 930471 alexan...@alphamar.org thanks Hi! As I use it I intend to create a package in the coming days. Best regards, Alexander
Bug#989803: podman 3.0.1 rootless network issues: Connection reset by peer
Hi! Thanks for the fast reaction: I build it and can confirm that it solves the issue! Best regards, Alexander Am 2021-06-14 00:33, schrieb Reinhard Tartler: Hi Alexander, thank you for reporting this issue. I've prepared a fix for this that adds the referenced commit as a distro patch. Can you please try to build https://salsa.debian.org/debian/libpod/-/merge_requests/4 and let me know if that fixes the issue? Thanks! On Sun, Jun 13, 2021 at 12:27 PM Alexander Reichle-Schmehl wrote: Hi! Found a minimal example at https://stackoverflow.com/questions/67049585/how-to-publish-ports-in-user-defined-network-in-rootless-podman To reproduce: $ podman network create samplenet $ podman network ls NAME VERSION PLUGINS samplenet 0.4.0bridge,portmap,firewall,tuning,dnsname $ podman run -dt --name test --network=samplenet --rm --publish 8080:80 nginx $ podman port -l 80/tcp -> 0.0.0.0:8080 $ curl localhost:8080 curl: (56) Recv failure: Connection reset by peer Best regards, Alexander Am 2021-06-13 18:01, schrieb Alexander Reichle-Schmehl: Package: podman Version: 3.0.1+dfsg1-2+b2 Severity: important Tags: patch upstream X-Debbugs-Cc: alexan...@alphamar.org Running podman containers rootless seems I was unable to access any network services in a container. The apps work inside the container, but not from the host system. Searching around I found https://github.com/containers/podman/issues/9532 which seems to be the isse I run into. The bug log also mentiones a missing patch in 3.0.1. -- System Information: Debian Release: 11.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages podman depends on: ii conmon 2.0.25+ds1-1 ii containernetworking-plugins 0.9.0-1+b5 ii crun 0.17+dfsg-1 ii golang-github-containers-common 0.33.4+ds1-1 ii init-system-helpers 1.60 ii iptables 1.8.7-1 ii libc62.31-12 ii libdevmapper1.02.1 2:1.02.175-2.1 ii libgpgme11 1.14.0-1+b2 ii libseccomp2 2.5.1-1 Versions of packages podman recommends: ii buildah 1.19.6+dfsg1-1+b4 ii catatonit 0.1.5-2 ii fuse-overlayfs1.4.0-1 ii golang-github-containernetworking-plugin-dnsname 1.1.1+ds1-4+b6 ii slirp4netns 1.0.1-2 ii uidmap1:4.8.1-1 Versions of packages podman suggests: pn containers-storage pn docker-compose -- no debconf information -- regards, Reinhard
Bug#989803: podman 3.0.1 rootless network issues: Connection reset by peer
Hi! Found a minimal example at https://stackoverflow.com/questions/67049585/how-to-publish-ports-in-user-defined-network-in-rootless-podman To reproduce: $ podman network create samplenet $ podman network ls NAME VERSION PLUGINS samplenet 0.4.0bridge,portmap,firewall,tuning,dnsname $ podman run -dt --name test --network=samplenet --rm --publish 8080:80 nginx $ podman port -l 80/tcp -> 0.0.0.0:8080 $ curl localhost:8080 curl: (56) Recv failure: Connection reset by peer Best regards, Alexander Am 2021-06-13 18:01, schrieb Alexander Reichle-Schmehl: Package: podman Version: 3.0.1+dfsg1-2+b2 Severity: important Tags: patch upstream X-Debbugs-Cc: alexan...@alphamar.org Running podman containers rootless seems I was unable to access any network services in a container. The apps work inside the container, but not from the host system. Searching around I found https://github.com/containers/podman/issues/9532 which seems to be the isse I run into. The bug log also mentiones a missing patch in 3.0.1. -- System Information: Debian Release: 11.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages podman depends on: ii conmon 2.0.25+ds1-1 ii containernetworking-plugins 0.9.0-1+b5 ii crun 0.17+dfsg-1 ii golang-github-containers-common 0.33.4+ds1-1 ii init-system-helpers 1.60 ii iptables 1.8.7-1 ii libc62.31-12 ii libdevmapper1.02.1 2:1.02.175-2.1 ii libgpgme11 1.14.0-1+b2 ii libseccomp2 2.5.1-1 Versions of packages podman recommends: ii buildah 1.19.6+dfsg1-1+b4 ii catatonit 0.1.5-2 ii fuse-overlayfs1.4.0-1 ii golang-github-containernetworking-plugin-dnsname 1.1.1+ds1-4+b6 ii slirp4netns 1.0.1-2 ii uidmap1:4.8.1-1 Versions of packages podman suggests: pn containers-storage pn docker-compose -- no debconf information
Bug#989803: podman 3.0.1 rootless network issues: Connection reset by peer
Package: podman Version: 3.0.1+dfsg1-2+b2 Severity: important Tags: patch upstream X-Debbugs-Cc: alexan...@alphamar.org Running podman containers rootless seems I was unable to access any network services in a container. The apps work inside the container, but not from the host system. Searching around I found https://github.com/containers/podman/issues/9532 which seems to be the isse I run into. The bug log also mentiones a missing patch in 3.0.1. -- System Information: Debian Release: 11.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages podman depends on: ii conmon 2.0.25+ds1-1 ii containernetworking-plugins 0.9.0-1+b5 ii crun 0.17+dfsg-1 ii golang-github-containers-common 0.33.4+ds1-1 ii init-system-helpers 1.60 ii iptables 1.8.7-1 ii libc62.31-12 ii libdevmapper1.02.1 2:1.02.175-2.1 ii libgpgme11 1.14.0-1+b2 ii libseccomp2 2.5.1-1 Versions of packages podman recommends: ii buildah 1.19.6+dfsg1-1+b4 ii catatonit 0.1.5-2 ii fuse-overlayfs1.4.0-1 ii golang-github-containernetworking-plugin-dnsname 1.1.1+ds1-4+b6 ii slirp4netns 1.0.1-2 ii uidmap1:4.8.1-1 Versions of packages podman suggests: pn containers-storage pn docker-compose -- no debconf information
Bug#989510: debian-installer: Successfull installation
Package: installation-reports Boot method: CD-ROM Image version: https://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso Date: 2021-06-05 Machine: KVM based virtual server Processor: Intel(R) Xeon(R) Gold 6230 CPU @ 2.10GHz, 4 Cores Memory: 16GB Partitions: Filesystem Type 1K-blocks Used Available Use% Mounted on udev devtmpfs 8178820 0 8178820 0% /dev tmpfs tmpfs 1639312500 1638812 1% /run /dev/mapper/senet--vg-lv--root ext4 19047080 903152 17932248 5% / tmpfs tmpfs 8196540 0 8196540 0% /dev/shm tmpfs tmpfs 5120 0 5120 0% /run/lock /dev/sda1 ext2480618 48658426974 11% /boot /dev/mapper/senet--vg-lv--home ext4 9509056124 9394900 1% /home /dev/mapper/senet--vg-lv--tmp ext4 4721184 64 4655912 1% /tmp /dev/mapper/senet--vg-lv--var ext4 9509056 300616 9094408 4% /var /dev/mapper/senet--vg-lv--srv ext4 435169056 28 430720160 1% /srv tmpfs tmpfs 1639308 0 1639308 0% /run/use Output of lspci -knn (or lspci -nn): 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100] 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] [8086:7000] Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100] 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] [8086:7010] Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100] Kernel driver in use: ata_piix Kernel modules: ata_piix, ata_generic 00:01.2 USB controller [0c03]: Intel Corporation 82371SB PIIX3 USB [Natoma/Triton II] [8086:7020] (rev 01) Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] Kernel driver in use: uhci_hcd Kernel modules: uhci_hcd 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 03) Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100] Kernel driver in use: piix4_smbus Kernel modules: i2c_piix4 00:02.0 VGA compatible controller [0300]: Device [1234:] (rev 02) Subsystem: Red Hat, Inc. Device [1af4:1100] Kernel driver in use: bochs-drm Kernel modules: bochs_drm 00:03.0 Ethernet controller [0200]: Red Hat, Inc. Virtio network device [1af4:1000] Subsystem: Red Hat, Inc. Virtio network device [1af4:0001] Kernel driver in use: virtio-pci Kernel modules: virtio_pci 00:1c.0 Communication controller [0780]: Red Hat, Inc. Virtio console [1af4:1003] Subsystem: Red Hat, Inc. Virtio console [1af4:0003] Kernel driver in use: virtio-pci Kernel modules: virtio_pci 00:1d.0 SCSI storage controller [0100]: Red Hat, Inc. Virtio SCSI [1af4:1004] Subsystem: Red Hat, Inc. Virtio SCSI [1af4:0008] Kernel driver in use: virtio-pci Kernel modules: virtio_pci Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Well, not much to say: Installed a new minimal servr and it worked like a charm :) -- System Information: Debian Release: 11.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#942055: ghostscript in buster partly broken on armel?
reassign 942055 cups-filters thanks Hi Jonas! * Jonas Smedegaard [200205 11:02]: > > I'm open for suggestion on how to continue next, but have honestly. If > > I should fill a bug against an other package, please let me know which > > one, as I have no idea, how these parts are interacting with each > > other. > > Seems to me that this bugreport was initially filed against > cups-filters, and then reassigned to ghostscript by you. > > My suggestion is simply to revert that reassignment. Seems ressonable, thanks for the hint and your work! Best regards, Alexander
Bug#942055: ghostscript in buster partly broken on armel?
Hi! Am 2020-02-04 22:09, schrieb Jonas Smedegaard: Most notable change between 9.22 and 9.24 - and also applied to various degree in security updates - was a security fix affecting interpretation of Postscript code. Maybe a stupid question, but does that fix work? I'm just wondering, if the firx triggers a problem on one arm but not on amd64, is it working? Please do not reassign these bugs to Ghostscript, even though provable that they are "fixed" by downgrading Ghostscript. The fix needs to be applied at the consumer end. I'm open for suggestion on how to continue next, but have honestly. If I should fill a bug against an other package, please let me know which one, as I have no idea, how these parts are interacting with each other. Best regards, Alexnader
Bug#942055: version in oldstable not affected
notfound 942055 9.26a~dfsg-0+deb9u5 thanks Version in oldstable is not affected by this regression.
Bug#942055: ghostscript in buster partly broken on armel?
reassign 942055 ghostscript severity 942055 important found 942055 9.27~dfsg-2+deb10u1 thanks Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I upgraded my server running on armel from stretch to buster. Since then I was unable to print pictures via my cups server installed on the armel system. * What exactly did you do (or not do) that was effective (or * What was the outcome of this action? ineffective)? Printing the cups test page results in just the test being printed, not the images. Same for other documents. * What outcome did you expect instead? Testpage should print with images :) *** End of the template - remove these template lines *** After the upgrade from stretch to buster, I noticed that I can't images anymore. When printing pages with images, the part of the page is usually left empty. Same problem with text containing special characters. Installing cups on my amd64 notebook, I can print without problems anymore, so it doesn't seem to be a general problem. Downgrading the ghostscript pagages to the version in Debian 9 solved my issues. Please feel free to contact me for futher tests or debugg output. I grant that this issue might not be easy to reproduce ;) Best regards, Alexander -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armel (armv5tel) Kernel: Linux 4.19.0-5-marvell Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cups-filters depends on: ii bc 1.07.1-2+b1 ii cups-filters-core-drivers 1.21.6-5 hi ghostscript9.26a~dfsg-0+deb9u5 ii libc6 2.28-10 ii libcups2 2.2.10-6+deb10u1 ii libcupsfilters11.21.6-5 ii libcupsimage2 2.2.10-6+deb10u1 ii libfontconfig1 2.13.1-2 ii libfontembed1 1.21.6-5 ii libgcc11:8.3.0-6 ii libqpdf21 8.4.0-2 ii libstdc++6 8.3.0-6 ii poppler-utils 0.71.0-5 Versions of packages cups-filters recommends: ii colord 1.4.3-4 ii liblouisutdml-bin 2.7.0-5+b1 Versions of packages cups-filters suggests: pn antiword pn docx2txt ii foomatic-db-compressed-ppds [foomatic-db] 20181217-2 ii imagemagick8:6.9.10.23+dfsg-2.1 ii imagemagick-6.q16 [imagemagick]8:6.9.10.23+dfsg-2.1 -- no debconf information
Bug#942055: cups-filters: ghostscript on armel partly broken?
reassign 942055 ghostscript severity 942055 important found 942055 9.27~dfsg-2+deb10u1 thanks Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I upgraded my server running on armel from stretch to buster. Since then I was unable to print pictures via my cups server installed on the armel system. * What exactly did you do (or not do) that was effective (or * What was the outcome of this action? ineffective)? Printing the cups test page results in just the test being printed, not the images. Same for other documents. * What outcome did you expect instead? Testpage should print with images :) *** End of the template - remove these template lines *** After the upgrade from stretch to buster, I noticed that I can't images anymore. When printing pages with images, the part of the page is usually left empty. Same problem with text containing special characters. Installing cups on my amd64 notebook, I can print without problems anymore, so it doesn't seem to be a general problem. Downgrading the ghostscript pagages to the version in Debian 9 solved my issues. Please feel free to contact me for futher tests or debugg output. I grant that this issue might not be easy to reproduce ;) Best regards, Alexander -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armel (armv5tel) Kernel: Linux 4.19.0-5-marvell Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cups-filters depends on: ii bc 1.07.1-2+b1 ii cups-filters-core-drivers 1.21.6-5 hi ghostscript9.26a~dfsg-0+deb9u5 ii libc6 2.28-10 ii libcups2 2.2.10-6+deb10u1 ii libcupsfilters11.21.6-5 ii libcupsimage2 2.2.10-6+deb10u1 ii libfontconfig1 2.13.1-2 ii libfontembed1 1.21.6-5 ii libgcc11:8.3.0-6 ii libqpdf21 8.4.0-2 ii libstdc++6 8.3.0-6 ii poppler-utils 0.71.0-5 Versions of packages cups-filters recommends: ii colord 1.4.3-4 ii liblouisutdml-bin 2.7.0-5+b1 Versions of packages cups-filters suggests: pn antiword pn docx2txt ii foomatic-db-compressed-ppds [foomatic-db] 20181217-2 ii imagemagick8:6.9.10.23+dfsg-2.1 ii imagemagick-6.q16 [imagemagick]8:6.9.10.23+dfsg-2.1 -- no debconf information
Bug#931303: needrestart: Possibility to check in a proactive way
Package: needrestart Version: 3.4-5~bpo9+1 Severity: wishlist Dear Maintainer, on our company we often have to coordinate with the actual application administrators before installing any package updates. I guess it is similar for other companies. It would be usefull, if needrestart had a parameter to check what has to be restarted, if certain (libraries) are changed. For example you provide a list of files from a pending package upgrade, and needrestart would check which services you will have to restart after installing it. Best regards, Alexander PS: I understand that this request is not strictly the purpose of needrestart, but it seemed to fit best. -- Package-specific info: needrestart output: -- System Information: Debian Release: 9.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armel (armv5tel) Kernel: Linux 4.9.0-9-marvell Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages needrestart depends on: ii binutils 2.28-5 ii dpkg 1.18.25 ii gettext-base 0.19.8.1-2 ii libintl-perl 1.26-2 ii libmodule-find-perl0.13-1 ii libmodule-scandeps-perl1.23-1 ii libproc-processtable-perl 0.53-2 ii libsort-naturally-perl 1.03-1 ii libterm-readkey-perl 2.37-1 ii perl 5.24.1-3+deb9u5 ii xz-utils 5.2.2-1.2+b1 Versions of packages needrestart recommends: ii libpam-systemd 232-25+deb9u11 Versions of packages needrestart suggests: pn iucode-tool pn needrestart-session | libnotify-bin -- no debconf information
Bug#925598: upgrade-reports: Successfull upgrading armel NAS box jessie -> stretch, bug stumbled over a known bug
Package: upgrade-reports Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Jessie got removed form the archive ;) * What exactly did you do (or not do) that was effective (or ineffective)? Read the release notes and followed the steps described * What was the outcome of this action? I now have strech installed, but had to change /bin/sh from bash to dash * What outcome did you expect instead? Having stretch installed independend of where /bin/sh points to I just finished my last box from Jessie (with some backports (dehydrated) and handpicked manual installed packages (e.g. restic)) to stretch. During the upgrade however I seem to have run into Bug #870430: flash-kernel didn't found the dtb file for my device. Changing the symlink as described via "dpkg-reconfigure dash" solved the upgrade issue for me, so I'm fine now. I can't remmeber to have set the default shell to bash myselfe, so assume it is still the default shell? Then I think this bu should be fixed in stable, too. Best regards and many thanks, Alexander -- System Information: Debian Release: 9.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armel (armv5tel) Kernel: Linux 4.9.0-0.bpo.6-marvell Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#910082: molly-guard: Please ask for confirmation / list other user sessions
Package: molly-guard Version: 0.6.4 Severity: wishlist Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Reboot triggered by a collegue A, while an other collegue B was loged in * What exactly did you do (or not do) that was effective (or ineffective)? Collegue A run "reboot". * What was the outcome of this action? System rebooted. * What outcome did you expect instead? Would have been nice, if molly-guard had asked collegue A wheter it is OK to reboot. Not yet a patch, but an idea, how that might work: USERS=$(who | grep -v $( whoami ) ) if [ -n "$USERS" ] ; then echo -e "Following other users are loged in:\n$USERS\n\nAre you sure to reboot?" fi *** End of the template - remove these template lines *** -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/2 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages molly-guard depends on: ii procps 2:3.3.12-3+deb9u1 molly-guard recommends no packages. molly-guard suggests no packages. -- no debconf information
Bug#901445: apticron: Please allow adding option to add custom headers
Package: apticron
Version: 1.1.57
Severity: wishlist
Tags: patch
Dear Maintainer,
to remote controll our ticketing system, we had add custom mail headers to the
reports send by apticron.
The attached patch allows us to do so at least with bsd-mailx. I don't know how
others mailx implementation might
work.
With tha attached patch, you can simply configure as many e-mail headers as
desired by adding a CUSTOM_HEADER[x] array
to /etc/apticron/apticron.conf:
CUSTOM_HEADER[1]="X-OTRS-Priority: 3 normal - prio 3"
CUSTOM_HEADER[2]="X-OTRS-Queue: foo::bar::baz"
CUSTOM_HEADER[3]="X-OTRS-Service: Linux Operating System"
CUSTOM_HEADER[4]="X-OTRS-SenderType: system"
CUSTOM_HEADER[5]="X-OTRS-Loop: false"
CUSTOM_HEADER[6]="X-OTRS-DynamicField-foo: bar"
Best regards,
Alexander
PS: Thanks to Ansgar Burchardt for recommending the usage of arrays for this.
--- /usr/sbin/apticron 2014-10-01 18:27:20.0 +0200
+++ apticron 2018-06-13 11:38:29.862441874 +0200
@@ -16,18 +16,17 @@
else
# bsd-mailx/mailutils' mailx don't do character set
# conversion, but do not support MIME either.
+ MAILX_CMD='/usr/bin/mailx'
+ MAILX_CMD_ARGS=("-a" "MIME-Version: 1.0" "-a" "Content-type: text/plain; charset=UTF-8" "-a" "Content-transfer-encoding: 8bit")
+
+ for hdr in "${CUSTOM_HEADER[@]}" ; do
+ MAILX_CMD_ARGS+=("-a" "${hdr}")
+ done
+
if [ -n "$CUSTOM_FROM" ] ; then
- /usr/bin/mailx -a "MIME-Version: 1.0" \
--a "Content-type: text/plain; charset=UTF-8" \
--a "Content-transfer-encoding: 8bit" \
--a "From: $CUSTOM_FROM" \
-"$@"
- else
- /usr/bin/mailx -a "MIME-Version: 1.0" \
--a "Content-type: text/plain; charset=UTF-8" \
--a "Content-transfer-encoding: 8bit" \
-"$@"
+MAILX_CMD_ARGS+=("-a" "From: $CUSTOM_FROM")
fi
+ $MAILX_CMD "${MAILX_CMD_ARGS[@]}" "$@"
fi
}
Bug#288763: Calling apt-list-changes via cron-apt
Hi! I recently run into the same problem, found that ticket, found a work around, and thought I update the ticket, as my workaround might be useful for someone else, too. The basic idea is to call apt-listchanges over all files downloaded to /var/cache/apt/archives. To avoid getting the changelog of cruft collected in that directory, I first run apt-get. To do that, I created /etc/cron-apt/action.d/1-clean which contains: clean I also created /etc/cron-apt/config.d/4-listchanges containing: APTCOMMAND="/usr/bin/apt-listchanges" OPTIONS="" And finnally I created /etc/cron-apt/4-listchanges containing: /var/cahce/apt/archives/*.deb WARNING: Using this solution might not be what you want, as you'll download package updates daily, just to remove them the next day from the cache and downloading them again (unless you install them in time). It might also remove packages from the archive cache, you might want to keep. Best regards, Alexander
Bug#888765: roundcube-plugins-extra: keyboard_shortcuts extension not working, shipped as keyboard-shortcuts
Package: roundcube-plugins-extra Version: 1.2.1-20160803 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Installation of package and actiavtion of keyboard-shortcuts * What exactly did you do (or not do) that was effective (or ineffective)? Added keyboard-shortcuts to the plugins in my roundcube config * What was the outcome of this action? roundcube broke. * What outcome did you expect instead? Plugin to be activated. *** End of the template - remove these template lines *** While the extension is called keyboad_shortcuts it is shipped in a folder keyboard-shortcuts. Temporary solution for me: Adding a symlink keyboard_shortcuts to keyboard-shortcuts in /var/lib/roundcube/plugins/. Best regards, Alexander -- System Information: Debian Release: 9.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-5-amd64 (SMP w/2 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages roundcube-plugins-extra depends on: ii libjs-jquery-mousewheel 11-3 ii roundcube-core 1.2.3+dfsg.1-4+deb9u1 roundcube-plugins-extra recommends no packages. Versions of packages roundcube-plugins-extra suggests: ii fail2ban 0.9.6-2 -- no debconf information
Bug#727670: Working and developer carddav plugin
Hi! FWIW: I found a working plugin at https://github.com/blind-coder/rcmcarddav/. Last commit was 1 year ago, but the release download doesn't require you do download other external sources, but does contain additional software. But as license is shipped and free, it should be possible to package it. Best regards, Alexander
Bug#736232: Missing point in retire procedure: Getting removed from e-mail aliases
Package: developers-reference Hi! Section 3.2.5. Retiring misses a small point: To get yourselves removed from @debian.org e-mail aliases, one has to open a RT ticket. Proposal: 4. If you received mails via a @debian.org e-mail alias (e.g. pr...@debian.org) and would like to get removed, open a RT ticket for the Debian System Administrators. Just send an e-mail to ad...@rt.debian.org with Debian RT somewhere in the subject stating from which aliases you'd like to get removed. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726552: Acknowledgement (RFA: mii-diag)
reassign 726552 ftp.debian.org retitle 726552 RM: mii-diag -- Unmaintained, upstream dead, low popcon, replacements exist thanks Hi! Thinking about it I see no point in keeping the package longer in Debian. So instead of orphaning it, I think we should go directly to removing it. I havn't used it myself for quite some time and it doesn't seem anyone else is actively using it nowadays. Also I can't think of anything ethtool and others can't do (and much more). Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728261: O: ht - Viewer/editor/analyser (mostly) for executables
Package: wnpp Severity: normal Hi! I am unfortunately no longer able to take proper care of this package. It is a very easy package with low maintenance, but could use a little clean up. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726546: RFA: etherwake
Package: wnpp Severity: normal Hi! I am unfortunately no longer able to take proper care of this package. It is a very easy package with low maintenance, but could use a little clean up. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726548: RFA: httperf
Package: wnpp Severity: normal Hi! I am unfortunately no longer able to take proper care of this package. It is a very easy package with low maintenance, but could use a little clean up. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726549: RFA: iftop
Package: wnpp Severity: normal Hi! I am unfortunately no longer able to take proper care of this package. It is a very easy package with low maintenance, but could use a little clean up. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726547: RFA: hexedit
Package: wnpp Severity: normal Hi! I am unfortunately no longer able to take proper care of this package. It is a very easy package with low maintenance, but could use a little clean up. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726550: RFA: linuxlogo
Package: wnpp Severity: normal Hi! I am unfortunately no longer able to take proper care of this package. It is a very easy package with low maintenance, but could use a little clean up. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726555: RFA: xpenguins
Package: wnpp Severity: normal Hi! I am unfortunately no longer able to take proper care of this package. It is a very easy package with low maintenance, but could use a little clean up. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726554: RFA: userinfo
Package: wnpp Severity: normal Hi! I am unfortunately no longer able to take proper care of this package. It is a very easy package with low maintenance, but could use a little clean up. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726552: RFA: mii-diag
Package: wnpp Severity: normal Hi! I am unfortunately no longer able to take proper care of this package. It is a very easy package with low maintenance, but could use a little clean up. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726553: RFA: tofrodos
Package: wnpp Severity: normal Hi! I am unfortunately no longer able to take proper care of this package. It is a very easy package with low maintenance, but could use a little clean up. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726551: RFA: microcom
Package: wnpp Severity: normal Hi! I am unfortunately no longer able to take proper care of this package. It is a very easy package with low maintenance, but could use a little clean up. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726564: RM: nagiosgrapher -- ROM; upstream discontinued
Hi! * Markus Frosch mar...@lazyfrosch.de [131016 19:27]: This request has been approved by tolimar. Away with it... The only it's still in the archive is, that I didn't had the time to fill the removal request myself. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712348: ht: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)
Hi! Am 2013-07-08 08:59, schrieb Helmut Grohne: Please find a fix attached. I am uploading it to DELAYED/7 now, since tolimar is now lownmu. Yeah, I did forget the patch... Many thanks! Feel free to reschedule to DELAYED/7 and if you like committ your changes to the SVN repo. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712348: ht: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)
Hi! Am 2013-07-09 07:26, schrieb Helmut Grohne: Many thanks! Feel free to reschedule to DELAYED/7 and if you like committ your changes to the SVN repo. Changes are committed to collab-maint as requested. The NMU is already sitting in DELAYED/6, so there is nothing to reschedule. Sorry, typo. I meant: DELAYED/0. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#711363: rt-tests: hackbench does not work in stable on armhf
Hi! Am 2013-06-06 23:15, schrieb Uwe Kleine-König: It is not in 0.84. Can you fix this in stable, please? armel seems not to be affected. fwiw, as unstable also has 0.83, it would need to be fixed there first. Yeah, I have a 0.84-1 package in the queue and I'm already nagging my sponsor. I'll try to upload it this weekend. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707228: RM: at-spi -- ROM; obsoleted by at-spi2
severity 709213 serious severity 709214 serious thanks Hi! * Josselin Mouette j...@debian.org [130524 15:20]: # Broken Build-Depends: java-access-bridge: at-spi (= 1.8) libatspi-dev pyspi: libatspi-dev I don’t think these two packages can do anything useful with at-spi 1.x being deprecated. Yeah, after actually reading the package descriptions I agree ;) Maybe we can just bump the bug severity? Done. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680311: Your package pyjamas is about to be removed
clone 680311 -1 reassing -1 ftp.debian.org retitle -1 RM: pyjamas -- RoQA, tags -1 +moreinfo thanks Hi Maintainer! * Alexander Reichle-Schmehl alexan...@schmehl.info [120705 00:06]: As subject says: sugar-hulahop is too difficult to adapt to recent PyXPCOM and is dead upstream. [..] Sadly bug #680311 is still unfixed, rendering the package basically useless. As that bug was filled nearly a year ago, I guess it's about time to remove pyjamas from the archive. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709200: closed by Debian FTP Masters ftpmas...@ftp-master.debian.org (Bug#709200: Removed package(s) from unstable)
Hi! * Sven Joachim svenj...@gmx.de [130522 20:59]: We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: .. There is still a version of texlive-doc in experimental that most probably should be removed as well. Do you need a new bug report, or should I reopen the current one? Ah, thanks for noticing. Please open a new bug for that. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707228: RM: at-spi -- ROM; obsoleted by at-spi2
tags 707228 +moreinfo clone 707228 -1 -2 reassing -1 java-access-bridge reassing -2 pyspi retitle -1 Depengs on package at-spi scheduled for removal retitle -2 Depengs on package at-spi scheduled for removal severity -1 important severity -2 important thanks Hi! * Josselin Mouette j...@debian.org [130508 12:58]: please remove at-spi from the archive. The only remaining reverse dependencies are: - gnome-mag (removal requested) - python-dogtail (RC bug filed, fixed in experimental) - dasher (just fixed in unstable) Sorry, I can't do that right now. I still get: Checking reverse dependencies... # Broken Depends: pyspi: python-at-spi # Broken Build-Depends: java-access-bridge: at-spi (= 1.8) libatspi-dev pyspi: libatspi-dev Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707333: RM: stlport4.6 -- ROM; obsolete; (now) unused
tags 707333 +moreinfo clone 707333 -1 reassing -1 kawari8 retitle -1 Depends on package stlport4.6 scheduled for removal severity -1 important thanks Hi! * Rene Engelhard r...@debian.org [130509 09:21]: $ rmadison -S -s unstable stlport4.6 libstlport4.6-dev | 4.6.2-7 | sid | i386 libstlport4.6ldbl | 4.6.2-7 | sid | i386 stlport4.6| 4.6.2-7 | sid | source Was only kept around (and only on i386!) for compatibility with old OOo extensions. Stuff using stlport was moving onto 5.x long ago - and even that was removed from Debian AFAICS Now that LibreOffice dropped that stlport compatibility thing in 4.0 beta2[1] this is now moot and unneeded. Thus please remove stlport4.6 source package and all it's binaries. Sorry, but I can't do that right now: Checking reverse dependencies... # Broken Depends: kawari8: kawari8 [i386] # Broken Build-Depends: kawari8: libstlport4.6-dev libreoffice: libstlport4.6-dev (= 4.6.2-3) Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677141: iftop: possible memory leak
Hi!
Many thanks for the debugging and the explanation how to reproduce the
problem! I'll see that I upload a fixed version soonish, and ask Debian
release managers also for inclusion into the next point releases.
Best regards,
Alexander
Am 2013-05-05 21:24, schrieb Olivier Allard-Jacquin:
Hi,
according to e3zhbo6k AT arcor.de :
mail
Upstream didn't respond nor did they fix it.
The memory leak is in resolver.c introduced by commit Frédéric
Perrin patch for ipv6 reverse resolution via address structure that
retains IP family.. A struct addr_storage is always allocated in
resolve(). If dns resolution is turned off it will not be freed.
Possible fix?
diff --git a/resolver.c b/resolver.c
index c09de9d..e3b965d 100644
--- a/resolver.c
+++ b/resolver.c
@@ -472,15 +472,15 @@ void resolve(int af, void* addr, char* result,
int
buflen) {
int added = 0;
struct addr_storage *raddr;
-raddr = malloc(sizeof *raddr);
-memset(raddr, 0, sizeof *raddr);
-raddr-af = af;
-raddr-len = (af == AF_INET ? sizeof(struct in_addr)
- : sizeof(struct in6_addr));
-memcpy(raddr-addr, addr, raddr-len);
-
if(options.dnsresolution == 1) {
+raddr = malloc(sizeof *raddr);
+memset(raddr, 0, sizeof *raddr);
+raddr-af = af;
+raddr-len = (af == AF_INET ? sizeof(struct in_addr)
+ : sizeof(struct in6_addr));
+memcpy(raddr-addr, addr, raddr-len);
+
pthread_mutex_lock(resolver_queue_mutex);
if(hash_find(ns_hash, raddr, u_hostname.void_pp) ==
HASH_STATUS_OK) {/mail
/mail
I confirm this patch does fix memory leak issue.
Tested on both i386 and amd64 arch, with sources from
http://packages.debian.org/wheezy/iftop (iftop_1.0~pre2.orig.tar.gz
iftop_1.0~pre2-3.diff.gz)
Test procedure
iftop -n -i lo
ping -f localhost
top
- memory leak clearly appear after about 2min (~300Mo used)
- without -n parameter, there is no memory leak (iftop process use
about 45Mo)
/Test procedure
Best regards,
Olivier
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706931: microcom: newline handling doesn't work to driver debian installer
Hi! Am 2013-05-06 11:58, schrieb Uwe Kleine-König: when pressing Enter microcom sends a \n to the serial device. Minicom does instead send a \r. With \n it's not possible to drive the menus of the debian installer. Upstream patch 938404e757b232b13704400105c4cb908954bc76 fixes that. Can you please include that for the next upload? Or you could just create a new official upstream release ;) Best regards, Alexander PS: You'd like to adopt it? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701008: unblock: nagvis/1:1.6.6+dfsg.1-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package nagvis I uploaded a backport with wrong version to squeeze-backports, so upgrades from squeeze+squeeze-backports to wheezy are broken. The easiest fix is to bump the version in the sid/wheezy package to be higher again, so as discussed in #debian-release I uploaded a new package. The debdiff is: $ debdiff nagvis_1.6.6+dfsg.1-2.dsc nagvis_1.6.6+dfsg.1-3.dsc diff -Nru nagvis-1.6.6+dfsg.1/debian/changelog nagvis-1.6.6+dfsg.1/debian/changelog --- nagvis-1.6.6+dfsg.1/debian/changelog2012-06-11 18:45:44.0 +0200 +++ nagvis-1.6.6+dfsg.1/debian/changelog2013-02-20 11:40:40.0 +0100 @@ -1,3 +1,10 @@ +nagvis (1:1.6.6+dfsg.1-3) unstable; urgency=medium + + * Bump version number to allow smooth upgrades from squeeze-backports +(Containing a backport versioned 1:1.6.6+dfsg.1-3~bpo60+1 by mistake) + + -- Alexander Reichle-Schmehl toli...@debian.org Mon, 02 Jul 2012 12:46:07 +0200 + nagvis (1:1.6.6+dfsg.1-2) unstable; urgency=low [ The missed upload by 12 minutes release ] unblock nagvis/1:1.6.6+dfsg.1-3 -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691736: new list: debian-cloud
* Stefano Zacchiroli z...@debian.org [121029 10:56]: Name: debian-cloud Seconded. signature.asc Description: Digital signature
Bug#688581: RM: libpng (from experimental) -- package is fundamentally broken
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi! Am 24.09.2012 09:45, schrieb Julien Cristau: The current package in experimental is so broken it's not even funny. The maintainers haven't been able or willing to fix it in like 6 months, I don't think their opinion should matter at this point. A fixed package can easiy be reuploaded later anyway, it's not like this was a removal from sid. Okay, it's gone. Best regards, Alexander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJQYIyfAAoJEMJLZaJnLIsSVicP/0M+dPwHeJxNNptG8QOAoQH7 Ip5In3CHf/8y6tMkBZmY3SNPT2RU2jzykqltQwy01mI68z12/4QzLojJ5pc/swJq 66O0O1VCWoEguTCGhjdQ5HKc2rQVOGxC/B5yX7r1YF3MMRpUvCrc2ASAJ03EFhd2 Sewx88yyOiGfp8eDtcIXFp8Ubfw5ayKYMnCZrVEDyCvvrAc6TotSEQWE7dHWlCo9 zJZBbCUH1tkOGI6XdCjjZKPmhTXnAL8rxKAtXBFnwS4r0FjiSgOb3lO4gXDghYmN WZiR6I/WU7WOoEd4ITEcj4I8sT6EpFdy74lcFD25ED0UaQJdg5FXdP8FKxuggudH B03wWuwNZsBhdZ04ADwlT5733DKFqTE759rSFENW+XDn3xBDL5zGNrOJgS+P5bu8 ZXh3LTTmkVnP21qJ8d1i5WvbnzrPipNqIxZwAf+hUzjzyXVlW5njIDtE/HBi02jP XjRf0bQPP9NA4WdW4Sbd5KBOOx7EMDwu+t4NJ+l614Cag6KLknSkHDqaQSJ7O30f IYzZzwu1ISu1abySzE0JCJcenf9gdC7t23T+vI+OPGMCW/8GslXyh/+amjoJt1Pk p88sHCn2wVcqfv9WF2ZZBaXXVdGP9iuVekNKiwjj6Rbz18p0cbOzKEBNiI08hgG7 EBF+gBuVP7dLIyE8c7mn =ZLaS -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688672: RM: gassst/1.28-2
Package: release.debian.org Hi! Am 24.09.2012 16:16, schrieb Olivier Sallou: Hi ftpmasters, could you please remove package gassst from testing due to bug #680433. Removals from testing are done by the release team. Creating a bug report for them. Best regards, Alexander signature.asc Description: OpenPGP digital signature
Bug#688581: RM: libpng (from experimental) -- package is fundamentally broken
tags 688581 + moreinfo
thanks
Hi Sjoerd!
As far as I can see you are not listed as maintainer or uploader of said
package, and we generally try to avoid removing packages against the
will of the maintainers. Therefore I'm CCing Anibal and Nobuhiro, so
they can comment.
* Sjoerd Simons sjo...@debian.org [120923 23:00]:
The libpng package in experimental (1.5.11-1) is incredibly broken and has
been
so since at least december last year. Some grave bugs caused by this are
#652001 and #673542 (open since respectively last december and last may).
While this is ofcourse an experimental package, it seems to be so
fundamentally
broken it shouldn't ever have been near any section of the debian archive
ever.
Imho the bit that says it all is:
$ head -n1 libpng12-0.links.in
/lib/${DEB_HOST_MULTIARCH}/libpng15.so.15
/usr/lib/${DEB_HOST_MULTIARCH}/libpng12.so.0
Even though libpng15 and libpng12 aren't ABI compatible.. The packaging turns
out
to do the same for the -dev packages (symlinking even though the APIs aren't
compatible).
While an NMU would be possible, it seems best (at least to me) to simply
remove the package
from the archive until that time.
Best regards,
Alexander
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687797: RM: ipset-source -- NBS; not built anymore
tags 687797 +moreinfo thanks Hi Arno! * Arno Töll a...@debian.org [120916 00:11]: please remove the ipset-source binary package. It is not built anymore by any source package. It's original producer was the ipset source package, which stopped doing so as of ipset (6.11-1) uploaded Sat, 04 Feb 2012 14:44:50 +0700. Maybe I'm missing something, but I can find ipset-source only in stable: tolimar@franck:~$ dak ls -S ipset-source ipset-source |2.5.0-1 |stable | all Best regards. Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687920: RM: phy-spread -- ROM; Package es renamed in unstable (only!)
tags 687920 +moreinfo thanks Hi Andreas! * Andreas Tille ti...@debian.org [120917 08:49]: [..] The package should *not* be removed from testing. If this request is hard to fullfill with dak I do not see any problem to close this bug after the release. Sorry, but package removals in unstable propagate to automatically to testing, unless something in testing depends the removed package. As that doesn't seem to be the case here, I tag this bug moreinfo. So it will appear from our immediate removal radar. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687797: RM: ipset-source -- NBS; not built anymore
reassing 687797 www.debian.org tags 687797 -moreinfo retitle 687797 ipset-source package listed for unstable although it has been removed thanks Hi Arno! * Arno Töll a...@debian.org [120918 00:06]: there appears to be an arch:all package in Sid at that version. At least, that's what [1] suggests. That said, I cannot find it in the Packages.gz file on mirrors either. This looks weird to me, maybe you can help me, to tell what's going on here. Could it be, the packages.d.o site lists an obsolete arch:all package from a Debian port? [1] http://packages.debian.org/sid/ipset-source Sorry, I have no idea, how packages.debian.org works, so I can't be of help here. Best thing I can do is to reassign this bug to the web team. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686697: RM: desktopcouch -- ROM; RC buggy, not installable
clone 686697 -1 reassign -1 python-dmedia retitle -1 Depends on obsoleted package desktopcouch / desktopcouch-tools severity -1 important block 686697 by -1 tags 686697 +moreinfo thanks Hi David, hi dmedia maintainers! * David Paleino da...@debian.org [120904 22:21]: please remove source package desktopcouch from Debian. - It's always been quite buggy, and has received not too much love from upstream either, AFAICS. - I myself haven't used it in a while, and seems like only one other Debian user ever used it (or, reported bugs). - It's been for a while in RFA state, with no one popping up for adoption. - It depends on a now removed package (ubuntu-sso-client), thus not installable. Please remove it from the archive. Will do, as soon as the reverse dependencies are resolved, but currently it looks like this: Checking reverse dependencies... # Broken Depends: dmedia: python-dmedia So I'll clone this bug to dmedia, as python-dmedia needs to stop depending on desktopcouch first. BTW: ubuntu-sso-client hasn't been removed, yet. It's scheduled to be removed (see Bug #686362 for details), but we'll wait for desktopcouch to be solved, before removing it. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681285: RM: module-init-tools -- ROM; replaced by kmod
tags 681285 +moreinfo thanks * Alexander Reichle-Schmehl toli...@debian.org [120903 15:35]: Could you please confirm that it is now save to remove module-init-tools now that #683790 has been solved? Just trying not to break anything again ;) From #debian-ftp: 12-09-03 17:10:26 DktrKranz KiBi: with your d-i hat on, do you think it's safe for module-init-tools to go away? (see #681285) 12-09-03 17:12:43 KiBi I'll reply to that mail when I can.. 12-09-03 17:13:34 DktrKranz thanks 12-09-03 17:22:16 KiBi probably after beta2 is out, meaning after cd images are built, meaning after ftpmasters have copied d-i Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682896: Please remove doc-linux-de
Hi! * Alexander Reichle-Schmehl toli...@debian.org [120726 22:19]: Okay, but first let's ask the current maintainer for any comments. No maintainer reaction for quite some time; I'm going on with the removal. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686362: RM: ubuntu-sso-client -- RoQA; outdated, RC-buggy, unused
tags 686362 +moreinfo clone 686362 -1 reassign -1 desktopcouch retitle -1 Depends on removed package ubuntu-sso-client severity -1 important block 686362 by -1 thanks Hi! * Moritz Muehlenhoff j...@debian.org [120831 17:40]: Please remove ubuntu-sso-client: - It's totally outdated in comparison to upstream - Very low popcon - Just a single upload 16 months ago - No followup to RC bug 680492 since more than six weeks desktopcouch depends on ubuntu-sso-client, so I'm not removing it for now but CC desktopcouch's maintainers for comments. Your options are: To adopt ubuntu-sso-client, drop the dependency on it or ask for your package to get removed, too. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686577: RM: fparser -- ROM; RC buggy, no more rdepends
Hi Scott! * Scott Howard showard...@gmail.com [120320 23:17]: please remove fparser from unstable. It is RC buggy, the packages that depended on it have switched to muparser, and upstream doesn't believe in shared libraries so we've been maintaining the build system which is now giving us problems. There seem to have been a problem with your mail, as we just received it now. So just to be on the safe side, could you confirm that you'd still like fparser to be removed from the Debian archive? Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681285: RM: module-init-tools -- ROM; replaced by kmod
Hi! Could you please confirm that it is now save to remove module-init-tools now that #683790 has been solved? Just trying not to break anything again ;) Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686481: debian-reference instructs users on how to install non-free software
Hi! Am 03.09.2012 15:14, schrieb Osamu Aoki: If the bug reporter wishes to kill everything about non-free from Debian related documents and archive area, I can tell him to go to the source :-) Debian policy (Sure this is in our main area which is the real Debian system) 2.2.3 The non-free archive area http://www.debian.org/doc/debian-policy/ch-archive.html#s-non-free If the bug reporter can convince Debian folks in debian-project to agree to remove these writings on non-free in our policy and make Debian not to have non-free area, I will reconsider this bug report. [..] Policy is the wrong point to start removing policy. non-free (and contrib FWIW) are written down in social contract §5, so we would need to change that first. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684114: RM: beast-doc [armel armhf ia64 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390 s390x sparc] -- ANAIS; Binary package should never have been existed
tags 684114 +moreinfo thanks Hi! * Andreas Tille ti...@debian.org [120807 08:57]: it seems that some binary packages for arches were autobuilded for a package in contrib even if they should not (because of its non-free dependencies). I would like you to remove beast-doc for the following architectures: armel armhf ia64 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390 s390x sparc ATTENTION: The package beast-doc is also builded from the beast package. The removal above is for the binary package which was created from the source beast-mcmc. Sorry for the confusion. Uhm... I'm confused. Or dak is, or we both are. The current state is: tolimar@franck:~$ dak ls beast-doc beast-doc |0.7.4-4 | testing | all beast-doc |0.7.4-4 | unstable | all beast-doc |1.6.2-1 | unstable/contrib | all So we can't remove it from the named architectures, as it's arch any (which makes sense, as it is a doc package). So, and if I understand correctly, you want the beast-doc/1.6.2-1 to be removed, correct? I think we might need help from a ftp-master here; it appears I can only remove both package (0.7.4-4 as well ass 1.6.2-1). Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683554: RM: horde3 and reverse dependencies -- ROM; Obsolete version
clone 683554 -1 clone 683554 -2 clone 683554 -3 clone 683554 -4 clone 683554 -5 clone 683554 -6 clone 683554 -7 clone 683554 -8 clone 683554 -9 clone 683554 -10 clone 683554 -11 clone 683554 -12 clone 683554 -13 clone 683554 -14 clone 683554 -15 clone 683554 -16 retitle 683554 RM: horde3 -- ROM; Obsolete retitle -1 RM: ansel1 -- ROM: Depend on obsoleted horde3 retitle -2 RM: chora2 -- ROM: Depend on obsoleted horde3 retitle -3 RM: dimp1 -- ROM: Depend on obsoleted horde3 retitle -4 RM: gollem -- ROM: Depend on obsoleted horde3 retitle -5 RM: horde-sam -- ROM: Depend on obsoleted horde3 retitle -6 RM: imp4 -- ROM: Depend on obsoleted horde3 retitle -7 RM: ingo1 -- ROM: Depend on obsoleted horde3 retitle -8 RM: kronolith2 -- ROM: Depend on obsoleted horde3 retitle -9 RM: mnemo2 -- ROM: Depend on obsoleted horde3 retitle -10 RM: nag2 -- ROM: Depend on obsoleted horde3 retitle -11 RM: sork-forwards-h3 -- ROM: Depend on obsoleted horde3 retitle -12 RM: sork-passwd-h3 -- ROM: Depend on obsoleted horde3 retitle -13 RM: sork-vacation-h3 -- ROM: Depend on obsoleted horde3 retitle -14 RM: turba2 -- ROM: Depend on obsoleted horde3 reassign -15 release.debian.org reassign -16 release.denian.org retitle -15 RM: php-kolab-filter/0.1.9-4.1 retitle -16 RM: php-kolab-freebusy/0.1.5-3 user release.debian@packages.debian.org usertags -15 rm usertags -16 rm thanks Hi! * Mathieu Parent math.par...@gmail.com [120801 19:08]: Please remove the following packages from unstable (then testing/wheezy), they are obsolete|1] and not supported anymore: [..] Will do, but we need sepperate bug reports for them, hence the clones above. Please note that we (as the ftp team) will remove the packages only from unstable. The removal of these packages however should propagate to testing automatically (as soon as it would brake any reverse-depends; as you want all remover that should happen pretty quickly). Please also remove the following packages managed by the pkg-kolab team, from testing only: php-kolab-filter php-kolab-freebusy Removals from testing are done by the release team; cloning some bugs for them, too. The php-horde-* packages are meant to replace them (Horde = 4). Hmmm... As that is a quite trastic change you might want to propose a paragraph for the release notes? IIRC that's done by filling a bug against the package release-notes. Best regars, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683616: www.debian.org: Please document usage of usertags on bugs pages
Package: www.debian.org Severity: normal Hi! It seems that the usage of usertags is not documented anywhere on www.debian.org/Bugs/. At least http://www.debian.org/Bugs/server-control should mention, that one can set them by specifing user email (if different from sender) and setting them via usertag bugnumber tag. Best regards, Alexander -- System Information: Debian Release: 6.0.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683554: RM: horde3 and reverse dependencies -- ROM; Obsolete version
tags 683554 moreinfo thanks Hi again! * Mathieu Parent math.par...@gmail.com [120801 19:08]: Please remove the following packages from unstable (then testing/wheezy), they are obsolete|1] and not supported anymore: ansel1 chora2 dimp1 gollem horde-sam imp4 ingo1 kronolith2 mnemo2 nag2 sork-forwards-h3 sork-passwd-h3 sork-vacation-h3 turba2 As you probably noticed these packages are now gone from unstable, and should also be removed from testing soonish. However, there seems to be a problem with: horde3 Trying to remove it results in: # Broken Depends: php-kolab-filter: php-kolab-filter php-kolab-freebusy: php-kolab-freebusy # Broken Build-Depends: php-horde-activesync: pear-horde-channel php-horde-alarm: pear-horde-channel php-horde-argv: pear-horde-channel php-horde-auth: pear-horde-channel php-horde-autoloader: pear-horde-channel php-horde-browser: pear-horde-channel php-horde-cache: pear-horde-channel php-horde-cli: pear-horde-channel php-horde-compress: pear-horde-channel php-horde-constraint: pear-horde-channel php-horde-controller: pear-horde-channel php-horde-core: pear-horde-channel php-horde-crypt: pear-horde-channel php-horde-data: pear-horde-channel php-horde-date: pear-horde-channel php-horde-date-parser: pear-horde-channel php-horde-db: pear-horde-channel php-horde-editor: pear-horde-channel php-horde-exception: pear-horde-channel php-horde-form: pear-horde-channel php-horde-group: pear-horde-channel php-horde-history: pear-horde-channel php-horde-http: pear-horde-channel php-horde-icalendar: pear-horde-channel php-horde-image: pear-horde-channel php-horde-imap-client: pear-horde-channel php-horde-injector: pear-horde-channel php-horde-itip: pear-horde-channel php-horde-lock: pear-horde-channel php-horde-log: pear-horde-channel php-horde-logintasks: pear-horde-channel php-horde-mail: pear-horde-channel php-horde-mime: pear-horde-channel php-horde-mime-viewer: pear-horde-channel php-horde-nls: pear-horde-channel php-horde-notification: pear-horde-channel php-horde-perms: pear-horde-channel php-horde-prefs: pear-horde-channel php-horde-rdo: pear-horde-channel php-horde-role: pear-horde-channel php-horde-rpc: pear-horde-channel php-horde-secret: pear-horde-channel php-horde-serialize: pear-horde-channel php-horde-sessionhandler: pear-horde-channel php-horde-share: pear-horde-channel php-horde-spellchecker: pear-horde-channel php-horde-stream-filter: pear-horde-channel php-horde-stream-wrapper: pear-horde-channel php-horde-support: pear-horde-channel php-horde-syncml: pear-horde-channel php-horde-template: pear-horde-channel php-horde-text-diff: pear-horde-channel php-horde-text-filter: pear-horde-channel php-horde-text-filter-csstidy: pear-horde-channel php-horde-text-flowed: pear-horde-channel php-horde-token: pear-horde-channel php-horde-translation: pear-horde-channel php-horde-tree: pear-horde-channel php-horde-url: pear-horde-channel php-horde-util: pear-horde-channel php-horde-vfs: pear-horde-channel php-horde-view: pear-horde-channel php-horde-xml-element: pear-horde-channel php-horde-xml-wbxml: pear-horde-channel php-kolab-filter: pear-horde-channel php-kolab-freebusy: pear-horde-channel Breaking php-kolab-filter and php-kolab-freebusy is probably okay, as you requested their removal from testing, however all the build-depends on pear-horde-channel look like a problem. Maybe I missed something, but I couldn't find an other package providing pear-horde-channel, nor is there dummy package available build from a higher horde version. Could you please check, that removing horde3 won't result in a lot FTBFS bugs? Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639472: pgsql-asn1oid: Please move from postgresql-8.4 to postgresql-9.1
Hi! * Martin Pitt mp...@debian.org [110827 15:31]: as announced recently [1] we want to move Debian unstable/testing to postgresql-9.1 and drop postgresql-8.4 and -9.0 completely. Please rebuild this package against postgresql-server-dev-9.1 instead of -8.4, or consider just using postgresql-server-dev-all. [..] [1] http://lists.alioth.debian.org/pipermail/pkg-postgresql-public/2011-August/000570.html Just asmall update: ftpmaster just removed postgresql-server-dev-8.4, so this package now FTBFS due to unresolvable build-depends. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682896: Please remove doc-linux-de
retitle 682896 RM: doc-linux-de -- RoQA outdated tags 682896 moreinfo severity 682896 important thanks [ resending mail with unbroken header; sorry for the inconvenience ] Hi! * Martin Eberhard Schauer martin.e.scha...@gmx.de [120726 21:47]: by accident I had a look at my old mails (1). The improved machine translation is roughly How are the German HOWTOs involved? Those responsible have disappeared, but the HOWTOs crop up yet. Is the whole project dead? Smells like somehow like this ... : - 1: http://lists.debian.org/debian-l10n-german/2011/02/msg00070.html Okay, but first let's ask the current maintainer for any comments. I choose severity grave because it is so outdated that it seems to me that its age makes the package in question unusable or mostly so. Uhm... Well, it doesn't actually matter much for removal bugs, but I don't think (partly?) outdated documentation is release critical. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681560: Please upgrade source format and don't store changes to config/config.*
tags 681560 +wontfix -patch thanks Hi! * Graham Inggs graham.in...@uct.ac.za [120714 11:27]: The attached patch upgrades to source format 3.0 (quilt) and prevents changes to config/config.guess and config/config.sub from being stored. For this package I don't see any benefit in migrating to source format 3.0, so I'm currently not considering doing it. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593463: MySQL is still in unstable (Re: Bug#593463 closed by Debian FTP Masters ftpmas...@ftp-master.debian.org (Bug#680362: Removed package(s) from unstable))
Hi! On 11.07.2012 04:45, Filipus Klutiero wrote: Although mysql-5.1 was indeed removed from unstable, MySQL wasn't. mysql-5.1 was simply removed because MySQL has a version number in source package names and the number changed. MySQL is now packaged as mysql-5.5: http://packages.qa.debian.org/m/mysql-5.5.html Citing from our mail to the maintainers: We try to close Bugs which have been reported against this package automatically. But please check all old bugs, if they where closed correctly or should have been re-assign to another package. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680748: RM: loop-aes-utils -- RoQA; unsupported
tags 680748 +moreinfo clone 680748 -1 reassign -1 partman-crypto-loop retitle -1 Depends on obsoleted package loop-aes-utils severity -1 important block 680748 by -1 thanks Hi! * Bastian Blank wa...@debian.org [120708 12:53]: The old loop-aes support is dead. dm-crypt with cryptsetup supports this modes in the meantime for backward compatibility. Sorry, can't do right now: Checking reverse dependencies... # Broken Depends: partman-crypto: partman-crypto-loop Cloning this bug to partman-crypto. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680205: RM: canorus/0.7+dfsg+svn1256-2 -- RoM, has RC bug #679297
reassign 680205 release.debian.org user release.debian@packages.debian.org usertags +rm thanks Hi! On 04.07.2012 14:08, Tobias Quathamer wrote: I would like you to remove canorus from testing. Removals from testing are done by the release team. So reassigning this bug. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679748: RM: ia32-libs [ia64] -- RoM; ANAIS; No longer supported by kernel
clone 679748 -1 clone 679748 -2 clone 679748 -3 clone 679748 -4 clone 679748 -5 reassign -1 fglrx-driver reassign -2 pluginwrapper reassign -3 nvidia-graphics-drivers-legacy-173xx reassign -4 nvidia-graphics-drivers reassign -5 wine-unstable severity -1 serious severity -2 serious severity -3 serious severity -4 serious severity -5 serious tags -1 wheezy, sid tags -2 wheezy, sid tags -3 wheezy, sid tags -4 wheezy, sid tags -5 wheezy, sid retitle -1 build depends on obsoleted package ia32-libs on ia64 retitle -2 build depends on obsoleted package ia32-libs on ia64 retitle -3 build depends on obsoleted package ia32-libs on ia64 retitle -4 build depends on obsoleted package ia32-libs on ia64 retitle -5 build depends on obsoleted package ia32-libs on ia64 thanks Hi maintainers! Your package build depends on ia32-libs, which is scheduled to be removed on ia64 making your package FTBFS on that arch. For details please see #679748. Please either drop that build dependency somehow, or reassign the bug back to ftp.debian.org asking for removal of your package on said ia64 (and remove ia64 from your packages arch list). Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679748: RM: ia32-libs [ia64] -- RoM; ANAIS; No longer supported by kernel
On 04.07.2012 15:23, Alexander Reichle-Schmehl wrote: Your package build depends on ia32-libs, which is scheduled to be removed on ia64 making your package FTBFS on that arch. ... which is okay, as your package isn't build on ia64 anyway. Sorry for the noise; apparently dak was a bit strict when checking reverse depends. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680072: RM: sugar-hulahop -- ROM; dead upstream; too difficult to adapt to recent PyXPCOM
clone 680072 -1 reassign -1 pyjamas-desktop severity -1 serious retitle -1 Depends on obsoleted package sugar-hulahop block 680072 by -1 thanks Hi! * Alexander Reichle-Schmehl alexan...@schmehl.info [120703 15:41]: As subject says: sugar-hulahop is too difficult to adapt to recent PyXPCOM and is dead upstream. Sorry, can't do, yet: Checking reverse dependencies... # Broken Depends: pyjamas: pyjamas-desktop sugar-browse-activity-0.84: sugar-browse-activity-0.84 sugar-browse-activity-0.86: sugar-browse-activity-0.86 Thanks for your work so far to solve the issues, now only pyjamas remains. I didn't notice, that pyjamas isn't also maintained by you like the other packages, so I open a new bug report against that package to get the issue tracked. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679937: RM: haskell-cryptocipher and reverse dependencies [powerpc] -- ROM; Broken on powerpc, no fix in sight
tags 679937 +moreinfo thanks Hi Joachim! Could you please recheck your removal requests? Somethings seems to be wrong. * Joachim Breitner nome...@debian.org [120702 17:35]: haskell-cryptocipher/0.2.14-1 Only found 0.3.0-3. haskell-clientsession/0.7.3.1-1 No powerpc binaries found. haskell-cprng-aes/0.2.1-1 Only found 0.2.3-3 packages. haskell-tls/0.8.1-1 Only found 0.9.5-1. haskell-tls-extra/0.4.0-1 Only found 0.4.6-1. haskell-authenticate/0.10.3.1-1 Only found 1.0.0.1-1 haskell-hledger-web/0.18-1 No powerpc binaries found. haskell-http-enumerator/0.7.1.8-1 Not found at all, 0.7.3 got removed on the 2012-05-19. haskell-yesod-core/0.9.3.4-1 No powerpc binaries found. haskell-yesod/0.9.3.4-1 No powerpc binaries found. haskell-yesod-auth/0.7.7-1 No powerpc binaries found. haskell-yesod-form/0.3.4-1 No powerpc binaries found. haskell-yesod-json/0.2.2.1-1 No powerpc binaries found. haskell-yesod-persistent/0.2.2-1 No powerpc binaries found. haskell-yesod-static/0.3.2-1 No powerpc binaries found. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679699: RM: pppstatus -- ROM; Dead upstream (for many years), little used (2. try)
Hi! On 03.07.2012 15:22, Joachim Wiedorn wrote: now I have seen there is another tool which make (nearly) the same: slurm. So there is no need to reactivate pppstatus. Sorry for cause trouble. Well, based upon the last source package, you fix known bugs and improve the packaging. When you have a good release ready, you can ask on the debian-mentors lists for reviews and a sponsor to upload your package to the archive. In theory your next step would then be to ask the release team for a freeze exception, providing them with a diff between the old version and the new one. However, they might not accept the introduction of new packages into the release at that point. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680072: RM: sugar-hulahop -- ROM; dead upstream; too difficult to adapt to recent PyXPCOM
tags 680072 +moreinfo thanks * Jonas Smedegaard d...@jones.dk [120703 13:12]: As subject says: sugar-hulahop is too difficult to adapt to recent PyXPCOM and is dead upstream. Sorry, can't do, yet: Checking reverse dependencies... # Broken Depends: pyjamas: pyjamas-desktop sugar-browse-activity-0.84: sugar-browse-activity-0.84 sugar-browse-activity-0.86: sugar-browse-activity-0.86 Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680103: www.debian.org: Debian testing security team apparently inactive
Package: www.debian.org Severity: important Hi! http://www.debian.org/security/faq.en.html#testing reads: The Debian testing security team handles issues for testing. They will make sure that the fixed packages enter testing in the usual way by migration from unstable (with reduced quarantine time), or, if that still takes too long, make them available via the the normal http://security.debian.org infrastructure. I'm not entirely sure (hence the CC to the team), but it seems to me, that the testing security team is kind of inactive. Judging from the archives of their mailing lists at http://lists.debian.org/debian-testing-security-announce/ and http://lists.alioth.debian.org/pipermail/secure-testing-team/. Please correct me, if I got the wrong impression and close the bug, but if it's the case, this paragraph should be rewritten. Best regards, Alexander -- System Information: Debian Release: 6.0.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679862: RM: papyon -- ROM; dead project
tags 679862 +moreinfo clone 679862 -1 reassign -1 telepathy-butterfly retitle -1 Depends on obsolete package papyon severity -1 important block 679862 by -1 thanks Hi! * Devid Antonio Filoni devid...@gmail.com [120702 09:25]: Please remove papyon package, upstream looks dead and last commit was a year ago. Sorry, but it's still used: Checking reverse dependencies... # Broken Depends: telepathy-butterfly: telepathy-butterfly Dear telepathy maintainers, would it be possible to drop that dependency? Best regards. Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679915: RM: telepathy-butterfly -- ROM; dead project, replaced by telepathy-haze and libpurple
tags 679915 +moreinfo clone 679915 -1 reassign -1 meta-kde-telepathy retitle -1 meta-kde-telepathy depends on obsoloete package telepathy-butterfly block 679915 by -1 thanks Hi! * Laurent Bigonville bi...@debian.org [120702 15:22]: Yes please remove telepathy-butterfly package. This telepathy connection-manager is not maintained anymore. It has been replaced by telepathy-haze and libpurple or by telepathy-gabble when connecting to MSN using XMPP. Thanks for your fast answer, however we currently can't remove telepathy-butterfly, too: # Broken Depends: meta-kde-telepathy: kde-telepathy-minimal So cloning this bug again to the KDE people. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679629: powertop: FTBFS on ia64: required file `./ar-lib' not found
Package: powertop
Version: 2.0-0.1
Severity: serious
Hi!
powertop currently FTBFS on ia64 with the following error message:
config.status: creating po/POTFILES
config.status: creating po/Makefile
config.status: executing depfiles commands
config.status: executing libtool commands
configure: WARNING: unrecognized options: --disable-maintainer-mode,
--disable-silent-rules
touch debian/stamp-autotools
/usr/bin/make -C .
make[1]: Entering directory
`/build/buildd-powertop_2.0-0.1-ia64-XBFoMz/powertop-2.0'
CDPATH=${ZSH_VERSION+.}: cd . /bin/bash
/build/buildd-powertop_2.0-0.1-ia64-XBFoMz/powertop-2.0/missing --run
aclocal-1.11 -I m4
cd . /bin/bash
/build/buildd-powertop_2.0-0.1-ia64-XBFoMz/powertop-2.0/missing --run
automake-1.11 --foreign
configure.ac:17: required file `./ar-lib' not found
configure.ac:17: `automake --add-missing' can install `ar-lib'
make[1]: *** [Makefile.in] Error 1
make: *** [debian/stamp-makefile-build] Error 2
make[1]: Leaving directory
`/build/buildd-powertop_2.0-0.1-ia64-XBFoMz/powertop-2.0'
Best regards,
Alexander, who stumbled over this while working on #671931
-- System Information:
Debian Release: 6.0.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671931: RM: libnl2 -- ROM; obsolete, unmaintained
tags 671931 +moreinfo block 671931 by 679629 thanks Hi! * Michael Biebl bi...@debian.org [120628 19:47]: All reverse dependencies have been updated and libphone-ui-shr just needs a simple binNMU, which I've requested as #679438. Sorry, but dak begs to differ: Checking reverse dependencies... # Broken Depends: phoneuid: phoneuid [amd64 armel armhf i386 ia64 mips mipsel powerpc s390 s390x sparc] powertop: powertop [ia64] # Broken Build-Depends: powertop: libnl2-dev The ia64 problem is due to outdated binaries on that arch, as powertop 2.0-0.1 FTBFS on ia64. I opened #679629 for that. However, I'm not sure about phoneuid. Re-assigning to ftp.debian.org to get the package removed. Once the above mentioned problems are solved, we'll do it gladly. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677746: RM: ia32-libs-core -- ROM; Kernel support removed
tags 677746 + moreinfo thanks Hi! * Goswin von Brederlow goswin-...@web.de [120616 18:53]: I've been told that some time ago the ia64 port has dropped the kernel support for 32bit on ia64. So ia32-libs-core is now obsolete. What about the following: Debiaa32-libs: ia32-libs [ia64] ia32-libs-gtk: ia32-libs-gtk [ia64] # Broken Build-Depends: ia32-libs: ia32-libs-core ia32-libs-gtk: ia32-libs-core Please open sepperate bugs, if they should be removed, too. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677661: RM: microcom [kfreebsd-amd64 kfreebsd-i386] -- ANAIS; New upstream release is linux only
Package: ftp.debian.org Severity: normal Hi! Please remove the binaries from microcom for kfreebsd.amd64 and kfreebsd-i386. The lates upstream release is (currently) linux only due to the support of a feature (CAN support) which appears to be not available on kfreebds-*. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677556: frozen-bubble: Server doesn't start; looks for binary in wrong path
Package: frozen-bubble Version: 2.212-2 Severity: important Dear Maintainer, I tried to play frozen-bubble in a local network (start lan game). After it failed to find a server, it also failed to start one. On the console I saw the messade: /usr/games/fb-server is missing or not executable! Symlinking /usr/lib/games/frozen-bubble/fb-server to /usr/games/fb-server solved the issue for me, so I guess it get's installed in the wrong directory. Best regards, Alexander -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages frozen-bubble depends on: ii frozen-bubble-data 2.212-2 ii libalien-sdl-perl 1.430-4 ii libc6 2.13-33 ii libcompress-bzip2-perl 2.09-2+b2 ii libglib2.0-02.32.3-1 ii liblocale-gettext-perl 1.05-7+b1 ii libsdl-mixer1.2 1.2.12-2 ii libsdl-pango1 0.1.2-6 ii libsdl-perl 2.540-1 ii libsdl1.2debian 1.2.15-3 ii perl5.14.2-11 ii perl-base [perlapi-5.14.2] 5.14.2-11 frozen-bubble recommends no packages. frozen-bubble 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#677141: iftop: possible memory leak
tags 677141 +unreproducible thanks Hi Olivier! * olivier olivie...@free.fr [120611 22:34]: since last iftop upgrade (probably iftop:i386 0.17-19 - 1.0~pre2-2 ), I've observe that iftop memory usage increase constantly. I use iftop since many years, and I never observe this behaviour. 2 computers are affected (both under testing), and upgradinng iftop:i386 1.0~pre2-2 - 1.0~pre2-3 (unstable .deb) does not fix issue. [..] Architecture: i386 (i686) Many thanks for your bug report! However, I'm sorry that so far I fail to reproduce it on my machines. The only difference I see so far is that my test machines are running amd64. Is the second machine you noticed this problem also an i386 based one? Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674859: [BTS#674859] templates://nagvis/{nagvis.templates} : Final update for English review
Hi Bubulle! * Christian PERRIER bubu...@debian.org [120601 07:12]: Please avoid uploading a package with fixed or changed debconf templates and/or translation updates in the meantime. Of course, other changes are safe. [..] Around Tuesday, June 26, 2012, I will contact you again and will send a final patch summarizing all the updates (changes to debconf templates, updates to debconf translations and new debconf translations). Just to avoid misunderstandings: I may upload the new upstream release (and should given that we are approaching a freeze), however that upload should not yet include the reviewed english template or and tranlsations, correct? Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669150: RM: liboce-*1 -- RoM
clone 669150 -1 retitle -1 RM: elmer elmer-dbg libelmer-dev [armel armhf] -- RoQA FTBFS; hinders package from migrating to testing thanks Hi! * D. Barbier bou...@gmail.com [120608 10:56]: What about removing elmerfem on armel and armhf? I understand, it is not the best solution. But, for example, freecad is hanging in sid since March not being able to migrate to testing because of this. AFAICT there has been no progress on the R front (#672749) and OCE is ready to migrate, so your suggestion seems reasonable. Okay, let's remove it then. Will do so soonish. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676326: reportbug: Version check via madison seems to pick up hurd-i386 versions on i386
Package: reportbug Version: 6.3.1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, I was about to report a bug against the package aisleriot, but got the following message: - -- alex@undine:~$ reportbug aisleriot [..] Getting status for aisleriot... Checking for newer versions at madison... Your version (1:3.4.1-1) of aisleriot appears to be out of date. The following newer release(s) are available in the Debian archive: unstable: 1:3.4.1-1+b1 Do you still want to file a report [y|N|q|?]? - -- However, that version is only available in hurd-i386: - -- alex@undine:~$ rmadison -a i386,hurd-i386 -s sid aisleriot aisleriot | 1:3.4.1-1| sid | i386 aisleriot | 1:3.4.1-1+b1 | sid | hurd-i386 - -- That was on a i386 system. I was unable to reprpduce it on my amd64 box. Best regards, Alexander - -- Package-specific info: ** Environment settings: DEBEMAIL=toli...@debian.org EMAIL=alexan...@schmehl.info DEBFULLNAME=Alexander Reichle-Schmehl ** /home/alex/.reportbugrc: sign gpg email toli...@debian.org realname Alexander Reichle-Schmehl - -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages reportbug depends on: ii apt 0.9.5.1 ii python2.7.2-10 ii python-reportbug 6.3.1 reportbug recommends no packages. Versions of packages reportbug suggests: ii debconf-utilsnone ii debsums none ii dlocate none ii emacs22-bin-common | emacs23-bin-common none ii file 5.11-1 ii gnupg1.4.12-4 ii postfix [mail-transport-agent] 2.9.1-5 ii python-gtk2 2.24.0-3 ii python-gtkspell 2.25.3-11 ii python-urwid none ii python-vte none ii xdg-utils1.1.0~rc1+git20111210-6 Versions of packages python-reportbug depends on: ii apt 0.9.5.1 ii python2.7.2-10 ii python-debian 0.1.21 ii python-debianbts 1.11 ii python-support1.0.14 python-reportbug suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJPzwtPAAoJEMJLZaJnLIsStwAP/im9gpmyFi9fERNPewKYnPse TW9zEY3wsUgXl/3N6xq5pxBMO9AEgWFgNPx0RBgaI6lltm/6aDgZjG3KQTWpmsUX PSn91pEzGjsb0jmH587RBYtO0IrKLRfaM22ctRfkHZVW284elWM2XZme7n8AXMAG TxTq4DaZ89I/LkFIU5bXDUbZ4F8VAOrRl3Kc5SCWZQgbtai040c8bUUAOsRskiUP Sbc/K2WUQFenAfXiXDE5Wb+3U8JMr8tlhCqxgyPxA3dbipcNNxXktx+7/NafWCNz 0opn0DxCfU2ejDIQXQWPFGJl7y6tl4duofCD9aDjs1Y0ETRwfOreO1dP+6yTP4PW Armm+A1tAGioOq7OIXykk5mNOSHUml9r/Os4uSP5wGAYbTfleDG8t26xGyMHLNo7 FWO2f1XZawciiWL/zJEhsOeJPejsTERHjBxTNNO6Py+HRSsjdCtXI7hepYoMDoRr L1DIFYcXA3ab+SEeyquMY5JeZHgrNqvZrOop7JN8/fAl2YrjpqvIuwRyKIKlRgRr q/FRsp9tJcK9QRJpRhQ1afl/UyCuGUHsHsso1MwsXt+rU8PsB7rSn3gWC//xXCJQ tUhnvWJuGNeoE9KVi+JT0hkKkM3QIXFjKq5GFLTBkfaSYdcLlmpfSz7xeHikK3iL vT8MlQNrcbe3n/XowJkg =SWTP -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673096: Bug#674850: Bug#675167: Bug#674850: RM: figlet -- RoQA; license which specifically excludes the right to re-distribute
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi! On 04.06.2012 19:56, Julien Cristau wrote: There seems to be just about 0 creative content in that file. What exactly is the problem with it? Figlet 2.2.5 has just been released with the following changelog [1]. That doesn't seem to answer the above question. The problem is that someone claims that he has copyrights on some of these files. It doesn't actually matter, what I or anyone else thinks about that, unless it's a judge ruling that said files are not copyrightable. Best regards, Alexander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJPzQzPAAoJEMJLZaJnLIsSpR0P+gPw6X5ZoP32wMnlqJB8dKA7 wXAaoHDSsWn8oGQXvHOI9tysic+jcjKnjbbaqXlyr+YMeTNPWlxFieHtmRMhNv7l komcM7ckMfFQyhNHGMHk8cSQlEPBW9+0YFVp4bknSqAsGKWAzJWTZBLxXv1il/+o aKuGVK1v6aQjh271/vGNYUzzA5TzBrJsRnruIm4wIapZrXdPzvaKz5JY7Cr+4mnE bAI+/6EdGBjP9/4w2fIQZp+w5jL1rUJPaYfme3kiLTLZna9DKFZt3mOCWdbl0U3w 8n+9MB3HsVBEB5+xn/Dy96da83GNp+9PYT38nxSG24NwaLu6FAwKrLGg2aYumA8L qQcKMwyZ8MURL7JiW7+VgyRZWiFm9XIb/eJUoYY0epRHP9ecamSHfwBrmnggpGRb Ro0Ze52geLU2osmqghOiwU3wkrBJPuOxW8SYrokLZsPLrA9hILqWxxhJQF9MqIt2 8MyV7nfaMouwrypPTTHJy81ZzIoKKNG68M0B8IGD84jUDi2HuHCpzKFYphZjYzhi xpMBkvTCYEseHUSG4xPprro2B4bYg+YZDNoqsP6mMdIo+2IsDnmpxfkvQrFJO4J5 xiraUo8trC+YsgO49EfeEuo5O4i+RMefVmO8x7fgkyYalE96yvwwECQ56vPUm9O2 Si26VsLe0Wzt85OSoNNN =ya74 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
