Bug#1095376: more info

Here are the results of running valgrind with a debugging build of every relevant package installed: ==241689== Invalid read of size 8 ==241689==at 0x53A92E: UnknownInlinedFun (objimpl.h:6) ==241689==by 0x53A92E: _PyObject_New (object.c:534) ==241689==by 0x70D3532: SWIG_Python_newvarl

Bug#1098793: fixed in refpolicy

severity 1098793 normal thanks This is fixed in refpolicy 2.20250213-1 by depending on the right versions of everything. I'll leave it open for the moment while things are still getting through to testing but I've lowered the priority. -- My Main Blog http://etbe.coker.com.au/ My Docu

Bug#1091109: fixed upstream

close 1091109 thanks The 3.8 upstream release incorporated a fix for this. Sorry for dropping the NMU changelog entry. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/

Bug#1095376: the cause of this

The command "python3 -bb -t -t -E -W error support/validate-appconfig.py -c / usr/bin/chkcon -l -s -v -x tmp/appconfig tmp/policy.bin" is crashing. Here's a backtrace: #0 0x005378ee in _PyObject_New () #1 0x7763919f in SWIG_Python_newvarlink () at ./src/ selinuxswig_python_wrap

Bug#1081514: libcurl-gnutls.so.4: undefined symbol: gnutls_free

On Thursday, 12 September 2024 22:51:39 AEST Simon McVittie wrote: > Looks like a duplicate of which is a > regression in libcurl3t64-gnutls. libcurl4t64 (curl with OpenSSL) looks OK > according to packages.debian.org. Yes the same issue. Thanks for the quick res

Bug#1051181: more info

# id test uid=1001(test) gid=1001(test) groups=1001(test),1003(),1004(zzz2), 1005(test2),1006(test6),1007(test7),1008(test8),1009(test9),1010(test10), 1011(test11),1012(test12),1013(test13),1014(test14),1015(test15),1016(test16), 1017(test17),1018(test18),1019(test19) The above is the test use

Bug#1051181: FTBFS: can't build package when user has more than 16 supplementary groups

Package: fapolicyd Version: 1.1.7-5 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) # TOTAL: 2 # PASS: 1 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: gid_proc_test === ./g

Bug#1037890: fixed in 4.3.5

close 1037890 thanks This was fixed upstream in 4.3.5 -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/

Bug#985883: python3-pep8: Does not install /usr/bin/pep8

On 28/3/21 3:01 am, Andrey Rahmatullin wrote> On Thu, Mar 25, 2021 at 07:30:14PM +1000, Russell Stuart wrote:>> Justification: renders package unusable> >> python3-pep8 does not install the pep8 executable under /bin or>> /usr/bin.> There is no pep8 executable an

Bug#985883: python3-pep8: Does not install /usr/bin/pep8

Package: python3-pep8 Version: 1.7.1-9 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 python3-pep8 does not install the pep8 executable under /bin or /usr/bin. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZqiOeH6lCkTWvjmorNSfiF5UUm4FAmBc

Bug#985043: nagios4-cgi: fails to install with --install-recommends enabled

I can't reproduce this. I've tried running piuparts on the .changes file, I've manually installed it into a minimal chroot, and in fact I use it in production. I used piuparts on bullseye, amd64. Attached is the output of my run "piuparts --apt --logfile=/tmp/nagios4-cgi_4.46-2.log nagios4-

Bug#963497: not a bug for that version

close 963497 thanks Run "setsebool allow_execmem 1" before running certbot and it will be fine. After running certbot you can run "setsebool allow_execmem 0". Or you could run "setsebool -P allow_execmem 1" to make the change continue to apply after a reboot. The 2:2.20161023.1-9 policy does

Bug#963495: not a bug

close 963495 thanks Run "setsebool allow_execmem 1" before running certbot and it will be fine. After running certbot you can run "setsebool allow_execmem 0". Or you could run "setsebool -P allow_execmem 1" to make the change continue to apply after a reboot. There is no good solution to thi

Bug#938554: RFS: spyne/2.13.15-0.1 [NMU, RC] -- Python library for writing and calling soap web service

On Tue, 2020-06-16 at 02:00 +0200, Bastian Germann wrote: > It is no longer marked as alpha; version 2.13.15 > 2.13.4-alpha. > Please check the RFS again. Apologies Bastian, I was looking at spyne's home page. The non-alpha version has indeed been released today. How "released today" translates

