Bug#1013480: hyperkitty: FTBFS: TypeError: __init__() got an unexpected keyword argument 'providing_args'

Dear Charlemagne, Charlemagne Lasse wrote: Am Mo., 14. Nov. 2022 um 10:53 Uhr schrieb Pierre-Elliott Bécue : I really don't need reminders about the bugs on my packages. This is not a reminder. I was just going through the mailman3 packages to understand what is currently blocking the

Bug#989183: CVE-2021-33038

Hey Moritz, Moritz Muehlenhoff wrote: This was assigned CVE-2021-33038: https://gitlab.com/mailman/hyperkitty/-/issues/380 Patch is here: https://gitlab.com/mailman/hyperkitty/-/commit/9025324597d60b2dff740e49b70b15589d6804fa Thanks a lot for reporting the security bug! I'll upload

Bug#989183: CVE-2021-33038

Hey Moritz, Moritz Muehlenhoff wrote: On Fri, May 28, 2021 at 11:06:31AM +0200, Jonas Meurer wrote: Moritz Muehlenhoff wrote: This was assigned CVE-2021-33038: https://gitlab.com/mailman/hyperkitty/-/issues/380 Patch is here: https://gitlab.com/mailman/hyperkitty/-/commit

Bug#989183: CVE-2021-33038

Hey Moritz, Moritz Muehlenhoff wrote: This was assigned CVE-2021-33038: https://gitlab.com/mailman/hyperkitty/-/issues/380 Patch is here: https://gitlab.com/mailman/hyperkitty/-/commit/9025324597d60b2dff740e49b70b15589d6804fa Thanks a lot for reporting the security bug! I'll upload

Bug#987654: [Pkg-mailman-hackers] Bug#987654: Adjusting severity

Hey Kunal, Kunal Mehta wrote: severity 987654 serious thanks Upping priority to serious as this is technically a violation of policy that all software in main should be self-contained to main, and I believe there is a general acceptance in Debian that such privacy breaches are not

Bug#971093: closed by Debian FTP Masters (reply to Jonas Meurer ) (Bug#971093: fixed in lazr.config 2.2.2-1)

Hey Colin, Am 26.01.21 um 11:12 schrieb Colin Watson: On Mon, Jan 25, 2021 at 10:59:28PM +, Colin Watson wrote: On Sat, Jan 02, 2021 at 12:24:05AM +, Debian Bug Tracking System wrote: * Disable test `test_not_stackable` which fails for python3.9 (Closes: #970148) Thanks

Bug#977061: djangorestframework FTBFS with pytest 6

Control: tag -1 moreinfo Control: severity -1 important Hey Christian, On Thu, 10 Dec 2020 19:40:08 +0100 Christian Kastner wrote: djangorestframework FTBFS with pytest 6 in experimental. I'm unable to reproduce the bug with pytest 6.0.2-2 from unstable. Also, according to ci.debian.net,

Bug#945033: enigmail in Buster uninstallable due to thunderbird 1:68.2.2-1~deb10u1

Package: enigmail Version: 2:2.0.12+ds1-1~deb10u1 Severity: grave Hello, unfortunately, the latest security update of thunderbird (to 1:68.2.2-1~deb10u1) rendered enigmail uninstallable in Buster. That's because thunderbird 1:68.2.2-1~deb10u1 has `enigmail (<< 2:2~)` listed in its `Breaks`

Bug#930133: Postinst tries to invoke systemctl on non-systemd systems

Package: mailman3-web Version: 0+20180916-7 Severity: serious Hello, the mailman3-web postinst runs 'systemctl daemon-reload' during upgrades, regardless of whether systemd is installed on the system or not. This breaks installation of mailman3-web on systems with sysvinit. Cheers jonas

Bug#924616: CVE-2018-15587

Hi Salvatore, hi Evolution maintainers, Salvatore Bonaccorso: > Hi Jonas, hi Evolution maintainers, > > What is the status here for buster? Thanks for prodding :) I'll take care of this via NMU during MiniDebCamp in Hamburg (this week) if nobody objects. Cheers jonas signature.asc

Bug#924616: RFT and RFC: Updates for evolution{,-data-server}

Hi Mike, Mike Gabriel: > On  Mi 24 Apr 2019 12:56:18 CEST, Jonas Meurer wrote: > >> Jonas Meurer: >>> With evolution-data-server, the situation is slightly more complicated. >>> I'm still debugging issues with the patches[5] that are supposed to fix >>>

Bug#924616: RFT and RFC: Updates for evolution{,-data-server}

Jonas Meurer: > With evolution-data-server, the situation is slightly more complicated. > I'm still debugging issues with the patches[5] that are supposed to fix > the "[GPG] Mails that are not encrypted look encrypted" issue. > > [5] https://gitlab.gnome.org/GNOME/evo

Bug#924616: RFT and RFC: Updates for evolution{,-data-server}

