Bug#306261: #306261 and sarge

Hello, according to bugzilla this bug is fixed in version 2.4.3-20050321+2, but debian sarge still has version 2.4.3-20050321+1 affected by this bug. Could you please upload a fixed version to sarge? Maxi signature.asc Description: This is a digitally signed message part

Bug#421194: (no subject)

Package: psi Version: 0.11-3 --- Please enter the report below this line. --- I think this is the same Problem I got after updating my system some days ago. When starting Psi with gpg enabled it should ask for the pgp passphrase, but the dialog is never shown, so it just hangs waiting for a

Bug#447200: acpid spams my syslog

Package: acpid Version: 1.0.6-4 Severity: normal --- Please enter the report below this line. --- When I start acpid I'm getting lots of messages in my syslog logfile that make it quite unreadable. Every minute acpid logs 25 lines which is already a lot if is is only running for an hour. It would

Bug#483561: [eagle] New version available (5.0.0)

Package: eagle Version: 4.16r2-1 Severity: wishlist --- Please enter the report below this line. --- There is a new version of eagle available (5.0.0) at http://www.cadsoft.de/download.htm It would be nice to see it in debian. --- System information. --- Architecture: i386 Kernel: Linux

Bug#477221: [libfreebob0] new version available (1.0.11)

Package: libfreebob0 Version: 1.0.7-1 Severity: wishlist --- Please enter the report below this line. --- There is a new version of libfreebob available. It would be nice to see it in debian. More information can be found here: http://article.gmane.org/gmane.linux.audio.users/46958

Bug#476122: [psi] psi crashes with qt4.4 when last tab is closed

Package: psi Version: 0.11-7 Severity: important Tags: patch --- Please enter the report below this line. --- When I close the last tab of the chatwindow psi crashes. This started with upgrading my system to qt4.4. A patch fixing this can be found in upstream svn rev 1101:

Bug#597476: dovecot: Exp, Sid packages for Dovecot 2

Any progress on this? Now that Squeeze is released I don't see any reason why Dovecot 2 can't be uploaded to unstable (or at least experimental). I've seen there is a debian-2.0 branch in the dovecot git repository on git.debian.org that seems to be quite well maintained. I compiled dovecot 2

Bug#533406: cssh real name / given name handling changed in 3.26, breaking some known_hosts

On Wednesday 02 December 2009 10:24:21 Duncan Ferguson wrote: On 20 Nov 2009, at 10:20, Josip Rodin wrote: A couple of us noticed and reported a problem with cssh 3.26 in Debian at http://bugs.debian.org/533406 that you may be interested in fixing. I have just put a code fix into git - can

Bug#561637: [isatapd] New version available (0.9.6)

Package: isatapd Version: 0.9.5-1 Severity: wishlist Hello, A new version (0.9.6) of isatapd has been released. Among other things it fixes isatapd for kernels 2.6.31 It would be nice to have it in debian. Greetings, Maxi signature.asc Description: This is a digitally signed message part.

Bug#541653: kdelibs5: several (https) SSL certificates cannot be validated for internal reasons

I can confirm this bug. I have a laptop with Debian unstable and KDE 4.3 and a desktop PC with Debian testing and KDE 4.2 and both are affected by this bug. However on my desktop PC (KDE 4.2) this problem just occurred recently, so I don't think it's caused by kdelibs5. I think the real cause

Bug#552152: [geda] new stable version available (1.6.0)

Package: geda Version: 1:1.4.0.2 Severity: wishlist A new stable version (1.6.0) of geda has been released. See the announcement http://www.seul.org/pipermail/geda-announce/2009-October/89.html and the download page http://www.gpleda.org/sources.html It would be nice to see geda 1.6.0 in

Bug#617317: autofs5: crashed in a nested setup in combination with negative lookups on *

tags 617317 +patch thanks I was working together with Johannes on this bug and we found that it is already fixed upstream by [1]. Applying this patch on the current squeeze version (5.0.4-3.2) fixes the mentioned crash for us. It would be nice to see this fixed in Squeeze as it might affect

Bug#640457: [openssl] some VeriSign certificates fail to verify