Bug#938554: RFS: spyne/2.13.15-0.1 [NMU, RC] -- Python library for writing and calling soap web service

On Tue, 2020-06-16 at 00:58 +0200, Bastian Germann wrote: > Dear mentors, > > I am looking for a sponsor for the package "spyne" which has a > py2removal RC and a grave bug and was autoremoved from testing. The > package is Python 2 only but the current upstream version has Python > 3 support. I c

Bug#956568: libsepol: should build-depend on libselinux1-dev

Source: libsepol Version: 3.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Gives a compile error about missing flask.h. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Arch

Bug#954189: acmetool: Buster acmetool stops working in June 1, 2020

For what it's worth, the version currently in Testing (which does support ACMEv2) will install on Buster with no additional dependencies and seems to be working. Hopefully this means a backport? If nothing else, this does present a work-around. -Russ

Bug#943495: Can't reproduce

severity 943495 normal thanks I was unable to reproduce a problem when building with the latest packages from Unstable. It appears to be building the Python 3.8 stuff in the cpython3_3.8 directory. I've installed the gcc package from experimental to make all the gcc links point to version 10,

Bug#952896: kmail: message body section of kmail flickers rapidly and displays no content

Package: kmail Version: 4:19.08.3-1 Severity: critical Justification: breaks unrelated software I tagged this critical and breaks unrelated software as there seems no better tag for software that is dangerous for epileptic people to use. Every time I launch kmail the message body section flickers

Bug#938554: Bug#877783: spyne_2.13.11a0-0.1_source.changes REJECTED

On Tue, 2019-12-17 at 09:52 +0100, Bastian Germann wrote: > The "unlikely scenario" is reality NOW. Maybe you did not check but > spyne is already gone in testing. > That is what I wanted to draw your attention at. Ahh OK. I didn't realise you considered it being dropped from testing as important.

Bug#938554: spyne_2.13.11a0-0.1_source.changes REJECTED

On Mon, 2019-12-16 at 19:19 +0100, Bastian Germann wrote: > Yes, I missed that. But maybe you have made up your mind now that > spyne got auto-removed from testing. > Isn't it better to have an alpha version in testing than no version > at all? As I said in my reply to the bug report, the "no vers

Bug#928415: fixed in firefox-esr 60.6.2esr-1

Thanks for the quick turn-around! Any idea when this will show up in Stable? -Russ

Bug#928415: firefox-esr: Bugzilla 1548973 All extensions disabled due to expiration of intermediate signing cert

Package: firefox-esr Version: 60.6.1esr-1~deb9u1 Severity: grave Tags: upstream Justification: causes non-serious data loss >From Bugzilla 1548973 https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Steps to reproduce: Wait until it's past midnight on 2019-05-04 UTC. Actual results: All add

Bug#894066: purple-matrix: Can't login: Invalid response from server

Package: purple-matrix Version: 0.0.0+git20180325-1 Severity: grave Tags: upstream Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Maintainer, Attemping to login to matrix

Bug#885525: [Pkg-utopia-maintainers] Bug#885525: better log output

Sean, That worked for me too! Thanks a lot. When this patch is finally released by gnome, do I need to worry about removing the patch I just intalled? Or will apt properly install over top of it? Thanks agian, Russell On Tue, Jan 9, 2018 at 11:13 AM, Laurent Martelli wrote: On Tue, 9

Bug#885525: [Pkg-utopia-maintainers] Bug#885525: better log output

On 2017-12-28 15:31, Michael Biebl wrote: Control: tags -1 + moreinfo Please install dbgsym packages for at least libnm0, libnma0 and network-manager-gnome to get a more useful backtrace. https://wiki.debian.org/HowToGetABacktrace This is the output of gdb after installing a bunch of -dbgsym

Bug#881162: tomcat7: Server reports 404 on any request, even /

eeing if the context loads and serves up the initial page. Many thanks. -- Russell A Jackson Information Security and Emerging Technologies California State University, San Bernardino

Bug#881162: tomcat7: Server reports 404 on any request, even /

Just adding a me too. Update took out our entire app cluster last night. Rolling back to previous version resolved outage. -- Russell A Jackson Information Security and Emerging Technologies California State University, San Bernardino