Hello, The last days, I spent quite some hours on backporting and debugging patches for CVE-2018-15587 (Signature Spoofing in PGP encrypted email) to evolution and evolution-data-server packages for Jessie LTS. One problem is that the scope of CVE-2018-15587 is a bit blurry. While the CVE

Bug#924616: CVE-2018-15587

Hello, Tobias Frost wrote: > On Thu, 14 Mar 2019 23:18:39 +0100 Moritz Muehlenhoff > wrote: > > Source: evolution > > Severity: grave > > Tags: security > > > > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-15587: > > > > https://bugzilla.gnome.org/show_bug.cgi?id=796424 > > >

Bug#924591: this requires linking in libsparse, which is from Android sources

Hans-Christoph Steiner: > Theodore Ts'o: >> So your choice --- we can either reassign this bug back to fastboot or >> android-sdk-platforms-tools, or I can downgrade the severity of this >> bug for e2fsprogs down to wishlist[1]. Let me know how you want to >> handle this. >> >> [1] This is

Bug#924591: fastboot format:ext4 misses /usr/lib/android-sdk/platform-tools/mke2fs

Control: reopen -1 Hello, Hans-Christoph Steiner: > circular Depends:/Recommends: are easy, circular Build-Depends: are > what's hard. Plus using the /usr/bin/ method, that will make fastboot > require e2fsprogs and other packages, rather than just recommend. Unfortunately, the bug is not

Bug#924591: fastboot format:ext4 misses /usr/lib/android-sdk/platform-tools/mke2fs

Package: fastboot Version: 1:8.1.0+r23-4 Severity: serious Hello, after dist-upgrade to Buster, 'fastboot format:ext4' is broken. It tries to execute '/usr/lib/android-sdk/platform-tools/mke2fs' which doesn't exist and is not available in the Debian archive: $ fastboot format:ext4:0xcd3771e00

Bug#909000: marked as done (Enigmail 2.0 needed in Stretch after Thunderbird 60 upload)

Hi dkg, Am 03.11.18 um 18:06 schrieb Debian Bug Tracking System: > Source: enigmail > Source-Version: 2:2.0.8-5~deb9u1 > > We believe that the bug you reported is fixed in the latest version of > enigmail, which is due to be installed in the Debian FTP archive. >> -BEGIN PGP SIGNED

Bug#909000: Thunderbird 60 cannot STILL be at stretch normal repository

Hello, On Wed, 10 Oct 2018 19:19:53 +0200 Narcis Garcia wrote: > Stable packages aren't ready for Thunderbird 60 presence. > It's better to wait for better repository consistence before adding this > update. With keeping Thunderbird at version 52 in stretch you mean to keep the packages with

Bug#909000: Enigmail 2.0 needed in Stretch after Thunderbird 60 upload

Hi dkg, Am 02.10.2018 um 21:31 schrieb Daniel Kahn Gillmor: > On Mon 2018-09-17 15:44:03 -0400, Daniel Kahn Gillmor wrote: >> * i subsequently discovered that the enigmail test suite was inadequate >>for the Autocrypt Setup Message -- i'm currently working on fixing >>that. (this is

Bug#909587: Bug #909587 in hyperkitty marked as pending

Control: tag -1 pending Hello, Bug #909587 in hyperkitty reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#909000: Enigmail 2.0 needed in Stretch after Thunderbird 60 upload

Hi dkg, Am 17.09.2018 um 21:44 schrieb Daniel Kahn Gillmor: > On Mon 2018-09-17 10:14:31 +0200, Jonas Meurer wrote: >> yesterday, Thunderbird 1:60.0-2~deb9u1 got uploaded to Stretch (via >> security). This thunderbird version breaks enigmail (<< 2:2~), which >> lead

Bug#909000: Enigmail 2.0 needed in Stretch after Thunderbird 60 upload

Source: enigmail Version: 2:1.9.9-1~deb9u1 Severity: grave Dear maintainers, yesterday, Thunderbird 1:60.0-2~deb9u1 got uploaded to Stretch (via security). This thunderbird version breaks enigmail (<< 2:2~), which leads to uninstallable/unusable Enigmail in Debian Stretch. May I suggest to

Bug#886756: [debian-mysql] Bug#886756: Regression: Specified key was too long; max key length is 767 bytes

! Cheers jonas > ti 9. tammik. 2018 klo 17.45 Jonas Meurer (jo...@freesources.org) kirjoitti: >> >> Package: mariadb-server-10.1 >> Version: 1:10.1.29-6 >> Severity: serious >> Tags: upstream >> >> Control: -1 forwarded https://jira.mariadb.org/

Bug#886756: [debian-mysql] Bug#886756: Regression: Specified key was too long; max key length is 767 bytes

Am 07.08.2018 um 10:51 schrieb Jonas Meurer: > Hey Otto, > > Am 06.08.2018 um 23:09 schrieb Otto Kekäläinen: >> I plan to have this commit included in the next upload of MariaDB >> 10.1.x into Debian: >> https://salsa.debian.org/maria

Bug#900967: Security vulnerability: Stack overflow in BGP mask expressions