Package: openssl Version: 1.0.0d-3 Severity: important Hello, I'm having problems verifying some VeriSign certificates. As far as I traced this back I think this is a problem with openssl. But if you think this bug should be fixed elsewhere feel free to reassign the report. Here is a

Bug#640457: [openssl] some Verisign certificates fail to verify

On Friday 14 October 2011 07:28:00 Kyle Moffett wrote: So chain-0 can be verified by chain-1 and chain-1 can be verified by the system installed CAs. The problem is that VeriSign_Class_3_Public_Primary_Certification_Authority_-_G5.crt got updated in ca-certificates 20110421. And the

Bug#645822: [gcc-avr] FTBFS on mips, mipsel and sparc

Package: gcc-avr Version: 1:4.5.3-1 Severity: normal gcc-avr failed to build on mips, mipsel and sparc. Thus it can't migrate to testing. See this link here: http://release.debian.org/migration/testing.pl?package=gcc-avr It would be nice to see this fixed, so avr-gcc can enter testing again

Bug#639667: [telepathy-gabble] Claims my server's certificate is self-signed

Package: telepathy-gabble Version: 0.16.1-1 I think this is the same problem I have. I tried three different jabber server of which I know they have valid certificates and other jabber clients validate them just fine, but telepathy-gabble always gives me this error that the certificate is

Bug#718310: [gnuradio-dev] Please ship GnuradioConfig.cmake and GnuradioConfigVersion.cmake

Package: gnuradio-dev Version: 3.7.0-2 Severity: wishlist Tags: patch Please ship these two files in gnuradio-dev: /usr/lib/cmake/gnuradio/GnuradioConfig.cmake /usr/lib/cmake/gnuradio/GnuradioConfigVersion.cmake The following patch should do this: ---

Bug#718707: [gnuradio] gnuradio from experimental uninstallable

Package: gnuradio Version: 3.7.0-3 Severity: normal --- Please enter the report below this line. --- gnuradio from experimental (version 3.7.0-3) depends on version 3.7.1 of libvolk0.0.0 which isn't available in Debian. However there is libvolk0.0.0 version 3.7.0-3, which is built from the

Bug#657122: fixed in collectd 5.2.0-1

This bug is still present in testing/unstable. Are there any plans to fix it there? signature.asc Description: This is a digitally signed message part.

Bug#698584: [collectd] collectd crashes when enabling ethstat plugin

Package: collectd Version: 5.1.0-3 Severity: normal Tags: patch --- Please enter the report below this line. --- When enabling the ethstat plugin collectd crashes on startup: $ /etc/init.d/collectd start [] Starting statistics collection and monitoring daemon: collectd*** glibc detected ***

Bug#721742: [arduino] Please provide arduino version 1.5

the latest upstream version is 1.5.3. As this version is still marked as Beta it might make sense to only provide it in experimental for now. Greetings, Maximilian Engelhardt --- System information. --- Architecture: amd64 Kernel: Linux 3.10-2-amd64 Debian Release: jessie/sid 500 testing

Bug#733319: [psi-plus-plugins] OTR conversations between psi-plus and pidgin sometimes don't work

Hi Boris, Thanks for your patch. Today I had some time to test it and is does fix all the OTR problems I had before. So I can confirm that the patch fixes this bug. Greetings, Maxi signature.asc Description: This is a digitally signed message part.

Bug#733319: [psi-plus-plugins] OTR conversations between psi-plus and pidgin sometimes don't work

Package: psi-plus-plugins Version: 0.16.262-1 Severity: normal First, I'm not sure this bug is in psi-plus-plugins, but at the moment it seems to be the most likely package, so feel free to reassign if you think this has to be fixed somewhere else. How to reproduce: You need two XMPP accounts,

Bug#733319: [psi-plus-plugins] OTR conversations between psi-plus and pidgin sometimes don't work

On Saturday 28 December 2013 18:55:59 Boris Pek wrote: control: reassign 733319 libotr 4.0.0~rc1-1 Hi, ... When I'm trying to start a OTR session from pidgin I get We received a malformed data message from myaccountname@myserver in an endless loop on the pidgin client. Trying to

Bug#741743: [src:kicad] FTBFS on all architectures