Bug#877390: Fwd: facter: Potential leak of IAM instance profile role authentication information stored in fact

Package: facter Version: 2.2.0-1 Severity: critical Tags: security upstream Justification: root security hole Dear Maintainer, Due to https://tickets.puppetlabs.com/browse/FACT-800, Facter caches IAM role AKID/SAKID and Token under ec2_metadata fact. Facts are stored under /var/lib/puppet/yaml/fa

Bug#874191: not serious

severity 874191 normal thanks Daemon in the wrong domain is not a reason to have the package removed from testing. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/

Bug#874191: might be a duplicate

On Thursday, 7 September 2017 8:06:12 PM AEST Harlan Lieberman-Berg wrote: > Hm. Looking more, you may be right. What's odd is that some binaries > that are (presumably) being launched by Gnome are being correctly > given the right context; for example, gdm and X are running as > system_u:system_

Bug#874191: might be a duplicate

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874201 Yesterday I was investigating an issue that might be related and I just filed the above bug report. Please investigate whether that might be the cause. # ps axZ|grep sddm system_u:system_r:xdm_t:s0-s0:c0.c1023 963 ? Ssl0:00 /usr/bin

Bug#853207: bluez: bluetooth.service doesn't start with systemd

Package: bluez Version: 5.43-1 Severity: grave Justification: renders package unusable # systemctl restart bluetooth.service # systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: inac

Bug#817677: already fixed

close 817677 thanks I fixed this in version 2.2.1-2 but forgot to put a closes: entry in the changelog. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/

Bug#800258: already fixed

close 800258 thanks This was fixed in 0.13e but I forgot to list it in the changelog. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/

Bug#849787: probably best to just ignore this for Stretch

priority 849787 wishlist thanks I've made selinux policy packages conflict with mcstrans so this shouldn't be a problem any more. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/

Bug#840227: libgit2: CVE-2016-8568 CVE-2016-8569

it2/libgit2/issues/3937 > [5] https://github.com/libgit2/libgit2/pull/3956 > > Please adjust the affected versions in the BTS as needed. > > Regards, > Salvatore -- Cheers, Russell

Bug#830472: can't reproduce, not serious

severity 830472 normal thanks I can't reproduce this. Version 0.74 fixed all the GCC6 related bugs that occur on my system. Version 0.75 should stay in testing because the amd64 package I uploaded compiled without any serious warnings. I'll fix this bug if I can reproduce it, but it's not a r

Bug#849787: mcstrans: Running mcstrans triggers 849748 and is the most serious SE Linux problem

Package: mcstrans Version: 2.6-2 Severity: critical Tags: upstream Justification: breaks unrelated software While mcstrans has no problems for what it does, it triggers bad interactions between systemd, dbus, and SE Linux. I don't think it is possible to properly solve these issues before the sid

Bug#841532: libgit2 update in debian fixing #841532

k that it would make it past freeze. But it appears that my assumption was mistaken. Thanks for prodding me I'll wait until after the full freeze to package and push 0.25.0 to experimental. Thanks, Russell On 28 December 2016 at 00:27, Andreas Henriksson wrote: > Hello Russell Sim. >

Bug#841532: libgit2: FTBFS under some timezones (eg. GMT-14)

amb writes: > forwarded 841532 https://github.com/libgit2/libgit2/issues/3970 > thanks > > Russell Sim wrote: > >> I have forwarded this bug report upstream >> https://github.com/libgit2/libgit2/issues/3970 in the mean time I'll add >> a fix to the existing pa

Bug#841532: libgit2: FTBFS under some timezones (eg. GMT-14)

Expression is not true: expected->when.offset == actual->when.offset > > > 50% tests passed, 1 tests failed out of 2 > > Total Test time (real) = 16.30 sec > > The following tests FAILED: > 1 - libgit2_clar (Failed) > Errors while running CTest > > […] > > The full build log is attached. > > > Regards, -- Cheers, Russell

Bug#835910: warzone2100: FTBFS when newer automake is installed

Package: warzone2100 Version: 3.1.1-3 Severity: serious Tags: upstream patch Justification: fails to build from source (but built successfully in the past) The warzone2100 build system insists on automake and aclocal version 1.11. If you have 1.15 installed it won't build. The following patch ma