Source: bird Version: 1.6.3-2 Severity: critical Tags: security According to the upstream website[1] and changelog[2], bird release 1.6.4 includes an "important security bugfix". The changelog mentions "Filter: Fixed stack overflow in BGP mask expressions". A quick scan through the git history

Bug#897536: mustache.js: FTBFS: make[1]: rake: Command not found

Control: tag -1 +moreinfo Hello, I just tried to reproduce the FTBFS and failed. rake is defined as build-dependency and correctly pulled in according to linked the build logs. My best guess is that rake 12.3.1-2 had some bug that got fixed in 12.3.1-3. Lucas, could you trigger another rebuild

Bug#886756: Regression: Specified key was too long; max key length is 767 bytes

Package: mariadb-server-10.1 Version: 1:10.1.29-6 Severity: serious Tags: upstream Control: -1 forwarded https://jira.mariadb.org/browse/MDEV-14904 Hello, I just discovered that MariaDB 10.1 packages in Sid, Buster and Stretch break applications that expect a maximum allowed size of 255

Bug#886489: FTBFS: json_object.c:554:5: error: this statement may fall through [-Werror=implicit-fallthrough=]

it when trying to build json-c. Closing this bug as a duplicate of #853462. Cheers jonas Am 06.01.2018 um 18:41 schrieb Jonas Meurer: > Source: json-c > Version: 0.12.1-1 > Severity: serious > Justification: fails to build from source > > Dear Maintainer, > > json-c fails

Bug#886489: FTBFS: json_object.c:554:5: error: this statement may fall through [-Werror=implicit-fallthrough=]

Source: json-c Version: 0.12.1-1 Severity: serious Justification: fails to build from source Dear Maintainer, json-c fails to build from source due to a potential implicit fall-through in function json_object_get_int64() from json_object.c: libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wdate-time

Bug#862249: Mounting an SFTP share with path may lead to data being deleted

Package: nautilus Version: 3.22.3-1 Severity: critical Hello, I just discovered a severe bug in the sftp protocol support of nautilus: I tried to mount a remote folder via SFTP/SSH by using a syntax similar to the following: 'sftp:///path/to/directory'. Instead of displaying

Bug#855094: [pkg-cryptsetup-devel] Bug#855094: initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't

Hi intigeri, hi Guilhem, Am 02.04.2017 um 10:10 schrieb Guilhem Moulin: > On Sun, 02 Apr 2017 at 09:50:55 +0200, intrigeri wrote: >> So at this point, I suggest this bug is reassigned to cryptsetup, and >> option 3 is implemented there. But downgrading to non-RC and leaving >> things as-is seems

Bug#856536: [Packaging] Bug#856536: munin: regression from DSA-3794-2: spams munin logs with unitialized warnings: [PERL WARNING] Use of uninitialized value $size_x in string eq at /usr/lib/munin/cgi/

Hi Holger, Am 06.03.2017 um 12:54 schrieb Holger Levsen: > could you please be so kind and push your wheezy and jessie uploads to > munin.git too? It's lives in collab-maint on alioth, so you both should > have write access already :) > > Please just push it as signed tags (based on previous

Bug#856536: munin: regression from DSA-3794-2: spams munin logs with unitialized warnings: [PERL WARNING] Use of uninitialized value $size_x in string eq at /usr/lib/munin/cgi/munin-cgi-graph line 453

Hi Salvatore, hi Holger, On Thu, 02 Mar 2017 08:12:24 +0100 Salvatore Bonaccorso wrote: > Source: munin > Version: 2.0.25-1+deb8u1 > Severity: serious > Tags: upstream > > Only after releasing the DSA, I noticed that the update introduced > another regression, causing to spam

Bug#855705: [munin-monitoring/munin] munin-cgi-graph CGI::param security problem (#721)

Hi Holger, hi Steve, first thanks for Steve to patching munin 2.0 upstream: https://github.com/munin-monitoring/munin/commit/42ce18f24d3eae8be33526a198bf21e4f2330230 Am 24.02.2017 um 21:30 schrieb Holger Levsen: > On Fri, Feb 24, 2017 at 09:00:00PM +0100, Jonas Meurer wrote: >>

Bug#855705: [munin-monitoring/munin] munin-cgi-graph CGI::param security problem (#721)

Hi Holger, hi Steve, On Fri, 24 Feb 2017 11:24:42 + Holger Levsen wrote: > On Fri, Feb 24, 2017 at 01:37:55AM -0800, mejo- wrote: > > I just gave 2.0.6 (from Debian/Wheezy) a try and indeed it's > > vulnerable too. > > The proposed patch by Tomaž Šolc from Debian

Bug#847751: lurker: FHS violation: default configuration writes to files in /usr

Hi Dominic, Am 11.12.2016 um 13:10 schrieb Dominic Hargreaves: > Package: lurker > Version: 2.3-5+b1 > Severity: serious > Justification: Policy 9.1.1 > > As of 2.3-1 the Debian package of lurker unfortunately started > violating the FHS, because it moved its HTML generation output to >