Source: kicad Version: 0.20140224+bzr4027-3 Severity: serious Hello, kicad currently FTBFS on all architectures. See here for the build logs: https://buildd.debian.org/status/package.php?p=kicad Maxi signature.asc Description: This is a digitally signed message part.

Bug#756842: [linux-image-3.16-rc6-amd64] please enable CONFIG_SND_BEBOB

Package: linux-image-3.16-rc6-amd64 Version: 3.16~rc6-1~exp1 Severity: wishlist Hello, Please enable CONFIG_SND_BEBOB which has been newly added to the kernel in 3.16. This provides a in-kernel driver for BeBob Firewire audio devices. You probably might also want to enable CONFIG_SND_DICE

Bug#763683: [kicad] cvpcb shows Load Error on start

Package: kicad Version: 0.20140622+bzr4027-3 Severity: normal --- Please enter the report below this line. --- when starting cvpcb on a new project I get the following Load Error: Some files could not be found! * smd_crystaloscillator.mod * smd_dil.mod This seems to be caused by module

Bug#770659: WebRTC camera/microphone sharing does not work

I can confirm this. If I remember my tests correctly in all versions of chromium 37 that hit the Debian archive webrtc was working and in all versions 38 it is broken. Sadly I have no idea what might be the cause of this. signature.asc Description: This is a digitally signed message part.

Bug#770659: seems to be related to using the Debian srtp library

I did some tests to track this down a bit. starting chromium with --enable-logging --v=4 I do get this in my .config/chromium/chrome_debug.log: [49:62:1219/210401:VERBOSE3:channel.cc(783)] Installing keys from DTLS-SRTP on audio RTP [49:62:1219/210401:VERBOSE1:srtpfilter.cc(699)] Failed to

Bug#770659: Workaround to get WebRTC working again

Package: chromium Version: 40.0.2214.91-1 I had another look at this today and noticed that it seems to be related to the chromium sandbox and the external libsrtp. I found that a workaround to get WebRTC running on Debian is disabling the sandbox: $ chromium --no-sandbox With this parameter

Bug#775005: [macchanger] MAC randomization doesn't generate a random MAC

Package: macchanger Version: 1.7.0-3.2 Severity: grave Trying to randomize the MAC address of an interface toggles between two MAC addresses instead of setting a random MAC address. See the following example: $ macchanger -A wlan8 Current MAC: 00:05:01:98:56:c3 (CISCO SYSTEMS, INC.) Permanent

Bug#770659: WebRTC in chromium

The handling of this bug is really bad, nobody seems to care about it and it's broken now a long time. I see two possible solutions for this issue. Either WebRTC in chromium should be fixed or it should be disabled in the Debian version of chromium. It simply doesn't make any sens to ship a

Bug#785153: [src:linux] Please enable support for DVBSky T9580

Package: src:linux Version: 4.0.2-1 Severity: wishlist --- Please enter the report below this line. --- Please set CONFIG_DVB_SMIPCIE=m to enable support for the DVBSky T9580 card. I did a test build with this option enabled on linux-image-3.19 and the card did work without problems. Regards,

Bug#786772: [dhcpcd5] please package a newer version

Package: dhcpcd5 Version: 6.0.5-2 Severity: wishlist --- Please enter the report below this line. --- A new upstream version (currently 6.9.0) is available with many bug fixes, improvements and features. The version currently in Debian (6.0.5, upstream release Aug 2013) is quite old and for me

Bug#786774: [xul-ext-https-everywhere] a newer upstream version is available

Package: xul-ext-https-everywhere Version: 4.0.3-1 Severity: wishlist --- Please enter the report below this line. --- Upstream currently ships version 5.0.4 while Debian still has 4.0.3. It probably makes sens to update to the latest upstream version. --- System information. --- Architecture:

Bug#822817: [src:linux] sound stops working and dmesg spammed with hpet1: lost XXX rtc interrupts

Hi Dietz, Thanks for your information. In my case I need the irqpoll option because of this bug: https://bugzilla.kernel.org/show_bug.cgi?id=47191 However, setting the "hpet=disable" option additionally seems to work well for me. Does anyone know if this can have any negative implications?

Bug#822817: bug still present in 4.6

Hi, This bug is still present for me in Linux 4.6 from experimental. However I found that booting with "hpet=disable" results in a usable system again. Is this something I should report upstream? Thanks, Maxi signature.asc Description: This is a digitally signed message part.