Bug#778599: Vulnerabilities in nanohttp

On Thu, 21 Apr 2016 02:58:18 PM Salvatore Bonaccorso wrote: > Given the package looks unmaintained (last update by maintainer back > in 20 Jun 2010, I think it is the best option to remove the package as > well from unstable). It is already gone in testing, so will not be > included in stretch and

Bug#805492: /var/lib

On Mon, 29 Feb 2016 02:47:04 AM Laurent Bigonville wrote: > Le 28/02/16 11:05, Russell Coker a écrit : > >> the easiest would be to do like fedora and install the modules directly > >> in the /var/lib/selinux//100 store instead of copying/loading > >> them at installa

Bug#805492: /var/lib

> the easiest would be to do like fedora and install the modules directly in > the /var/lib/selinux//100 store instead of copying/loading them at > installation time Do you mean having files in the package under /var/lib? If so that seems like a FHS violation. Why not just keep them under /usr/

Bug#815861: mcstrans: doesn't create /var/run/setrans on startup with systemd

Package: mcstrans Version: 2.4-4 Severity: grave Justification: renders package unusable /var/run/setrans 0755 root root - - I think we need a /usr/lib/tmpfiles.d file with something like the above to create it when systemd is in use. Currently mcstrans doesn't start on Unstable. -- System Inf

Bug#756729: I just uploaded a package to fix this

deb http://www.coker.com.au jessie selinux It's at the above repository if you can't wait for it to get into Unstable/Testing. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/

Bug#756729: about to close

I'm going to upload a new policy to unstable that closes this bug. It allows udev to restart systemd services (the core problem with allow-hotplug). The policy in question doesn't support all the features of the version of systems in unstable (I'll get to that later). deb http://www.coker.com

Bug#786494: libgit2: diff for NMU version 0.22.2-1.1

possible. Is that ok? Cheers, Russell On 31 May 2015 at 07:30, Jonathan Wiltshire wrote: > Control: tags 786494 + patch > Control: tags 786494 + pending > > Dear maintainer, > > I've prepared an NMU for libgit2 (versioned as 0.22.2-1.1) and > uploaded it to DELAYED/2

Bug#786494: libgit2: loss of libssh2 functionality; please add "pkg-config" to Build-Depends

port. > > After adding "pkg-config" to Build-Depends the following should appear in > build log: > > -- checking for module 'libssh2' > -- found libssh2, version 1.5.0 > > and "libgit2-22" will Depend on "libssh2-1". > >

Bug#771484: fixed in 2.20140421-8

close 771484 thanks Version 2.20140421-8 fixed this. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.o

Bug#755834: How to reproduce

Run the following commands as root: # debootstrap ssu debootstrap --variant=minbase jessie bug-755834 # cd bug-755834 # sed -i '1s/\*//' etc/shadow # systemd-nspawn --boot # # ... log in as root # apt-get install isc-dhcp-server The last lines of output from the final step are:

Bug#756729: Already fixed

close 756729 thanks This was fixed in testing ages ago. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian

Bug#761170: upstream

alise it's probably futile but could you please run stat and compare your device id's. That is how they are checking that they are the same FS in the clone code. -- Cheers, Russell -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#761539: libgit2: FTBFS: Tests failures

g_options)) >> error -1 - git_path_direach callback returned -1 It has been identified that this failure is caused by having the tmp dir exist on a different mount to the package source. This can be fixed by setting the TMP_DIR to the package build dir before running the tests. -- Cheers, Russell -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#761170: upstream

e avoided unless we explicitly fail when building on those architectures. I'm happy to split the this into 2 bugs and 2 uploads. One revision to fix the TMP_DIR bug that is messing with the i386 build. And a new version that I'll get uploaded once we unfreeze. So is the best course of action: - Split bugs - Create new revision that only fixes the failing test on i386, it will also force and kfreebsd build to fail. -- Cheers, Russell -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#761170: upstream

patch, I only yesterday did exactly the same thing. It's included in the yet to be uploaded 0.21.3-1 that will also address the recent CVE. 0. http://anonscm.debian.org/cgit/users/arrsim-guest/libgit2.git/commit/?id=bd3a1fc82c5af703fe061fb22022eb48fb89be50 -- Cheers, Russell -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#771484: selinux-policy-default: GPG is totally broken