Bug#847196: monit segfault on stop and start

Hi Marco, Victor, Chris, Am 06.12.2016 um 14:04 schrieb Chris Lamb: > [Adding Jonas as they made the relevant upload] > > Hey, > >> monit segfault on stop and start > > This appears to be a regression in the latest LTS upload so pinging > the relevant people. thanks to bugreport, patch and

Bug#846649: Frequent segfaults of coturn

Am 02.12.2016 um 23:52 schrieb Jonas Meurer: > I encounter frequent segfaults of coturn on a Debian Squeeze VM with > recent kernel (4.8.7-1). > [...] > I'll gladly further debug the issue if you give me instructions. I ran coturn in gdb now (with coturn-dbg and libssl1.0.2-d

Bug#846649: Frequent segfaults of coturn

Package: coturn Version: 4.5.0.5-1 Severity: serious Hi, I encounter frequent segfaults of coturn on a Debian Squeeze VM with recent kernel (4.8.7-1). I don't know much about coturn, just use it for a Spreed.ME installation and so far it worked well. But recently it started to segfault out of

Bug#844299: big $HISTSIZE causes exessive memory usage

Package: bash Version: 4.4-1 Severity: serious Hello, apparently bash 4.4 as available in Debian Stretch introduced a regression compared to 4.3 from Debian Jessie: when setting $HISTSIZE to a big value (e.g. as suggested in a lot of docs out there on the web), the resulting bash

Bug#798080: mysql-server-5.6: service stop hangs forever on systemd -- fixed upstream

Control: notfixed -1 5.6.30-1 Hello, On Sun, 2 Oct 2016 15:07:31 -0400 "William L. DeRieux IV" wrote: > I had an older version installed and could confirm the issue existed; > but as of v5.6.30-1 this is no longer an issue. unfortunately, this bug seems to be not fixed in the MySQL 5.6 packages

Bug#841289: [drm/i915] GPU HANG: ecode 9:0:0xfffffffe, in Xorg [2507], reason: Engine(s) hung, action: reset

Package: src:linux Version: 4.7.6-1 Severity: grave Justification: renders package unusable Hello, recently, something on my system related to drm/i915 broke. Since no xserver/drm packages have been upgraded, I strongly suspect the latest linux kernel upgrade to be the culprit. Since several

Bug#839888: [pkg-cryptsetup-devel] Bug#839888: closed by Jonas Meurer <m...@debian.org> (Bug#839888: fixed in cryptsetup 2:1.7.2-2)

Hi Marc, Am 06.10.2016 um 12:57 schrieb Marc Haber: > thanks for the quick fix. I have, however, to add that my systems do > have systemd as PID 1. Interesting. So you use systemd and still the cryptdisks initscript is invoked. I guess that you manually configured your system to do so because

Bug#783297: [pkg-cryptsetup-devel] Bug#783297: breaks initramfs if BUSYBOX=n

severity 783297 wishlist thanks This mail clones the original bugreport two times and reassigns the clones to the busybox and initramfs-tools packages with appropriate titles. See below for details. Am 27.12.2015 um 07:35 schrieb Ben Hutchings: > On Fri, 2015-12-25 at 14:46 +0100, Jonas Meurer wr

Bug#783297: [pkg-cryptsetup-devel] Bug#783297: breaks initramfs if BUSYBOX=n

Hi Michael, hi Ben, Am 26.04.2015 um 01:35 schrieb Michael Biebl: > On Sat, 25 Apr 2015 16:22:13 +0200 Michael Biebl wrote: >> if the cryptsetup package is installed, it also installed a >> initramfs-tools hook. >> >> I use BUSYBOX=no in initramfs.conf, but the cryptroot hook

Bug#782996: smsd: 'reload' function of initscript broken if used by systemd

Am 21.04.2015 um 15:15 schrieb Jonas Meurer: I consider this bug as release-critical for Jessie, as it renders smmstools unusable on Jessie installations whenever logrotate is installed. Thus I suggest to push the fix into Jessie within the next days. I'll gladly do an NMU if the maintainer(s

Bug#782996: smsd: 'reload' function of initscript broken if used by systemd

Hi again, Am 2015-04-20 11:55, schrieb Jonas MEURER: The bug can be fixed by renaming the 'reload' function to 'force-reload' and dropping the original 'force-reload' alias for 'restart'. Please note, that fixing the 'Usage:' line by dropping 'reload' from the list of supported actions

Bug#782996: smsd: 'reload' function of initscript broken if used by systemd

Am 2015-04-21 15:15, schrieb Jonas Meurer: See the attached patch for a proper fix. I attached an updated patch. Argh, this time with the updated patch :) Cheers, jonasdiff -rNu smstools-3.1.15.orig/debian/changelog smstools-3.1.15/debian/changelog --- smstools-3.1.15.orig/debian/changelog

Bug#782996: smsd: 'reload' function of initscript broken if used by systemd