Bug#821033: [avrdude] new upstream version (6.3) available

Package: avrdude Version: 6.2-5 Severity: wishlist --- Please enter the report below this line. --- Hi, A new upstream version of avrdude is available: "AVRDUDE 6.3 released" https://savannah.nongnu.org/forum/forum.php?forum_id=8461 Please consider packaging it in Debian. Thanks, Maxi ---

Bug#779495: upstream avr-libc-2.0.0 available

Hi, in the meantime avr-libc-2.0.0 has been released upstream. I don't know if this helps with the issues you mentioned but maybe it's worth having a look. Thanks, Maxi signature.asc Description: This is a digitally signed message part.

Bug#752446: wsjtx: Upstream v1.3 is available

Any news on this? Currently Version 1.6.0 is available. signature.asc Description: This is a digitally signed message part.

Bug#714836: Any news on the qucs package?

It seems there has been some upstream progress with the issues. Also upstream seems to have at least some interest in a Debian package. See this mailing list post from march this year: https://sourceforge.net/p/qucs/mailman/message/34967589/ signature.asc Description: This is a digitally signed

Bug#850620: [Pkg-utopia-maintainers] Bug#850620: [network-manager] does not update lifetime of temporary ipv6 addresses anymore, resulting in connection breakage

On Sonntag, 8. Januar 2017 17:34:09 CET Michael Biebl wrote: > Hi > > Am 08.01.2017 um 16:48 schrieb Maximilian Engelhardt: > > Package: network-manager > > Version: 1.4.4-1 > > Severity: important > > > > --- Please enter the report below this line. --- &g

Bug#843534: workaround

I ran into this bug today. For me this is really a grave bug as is completely broke my mail setup. I found two ways how I could work around this bug: (A) install mysql-server and purge it again. (B) execute the following commands as root: # mkdir -m700 /var/lib/mysql-files # chown

Bug#841458: [src:libkf5ksieve] managing sieve scripts broken in kmail

Package: src:libkf5ksieve Version: 4:16.04.2-2 Severity: important Tags: patch --- Please enter the report below this line. --- Hi, Managing sieve scripts from kmail is currently broken. When trying to edit the rules I get this error: Sieve operation failed. The server responded: require

Bug#830288: status of updated wireless-regdb

Hi, I just wanted to ask about the status of this. Are there any problems beside missing resources for packaging? It would be good to have an updated wireless-regdb for stretch. Thanks, Maxi signature.asc Description: This is a digitally signed message part.

Bug#845798: patch for amarok

Hi, I created a patch for amarok that switches to using mariadb. I don't see how the current mysql-defaults system can be used in amarok, as there is no default-mysqld-dev package. $ diff -u debian.orig/amarok-2.8.0/debian/control debian/amarok-2.8.0/debian/control ---

Bug#850462: [src:libkf5ksieve] managing sieve scripts in kmail stops working after some time

Package: src:libkf5ksieve Version: 4:16.04.3-1 Severity: normal --- Please enter the report below this line. --- Hello, After a fresh start of kmail managing sieve scripts does work as expected. After some time it doesn't work any more. Opening Settings -> Manage Sieve Scripts... only shows a

Bug#850620: [network-manager] does not update lifetime of temporary ipv6 addresses anymore, resulting in connection breakage

Package: network-manager Version: 1.4.4-1 Severity: important --- Please enter the report below this line. --- After updating to network-manger 1.4.4-1 I noticed a lot of breakages in ssh connections. It turned out this is related to temporary ipv6 addresses being deprecated, deleted and

Bug#849598: [Pkg-kde-extras] Bug#849598: amarok: FTBFS (cannot find -lmysqlclient)

This is fixed by adding libmariadbclient-dev-compat to the build dependencies. I'm not sure why this is needed now. diff -ur debian.orig/control debian/control --- debian.orig/control 2016-12-23 16:05:31.0 +0100 +++ debian/control 2017-01-06 16:21:18.0 +0100 @@ -11,7 +11,7

Bug#849326: amarok: deleting/renaming errmsg.sys solves the problem