Package: selinux-policy-default Version: 2:2.20140421-7 Severity: grave Justification: renders package unusable "gpg" doesn't work on the command-line, gpg-agent can't be statted, and the whole X login process that spawns gpg-agent doesn't work for most user roles. -- System Information: Debian R

Bug#761170: upstream

OK, I'm about to request an upload of 0.21.2. Seems that it's still failing on kfreebsd. 1) Failure: repo::init::extended_1 [/home/russell/libgit2-0.21.2/tests/repo/init.c:340] Function call failed: (git_repository_init_ext(&_repo, "root/b/c.git", &opts)

Bug#736782: roundcube: diff for NMU version 0.9.5+dfsg1-4.1

rally this means you should use uscan to download the .orig.tar.gz from now on. The diff has had the files removed from the .orig.tar.gz below. Lines 1000's of characters long don't help clarity. Regards, Russell Stuart diff -Nru roundcube-0.9.5/debian/changelog roundcub

Bug#750350: smstools: diff for NMU version 3.1.15-1.1

Control: tags 750350 + patch Control: tags 750350 + pending Dear maintainer, I've prepared an NMU for smstools (versioned as 3.1.15-1.1) and uploaded it to DELAYED/10. Please feel free to tell me if I should delay it longer. Regards. Russell Stuart diff -u smstools-3.1.15/debian/chan

Bug#755404: NMU to fix

On Mon, 28 Jul 2014 09:53:25 Emilio Pozuelo Monfort wrote: > On 28/07/14 09:22, Russell Coker wrote: > > I've uploaded a NMU to fix this to the 7 day delayed > > queue. I made no code changes and just rebuilt it. > > Why not request a binNMU instead? I didn't rea

Bug#755404: NMU to fix

I've uploaded a NMU to fix this to the 7 day delayed queue. I made no code changes and just rebuilt it. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/

Bug#752591: Bug#752605: udev: luks/lvm not detected rendering system unbootable

On Wed, 25 Jun 2014 09:02:59 Michael Biebl wrote: > Russel, can you confirm that that reverting the "kmod load sg" patch > also fixes your problem? It seems to. Booted once since applying it and it worked. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.c

Bug#721454: libgit2 contiains mix of LGPL2 and Apache2

Paul Tagliamonte writes: > On Fri, Sep 06, 2013 at 10:35:07AM +1000, Russell Sim wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Paul Tagliamonte writes: >> >> > On Mon, Sep 02, 2013 at 11:32:09PM +1000, Russell Sim wrote: >>

Bug#721454: libgit2 contiains mix of LGPL2 and Apache2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Tagliamonte writes: > On Mon, Sep 02, 2013 at 11:32:09PM +1000, Russell Sim wrote: >> Paul Tagliamonte writes: >> >> > I notice there's a mix of GPLv2 and Apache2 code in the same binary. >> > This comb

Bug#721454: libgit2 contiains mix of LGPL2 and Apache2

rom my understanding it's also incompatible with the GPLv2 and GPLv3. I'll send a message upstream regarding these issues. In the mean time is there an action I should take regarding the package, it's currently in experimental, will it need to be removed from the archive? Thanks again,

Bug#611698: Prominent warning needed on installation

Seeing as so many things depend on 'node' being the node.js interpreter, such as the npm package and the build system used by pdf.js, there really ought to be a prominent warning shown on installation that users probably want to symlinke /usr/local/bin/node to /usr/bin/nodejs. The name conflict is

Bug#678853: maildir-bulletin: should it be removed? /home/bulletins/removed

On Sat, 25 Aug 2012, Ivo De Decker wrote: > Is anybody still interested in maintaining this package in debian? Perhaps > it makes more sense to remove it. > > - it has very few users (popcon says 16) > - it is RC buggy (writes in /home) > - the last upload was in 2008 > - the maintainer put it up

Bug#668954: not a serious bug, just a new feature that doesn't work.

ontinue to work without it. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/ Description: Add sandbox support for the sandbox utility from policycoreutils Author: Russell Coker Origin: Fedora Last-Update: 2012-06-26 Index: refpolicy-2.2011

Bug#667664: a fix for this

Bug #667664 is due to the latest versions of the libpcre3 library setting reg.re_nsub to an extremely large value and dansguardian trying to allocate memory for that many records and having malloc fail. I've attached a patch for dansguardian which fixes this. I'll upload a delayed NMU tomorrow

Bug#677759: ok

Fair point Laurent. As this is a corner case I'll change the mcstransd code to map the line in question to something it's happy with. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#672695: wordpress: no sane way for security updates in stable releases

On Sun, 13 May 2012, Bernd Zeimetz wrote: > Being forced to upgrade to a new major version by a stable security support > is nothing we should force our users to. Debian stable is known for > (usually) painfree updates and bugfixes only, not for shipping completely > new versions with a forced mig

Bug#668457: monotone: FTBFS (multiple test suite failures)

I've just had a go at building monotone in an i386 unstable chroot and had no issues. Perhaps whatever was causing the build failure is now fixed? Francis -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debi

Bug#668457: [Monotone-debian] Bug#668457: monotone: FTBFS (multiple test suite failures)

I had no issues rebuilding this on my 'testing' install, so I guess whatever's causing the issue hasn't hit it yet. Looking at the logs, it looks the the fails occur because monotone is failing to find its test databases, but the copy that creates them appears to complete successfully. Someone

Bug#665448: [Monotone-debian] Bug#665448: Bug#665448: monotone: FTBFS: testsuite failure

On 25/03/12 20:40, Thomas Moschny wrote: > Hi, > > this is a mini-patch I recently added to the Fedora package, to build > against newer PCRE. It deletes '(?<=\C)' from the list of regular > expressions in .mtn-ignore expected to throw an error. I wish you'd sent that a few hours earlier :) > Th

Bug#665448: monotone: FTBFS: testsuite failure

On 24/03/12 18:28, Ludovic Brenta wrote: > Please find the time to investigate and correct this problem. I suspect > something to do with libpcre3. I'll sponsor an upload as soon as you > can fix the problem. If you need help, scream. > I've pushed a fixed version, see the patch for details.

Bug#642736: already fixed

close 642736 2:2.20110726-1 thanks The Squeeze policy is never going to build in Wheezy. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Troubl

Bug#626720: policy changes

Martin, using the SE Linux libraries from Unstable I can't make the file_contexts.subs file take affect. I think that the only way to do this is to just have regular expressions that deal with this in the file contexts. It's a bit ugly and slows the relabel process down a little (probably no m

Bug#626720: support in squeeze

What I want to do is to have a policy in squeeze that supports running wheezy in a basic configuration. If a daemon that is in wheezy gets a new feature and breaks then I'm not too bothered (I am not aiming for full compatibility). But I want to have the basics work for everyone (which include

Bug#626720: sorry for being slack

I'm working on this now. http://userspace.selinuxproject.org/trac/browser/libselinux/src?order=date&desc=1 http://userspace.selinuxproject.org/trac/wiki/Releases Firstly please tell me what libraries you used when testing this patch? It seems that the necessary patch to libselinux was first pro

Bug#626720: SELinux refpolicy, initscripts and /run

Looks fine to me if the breaks line does what the changelog says it does. -- My bloghttp://etbe.coker.com.au Sent from an Xperia X10 Android phone -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.or

Bug#626720: SELinux refpolicy, initscripts and /run

Sorry for the delay. Yes please make it break the old version of policy. I hope to upload a fix on Sunday. -- My bloghttp://etbe.coker.com.au Sent from an Xperia X10 Android phone -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble?

Bug#628119: netatalk installs un-needed and non-FHS /default/ directory

On 27/05/2011, at 11:36 PM, Jonas Smedegaard wrote: > Indeed. Thanks for noticing. That gotta go! I'm sorta surprised I'm the first person to be annoyed by typing "foo /d" and being annoyed by completion to "/dev/" being broken, and wondering who was responsible... :) -- To UNSUBSCRIBE, e

Bug#623734: [Monotone-debian] Bug#623734: Bug#623734: monotone: FTBFS: test suite timeout

Aaron M. Ucko wrote: > At any rate, the Linux logs reveal that the (presumed) hang in question > occurs early on, perhaps as a result of attempting to make check in > parallel: Thank you! I attempted to build with a parallelism of 4, and make started consuming 100% CPU. We'll start working with t

Bug#623734: [Monotone-debian] Bug#623734: monotone: FTBFS: test suite timeout

Dear Aaron, this appears to be a hang, since the monotone test suite produces extensive output. Multiple monotone maintainers, developers and others have tried to replicate the hang and failed. At the very least, I believe the following configurations have been tested and found not to manifest the

Bug#584782: selinux-policy-default: /dev filesystem not labelled

On Fri, 14 Jan 2011, Julien Cristau wrote: > Thanks. I've unblocked refpolicy and selinux-basics, they should get in > over the weekend. I've just uploaded selinux-basics version 0.3.8. The diff is below. The change is that if dkim.pp is loaded then milter.pp (the new dependency of dkim.pp f

Bug#601850: monotone: Empty command string can be used to crash certain server configurations

Package: monotone Version: 0.48-2 Severity: serious Tags: upstream Monotone versions 0.46, 0.47 and 0.48 are affected by a bug whereby a client sending an empty command string to the server can cause it to terminate if remote command execution is enabled. This has been fixed in 0.48.1. Further d

Bug#591112: [Monotone-debian] Bug#591112: monotone: FTBFS: test failed

> This is a weird failure. The test in question marks a directory > unwritable via "chmod a-w" and then tries to perform a database > migration which needs write access to the database. The migration is > expected to fail because the database journal should not be writable to > the directory, but f

Bug#584782: selinux-policy-default: /dev filesystem not labelled

http://etbe.coker.com.au/2010/04/21/upgrading-se-linux-system-squeez/ At the above URL I have documented what you need to do to upgrade a SE Linux system to Squeeze. Manoj, is it possible to get a Lenny update for the policy? If not then we just have to close this bug. -- russ...@coker.com.a

Bug#559893: Bug#574512: Release-critical bugs in monotone: ping?

Ludovic Brenta wrote: Is anyone still interested in maintaining monotone in Debian? Just thought I'd add that I use monotone from Debian and know others who do as well. I'm willing to help in whatever way I can although I'm not a Debian Maintainer. Is this just a manpower issue? Francis

Bug#574512: Info received ([Monotone-debian] Bug#574512: monotone: mtn sync fails with 'fatal' error message)

Any progress on this bug? I assume it's not Debian-specific? Many thanks, Francis -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#574512: [Monotone-debian] Bug#574512: monotone: mtn sync fails with 'fatal' error message

Thomas Keller wrote: > This looks like a regression introduced in f65d9cb5 - please check if > this patch solves your problem: I rebuilt with the suggested patch and this appeared to fix the problem. Francis -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject o

Bug#560633: my workaround

I ran "cp /usr/share/libtool/config/ltmain.sh ." before building the package and it worked well. I don't know whether putting this command in the debian/rules would be the right thing to do. I'm not suggesting that the maintainer do this, merely noting it for other people like me who want to w

Bug#516394: djbdns: Thoughts on the dnscache cache poisoning issue

Package: djbdns Severity: normal Hi there, please do forgive me if I've got the wrong end of the stick here or the code I've posted is completely wrong or makes no sense. It would be nice to get djbdns back into testing. As I understand it, this bug works by getting dnscache to send extensive nu

Bug#536693: mayavi segfault with tk8.5

The problem still appears to exist in Debian testing. However, installing the latest python-vtk package from unstable (which also pulls in libvtk5.2) appears to fix it. Francis -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact

Bug#536693: mayavi segfault with tk8.5

Package: mayavi Version: 1.5-5 Severity: grave Justification: renders package unusable Mayavi segfaults instantly on startup in Debian testing. This appears to caused by upgrading python-tk from version 2.5.2-1 to 2.5.2-1.1 which switches python from using tk8.4 to tk8.5. -- System Information:

Bug#528029: googleearth-package: Workaround symbol problem in libcrypto prevents googleearth from starting

And this also seems to work: LD_LIBRARY_PATH=/usr/lib32:/usr/lib/googleearth/ /usr/lib/googleearth/googleearth-bin -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#532740: libdkim0d: Should use strtok_r() not strtok() for thread safety

Package: libdkim0d Version: 1:1.0.19-3 Severity: grave Tags: security Justification: user security hole The following patch makes libdkim use strtok_r() instead of strtok() for thread safety. If a server process has multiple threads operating on behalf of different users while verifying dkim dat

  1   2   >