by Jonas Meurer to push the fix into Jessie. + * Fix initscript: rename action 'reload' to 'force-reload' and drop 'reload' +from supported actions. Use 'force-reload' in logrotate post-rotate action. +This fixes 'force-reload' function when used through systemd tools and +prevents

Bug#774700: [pkg-cryptsetup-devel] Bug#774700: Cryptsetup tools are not included by update-initramfs command

Hi, Am 16.02.2015 um 19:36 schrieb Musy Bite: Hello Jonas! We run into this bug, too. There is mkinitramfs_debug.log you requested at message #25. Installation was performed from debian testing amd64 netinst ISO image built on unknown date, and apt-get dist-upgraded to jessie. cryptsetup

Bug#774700: initramfs-tools: Cryptsetup tools are not included by update-initramfs command

Hi Michael, On Tue, 06 Jan 2015 14:40 Michael P. wrote: The update-initramfs command create a initrd.img without cryptsetup tools, but my root partition is crypted. I tried to debug a little the /usr/share/initramfs-tools/hooks/cryptroot file and found that the add_device() function

Bug#767832: please test updated cryptsetup packages

Hello everyone, I prepared updated cryptsetup packages that fix the following bugs: #767832: cryptsetup: does not decrypt a split /usr as required by initramfs-tools = 0.118 #767921: files with the same name installed in / and /usr #764564: openrc: fail to boot when encryption + lvm are present

Bug#758755: [pkg-cryptsetup-devel] Bug#758755: Bug#758756: libgcrypt20: missing udeb: libgcrypt20-udeb

Hey Andreas and Cyril, Am 21.08.2014 um 19:25 schrieb Cyril Brulebois: Andreas Metzler ametz...@bebt.de (2014-08-21): On 2014-08-21 Cyril Brulebois k...@debian.org wrote: Package: libgcrypt20 [...] but there's no libgcrypt20-udeb! (in the archive or in NEW) [...] I have just uploaded

Bug#758755: [pkg-cryptsetup-devel] Bug#758755: libcryptsetup4-udeb: depends on libgcrypt20-udeb, which doesn't exist

Hi Cyril, Am 2014-08-21 01:10, schrieb Cyril Brulebois: Package: libcryptsetup4-udeb Version: 2:1.6.6-1 Severity: grave Justification: renders package unusable Hi, your package is no longer installable, because it now depends on libgcrypt20-udeb, which is nowhere to be found. now that you

Bug#710356: [Pkg-nagios-devel] Bug#710356: Info received (Fix for wheezy?)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 09.12.2013 12:09, schrieb Jasir Baftijari: Hi, Hello Jasir, why I can't see the new Version 3.4.1-3+deb7u1? # aptitude versions nagios3 Paket nagios3: i 3.4.1-3 stable 500 The package is in wheezy-proposed-updates. It's not part of the

Bug#710356: [Pkg-nagios-devel] Bug#710356: Fix for wheezy?

Hello, Am 2013-11-04 10:10, schrieb Jasir Baftijari: Hello, i'm waiting for wheezy, too. Please Upload the fix to wheezy asap. Hopefully this bug will be fixed through an upload to wheezy-updates within the next days. I'm awaiting the approval of debian-release for the upload at the

Bug#710356: Duplicate bugreports, please include in next stable update

Hello, I believe that bugs #701084 and #710356 are duplicates. In other words, #710356 should be closed now that nagios3 3.4.1-4 was uploaded :) And I would suggest to incorporate the patch into prospective uploads to stable-security and/or oldstable-security. It's a very nasty bug with an

Bug#714210: DRBD 8.3 userland incompatible with 8.4 kernel modules

Package: drbd8-utils Version: 2:8.3.13-2 Severity: grave Hello, as the subject already mentions, DRBD 8.3 userland in jessie/testing is incompatible with DRBD 8.4 kernel modules from the 3.9 linux package. DRBD kernel modules are at 8.4 branch in upstream linux kernel since kernel release 3.8.

Bug#656552: zope2.12-sandbox: fails to upgrade from testing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey Arnau, Am 22.11.2012 11:56, schrieb Arnaud Fontaine: Ivo De Decker ivo.dedec...@ugent.be writes: [...] In other words: the package creates an (empty) zope instance in the postinst, but fails to install if such an instance exists. This

Bug#682416: Bug renders package unusable

severity 682416 grave thanks Hello, this bug renders the package smstools mostly unusable for many users. I discovered the same bug. I can confirm, that the new upstream 3.1.15 fixes the bug. 3.1.15 has no changes apart from this fix, thus I suggest to push it into wheezy despite the freeze.

Bug#677127: [pkg-cryptsetup-devel] Bug#677127: relocation error

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey Milan, Am 12.06.2012 17:43, schrieb Milan Broz: On 06/11/2012 09:31 PM, p...@spth.de wrote: /sbin/crpytsetup: relocation error: /sbin/cryptsetup: symbol crypt_activate_by_key_file_offste, version CRYPTSETUP_1.0 not defined in file