On Donnerstag, 5. Januar 2017 19:39:52 CET Maria wrote: > Dear Maintainer, > > deleting or renaming /usr/share/kde4/apps/amarok/mysqle/errmsg.sys to > errmsg.sys.old solves the problem! > > Thanks - Maria Hi, Unfortunate this doesn't work for me because amarok then uses the errmsg.sys from

Bug#859560: fixed in xen 4.8.1-1

On Dienstag, 25. April 2017 00:08:20 CEST Ivar Smolin wrote: > On Tue, 18 Apr 2017 17:34:15 + Ian Jackson > > wrote: > > Source: xen > > Source-Version: 4.8.1-1 > > > > We believe that the bug you reported is fixed in the latest version of > > xen, which is due to

Bug#797844: kmail: TLSv1.1 and TLSv1.2 are not supported

tag 797844 + patch thanks Hi, I recently ran into this bug when my mail server switched to TLS 1.2 only. I backported the upstream changes to the Debian stretch packages and are running them now without problems. The patches are are attached to this mail. Affect source packages are kimap,

Bug#891254: [src:kde4libs] Please enable TLSv1.2 for smtp connections in stretch

Package: src:kde4libs Version: 4:4.14.26-2 Severity: important Tags: patch, stretch --- Please enter the report below this line. --- kmail in stretch only supports TLSv1.0 which hinders it to connect to mail servers that only support TLSv1.2 or TLSv.1.1. The attached patch is a backport of the

Bug#891255: [src:kimap] Please enable TLSv1.2 for imap connections in stretch

Package: src:kimap Version: 16.04.2-1 Severity: important Tags: patch, stretch --- Please enter the report below this line. --- kmail in stretch only supports TLSv1.0 which hinders it to connect to mail servers that only support TLSv1.2 or TLSv.1.1. The attached patch is a backport of the

Bug#891253: [src:libkf5ksieve] Please enable TLSv1.2 for sieve connections in stretch

Package: src:libkf5ksieve Version: 4:16.04.3-2 Severity: important Tags: patch, stretch --- Please enter the report below this line. --- kmail in stretch only supports TLSv1.0 which hinders it to connect to mail servers that only support TLSv1.2 or TLSv.1.1. The attached patch is a backport of

Bug#891253: Related bugs

Please also see the related bugs for smtp https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891254 and imap https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891255 signature.asc Description: This is a digitally signed message part.

Bug#891254: Related bugs

Please also see the related bugs for sieve https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891253 and imap https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891255 signature.asc Description: This is a digitally signed message part.

Bug#891255: Related bugs

Please also see the related bugs for sieve https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891253 and smtp https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891254 signature.asc Description: This is a digitally signed message part.

Bug#851560: dhcpcd5: update to new upstream version

The latest version of dhcpcd is currently 7.0.7: https://roy.marples.name/archives/dhcpcd-discuss/0002151.html Thanks, Maxi signature.asc Description: This is a digitally signed message part.

Bug#911457: [src:xen] please add Homepage and Version Control System fields to debian/control

Package: src:xen Version: 4.11.1~pre.20180911.5acdd26fdc+dfsg-5 Severity: wishlist Hi, please consider adding Homepage, Vcs-Browser and Vcs-Git fields in debian/ control so they will show up in tracker (and probably other places too). Something like this should work: Homepage:

Bug#910680: [tucnak] New upstream version available

Package: tucnak Version: 4.09-1 Severity: wishlist Tucnak version 4.14 has been released upstream at 07.07.2018. The version 4.09 currently in unstable has been released over one and a half years ago. It would be great to have a more modern version in unstable (and in the next Debian release).

Bug#918479: freecad autopkgtest

Hi, I had a quick look at this bug and notices the upstream parameters for launching the test command changed in [1]. Maybe it's enough to adjust the commands in 'debian/tests/freecadtest' [2] from freecadcmd -t 1 freecadcmd -t 2 to freecadcmd -t 0 However I currently don't have a

Bug#914211: Processed: fixed in 5.54.1-1

On Samstag, 19. Januar 2019 08:15:20 CET Pino Toscano wrote: > In data sabato 19 gennaio 2019 01:12:38 CET, Debian Bug Tracking System ha scritto: > > Processing commands for cont...@bugs.debian.org: > > > fixed 914211 5.54.1-1 > > > > Bug #914211 [src:kio] [src:kio] please remove insecure TLS