Bug#659688: [pkg-cryptsetup-devel] Bug#659688: cryptsetup: LVM on cryptsetup won't boot

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey Roland, Am 13.02.2012 09:35, schrieb Roland Mas: Package: cryptsetup Version: 2:1.4.1-2 Severity: critical To be honest I don't agree with you on the severity of this bug. I understand that the changes in LVM handling of cryptroot initramfs

Bug#659182: [pkg-cryptsetup-devel] Bug#659182: dangling .so symlink

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 12.02.2012 11:15, schrieb Michael Biebl: Hi Jonas, On 12.02.2012 00:29, Jonas Meurer wrote: Am 11.02.2012 04:54, schrieb Michael Biebl: If I should delay or cancel the NMU, please let me know. sorry for not replying earlier. I'll try

Bug#659182: [pkg-cryptsetup-devel] Bug#659182: dangling .so symlink

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey Michael, Am 11.02.2012 04:54, schrieb Michael Biebl: tags 659182 + patch pending thanks Hi, as I haven't gotten a reply so far and seen no updates in the pkg svn, I've prepared a fix and uploaded to DELAYED/2. debdiff is attached.

Bug#626711: convirt fails to start (config file missing)

Package: convirt Version: 2.0.1-5 Severity: grave Hello, Seems like convirt is missing the configuration file. /etc/convirt is not created at installation time. /usr/share/convirt/src/convirt/web/convirt/development.ini is a dangling to /etc/convirt/development.ini. For that reason, the daemon

Bug#626715: convirt fails to start (sqlalchemy.exc.ArgumentError)

Package: convirt Version: 2.0.1-5 Severity: grave Hey again, after I copied development.ini from the convirt source package to /etc/convirt/, convirt dies with another error: # /etc/init.d/convirt start Starting Convirt: PID file is /var/run/convirt/paster.pid No virtualenv found, will try to

Bug#626294: segmentation fault at opening imap folder

Package: mutt Version: 1.5.21-5 Severity: grave Hello, Since the upgrade to mutt 1.5.21-5, mutt occasionally crashes with a segmentation fault at opening a IMAP maildir folder. It doesn't matter, which IMAP folder is opened. I didn't discover this bug with mutt 1.5.21-4, with the exactly same

Bug#554506: (ugly) patch which should fix dm-crypt-on-lvm setups

Hey Alasdair, thanks for your comments. On 04/11/2010 Alasdair G Kergon wrote: If the complex processing doesn't work for everyone then yes, simplify it and activate everything always. To do it the other way you need logic something like: Every time you boot, check if the stack of

Bug#554506: (ugly) patch which should fix dm-crypt-on-lvm setups

Hey Christoph, On 04/11/2010 Christoph Anton Mitterer wrote: I haven't fully looked at this so perhaps it's unrelated,... But one main problem I see here (that may be related), is that lvm's init-scripts are simply wrong, and abusing some things. I've already told Bastian this and there are

Bug#554506: (ugly) patch which should fix dm-crypt-on-lvm setups

Hey Christoph, On 04/11/2010 Christoph Anton Mitterer wrote: I haven't fully looked at this so perhaps it's unrelated,... But one main problem I see here (that may be related), is that lvm's init-scripts are simply wrong, and abusing some things. I've already told Bastian this and there are

Bug#554506: (ugly) patch which should fix dm-crypt-on-lvm setups

Hello, Again I tried to work on this bugreport. I'm absolutely sure that different bugs are spotted. Most people are hitting the following bug: the debian-installer was changed to configure devices in fstab and crypttab in the 'UUID=...' style some time ago. this works for most systems, with the

Bug#586120: [pkg-cryptsetup-devel] Bug#586120: device-mapper: reload ioctl failed: Invalid argument

Hey Clayton, On 28/06/2010 Clayton wrote: On Sun, 27 Jun 2010 11:35:31 +0200 Jonas Meurer jo...@freesources.org wrote: On 27/06/2010 Clayton wrote: On Sat, 26 Jun 2010 12:32:02 +0200 Jonas Meurer jo...@freesources.org wrote: are you sure that this is the case? what does 'blkid

Bug#586120: [pkg-cryptsetup-devel] Bug#586120: device-mapper: reload ioctl failed: Invalid argument

Hey Clayton, On 27/06/2010 Clayton wrote: On Sat, 26 Jun 2010 12:32:02 +0200 Jonas Meurer jo...@freesources.org wrote: On 16/06/2010 clayton wrote: # cryptsetup create backcrypt /dev/sda2 Enter passphrase: device-mapper: reload ioctl failed: Invalid argument Can you post dmsetup

Bug#586120: [pkg-cryptsetup-devel] Bug#586120: device-mapper: reload ioctl failed: Invalid argument

hey, On 16/06/2010 clayton wrote: # cryptsetup create backcrypt /dev/sda2 Enter passphrase: device-mapper: reload ioctl failed: Invalid argument Can you post dmsetup table when this fails? greetings, jonas signature.asc Description: Digital signature

Bug#586161: bug#586162 [bash-completion,cryptsetup] decide who should ship completion for cryptsetup

hey, i just removed the bash-comletion file from cryptsetup svn. with the upload of 2:1.1.2-2, cryptsetup will no longer ship this file. thus i suggest to add a Conflicts: cryptsetup ( 2:1.1.2-2) to bash-completion in order to fix bug #586161. i'll upload cryptsetup 2:1.1.2-2 within the next

Bug#583387: no longer shipping static libraries causes cryptsetup FTBFS

Package: libdevmapper-dev Version: 2:1.02.47-1 Severity: grave hey, the most recent upload of lvm2 source package, which removed static libraries from the lib*-dev packages breaks build process of cryptsetup. cryptsetup staticly links against libdevmapper, as the library is located in /usr/lib,

Bug#583387: closed by Bastian Blank wa...@debian.org (Re: Bug#583387: no longer shipping static libraries causes cryptsetup FTBFS)

hey, On 27/05/2010 Bastian Blank wrote: On Thu, May 27, 2010 at 04:00:59PM +0200, Jonas Meurer wrote: cryptsetup staticly links against libdevmapper, This is not allowed under normal circumstances. Does the security team know about

Bug#583387: closed by Bastian Blank wa...@debian.org (Re: Bug#583387: no longer shipping static libraries causes cryptsetup FTBFS)

hey, On 27/05/2010 Bastian Blank wrote: On Thu, May 27, 2010 at 07:13:01PM +0200, Jonas Meurer wrote: but still the most recent update of libdevmapper broke cryptsetup build. see the build logs at https://buildd.debian.org/pkg.cgi?pkg=cryptsetup: make[3]: Entering directory `/build

Bug#576488: [pkg-cryptsetup-devel] Bug#576488: still present

hey, On 06/05/2010 Frederik Vanrenterghem wrote: Package: cryptsetup Version: 2:1.1.0-2.1 I still get this error (evmc_activate is not available) using kernel 2.6.32-4 and 2.6.32-5 on AMD64. I can't boot the system. 2.6.32-3 boots fine. please provide more information about

Bug#576488: [pkg-cryptsetup-devel] Bug#576488: cryptroot: boot script assumes to be run in initramfs

hey maks, On 05/04/2010 maximilian attems wrote: initramfs-tools 0.94 will break cryptsetup cryptroot boot script. The Ubuntu feature of pre-cached order got merged, will add a versioned breaks on cryptsetup their is a patch in Ubuntu cryptsetup for the situation, including it here.

Bug#566136: Removing packages which depend from Zope2 ?

hey Andreas, On 25/01/2010 Andreas Tille wrote: I did not followed the discussion closely any more about the Zope 2 issue but apt-cache has no hits for zope2 any more. This lets me assume that zope2 is not supported in Debian any more and so we should probably drop packages depending from

Bug#548570: minirok segfaults

hey adeodato, On 15/10/2009 Adeodato Simó wrote: + Jonas Meurer (Sun, 27 Sep 2009 12:30:28 +0200): Package: minirok Version: 2.0-1 Severity: grave Justification: renders package unusable hello, minirok segfaults on my up-to-date debian/unstable system: Hello Jonas

Bug#548861: upgrade fails with E: Internal Error, Could not perform immediate configuration (2) on perl

Package: perl Version: 5.10.1-3 Severity: serious hello, perl upgrade fails on my up-to-date debian/unstable system: # apt-get install libperl5.10 perl-base perl perl-doc perl-modules Reading package lists... Done Building dependency tree Reading state information... Done Suggested

Bug#548570: minirok segfaults

Package: minirok Version: 2.0-1 Severity: grave Justification: renders package unusable hello, minirok segfaults on my up-to-date debian/unstable system: $ minirok Traceback (most recent call last): File /usr/bin/minirok, line 9, in module minirok.main.main() File

Bug#544773: [pkg-cryptsetup-devel] Bug#544773: Update to cryptsetup 2:1.0.7-2 breaks booting

hey, On 04/09/2009 Paul Millar wrote: On Thursday 03 September 2009 19:43:28 Jonas Meurer wrote: [...] please run the following command: # sh -x mkinitramfs -o /tmp/initramfs 2/tmp/initramfs.log and send /tmp/initramfs.log to the bugreport. Attached. Incidentally, I opened up

Bug#544773: [pkg-cryptsetup-devel] Bug#544773: Update to cryptsetup 2:1.0.7-2 breaks booting

hey, On 02/09/2009 Paul Millar wrote: After upgrading a few packages (listed below) I discovered my laptop was unable to boot. The laptop uses a Luks partition with LVM (this was using a standard guided partitioning option back when I was installing Debian). The boot fails at around

Bug#544773: [pkg-cryptsetup-devel] Bug#544773: Update to cryptsetup 2:1.0.7-2 breaks booting