Bug#915866: [python3-dnspython] crashes on parsing DNS zone file with NSEC3

Package: python3-dnspython Version: 1.15.0-1 Severity: normal Tags: patch Hi, python3-dnspython crashes while parsing my zone files with DNSSEC and NSEC3. The zone files are generated by the knot DNS server and I thus believe them to be correct and valid. Traceback (most recent call last):

Bug#914212: [libkio5] please remove insecure TLS version fall-back mechanism

Package: libkio5 Version: 4:4.14.26-2 Severity: important Tags: patch Hi, Until recently KDE kio had a custom TLS version fall-back mechanism which made it possible to downgrade a TLS connection to TLSv1.0 even if the server and client support a higher TLS version. This has been fixed upstream

Bug#914211: [src:kio] please remove insecure TLS version fall-back mechanism

Package: src:kio Version: 5.49.0-1 Severity: important Tags: patch Control: found -1 5.28.0-2 Hi, Until recently KDE kio had a custom TLS version fall-back mechanism which made it possible to downgrade a TLS connection to TLSv1.0 even if the server and client support a higher TLS version. This

Bug#914211: link to other bug report

Please also see the bug report of this issue in libkio5 (src:kde4libs) here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914212 signature.asc Description: This is a digitally signed message part.

Bug#914212: link to other bug reports

Please also see the bug report of this issue in src:kio here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914211 If you consider fixing this in stretch please also have a look at this bug report about adding TLSv1.2 support for smtp connections to kde4libs in stretch:

Bug#922172: knot 2.7.6 in Buster?

Hi Ondřej, You uploaded knot 2.7.6 to unstable some days ago. I've seen it's currently blocked from testing migration by a regression in the knot-resolver package: https://qa.debian.org/excuses.php?package=knot This turned out to be due to a change in kdig exit code behavior which needs

Bug#922172: [src:knot-resolver] autopkgtest fails with knot 2.7.6-1

Package: src:knot-resolver Version: 3.2.0-1 Severity: important Tags: patch Control: affects -1 knot I'm nut sure about the correct severity, so I'm filing this as important. Feel free to adjust. With knot 2.7.6-1 (currently in unstable) autopkgtest for knot-resolver fails:

Bug#887733: Should this bug be closed?

This bug is still open but has been marked as fixed in the versions currently in testing/unstable and stable. It also has been fixed in oldstable-security. Should it be closed or is there any reason to still keep it open? signature.asc Description: This is a digitally signed message part.

Bug#942308: Maybe duplicate of #930919

Could this be the same problem as described in this bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930919 There is also a patch linked that you could try. signature.asc Description: This is a digitally signed message part.

Bug#923464: carbon-cache unusable in Buster

severity 923464 important thanks Hi, we also ran into this bug and I can confirm the attached patch by Mark fixed the issue for us. This should definitely be fixed in unstable/testing and then also in buster. I set the severity to important as the repeated crashes of carbon-cache caused

Bug#980253: libsdl1.2debian: unexpected key down release

Package: libsdl1.2debian Version: 1.2.15+dfsg2-4 Severity: important Tags: patch Hi, since some time I noticed a problem within a game (Unreal Tournament 2004) using libsdl1.2 that the forward movement suddenly stopped, while I still had the forward key pressed. This is an quite annoying bug

Bug#976597: A proposed fix, but blocked by a dh-python bug

Control: tags -1 + patch Control: block -1 980303 I implemented a fix for this issue in [1], however this is currently blocked due to a bug in dh_python. [1] https://salsa.debian.org/myx/debian-xen/-/commits/myx/fix_python_dependencies signature.asc Description: This is a digitally signed

Bug#980303: dh-python: doesn't recognize "python3-dev:any" as a python-dev build dependency