hey, On 03/09/2009 Linus Lüssing wrote: Yes, I'm having the same problem here. I updated cryptsetup yeseterday to 2:1.07-2 and now I can't boot my usual 2.6.30-1-amd64 anymore. My other kernels on this machine seem unaffected, just my usual kernel-image does not boot. So I can select/boot

Bug#544669: [pkg-cryptsetup-devel] Bug#544669: cryptsetup: /sbin/blkid is not in initramfs

reassign 544669 util-linux severity 544669 normal tag 544669 +patch thanks hey, On 02/09/2009 Mario 'BitKoenig' Holbe wrote: cryptsetup 1.0.7-2 recommends to replace vol_id and un_vol_id by blkid and un_blkid. Both of these scripts depend on /sbin/blkid. However, /sbin/blkid is not available

Bug#543667: [Python-modules-team] Bug#543667: The same

hey, On 27/08/2009 Nahuel ANGELINETTI wrote: I have the same problem today, and I do not find the new package, where can I find it? Or at least the source to build it myself? i've uploaded a fixed package today (1.2.2-10). it should be available on the mirrors tomorrow. until then you can find

Bug#542928: [pkg-cryptsetup-devel] Bug#542928: Bug#542928: cryptsetup fail with kernel 2.6.30-6

hey, On 26/08/2009 Guillaume JAOUEN wrote: You'll find in this mail all the output log. I add also dmesg output dpkg get-selections, lshw and lspci output. I hope it may help you understand what's happening : - dpkg-gzt-selections.txt was made under 2.6.29-2 kernel boot. -

Bug#542928: [pkg-cryptsetup-devel] Bug#542928: Bug#542928: cryptsetup fail with kernel 2.6.30-6

hey, On 27/08/2009 Guillaume JAOUEN wrote: I start again the laptop with kernel 2.6.30-1 amd64 and write carefully the output during the boot : ... Begin : Assembling all MD arrays... mdadm : No arrays found in config file or automatically Failure : failed to assemble all arrays. done.

Bug#542928: [pkg-cryptsetup-devel] Bug#542928: Bug#542928: cryptsetup fail with kernel 2.6.30-6

hey again, On 25/08/2009 Guillaume JAOUEN wrote: I use a standard sid install with only nvidia proprietary driver : thanks for the information. i run several debian/sid installations with linux-image-2.6.30-1-amd64 (2.6.30-6) without any issues, and so far I was unable to reproduce the bug you

Bug#542928: [pkg-cryptsetup-devel] Bug#542928: cryptsetup fail with kernel 2.6.30-6

hello, On 22/08/2009 Guillaume JAOUEN wrote: Since upgrade of the kernel to 2.6.30-6, my laptop fail to start and doesn't ask for the lucks passphrase so my LVM setup can't start and the system lost debian-root and debian-swap filesystem... Rebooting with 2.6.29 old kernel start properly.

Bug#540157: Bug#540158: doesnt use invoke-rc.d

hey, On 09/08/2009 Jonas Meurer wrote: ok, after discussing this with kobold, i finally implemented the following changes: - zope-debhelper uses invoke-rc.d in maintainer scripts - dzhandle uses invoke-rc.d for DZRestartPendingInstances.run() - zope2.1[01] init scripts support [ZEOSERVER

Bug#540159: Bug#540158: doesnt use invoke-rc.d

hello again, On 08/08/2009 Jonas Meurer wrote: On 06/08/2009 Holger Levsen wrote: during a test with piuparts I noticed your package starts processes where it shouldnt. This is very probably due to not using invoke-rc.d as mandated by policy 9.3.3.2. This is seriously disturbing

Bug#540157: Bug#540158: doesnt use invoke-rc.d

hey, On 06/08/2009 Holger Levsen wrote: during a test with piuparts I noticed your package starts processes where it shouldnt. This is very probably due to not using invoke-rc.d as mandated by policy 9.3.3.2. This is seriously disturbing! ;-) See

Bug#534013: zope2.10: FTBFS: /bin/sh: line 0: cd: z: No such file or directory

Hello again, On 03/07/2009 Lucas Nussbaum wrote: On 03/07/09 at 04:17 +0200, Jonas Meurer wrote: On 02/07/2009 Lucas Nussbaum wrote: if you take a look at debian/rules, there are several more commands in unpack-stamp than just the 'tar xfz'. According to your logfile, the build

Bug#534013: zope2.10: FTBFS: /bin/sh: line 0: cd: z: No such file or directory

Hello Lucas, On 21/06/2009 Lucas Nussbaum wrote: Package: zope2.10 Version: 2.10.8-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20090620 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on

Bug#534013: zope2.10: FTBFS: /bin/sh: line 0: cd: z: No such file or directory

On 02/07/2009 Lucas Nussbaum wrote: if you take a look at debian/rules, there are several more commands in unpack-stamp than just the 'tar xfz'. According to your logfile, the build-arch-stamp and patch-stamp targets are executed in the middle of the unpack-stamp target. I'm unable to

  1   2   >