Package: dh-python Version: 4.20201102 Severity: normal Tags: patch Hi, dh-python does not properly handle build dependencies with the ":any" suffix. This leads to a dependency like "python3-dev:any" not being recognized as a python-dev build dependency in the python_dev_in_bd variable (file

Bug#980310: dh-python: python dependency not generated for private directories

Package: dh-python Version: 4.20201102 Severity: normal Tags: patch Hi, if there are only python files in private directories and they only use a "/usr/bin/python3" shebang, dh-python does not add any dependencies in ${python3:Depends}, although a dependency to python3 should be added. I

Bug#975822: patch attached

Control: tags -1 + patch Attached is a simple patch fixing this issue in my local test build. Adrian Bunk, you marked this bug as pending, are you planning to upload a fixed version or has this been a mix up in bug numbers like in your other mail in this bug? Thanks, Maxidiff -ur

Bug#989560: xen-hypervisor-common: generates broken grub configuration on armhf

Package: xen-hypervisor-common Version: 4.14.1+11-gb0b734a8b3-1 Severity: important Installing xen-system-armhf in a test vm and running update-grub left me with a grub configuration that cannot boot the xen hypervisor and gets stuck in the grub menu. It's still possible to boot the normal

Bug#988901: xen: installing xen-system-amd64 does not always properly update grub configuration

Source: xen Severity: normal Version: 4.14.1+11-gb0b734a8b3-1 I noticed that installing xen-system-amd64 does not always lead to a grub configuration that will boot into the xen hypervisor. As a quick fix "update-grub" can be run manually after installation of xen-system-amd64 to generate the

Bug#975160: NMU still in DELAYED queue

Ping to avoid autoremoval. The NMU from Adrian Bunk should hit the archive within one day now. signature.asc Description: This is a digitally signed message part.

Bug#1003002: some more information

I did some more tests as I also ran into this problem. Here is what I could find out until now: I start qemu manually in a similar way as done by autopkgtest with the following command: $ qemu-system-arm -machine virt -m 1024 -smp 1 -display none -net nic,model=virtio -net

Bug#1006250: src:collectd: collectd should no longer build the xencpu plugin on i386

=medium + + * Non-maintainer upload. + * Don't build the xencpu plugin on i386. Starting with xen version 4.16, xen +is no longer built on the i386 architecture in Debian. + + -- Maximilian Engelhardt Sun, 20 Feb 2022 23:41:12 +0100 + collectd (5.12.0-8) unstable; urgency=medium [ Kentaro

Bug#1006300: src:libvirt: libvirt should no longer build the libvirt-daemon-driver-xen package on i386

+0100 @@ -1,3 +1,11 @@ +libvirt (8.0.0-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Remove i386 from ARCHES_XEN. Starting with xen version 4.16, xen is no +longer built on the i386 architecture in Debian. + + -- Maximilian Engelhardt Mon, 21 Feb 2022 23:13:01 +0100

Bug#1004269: Linker segfault while building src:xen

Control: found -1 2.37.90.20220123-2 Control: affects -1 src:xen Hi, this bug is still present in my sbuild chroot (updated about an hour ago) when compiling xen 4.14.3+32-g9de3671772-1 from unstable. I managed to run x86_64-linux-gnu-ld inside gdb to catch the segmentation fault. Please see

Bug#1003002: some more information - possible solution

On Sonntag, 4. Dezember 2022 01:42:14 CET Christian Kastner wrote: > Can anyone else give this patch a try before I submit an MR? Uh, this is great news and an easy fix. I did some tests and can confirm that your patch fixes this problem for me. signature.asc Description: This is a digitally

Bug#1033676: unblock: xen/4.17.0+74-g3eac216e6e-1

Control: retitle -1 unblock: xen/4.17.0+74-g3eac216e6e-1 On Sonntag, 2. April 2023 21:51:11 CEST Sebastian Ramacher wrote: > On 2023-03-29 23:27:11 +0200, Maximilian Engelhardt wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian...

Bug#1033676: unblock: xen/4.17.0+74-g3eac216e6e-1 (pre-approval)

x86/HVM pinned cache attributes mis-handling + XSA-428 CVE-2022-42333 CVE-2022-42334 +- x86: speculative vulnerability in 32bit SYSCALL path + XSA-429 CVE-2022-42331 + + -- Maximilian Engelhardt Thu, 23 Mar 2023 22:22:48 +0100 + xen (4.17.0+46-gaaf74a532c-1) unstable; urgency=medium

Bug#1036601: xenstore-utils: broken symlink /usr/bin/xenstore-control

Control: retitle -1 xenstore-utils: broken symlink /usr/bin/xenstore-control This is a bit more complicated: Up to bullseye the binaries in the xenstore-utils package were independent of the running xen version (as the xenstore interface is more or less supposed to be stable). Starting with

Bug#1036475: unblock: xen/4.17.1+2-gb773c48e36-1

00 +0100 +++ xen-4.17.1+2-gb773c48e36/debian/changelog 2023-05-18 21:26:30.0 +0200 @@ -1,3 +1,15 @@ +xen (4.17.1+2-gb773c48e36-1) unstable; urgency=medium + + * Update to new upstream version 4.17.1+2-gb773c48e36, which also contains +security fixes for the following issues: +

Bug#1042102: Also fixed in upstream stable-4.17 branch

This commit got also included in the upstream stable-4.17 branch: https://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=a91b946345b0c0550d0ee28816a15d3fc16abc50 signature.asc Description: This is a digitally signed message part.

Bug#1038901: xen dom0 erroneous detected as 'xen' virtualization by systemd-detect-virt

Package: systemd Version: 252.6-1 Severity: normal X-Debbugs-Cc: m...@daemonizer.de Control: affects -1 + src:xen When running the xen hypervisor, systemd-detect-virt erroneous detects 'xen' virtualization on the dom0: $ systemd-detect-virt xen The expected output should be 'none', in case of a

Bug#1063270: xen: NMU diff for 64-bit time_t transition

Control: found -1 4.17.2+76-ge1f9cb16e2-1 Hi Steve, Thanks for taking care about the 64-bit time_t transition. Unfortunately your attached patch looks a bit strange to me. It adds autogenerated files, but especially FTBFS in your experimental upload. You can find an updated patch attached to

Bug#1029998: [Pkg-xen-devel] Bug#1039422: xen and systemd support

resending so this also appears in #1029998. Hi Yann, Thanks for your mail. > Maybe one of those bugs should be marked as dup? Yes, doing so now. > I noticed that building this package with libsystemd-dev installed > causes a build failure, as unit files are then generated but not shipped > by

Bug#1039422: [Pkg-xen-devel] Bug#1039422: xen and systemd support

Control: forcemerge 1039422 1029998 Hi Yann, Thanks for your mail. > Maybe one of those bugs should be marked as dup? Yes, doing so now. > I noticed that building this package with libsystemd-dev installed > causes a build failure, as unit files are then generated but not shipped > by any

Bug#1057959: dhcpcd gets stopped during upgrade but never started again

On Mittwoch, 13. Dezember 2023 22:20:40 CET Martin-Éric Racine wrote: > I've uploaded the fix to unstable. > > Since this is not the sort of urgent issue that would warrant a > separate update to Bookworm, I won't upload it there for now. However, > I'll definitely include it if there ever is a

Bug#1057959: dhcpcd gets stopped during upgrade but never started again

Package: dhcpcd Version: 1:9.4.1-24~deb12u3 Severity: normal X-Debbugs-Cc: m...@daemonizer.de Hi, during the recent point release I noticed that during the unattended-upgrades run dhcpcd was stopped but never started again. This is undesired as it breaks internet connection for me and I need to

Bug#1057959: dhcpcd gets stopped during upgrade but never started again

On Montag, 11. Dezember 2023 08:51:36 CET Martin-Éric Racine wrote: [...] > > Unless I misunderstood, this is due to a change of debhelper behavior > since compatibility level 10. This leaves me with two possible > solutions: > > 1) No dh_install option. This will restart after upgrade (default

Bug#1053246: Security support ended for Xen 4.14 in Bullseye

On Montag, 2. Oktober 2023 19:18:49 CET Santiago Ruano Rincón wrote: > El 30/09/23 a las 00:09, Hans van Kranenburg escribió: > > Package: debian-security-support > > Version: 1:11+2023.05.04 > > Severity: normal > > > > Hi, > > > > Upstream security support for Xen 4.14 has ended recently. This

Bug#1062048: xen: FTBFS with Python 3.12 as default

Control: tags -1 +fixed-upstream Hi, this issue has been fixed upstream by https://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=40be6307ec005539635e7b8fcef67e989dc441f6 and was backported to the upstream stable-4.17 branch in

  1   2   >