Bug#600547: python-scipy: Scipy Documentation not in Debian
tags 600547 +patch pending stop I've updated the packaging in svn so that documentation is built in a dedicated binary. (This probably needs review though.) Regards, Denis. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747183: Icedove
Hi, I thank you for your help. The security lines are present in sources.lst file when you download and install a testing version. So, my question is why are they present? Regards -- Jean-Luc
Bug#734818: enable pam_keyinit by default
Le Wed, 7 May 2014 08:18:09 -0700, Steve Langasek a écrit : > On Wed, May 07, 2014 at 10:13:02AM +0200, Laurent Bigonville wrote: > > Le Tue, 6 May 2014 09:36:59 -0700, > > Steve Langasek a écrit : > > > > On Tue, May 06, 2014 at 09:12:59AM -0700, Russ Allbery wrote: > > > > Laurent Bigonville writes: > > > > > > On Fedora they are using: > > > > > > session optional pam_keyinit force revoke > > > > > force revoke looks good to me. I'm not sure that force is > > > > necessary, but it's probably a good idea in general. > > > > > > As it's only available on linux architectures, I was thinking > > > > > of adding a '-' at the beginning of the call. Do you think > > > > > this is OK for Debian? > > > > > Yes, although this is where it would be nice if this could > > > > somehow be handled by pam-auth-update so that the PAM module > > > > wouldn't be configured at all on systems that don't have it. > > > > As discussed on IRC, we don't want this to silently fail on Linux > > > systems because of some unrelated bug; that will just cause > > > difficult-to-diagnose problems. Since the module will be present > > > on all Linux systems, it's better to ship a different pam config > > > on Linux vs. non-Linux architectures, which can be done fairly > > > easily without duplication using dh-exec. > > > And couldn't we use the (dirty) trick we are using for pam_selinux? > > Which trick are you talking about? > pam_selinux is called like this in some pam services to not fail if the module is not existing: session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so open -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#690531: Help needed: Porting IRAF to MIPS
Hi David, On 08.05.2014 02:07, David Kuehling wrote: > Patch below works with both static and shared libraries. Makefile > patched so that shared library test can be built as well (set > LIBEXT to either ".a" or ".so" and comment out CFLAGS+=-fPIC > accordingly). Thank you very much for your patch! I will test it on unstable at the weekend and then use it for the MIPS port. Also, after I collected the assembler bits for the other missing archs, I will send them upstream. Best regards Ole -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#613143: there is /usr/lib64 symlink but no /usr/local/lib64
]] Aurelien Jarno > How can we progress on this bug? We now have bugs #720777, #720778 and > #720780 which ask for /usr/lib to be created if /lib exists. > It's something that can be implemented, but before doing so, I would > like to know if a decision has been taken wrt the policy. I think the whole lib thing should be avoided and we should nack it for any new ports. Ideally, we should also try to get ourselves out of the hole we've dug ourselves into. I don't see anybody being against relaxing the requirement for /usr/local/lib to exist, so we're presumably blocked on more seconds. -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747292: gdm3: Unable to login after last upgrade (version 3.8.4-7): fails to start a GNOME session
Le Wed, 07 May 2014 17:33:01 +0200, Benjamin Menant a écrit : > Well, I am not sure… It’s more or less a default Jessie installation. > I hope those following data will help. Please let me know. > > [...] So apparently I see a session opened here so logind itself seems to work as expected. But looking closer in the logs you posted, I see: gdm3][4091]: pam_systemd(gdm3:session): Failed to create session: No such file or directory This is a bit puzzling me. Could you please try to reinstall the libpam-systemd package maybe. Also in the logs I see the following warning/error: The value for the SHELL variable was not found the /etc/shells file Are you using some fancy shell for your user? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747292: gdm3: Unable to login after last upgrade (version 3.8.4-7): fails to start a GNOME session
Le Thu, 8 May 2014 09:08:36 +0200, Laurent Bigonville a écrit : > Le Wed, 07 May 2014 17:33:01 +0200, > Benjamin Menant a écrit : > > > Well, I am not sure… It’s more or less a default Jessie > > installation. I hope those following data will help. Please let me > > know. > > > > > [...] > > So apparently I see a session opened here so logind itself seems to > work as expected. > > But looking closer in the logs you posted, I see: > > gdm3][4091]: pam_systemd(gdm3:session): Failed to create session: No > such file or directory > > This is a bit puzzling me. Could you please try to reinstall the > libpam-systemd package maybe. > > Also in the logs I see the following warning/error: > > The value for the SHELL variable was not found the /etc/shells file > > Are you using some fancy shell for your user? Oh correction it seems to complain about gdm user shell: May 6 13:10:38 ** pkexec[3298]: Debian-gdm: The value for the SHELL variable was not found the /etc/shells file [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight- helper --set-brightness 16] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#741243: [PATCH] localedef fix on hppa architecture
Hello Aurelien, On 05/08/2014 01:06 AM, Aurelien Jarno wrote: >> could you please add this patch temporarily to the debian eglibc sources? > > I don't really understand why changing the alignment from 4MB to 4kB > will make the file mmapped at the same location. It's due to how the mmap logic was developed in glibc. Current logic will round the map-address up to the next SHMLBA alignment which may be wrong on parisc since the platform has specific hardware cache constraints which renders shared mappings then possibly not being in sync between different CPUs. > Anyway, in that case > instead of modifying a generic file common to all architecture, you > should create a with the HPPA specific > value. True. > Now that patch local-shmlba.diff from bug #725508 has been applied, is > this patch still needed? That's correct. This patch here is not needed any longer then. You can just close this bug report (or mark it as duplicate of #725508). Thanks! Helge -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747256: Chocolate Doom should be split into separate packages
Hi fraggle, Am Dienstag, den 06.05.2014, 15:39 -0400 schrieb Simon Howard: > Version 2 of Chocolate Doom added support for Heretic, Hexen and > Strife. The compiled binaries and manpages for the four games are > effectively separate, but Debian is currently distributing them as a > single package. It would make more sense to split them into four > separate packages so that people can just install the game(s) they > want to play. hm, as briefly discussed before, I am still not sure what this is supposed to achive. The whole package is about 3MB - unpacked. With the split approach I would also have to separate -server and -setup into different packages and introduce rather complex inter-package dependencies. Also, what should happen on upgrade? Not sure about that. :/ Cheers, Fabian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747388: autopkgtest depends on nonexisting python.zope.i18n (typo)
Package: python-chameleon Version: 2.6.1-2 Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu ubuntu-patch utopic User: autopkgtest-de...@lists.alioth.debian.org Usertags: autopkgtest Hello, python-chameleon's autopkgtest currently fails [1] because it can't find the "python.zope.i18n" package. This is just a typo in debian/tests/control, simple patch attached. Curiously this seems to work with pbuilder-satisfydepends-classic in the last run on ci.debian.net [2], but latest autopkgtest does not use pbuilder any more, so the test will soon break in Debian as well. Thanks for considering, Martin [1] https://jenkins.qa.ubuntu.com/job/utopic-adt-python-chameleon/ARCH=i386,label=adt/1/console [2] http://ci.debian.net/data/unstable-amd64/packages/p/python-chameleon/2014-05-06.log -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) diff -Nru python-chameleon-2.6.1/debian/changelog python-chameleon-2.6.1/debian/changelog --- python-chameleon-2.6.1/debian/changelog 2014-02-06 06:56:26.0 +0100 +++ python-chameleon-2.6.1/debian/changelog 2014-05-08 09:41:33.0 +0200 @@ -1,3 +1,9 @@ +python-chameleon (2.6.1-2ubuntu1) utopic; urgency=medium + + * Fix package name typo in test depends. + + -- Martin Pitt Thu, 08 May 2014 09:41:21 +0200 + python-chameleon (2.6.1-2) unstable; urgency=medium * Team upload. diff -Nru python-chameleon-2.6.1/debian/tests/control python-chameleon-2.6.1/debian/tests/control --- python-chameleon-2.6.1/debian/tests/control 2014-02-06 06:17:41.0 +0100 +++ python-chameleon-2.6.1/debian/tests/control 2014-05-08 09:41:19.0 +0200 @@ -1,2 +1,2 @@ Tests: all -Depends: @, python-zope.testing, python-zope.interface, python-zope.component, python.zope.i18n +Depends: @, python-zope.testing, python-zope.interface, python-zope.component, python-zope.i18n signature.asc Description: Digital signature
Bug#728240: Processed: Re: Bug#728240: libc6: S_IFMT constants not included when _POSIX_C_SOURCE is defined as 200112L
tags 728240 fixed-upstream thanks The story sadly is quite complicated. I added the following text to the page upstream: The definitions of most of the above file type test macros are provided if any of the following feature test macros are defined: _BSD_SOURCE (in glibc 2.19 and earlier), _SVID_SOURCE (in glibc 2.19 and earlier), or _DEFAULT_SOURCE (in glibc 2.20 and later). In addition, definitions of all of the above macros except S_IFSOCK and S_ISSOCK() are provided if _XOPEN_SOURCE is defined. The definition of S_IFSOCK can also be exposed by defining _XOPEN_SOURCE with a value of 500 or greater. The definition of S_ISSOCK() is exposed if any of the following feature test macros is defined: _BSD_SOURCE (in glibc 2.19 and earlier), _DEFAULT_SOURCE (in glibc 2.20 and later), _XOPEN_SOURCE with a value of 500 or greater, or _POSIX_C_SOURCE with a value of 200112L or greater. Cheers, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#517337: latex-beamer: \insertauthor doesn't report as empty even when no author is given
On 27.02.09 Micha Feigin (mi...@post.tau.ac.il) wrote: Hi Micha, > \insertauthor doesn't report as empty even when no author is given > which causes the follwing check that appears in several templates > to always be evaluated as false \ifx\insertauthor\@empty > This messes up the typesetting on the title page with no author > (the title has the wrong verical alignment) as there is an empty > line inserted > Are you still able to reproduce the bug? If yes: could you provide a minimal example for testing? Regards, Hilmar -- sigmentation fault -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#542954: libclamunrar: No detection with big rar-Files without compression
> Could it have something to do with --max-filesize & --max-scansize ? That was ist: - $ du * 52864 sp3.m0.rar 23624 sp3.m1.rar 21688 sp3.m2.rar 20152 sp3.m3.norm.rar 20108 sp3.m4.rar 20088 sp3.m5.rar $ file * sp3.m0.rar: RAR archive data, v14, os: Unix sp3.m1.rar: RAR archive data, v1d, os: Unix sp3.m2.rar: RAR archive data, v1d, os: Unix sp3.m3.norm.rar: RAR archive data, v1d, os: Unix sp3.m4.rar: RAR archive data, v1d, os: Unix sp3.m5.rar: RAR archive data, v1d, os: Unix $ clamscan * sp3.m0.rar: OK sp3.m1.rar: Eicar-Test-Signature FOUND sp3.m2.rar: Eicar-Test-Signature FOUND sp3.m3.norm.rar: Eicar-Test-Signature FOUND sp3.m4.rar: Eicar-Test-Signature FOUND sp3.m5.rar: Eicar-Test-Signature FOUND --- SCAN SUMMARY --- Known viruses: 3355606 Engine version: 0.98.1 Scanned directories: 0 Scanned files: 6 Infected files: 5 Data scanned: 0.00 MB Data read: 154.79 MB (ratio 0.00:1) Time: 7.183 sec (0 m 7 s) $ clamscan * --max-filesize=100M sp3.m0.rar: Eicar-Test-Signature FOUND sp3.m1.rar: Eicar-Test-Signature FOUND sp3.m2.rar: Eicar-Test-Signature FOUND sp3.m3.norm.rar: Eicar-Test-Signature FOUND sp3.m4.rar: Eicar-Test-Signature FOUND sp3.m5.rar: Eicar-Test-Signature FOUND --- SCAN SUMMARY --- Known viruses: 3355606 Engine version: 0.98.1 Scanned directories: 0 Scanned files: 6 Infected files: 6 Data scanned: 0.00 MB Data read: 154.79 MB (ratio 0.00:1) Time: 7.379 sec (0 m 7 s) - Thanks! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#743244: python-cffi: DEP8 test suite generates huge amounts of log
tag 743244 patch severity 743244 important user 743244 ubuntu-de...@lists.ubuntu.com usertags 743244 ubuntu-patch utopic thanks Hey Stefano, Antonio, all, Bumping severity as this pretty much DoSes our testing infrastructure. We had the same problem in Ubuntu as well, and this makes Jenkins explose :-) Simple fix attached. This fixes the test and avoids the enormous failure log. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) diff -Nru python-cffi-0.8.1/debian/changelog python-cffi-0.8.1/debian/changelog --- python-cffi-0.8.1/debian/changelog 2014-01-18 19:24:23.0 +0100 +++ python-cffi-0.8.1/debian/changelog 2014-05-08 10:06:01.0 +0200 @@ -1,3 +1,11 @@ +python-cffi (0.8.1-2) UNRELEASED; urgency=medium + + * Add missing build-essential test dependency. The lack of that made the +test fail and complain bitterly with a ginormous (~ 3 GB!) log file. +(Closes: #743244) + + -- Martin Pitt Thu, 08 May 2014 10:05:10 +0200 + python-cffi (0.8.1-1) unstable; urgency=medium * New upstream release. diff -Nru python-cffi-0.8.1/debian/tests/control python-cffi-0.8.1/debian/tests/control --- python-cffi-0.8.1/debian/tests/control 2013-08-08 00:33:13.0 +0200 +++ python-cffi-0.8.1/debian/tests/control 2014-05-08 10:04:54.0 +0200 @@ -1,5 +1,6 @@ Tests: unittests Depends: + build-essential, python-all-dbg, python-all-dev, python-cffi, @@ -10,6 +11,7 @@ Tests: unittests3 Depends: + build-essential, python-virtualenv, python3-all-dbg, python3-all-dev, signature.asc Description: Digital signature
Bug#725793: Pending fixes for bugs in the shadow package
tag 725793 + pending thanks Some bugs in the shadow package are closed in revision 4ea39732002aa50aa5372f0a2749c643975242c3 in branch 'master' by Christian Perrier The full diff can be seen at http://anonscm.debian.org/gitweb/?p=pkg-fonts/shadow.git;a=commitdiff;h=4ea3973 Commit message: Update French translations of programs messages and manpages. Done as an upstream patch, as of now and will be part of 4.2.1 Closes: #725793 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737803: chocolate-doom: FTBFS: race during parallel installation
Am Montag, den 05.05.2014, 23:15 -0700 schrieb Vincent Cheng: > Don't forget that the Debian Games team > has a sponsorship queue [1] that you can use if you're looking for a > sponsor within the team; I aim to regularly check the queue for > packages to sponsor. Alright, I have added my pending uploads there. - Fabian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#659878: Reasons for this bug to be RC are very vague
severity 659878 important thanks The rationale for setting this bug report as release critical is really vague for me. "breaks other software" hasn't been really explained in details : it "breaks" su for some specific uses of it, so it may fit the definition of important but certainly not the one of grave -- signature.asc Description: Digital signature
Bug#747389: atheme-services: New upstream version available (7.0.x)
Package: atheme-services Version: 6.0.11-1 Severity: normal Dear Maintainer, Upstream released a new major release a while ago, currently it's 7.0.7. Please consider packaging it in time for jessie so users can benefit from the new features. Thanks, Christoph -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.10.39 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747390: Homepage: URL borken
Package: atheme-services Version: 6.0.11-1 Severity: minor Dear Maintainer, The hostname provided in the Homepage: http://www.atheme.net/ information does not resolve. Please use http://atheme.net/atheme.html only. Thanks, Christoph -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.10.39 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747292: gdm3: Unable to login after last upgrade (version 3.8.4-7): fails to start a GNOME session
Hello, I reinstalled that package. # aptitude reinstall libpam-systemd […] Preparing to unpack .../libpam-systemd_204-10_amd64.deb ... Unpacking libpam-systemd:amd64 (204-10) over (204-10) ... Processing triggers for man-db (2.6.7.1-1) ... Paramétrage de libpam-systemd:amd64 (204-10) ... I’ll try to upgrade again gdm, and test it in a minute or two. # aptitude versions gdm3 libgdm1 Paquet gdm3 : i A 3.8.4-6 testing 500 p A 3.8.4-7 unstable500 Paquet gir1.2-gdm3 : i A 3.8.4-6 testing 500 p A 3.8.4-7 unstable500 Paquet libgdm1 : i A 3.8.4-6 testing 500 p A 3.8.4-7 unstable500 Otherwise, the gdm user has no shell. (seems sensible, right?) # cat /etc/passwd | grep gdm Debian-gdm:x:113:119:Gnome Display Manager:/var/lib/gdm3:/bin/false By the way, my user uses the /bin/zsh shell (not fancy to me :-). Here are various configuration files, which might be relevant? $ cat /etc/pam.d/common-session # # /etc/pam.d/common-session - session-related modules common to all services # # […] # here are the per-package modules (the "Primary" block) session [default=1] pam_permit.so # here's the fallback if no module succeeds session requisite pam_deny.so # prime the stack with a positive return value if there isn't one already; # this avoids us returning an error just because nothing sets a success code # since the modules above will each just jump around session requiredpam_permit.so # and here are more per-package modules (the "Additional" block) session requiredpam_unix.so session optionalpam_systemd.so session optionalpam_ck_connector.so nox11 # end of pam-auth-update config $ cat /etc/pam.d/gdm3 #%PAM-1.0 authrequisite pam_nologin.so authrequiredpam_succeed_if.so user != root quiet_success @include common-auth authoptionalpam_gnome_keyring.so @include common-account # SELinux needs to be the first session rule. This ensures that any # lingering context has been cleared. Without out this it is possible # that a module could execute code in the wrong domain. session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close session requiredpam_limits.so session requiredpam_env.so readenv=1 session requiredpam_env.so readenv=1 envfile=/etc/default/locale session requiredpam_loginuid.so @include common-session # SELinux needs to intervene at login time to ensure that the process # starts in the proper default security context. Only sessions which are # intended to run in the user's context should be run after this. session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so open session optionalpam_gnome_keyring.so auto_start @include common-password Thank you, Benjamin. Le 08/05/2014 09:11, Laurent Bigonville a écrit : > Le Thu, 8 May 2014 09:08:36 +0200, > Laurent Bigonville a écrit : > >> Le Wed, 07 May 2014 17:33:01 +0200, >> Benjamin Menant a écrit : >> >>> Well, I am not sure… It’s more or less a default Jessie >>> installation. I hope those following data will help. Please let me >>> know. >>> >>> >> [...] >> >> So apparently I see a session opened here so logind itself seems to >> work as expected. >> >> But looking closer in the logs you posted, I see: >> >> gdm3][4091]: pam_systemd(gdm3:session): Failed to create session: No >> such file or directory >> >> This is a bit puzzling me. Could you please try to reinstall the >> libpam-systemd package maybe. >> >> Also in the logs I see the following warning/error: >> >> The value for the SHELL variable was not found the /etc/shells file >> >> Are you using some fancy shell for your user? > > Oh correction it seems to complain about gdm user shell: > > May 6 13:10:38 ** pkexec[3298]: Debian-gdm: The value for the SHELL > variable was not found the /etc/shells file [USER=root] [TTY=unknown] > [CWD=/var/lib/gdm3] > [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight- helper > --set-brightness 16] > signature.asc Description: OpenPGP digital signature
Bug#740423: Ubuntu-GNOME has packaged Gitg 0.3.2 and its dependencies
You can check the Gitg 0.3.2 package from https://launchpad.net/~gnome3-team/+archive/gnome3-staging/+packages Available with all its the dependencies. Regards -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#596995: [Pkg-shadow-devel] Bug#596995: login: reset PATH in cowbuilder/pbuilder environment
Back to this fairly old issue Quoting Nicolas François (nicolas.franc...@centraliens.net): > Hello, > > On Wed, Sep 15, 2010 at 09:26:44PM +0200, Christoph Goehre wrote: > > > > according to my post on debian-devel[1], I've prospect the problem a > > little bit deeper. > > As I installed the old version of login (1:4.1.4.2-1), everything works > > great. My PATH looks like this: > > > > PATH is: /usr/lib/ccache:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin > > > > but with login 1:4.1.4.2+svn3283-1 /usr/lib/ccache is omitted. To except > > all failure by myself, I create a sid cowbuilder environment on another > > machine (i386) and end up with the same problem. > > > > [1] http://lists.debian.org/debian-devel/2010/09/msg00230.html > > Is this still a problem with current pbuilder / shadow packages? > > What tool is used? (su?, su -?, login?) > How can I reproduce it? > > Thank in advance, > -- > Nekral Christoph, can you give us a clue about ways to reproduce this problem...in case you still experience it (about 4 years after you reported it, sorry). Or do you think we can close the issue, as nobody else reported a similar issue since then? signature.asc Description: Digital signature
Bug#747391: Fix broken autopkgtest
Package: python-biopython Version: 1.63+dfsg-3 Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu ubuntu-patch utopic User: autopkgtest-de...@lists.alioth.debian.org Usertags: autopkgtest Hello, python-biopython's autopkgtest currently fails [1]: | adt-run [2014-05-07 22:27:05]: & apt0t-run-unit-test: [--- | cp: cannot stat '/usr/share/doc/python-biopython-doc/Tests': No such file or directory That's because the test does not actually depend on the biopython packages. After adding them, it fails because the test suite prints everything to stderr. Attached patch fixes both, the test succeeds now. Thanks for considering, Martin [1] http://ci.debian.net/data/unstable-amd64/packages/p/python-biopython/2014-05-07.log -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) diff -Nru python-biopython-1.63+dfsg/debian/changelog python-biopython-1.63+dfsg/debian/changelog --- python-biopython-1.63+dfsg/debian/changelog 2014-05-05 20:16:39.0 +0200 +++ python-biopython-1.63+dfsg/debian/changelog 2014-05-08 10:27:10.0 +0200 @@ -1,3 +1,10 @@ +python-biopython (1.63+dfsg-3ubuntu1) utopic; urgency=medium + + * Depend on our own packages in the autopkgtest and add missing +"allow-stderr" restriction. + + -- Martin Pitt Thu, 08 May 2014 09:50:56 +0200 + python-biopython (1.63+dfsg-3) unstable; urgency=medium * Set HOME=/tmp also in autopkgtest diff -Nru python-biopython-1.63+dfsg/debian/tests/control python-biopython-1.63+dfsg/debian/tests/control --- python-biopython-1.63+dfsg/debian/tests/control 2014-04-24 11:41:07.0 +0200 +++ python-biopython-1.63+dfsg/debian/tests/control 2014-05-08 10:18:30.0 +0200 @@ -1,2 +1,3 @@ Tests: run-unit-test -Depends: @builddeps@ +Depends: @, @builddeps@ +Restrictions: allow-stderr signature.asc Description: Digital signature
Bug#747183: icedove version
Hi LANG= apt-cache policy icedove icedove: Installed: 24.4.0-1 Candidate: 24.5.0-1~deb7u1 Version table: 24.5.0-1~deb7u1 0 500 http://security.debian.org/ stable/updates/main amd64 Packages *** 24.4.0-1 0 500 http://ftp.fr.debian.org/debian/ jessie/main amd64 Packages 100 /var/lib/dpkg/status The stable version is higher than testing version -- Jean-Luc
Bug#747392: gtk+3.0 has a cycle build-depency on itself
Package: src:gtk+3.0 Version: 3.12.1-1 gtk+3.0 buil-depends on gnome-icon-theme-symbolic, and gnome-icon-theme-symbolic depends on gnome-icon-theme, and then gnome-icon-theme depends on libgtk-3-bin. This will make it harder to bootstrap. Please consider break it. -- Yunqiang Su -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#586665: Where are in 2014, still have similar issue
I don't think that it is the same issue, because it appears last year for me. On debian stable i386, scanbuttond use scanimage and i have randomly segfault from scanimage. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747393: libsdformat2 and libsdformat1: error when trying to install together
Package: libsdformat1,libsdformat2 Version: libsdformat1/1.4.11-1 Version: libsdformat2/2.0.0-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-05-08 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package libboost-system1.54.0:amd64. (Reading database ... 10937 files and directories currently installed.) Preparing to unpack .../libboost-system1.54.0_1.54.0-5_amd64.deb ... Unpacking libboost-system1.54.0:amd64 (1.54.0-5) ... Selecting previously unselected package libboost-filesystem1.54.0:amd64. Preparing to unpack .../libboost-filesystem1.54.0_1.54.0-5_amd64.deb ... Unpacking libboost-filesystem1.54.0:amd64 (1.54.0-5) ... Selecting previously unselected package libboost-program-options1.54.0:amd64. Preparing to unpack .../libboost-program-options1.54.0_1.54.0-5_amd64.deb ... Unpacking libboost-program-options1.54.0:amd64 (1.54.0-5) ... Selecting previously unselected package libicu52:amd64. Preparing to unpack .../libicu52_52.1-3_amd64.deb ... Unpacking libicu52:amd64 (52.1-3) ... Selecting previously unselected package libboost-regex1.54.0:amd64. Preparing to unpack .../libboost-regex1.54.0_1.54.0-5_amd64.deb ... Unpacking libboost-regex1.54.0:amd64 (1.54.0-5) ... Selecting previously unselected package libboost-thread1.54.0:amd64. Preparing to unpack .../libboost-thread1.54.0_1.54.0-5_amd64.deb ... Unpacking libboost-thread1.54.0:amd64 (1.54.0-5) ... Selecting previously unselected package libtinyxml2.6.2:amd64. Preparing to unpack .../libtinyxml2.6.2_2.6.2-2_amd64.deb ... Unpacking libtinyxml2.6.2:amd64 (2.6.2-2) ... Selecting previously unselected package libconsole-bridge0.2:amd64. Preparing to unpack .../libconsole-bridge0.2_0.2.5-2_amd64.deb ... Unpacking libconsole-bridge0.2:amd64 (0.2.5-2) ... Selecting previously unselected package liburdfdom-model-state0.2:amd64. Preparing to unpack .../liburdfdom-model-state0.2_0.2.10+dfsg-1_amd64.deb ... Unpacking liburdfdom-model-state0.2:amd64 (0.2.10+dfsg-1) ... Selecting previously unselected package liburdfdom-model0.2:amd64. Preparing to unpack .../liburdfdom-model0.2_0.2.10+dfsg-1_amd64.deb ... Unpacking liburdfdom-model0.2:amd64 (0.2.10+dfsg-1) ... Selecting previously unselected package liburdfdom-sensor0.2:amd64. Preparing to unpack .../liburdfdom-sensor0.2_0.2.10+dfsg-1_amd64.deb ... Unpacking liburdfdom-sensor0.2:amd64 (0.2.10+dfsg-1) ... Selecting previously unselected package liburdfdom-world0.2:amd64. Preparing to unpack .../liburdfdom-world0.2_0.2.10+dfsg-1_amd64.deb ... Unpacking liburdfdom-world0.2:amd64 (0.2.10+dfsg-1) ... Selecting previously unselected package libsdformat1:amd64. Preparing to unpack .../libsdformat1_1.4.11-1_amd64.deb ... Unpacking libsdformat1:amd64 (1.4.11-1) ... Selecting previously unselected package liburdfdom-model-state0.3:amd64. Preparing to unpack .../liburdfdom-model-state0.3_0.3.0-1_amd64.deb ... Unpacking liburdfdom-model-state0.3:amd64 (0.3.0-1) ... Selecting previously unselected package liburdfdom-model0.3:amd64. Preparing to unpack .../liburdfdom-model0.3_0.3.0-1_amd64.deb ... Unpacking liburdfdom-model0.3:amd64 (0.3.0-1) ... Selecting previously unselected package liburdfdom-sensor0.3:amd64. Preparing to unpack .../liburdfdom-sensor0.3_0.3.0-1_amd64.deb ... Unpacking liburdfdom-sensor0.3:amd64 (0.3.0-1) ... Selecting previously unselected package liburdfdom-world0.3:amd64. Preparing to unpack .../liburdfdom-world0.3_0.3.0-1_amd64.deb ... Unpacking liburdfdom-world0.3:amd64 (0.3.0-1) ... Selecting previously unselected package libsdformat2:amd64. Preparing to unpack .../libsdformat2_2.0.0-2_amd64.deb ... Unpacking libsdformat2:amd64 (2.0.0-2) ... dpkg: error processing archive /var/cache/apt/archives/libsdformat2_2.0.0-2_amd64.deb (--unpack): trying to overwrite '/usr/share/sdformat/1.3/model.sdf', which is also in package libsdformat1:amd64 1.4.11-1 Errors were encountered while processing: /var/cache/apt/archives/libsdformat2_2.0.0-2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync):
Bug#747394: calendarserver: Problem with fresh installed Server when adding calendar
Package: calendarserver Version: 3.2+dfsg-4+deb7u1 Severity: important Hello I did a fresh installation of calendarserver. I use the Apple "Kalendar" (German) program on Mac OS 10.9.2 When I use the default calendar "calendar" I can create entries and there is no problem. In the error log ther is: [PooledMemCacheProtocol,client] [twext.web2.server#error] [Failure instance: Traceback: : [Errno 28] No space left on device: '/var/spool/caldavd/calendars/__uids__/d8/17/d817aaec-7d24-5b38-bc2f-6369da72cdd9/calendar' But everything works. I use a file as filesystem for /var/spool/caldavd with loop-device. That filesystem isn't full, so I ignore that error message. Now I create a second calendar with the program on Mac OS ... Before I can name that new calendar I get the message: (translated by me) Not allowed - 403 CalDAVAddCalendarQueableOperation Now the calendarserver is not usable anymore for me. Further error messages are 500 CalDAVAccountRefreshQueueableOperation The error.log says: 2014-05-08 10:13:04+0200 [-] [caldav-0] [PooledMemCacheProtocol,client] [twistedcaldav.method.mkcalendar#error] Attempt to create collection where resource exists: I hope you can reproduce this behavior. It prevents me from updating a Server from Debian 6 to Debian 7. The calendarserver-Version of Debian 6 (2.4.6) works fine! I can test every version which runs on Debian 7 (stable). So I couldn't test the new 5.2 in unstable, sorry. Jochen -- System Information: Debian Release: 7.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages calendarserver depends on: ii adduser3.113+nmu3 ii libc6 2.13-38+deb7u1 ii lsb-base 4.1+Debian8+deb7u1 ii memcached 1.4.13-0.2+deb7u1 ii python 2.7.3-4+deb7u1 ii python-dateutil1.5+dfsg-0.1 ii python-kerberos1.1+svn4895-1+b2 ii python-openssl 0.13-2+deb7u1 ii python-plist 1.8-1 ii python-pycalendar 2.0~svn188-1 ii python-pygresql1:4.0-3 ii python-pysqlite2 2.6.3-3 ii python-sqlparse0.1.4-1 ii python-twisted-conch 1:12.0.0-1 ii python-twisted-core12.0.0-1 ii python-twisted-mail12.0.0-1 ii python-twisted-web 12.0.0-1 ii python-twisted-words 12.0.0-1 ii python-xattr 0.6.4-2 ii python-zope.interface 3.6.1-3 ii ssl-cert 1.0.32 Versions of packages calendarserver recommends: ii python-ldap 2.4.10-1 ii python-pam 0.4.2-13 calendarserver suggests no packages. -- Configuration Files: /etc/caldavd/caldavd.plist changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747395: Repeated oops on S4 resume with i915 drm on 3.2.54-2 and 3.2.57-3
Package: linux-image-3.2.0-4-686-pae Version: 3.2.57-3 Severity: important Hello to the debian team again, this is Nick Barkas & John Barkas. Our second bug report is about 3.2 drm again but this one is on a 32 bit intel based system.The system is based on an ASRock P4i945GC mainboard (945GC chipset, socket 478) with Pentium 4 Northwood CPU. Every time the system resumes from S4 it complains about a "pipe B" which is supposed to be off but it is not. After the oops, the machine works but we cannot tell if it works at 100%. This old (by now) board was never really 100% compatible with Linux. The i915drm had serious i2c problems on older kernels (2.6.32) which resulted in corrupted DDC EDID and dmesg flooding... Every kernel we used nagged about the onboard VIA IDE PCIe ACPI DSDT code, but it worked fine despite the ACPI errors. The crappy/beta i915 is finally usable with GMA950 when running a 3.13.10 kernel. Please backport a newer i915 drm (from 3.13 for example) to 3.2. Mainboard DMI info: Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: P1.30 Release Date: 11/18/2009 Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: ASRock Product Name: P4i945GC Mainboard pci info: 00:00.0 Host bridge [0600]: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub [8086:2770] (rev 02) Subsystem: ASRock Incorporation Device [1849:2770] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: agpgart-intel 00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Device [1849:2772] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit- Address: Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: i915 02:00.0 IDE interface [0101]: VIA Technologies, Inc. VT6415 PATA IDE Host Controller [1106:0415] (prog-if 85 [Master SecO PriO]) Subsystem: ASRock Incorporation Device [1849:0415] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- ] ? warn_slowpath_common+0x68/0x79 [ 149.468806] [] ? assert_pipe+0x62/0x69 [i915] [ 149.468812] [] ? warn_slowpath_fmt+0x29/0x2d [ 149.468831] [] ? assert_pipe+0x62/0x69 [i915] [ 149.468849] [] ? intel_crtc_disable+0x39/0x60 [i915] [ 149.468857] [] ? drm_helper_disable_unused_functions+0xb0/0xd3 [drm_kms_helper] [ 149.468864] [] ? drm_helper_resume_force_mode+0xd5/0xdf [drm_kms_helper] [ 149.468874] [] ? i915_drm_thaw+0xb8/0xf7 [i915] [ 149.468885] [] ? i915_resume+0x35/0x47 [i915] [ 149.468891] [] ? pci_pm_restore+0x6b/0x7a [ 149.468896] [] ? pm_op+0xe4/0x108 [ 149.468900] [] ? device_resume+0x78/0xc1 [ 149.468904] [] ? async_resume+0x13/0x33 [ 149.468908] [] ? async_run_entry_fn+0x8d/0x125 [ 149.468913] [] ? process_one_work+0x12a/0x209 [ 149.468917] [] ? worker_thread+0xa9/0x122 [ 149.468921] [] ? manage_workers.isra.25+0x13d/0x13d [ 149.468925] [] ? kthread+0x63/0x68 [ 149.468929] [] ? kthread_worker_fn+0x101/0x101 [ 149.468934] [] ? kernel_thread_helper+0x6/0x10 [ 149.468937] ---[ end trace 6f38b2687002c058 ]--- onboard VIA PATA errors to whom it may concern : [1.116151] libata version 3.00 loaded. [1.116959] pata_via :02:00.0: version 0.3.4 [1.117298] ACPI Error: [IDEP] Namespace lookup failure, AE_NOT_FOUND (20131115/psargs-359) [1.117311] ACPI Error: Method parse/execution failed [\_SB_.PCI0.P0P6.VT00.GTM_] (Node f744e6e0), AE_NOT_FOUND (20131115/psparse-536) [1.117329] ACPI Error: Method parse/execution failed [\_SB_.PCI0.P0P6.VT00.CHN0._GTM] (Node f744dda0), AE_NOT_FOUND (20131115/psparse-536) [1.124520] scsi0 : pata_via [1.134252] scsi1 : pata_via [1.134406] ata1: PATA max UDMA/133 cmd 0xec00 ctl 0xe880 bmdma 0xe400 irq 18 [1.134414] ata2: PATA max UDMA/133 cmd 0xe800 ctl 0xe480 bmdma 0xe408 irq 18 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#502214: vnc4server asks for password even when -SecurityTypes None used
Thanks. I'll try to add this one.
Inguza Technology AB
Sent from a phone
Den 5 maj 2014 15:30 skrev "Beat Vontobel" :
> Hi Ola, hi Markus,
>
> just found this bug report after hitting the same problem and writing
> a patch.
>
> > Then my conclusion is that this is a wishlist bug. Rather easy to
> > fix, but still not something that is stated that it should work.
>
> Actually, I agree more with Markus and do not think it's just
> wishlist, but a real bug:
>
> As Markus says, vnc4server's man page clearly states that all unknown
> options are passed on to Xvnc4 and references that man page, which
> documents both -SecurityTypes as well as -rfbauth (which produces the
> same bug) as options, both unknown to vnc4server.
>
> So they should be passed on and work correctly (otherwise there's no
> way of running a passwordless server, as e.g. helpful if you only
> allow connections through an ssh tunnel and authenticate there).
>
> Unfortunately, an -rfbauth is hardcoded into vnc4server (without being
> mentioned in the docs). This conflicts with both -SecurityTypes as
> well as the manual use of -rfbauth to vnc4server.
>
> > If you can provide a patch I will include that one in next upload.
>
> I had to fix it for me anyway. So here is one. Not really tested. :)
> It just worked for me. The idea is...
>
> * to work exactly as before without any of the two options.
>
> * If -rfbauth is given use the explicitly requested file instead
>of the default ~/.vnc/passwd.
>
> * If -SecurityTypes None is given ignore -rfbauth completely (both
>the default and a manual option).
>
> See below.
>
> Cheers,
> Beat
>
>
>
> --- vnc4server.orig 2012-02-05 20:01:12.0 +
> +++ vnc4server 2014-05-05 12:55:30.117011996 +
> @@ -122,6 +122,7 @@
> "-help",0,"-h",0,"--help",0,
> "-clean",0, "-fp",1,
> "-alwaysshared",0, "-nevershared",0,
> + "-rfbauth",1,"-SecurityTypes",1,
> "-httpport",1,"-basehttpport",1);
>
> &Usage() if ($opt{'-help'} || $opt{'-h'} || $opt{'--help'});
> @@ -186,12 +187,20 @@
>
> # Make sure the user has a password.
>
> -($z,$z,$mode) = stat("$vncUserDir/passwd");
> -if (!(-e "$vncUserDir/passwd") || ($mode & 077)) {
> -warn "\nYou will require a password to access your desktops.\n\n";
> -system("vncpasswd $vncUserDir/passwd");
> -if (($? >> 8) != 0) {
> - exit 1;
> +unless ($opt{'-SecurityTypes'} eq "None") {
> +if ($opt{'-rfbauth'}) {
> +$rfbAuthFile = $opt{'-rfbauth'};
> +} else {
> +$rfbAuthFile = "$vncUserDir/passwd";
> +}
> +
> +($z,$z,$mode) = stat($rfbAuthFile);
> +if (!(-e $rfbAuthFile) || ($mode & 077)) {
> +warn "\nYou will require a password to access your desktops.\n\n";
> +system("vncpasswd " . "edString($rfbAuthFile));
> +if (($? >> 8) != 0) {
> +exit 1;
> +}
> }
> }
>
> @@ -257,7 +266,8 @@
> $cmd .= " -depth $depth" if ($depth);
> $cmd .= " -pixelformat $pixelformat" if ($pixelformat);
> $cmd .= " -rfbwait 3";
> -$cmd .= " -rfbauth $vncUserDir/passwd";
> +$cmd .= " -rfbauth " . "edString($rfbAuthFile) if ($rfbAuthFile);
> +$cmd .= " -SecurityTypes $opt{'-SecurityTypes'}" if
> ($opt{'-SecurityTypes'});
> $cmd .= " -rfbport $vncPort";
> $cmd .= " -pn";
>
>
Bug#747396: congruity: Error in mime type
Package: congruity Version: 17-1 Severity: normal Dear Maintainer, I had this following error while updating congruity : Processing triggers for mime-support (3.55) ... Warning: mailcap line not starting with a media type in congruity Problematic line: application/application/x-easyzapper-hex; congruity '%s' There's a duplicate "application/" for the media type in the file /usr/lib/mime/packages/congruity -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages congruity depends on: ii python [python-ctypes] 2.7.5-5 ii python-libconcord 1.1-1 ii python-suds 0.4.1-13 ii python-wxgtk2.8 2.8.12.1+dfsg2-1 ii shared-mime-info1.2-1 congruity recommends no packages. congruity suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747392: gtk+3.0 has a cycle build-depency on itself
On 08/05/14 10:30, Yunqiang Su wrote: > Package: src:gtk+3.0 > Version: 3.12.1-1 > > gtk+3.0 buil-depends on gnome-icon-theme-symbolic, > and gnome-icon-theme-symbolic depends on gnome-icon-theme, > and then gnome-icon-theme depends on libgtk-3-bin. > > This will make it harder to bootstrap. > Please consider break it. Hard to break it unless we disable the test suite, but you can do that when bootstrapping. Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#734609: Pending fixes for bugs in the shadow package
tag 734609 + pending thanks Some bugs in the shadow package are closed in revision dedf96dd6f17b4e953b2befbf2db33430ea9abc8 in branch 'master' by Christian Perrier The full diff can be seen at http://anonscm.debian.org/gitweb/?p=pkg-fonts/shadow.git;a=commitdiff;h=dedf96d Commit message: Fix some typos and errors in German translation of manpages. Done as an upstream patch, as of now and will be part of 4.2.1 Closes: #734609 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747397: policykit-1 forces using systemd and may break systems with sysvinit after update
Package: policykit-1 Version: 0.105-5 Severity: critical Justification: makes unrelated software on the system (or the whole system) break Hi, I have just found that new version of policykit-1 forces using systemd on users systems: $ sudo apt-get install policykit-1 -V --no-install-recommends Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libcryptsetup4 (1.6.4-4) libpam-systemd (204-10) systemd (204-10) systemd-sysv (204-10) Suggested packages: systemd-ui (3-2) The following packages will be REMOVED: sysvinit-core (2.88dsf-53) The following NEW packages will be installed: libcryptsetup4 (1.6.4-4) libpam-systemd (204-10) systemd (204-10) systemd-sysv (204-10) The following packages will be upgraded: policykit-1 (0.105-4 => 0.105-5) 1 upgraded, 4 newly installed, 1 to remove and 1 not upgraded. Need to get 1368 kB of archives. After this operation, 5175 kB of additional disk space will be used. Do you want to continue? [Y/n] It may be normal to use systemd by default on new Debian installations, but why users with already installed Debian should be forced to use it without alternatives? Have you checked what this serious change will not break users systems after updating from Wheezy to Jessie? Next, I have checked what I will lose if I will remove this package: $ sudo apt-get purge policykit-1 -V --no-install-recommends Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: aptdaemon* (1.1.1-3) colord* (1.0.6-1) policykit-1* (0.105-5) polkit-kde-1* (0.99.1-1) 0 upgraded, 0 newly installed, 4 to remove and 1 not upgraded. After this operation, 4279 kB disk space will be freed. Do you want to continue? [Y/n] And it looks that policykit-1 cannot be safely removed without losing convenient work in KDE. Please solve this issue somehow. Best regards, Boris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747392: gtk+3.0 has a cycle build-depency on itself
On 08/05/14 10:41, Emilio Pozuelo Monfort wrote: > On 08/05/14 10:30, Yunqiang Su wrote: >> Package: src:gtk+3.0 >> Version: 3.12.1-1 >> >> gtk+3.0 buil-depends on gnome-icon-theme-symbolic, >> and gnome-icon-theme-symbolic depends on gnome-icon-theme, >> and then gnome-icon-theme depends on libgtk-3-bin. >> >> This will make it harder to bootstrap. >> Please consider break it. > > Hard to break it unless we disable the test suite, but you can do that when > bootstrapping. Perhaps we can disable the test suite when on stage1. Would that work? Regards, Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747376: Requesting debian-lts-{changes,announce} mailing lists
On Thu, May 08, 2014 at 08:27:33AM +0200, Alexander Wirt wrote: > On Thu, 08 May 2014, Matthew Palmer wrote: > > Those changes lists are usually without any manual interaction. Unless > someone objects I would create this list similiar to the other -changes > lists. Ack, only dak should be able to send to this list. > > Post policy: Moderated. Pre-approval should be allowed for any message > > signed by a key in the Debian keyring. Initial moderators can be > > myself (mpal...@debian.org) and Moritz Muehlenhoff (j...@debian.org); > > we'll add more people as we get up to speed. > Our moderation method currently allows either moderation via keyring (bi it > developers/dms or a custom keyring) or classic moderation, but not a > combination of both. I/we can implement such a combination, but that needs > testing and time. If you want this list soon, I would recommend to stick to > one of the traditional methods (Moderators or a keyring). Ack, if only people in the debian.org/DM keyring can send this list we don't need moderation to keep the list spam free. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#730692: Pending fixes for bugs in the shadow package
tag 730692 + pending thanks Some bugs in the shadow package are closed in revision 11e8de1be1afb4171929f82756f8d348425c6d28 in branch 'master' by Christian Perrier The full diff can be seen at http://anonscm.debian.org/gitweb/?p=pkg-fonts/shadow.git;a=commitdiff;h=11e8de1 Commit message: Fix a typo in su manpage. Done as an upstream patch, as of now and will be part of 4.2.1 Closes: #730692 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747054: FTBFS: package javax.servlet.http does not exist
Hi, I've rebuilt eclipse package in current sid using pbuilder and didn't encounter any error. Can someone please confirm this bug is still relevant? Regards, Jakub -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747398: logcheck: make (almost) all cmdline flags settable in the config file
Package: logcheck
Version: 1.3.13
Severity: wishlist
i want to run multiple instances of logcheck on a syslog host, each configured
slightly differently (configuration for each instance lives in
/etc/${LC_INST}/, and the stats live in /var/lib(${LC_INST}).
i can do this with something like:
/usr/sbin/logcheck \
-c /etc/${LC_INST}/logcheck.conf \
-L /etc/${LC_INST}/logcheck.logfiles \
-S /var/lib/${LC_INST}
however, i fail to see why i cannot provide the stats-dir (as given with the
'-S' flag) and the logfiles-file ('-L') in the instance-specific config-file
('-c'), esp. since i *can* set the RULEDIR ('-r').
actually, I think one should be able to use set all cmdline flags in the
configfile (maybe with the exception of the '-c' flag).
most likely all this is already possible (looking at the source-code of
/usr/sbin/logcheck I see that it simply sources CONFIGFILE) but that's nowhere
documented.
fgmasdr
IOhannes
-- System Information:
Debian Release: 6.0.9
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages logcheck depends on:
ii adduser 3.112+nmu2 add and remove users and groups
ii cron 3.0pl1-116 process scheduling daemon
ii exim4-daemon-light [mail 4.72-6+squeeze3 lightweight Exim MTA (v4) daemon
ii lockfile-progs 0.1.15+squeeze1 Programs for locking and unlocking
ii logtail 1.3.13 Print log file lines that have not
ii mime-construct 1.11construct/send MIME messages from
ii syslog-ng [system-log-da 3.1.3-3 Next generation logging daemon
Versions of packages logcheck recommends:
ii logcheck-database 1.3.13 database of system log rules for t
Versions of packages logcheck suggests:
pn syslog-summary (no description available)
-- Configuration Files:
/etc/cron.d/logcheck changed [not included]
/etc/logcheck/logcheck.conf changed [not included]
/etc/logcheck/logcheck.logfiles changed [not included]
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747142: caused by DEB_BUILD_OPTS=parallel=6
reopen 747142 retitle 747142 fails with DEB_BUILD_OPTIONS=parallel= kthxbye On Thu, May 08, 2014 at 07:21:20AM +, Debian Bug Tracking System wrote: > From the Problems file: > > w) If you build out of a kernel git repositoty, and if the >repository is not in a clean annotated or signed tagged >state and LOCALVERSION= is not specified. then the script >scripts/setlocalversion will append a plus sign to the >version. This creates a problem with the packaging tools. > >Solutions: >+ Create a LOCALVERSION variable in the kernel configuration >+ export a shell LOCALVERSION variable >+ create a signed or annotated tag. I'm afraid this doesn't help, the build failure happens regardless whether the tree is exactly at a tag or not (ie, whether there is a plus or not). Setting LOCALVERSION makes no difference as well. On the other hand, I just found out that the failure was caused by the following environment variable: DEB_BUILD_OPTIONS=parallel=6 Unsetting it allows the build to succeed. It's a new regression, caused by make 4.0. -- Gnome 3, Windows 8, Slashdot Beta, now Firefox Ribbon^WAustralis. WTF is going on with replacing usable interfaces with tabletized ones? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737515: dictionaries-common-dev: dh_aspell
On Fri, Apr 11, 2014 at 11:41:28AM +0200, Agustin Martin wrote:
> On Thu, Apr 10, 2014 at 05:50:15PM +0200, Andreas Beckmann wrote:
> > On 2014-04-10 17:40, Agustin Martin wrote:
> > > However, postrm cannot rely on anything in dependencies, there is no
> > > warranty on removal ordering. So, script is not available and not run if
> > > dictionaries-common is removed first (which can happen) and those dirs are
> > > left behind. This is something I am trying to fix in new -dev debhelper
> > > snippets allowing for explicit removal of those dirs if empty.
> >
> > can't you do this cleanup already from somedict.postrm remove (instead
> > of somedict.postrm purge)?
>
> It is already done at postrm removal stage. However, I now notice that when
> the removal script in first snippet is run, even if there is a single
> installed dict, /var/lib/{a,i}spell still has some contents that will be
> removed later by the second snippet, and thus the dir is not removed. I have
> to think about reversing debhelper snippets ordering.
Hi,
I uploaded new dictionaries-common-dev with some fixes for the last issues
found and a number of updated dictionaries using that version. They have
reached testing without further bug reports or piuparts complaints once the
time delay is passed, so I hope there are no more big problems with the
other aspects of the implementation (none of them use aspell-simple).
Also, Ubuntu seems to have unlocked the Debian->Ubuntu migration path and I
see no related bug reports there, additional good news.
On Thu, Mar 27, 2014 at 11:20:38PM +0100, Tobias Frost wrote:
> Hallo Agustin,
>
> Just an idea: Maybe a sample package would be helpful as a reference? (I
> can prepare one after my vacation)
Better if we have one, thanks. Please make sure to use at least
dictionaries-common-dev 1.23.2 to get the most recent snippets.
Regards,
--
Agustin
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747399: jscoverage: discontinued in favor of JSCover
Package: jscoverage Severity: normal Dear Maintainer, according with Homepage: Note: Any future development of the JSCoverage code base will likely occur in the new JSCover project on GitHub, which reuses a substantial amount of JSCoverage code and aims for a high degree of backward compatibility with JSCoverage. JSCoverage itself is unlikely to have any further releases. http://siliconforks.com/jscoverage/ You should consider to remove this package from archive. Another intersting project: https://github.com/fishbar/jscoverage Regards, L. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#745402: fuse-emulator: Better support for ROM in Debian opense-basic package
On Wed, May 07, 2014 at 06:20:13PM +0200, Santiago Vila wrote: > Well, the problem is that there is not any machine for which the > default rom is opense.rom. [...] > Maybe a new machine for which this rom is the default, even if it's > identical in hardware to the classical 48K Spectrum. At risk of repeating myself, the problem is that opense.rom can be used in at least seven of the machines supported by Fuse, so I cannot just add "Spectrum 48 + OpenSE" to the list. To make things more complex, it's also possible to mix opense.rom and the original Spectrum ROMs in the 128k machines, as the OpenSE documentation explains. > > > While we are at it, it would be wonderful if the tape saving > > > routines from this ROM would work in accelerated mode as it > > > happens in the classical 48.rom. > > > > Ok, it's only the saving routines that are affected, right? > > I have not done extensive tests, sorry. I can try to take a look at that. Berto -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#729436: [libc6-dev] strcasecmp declared twice
tags 729436 fixed-upstream thanks On 05/05/2014 05:53 PM, Aurelien Jarno wrote: > reassign 729436 manpages-dev > retitle 729436 manpages-dev: please explain why strcasecmp(3) is defined in > both and > thanks > > > On Tue, Nov 12, 2013 at 10:26:56PM +0200, Török Edwin wrote: >> Package: libc6-dev >> Version: 2.17-93 >> Severity: normal >> >> --- Please enter the report below this line. --- >> >> According to strcasecmp(3) and strcasecmp(3p) the function strcasecmp should >> be declared in strings.h. >> >> However it is actually declared both in string.h and strings.h: >> /usr/include/string.h:extern int strcasecmp (const char *__s1, const char >> *__s2) >> /usr/include/string.h:extern int strcasecmp_l (const char *__s1, const char >> *__s2, >> /usr/include/strings.h:extern int strcasecmp (const char *__s1, const char >> *__s2) >> /usr/include/strings.h:extern int strcasecmp_l (const char *__s1, const char >> *__s2, __locale_t __loc) >> >> If the declaration in string.h is a typo, please remove it. > > This is not a typo, but there for historical reasons. The strcasecmp() > and strncasecmp() functions first appeared in 4.4BSD and have been > introduced the same way in the GNU libc. Their prototypes existed > previously in before they were moved to for > IEEE Std 1003.1-2001 (POSIX.1) compliance, as is supposed to > be for ISO C functions, and strcasecmp() is not an ISO C function. The > prototype in has been kept for compatibility reasons. > >> Otherwise please update the manpage to mention that on Linux the function is >> actually declared in both string.h and strings.h, and you should check >> yourself that you included strings.h because you won't get any warning from >> the compiler about implicit declarations. >> > > I am therefore reassigning this bug to the manpages-dev package to > update the corresponding manpage. Fair enough. Upstream, I have added the following text under NOTES: The strcasecmp() and strncasecmp() functions first appeared in 4.4BSD, where they were declared in . Thus, for reasons of historical compatibility, the glibc header file also declares these functions, if the _DEFAULT_SOURCE (or, in glibc 2.19 and earlier, _BSD_SOURCE) feature test macro is defined. Okay? Thanks, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747133: tmux: window-status-format, ## broken
Hi Joerg, Thank you for the report. This is already fixed upstream: http://sf.net/p/tmux/tmux-code/ci/8880bdb67c9d939ec53506d05f5ce1d75be10c97/ Unfortunately I missed it during my last cherry-picking sweep for 1.9-4, so this will be for 1.9-5. I'm away from my key right now and will be for a few days still, so expect an upload to unstable next week. Cheers, -- Romain Francoise http://people.debian.org/~rfrancoise/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#634259: #634259 - gnome-session: stop-multiple-users dialog fails to clear screen
On Wed, May 07, 2014 at 01:59:20PM +0100, althaser wrote: > Hey Adam, > > this is an old bug. > > Could you please still reproduce this issue with newer gnome-session > version like 3.4.2.1-4 or 3.8.4-3 ? I'm afraid I don't use Gnome[3] anymore, and installing it to test would take too much work because of hard-dependency on systemd gnome in unstable already has. Installing a fresh virtual machine would take quite a bit of time, too, so I'm sorry but I can't help test this bug right now. If I recall correctly, reproducing it back in 2011 (on Gnome 2) was a matter of trying to shutdown Gnome over 20ish times, with policykit forbidding the shutdown due to it believing there is another user logged on¹. Thus, the bug took quite an effort to reproduce. With the extent of changes Gnome underwent since then, I believe this report can be dropped unless someone else can test it. ¹ Those days, policykit had a race that _sometimes_ caused bogus failures if you had a root shell in a terminal in the session that was being torn down. Of course, you can force a legitimate failure by ssh-ing in from another machine, ie, having an actual other user. -- Gnome 3, Windows 8, Slashdot Beta, now Firefox Ribbon^WAustralis. WTF is going on with replacing usable interfaces with tabletized ones? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#745307: Re-assigning to OCamlgraph
On Wed, May 07, 2014 at 08:51:48PM +0100, Peter Michael Green wrote: > >This bug is due to an API change appeared in > >OCamlgraph 1.8.4 and then reverted > >back in 1.8.5. OCamlgraph 1.8.3 (present > >testing's version) is not affected. > Am I correct in thinking that means that the binnmus for dose3 should be > given back? If this means whether dose3 should be rebuild against ocamlgraph 1.8.5: yes, please ! -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747100: bug#17428: Bug#747100: emacs23: Insecure use of temporary files in included lisp libraries/packages
These issues have now had several CVE identifiers associated with them, for future tracking: http://www.openwall.com/lists/oss-security/2014/03/14/5 Steve -- http://www.steve.org.uk/
Bug#747100: bug#17428: Bug#747100: emacs23: Insecure use of temporary files in included lisp libraries/packages
Clearly I'm an idiot, the correct link is this: http://www.openwall.com/lists/oss-security/2014/05/07/7 Steve -- http://www.steve.org.uk/
Bug#744099: Not grave!
How this bug can be considered GRAVE? Read here: https://www.debian.org/Bugs/Developer#severities Marking this as grave is preventing the version 34.0.1847.132-1 migrating to testing, thus many people cannot install the newer version due to #746034. And how this bug is blocking #746034? They are completely unrelated, IMHO. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747376: Support for debian-lts mailing lists
Hello I wish to add my support for the creation of these lists, to allow the Debian LTS project to operate as smoothly as possible. Kind regards, Stephen Harker -- All postal correspondence to: The Positive Internet Company, 24 Ganton Street, London. W1F 7QY *Follow us on Twitter* @posipeople The Positive Internet Company Limited is registered in England and Wales. Registered company number: 3673639. VAT no: 726 7072 28. Registered office: Northside House, Mount Pleasant, Barnet, Herts, EN4 9EE. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747400: bash: Vcs-Bzr is out of date
Source: bash Version: 4.3-7 Severity: minor bash’s debian/control lists Vcs-Bzr: http://bazaar.launchpad.net/~doko/+junk/pkg-bash-debian However, this Bazaar repository doesn’t have any versions newer than 4.2+dfsg-1. Anders -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#690531: Help needed: Porting IRAF to MIPS
I will test it on both and have a symbolic link in the package for mips. The package is also probably not released as Debian package (except there is a demand to have this available for other programs than IRAF), but as part of IRAF. Best Ole On 08.05.2014 11:31, Thomas Bogendoerfer wrote: > On Thu, May 08, 2014 at 02:07:45AM +0200, David Kuehling wrote: >> Index: zsvjmp/zsvjmp-mipsel.s > > why only mipsel ? The code should look the same for big endian MIPS... > > Thomas. > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747401: RM: jscoverage -- RoQA; abandoned upstream; FTBFS; not in stable; orphaned;
Package: ftp.debian.org Severity: normal According with Homepage: Note: Any future development of the JSCoverage code base will likely occur in the new JSCover project on GitHub, which reuses a substantial amount of JSCoverage code and aims for a high degree of backward compatibility with JSCoverage. JSCoverage itself is unlikely to have any further releases. http://siliconforks.com/jscoverage/ JSConv: https://github.com/tntim96/JSCover Another intersting project: https://github.com/fishbar/jscoverage Regards, Leo. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#745605: apache2: ignores AddDefaultCharset
Stefan, can you reproduce this? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#746411: linux-image-3.2.0-4-amd64: regression: suspend/resume not working after update
Jens Thiele writes: > Ben Hutchings writes: > >> How is it 'not working'? > > didn't have time to inspect the details yet did some more tests - it doesn't matter wether i am on power or battery - I have a reproducible crash on every second resume (first resume works / second crashes without any output :( ) - tried to debug using netconsole, but unfortunately i don't get any netconsole output on the second resume - unfortunately i didn't find a linux-image-3.2.0-4-amd64_3.2.54-2.deb anymore, but using linux-image-3.2.0-4-amd64_3.2.46-1+deb7u1_amd64.deb from debian security suspend/resume works jens pgp9SY59QRFT9.pgp Description: PGP signature
Bug#746396: grub-common: Add support for NVMe devices in grub-mkdevicemap
Control: tag -1 pending
On Tue, Apr 29, 2014 at 05:43:44PM +0100, Dimitri John Ledkov wrote:
> Whilst legacy grub-mkdevicemap is still in use, I have noticed that it
> doesn't have support for NVMe devices. I've added the device pattern,
> for grub-mkdevicemap to probe NVMe devices following other similar
> devices. I've tested it using qemu-system, booted with UEFI edk2
> firmware and an NVMe device, here are sample instructions:
>
> cd `mktemp -d`
> cp /usr/share/ovmf/OVMF.fd .
> qemu-system-x86_64 -pflash OVMF.fd -m 1024 -drive
> file=nvme.img,if=none,id=D22 -device nvme,drive=D22,serial=1234 --enable-kvm
> -ctrl-grab -cdrom trusty-desktop-amd64.iso
>
> With the attached patch grub-mkdevicemap produces result for the nvme
> drive. Patch was created on top of locally generated
> `patched-experimental` branch.
Thanks, this looks good. I added this further patch so that other tools
can deal with partitions on NVMe devices properly:
diff --git a/grub-core/osdep/linux/getroot.c b/grub-core/osdep/linux/getroot.c
index 6788e39..f97f3a6 100644
--- a/grub-core/osdep/linux/getroot.c
+++ b/grub-core/osdep/linux/getroot.c
@@ -896,6 +896,20 @@ grub_util_part_to_disk (const char *os_dev, struct stat
*st,
*pp = '\0';
return path;
}
+
+ /* If this is an NVMe device. */
+ if (strncmp ("nvme", p, sizeof ("nvme") - 1) == 0)
+ {
+ /* /dev/nvme[0-9]+n[0-9]+(p[0-9]+)? */
+ p = strchr (p, 'p');
+ if (p)
+ {
+ *is_part = 1;
+ *p = '\0';
+ }
+
+ return path;
+ }
}
return path;
--
Colin Watson [cjwat...@debian.org]
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747229: (no subject)
Attached is a patch-set for the debian/unstable branch. They require for
the branch to be rebased to upstream version 0.27 first (bzr rev 221).
The patches update the changelog and bump the package version to 0.27-1,
split the package into two sub-packages and exclude the Ubuntu-specific
scripts.
Let me know if there's anything else I can do to move this forward.
...Juerg
>From d1d1d82956d9541eb1e20688c179bfbbe0e2e0a3 Mon Sep 17 00:00:00 2001
From: Juerg Haefliger
Date: Wed, 7 May 2014 14:33:13 +0200
Subject: [PATCH 1/3] Add changelog entry for new version 0.27-1
---
debian/changelog | 6 ++
1 file changed, 6 insertions(+)
diff --git a/debian/changelog b/debian/changelog
index 4cb9330..95a68bd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+cloud-utils (0.27-1) unstable; urgency=low
+
+ * Rebase to upstream version 0.27
+
+ -- Juerg Haefliger Wed, 07 May 2014 14:32:13 +0200
+
cloud-utils (0.26-2) unstable; urgency=low
* Fixes "trap cleanup EXIT" in growpart: replaces "EXIT" by 0, as it
--
1.8.3.2
>From da6a69571e2791a6117c915bba5552a898f3e7b1 Mon Sep 17 00:00:00 2001
From: Juerg Haefliger
Date: Wed, 7 May 2014 16:28:29 +0200
Subject: [PATCH 2/3] Refresh patch against rebased source
---
debian/patches/do-not-use-EXIT-when-trapping.patch | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/debian/patches/do-not-use-EXIT-when-trapping.patch b/debian/patches/do-not-use-EXIT-when-trapping.patch
index d8e6c9f..fc31af7 100644
--- a/debian/patches/do-not-use-EXIT-when-trapping.patch
+++ b/debian/patches/do-not-use-EXIT-when-trapping.patch
@@ -4,14 +4,14 @@ Author: Thomas Goirand
Forwarded: not-needed
Last-Update: 2013-06-11
cloud-utils-0.26.orig/bin/growpart
-+++ cloud-utils-0.26/bin/growpart
-@@ -109,7 +109,7 @@ done
- [ "${part#*[!0-9]}" = "${part}" ] || fail "partition-number must be a number"
+--- a/bin/growpart
b/bin/growpart
+@@ -569,7 +569,7 @@
+ debug 1 "update-partition set to $PT_UPDATE"
mktemp_d && TEMP_D="${_RET}" || fail "failed to make temp dir"
-trap cleanup EXIT
+trap cleanup 0
- change_out=${TEMP_D}/change.out
- dump_out=${TEMP_D}/dump.out
+ # get the ID of the first partition to determine if it's MBR or GPT
+ id=$(sfdisk --id --force "${DISK}" 1 2>/dev/null) ||
--
1.8.3.2
>From e54b2468122528660e37d77cf0f81155bc612f66 Mon Sep 17 00:00:00 2001
From: Juerg Haefliger
Date: Thu, 8 May 2014 09:51:55 +0200
Subject: [PATCH 3/3] Split the package into two sub-packages
The cloud-utils scripts have a lot of dependencies some of which are
undesirable for guest images (size matters). Putting the guest tools
(primarily growpart) into its own sub-package significantly reduces the
dependencies pulled into a guest image. All the other tools go into
another sub-package.
And this commit also removes the following Ubuntu-specific scripts
from the package:
- cloud-publish-ubuntu
- ubuntu-cloudimg-query
- ubuntu-ec2-run
---
debian/changelog | 2 ++
debian/cloud-utils-guest.install | 3 +++
debian/cloud-utils-image.install | 11 +
debian/cloud-utils-image.links | 8 +++
debian/cloud-utils.links | 8 ---
debian/control | 52
6 files changed, 56 insertions(+), 28 deletions(-)
create mode 100644 debian/cloud-utils-guest.install
create mode 100644 debian/cloud-utils-image.install
create mode 100644 debian/cloud-utils-image.links
delete mode 100644 debian/cloud-utils.links
diff --git a/debian/changelog b/debian/changelog
index 95a68bd..d6ae3a8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,8 @@
cloud-utils (0.27-1) unstable; urgency=low
* Rebase to upstream version 0.27
+ * Split the package into two sub-packages
+ * Remove Ubuntu-specific scripts
-- Juerg Haefliger Wed, 07 May 2014 14:32:13 +0200
diff --git a/debian/cloud-utils-guest.install b/debian/cloud-utils-guest.install
new file mode 100644
index 000..ecc8e2c
--- /dev/null
+++ b/debian/cloud-utils-guest.install
@@ -0,0 +1,3 @@
+usr/bin/ec2metadata
+usr/bin/growpart
+usr/share/man/*/growpart*
diff --git a/debian/cloud-utils-image.install b/debian/cloud-utils-image.install
new file mode 100644
index 000..1438807
--- /dev/null
+++ b/debian/cloud-utils-image.install
@@ -0,0 +1,11 @@
+usr/bin/cloud-localds
+usr/bin/cloud-publish-image
+usr/bin/cloud-publish-tarball
+usr/bin/cloud-run-instances
+usr/bin/resize-part-image
+usr/bin/write-mime-multipart
+usr/share/man/*/cloud-publish-image.*
+usr/share/man/*/cloud-publish-tarball.*
+usr/share/man/*/cloud-run-instances.*
+usr/share/man/*/resize-part-image.*
+usr/share/man/*/write-mime-multipart.*
diff --git a/debian/cloud-utils-image.links b/debian/cloud-utils-image.links
new file mode 100644
index 000..dd6b34f
--- /dev/null
+++ b/debian/cloud-utils-image.links
@@ -0,0 +1,8 @@
+usr/bin/cloud-publish-tarball usr/bin/uec-publish-tarball
+usr/bin/cloud-publish-image
Bug#747402: missing license in debian/copyright
Package: libguestfs Version: 1:1.26.1-3 Severity: serious User: alteh...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks Dear Maintainer, please add the missing licenses of: gnulib/* to debian/copyright. Thanks! Thorsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#696772: Fwd: #696772 - gnome-settings-daemon: Brightness won't reduce with shortcut, and increases.
just for the record -- Forwarded message -- From: bugs Date: 7 May 2014 16:48 Subject: Re: #696772 - gnome-settings-daemon: Brightness won't reduce with shortcut, and increases. To: althaser The problem has gone away completely since gnome 3.8, when I upgraded to Jessie. Thanks, Zack
Bug#747403: ITP: python-phonenumbers -- phonenumbers Python Library
Package: wnpp Serverity: wishlist Owner: Dr. Torge Szczepanek Package name: python-phonenumbers Version : 6.0.0a Upstream Author : David Drysdale URL : https://github.com/daviddrysdale/python-phonenumbers License : Apache-2.0 Programming Lang: Python Description : phonenumbers Python Library This is a Python port of libphonenumber, originally from http://code.google.com/p/libphonenumber/. It supports Python 2.5-2.7 and Python 3.x (in the same codebase, with no 2to3 conversion needed). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#745842: Review package description for liferea (Bug #745842)
David Smith wrote: > Please review this updated package description for the package liferea. You left out the synopsis line: Description: feed aggregator for GNOME This makes me wonder exactly how GNOME-specific it is, but otherwise looks good. > Liferea is a linux feed reader that brings together all of the content > from your favorite news feeds into an interface that's easy to organize > and browse. > > TinyTinyRSS and TheOldReader connections are supported so that you can > synchronize your feeds and (un)read items across multiple devices. > > Supported news formats include Rich Site Summary (RSS), Atom > Syndication (Atom), Resource Description Framework (RDF), and Channel > Definition Format (CDF). The original was somewhere low down on my list of packages to get round to, but expanding the initialisms does nothing to fix the main thing that was wrong with it. If I don't know what an RSS feed is, learning that it stands for "Rich Site Summary" isn't going to help, and expanding "Atom" to "Atom" is particularly futile. My only comment that really rates as an English usage issue is s/linux/Linux/, which had already been mentioned - you might even capitalise it as "LInux FEed REAder" to make the why-the-name hint clearer (see footnote). The main problem that's left is that if (like me) you've never used a feed reader, there's very little here to tell you what functionality such an application offers. It's very clear about which particular XML syndication formats it supports - but why should users care about that question if the answer is "all the standard ones"? Or are there important formats it _doesn't_ support? Compare Wikipedia, which describes it as supporting "the major feed formats including RSS/RDF and Atom", doesn't mention CDF, but later mentions that it also supports OCS and OPML, whatever those are. The mention of the interface is a definite improvement - at least now I can be sure Liferea isn't a CLI tool like wget, or a daemon that updates my bookmarks overnight, or some such. But it still doesn't really convey the idea that Liferea has a GTKish interface modelled after a threaded mail/newsclient with an embedded graphical browser; and there's still no mention of what it is that it's aggregating beyond the label "news", which is a poor description for most of the stuff people use subscriptions for. Looking at the upstream homepage I see that they list features like * Read articles when offline [...] * Permanently save headlines in news bins * Play Podcasts in Liferea Aren't these worth mentioning? I mean, maybe they're routine features of any Feed Reader, but now that the other Feed Readers aren't being mentioned any more... So I would suggest something roughly along the lines of: Description: feed aggregator for GNOME Liferea is a Linux feed reader that brings together all of the content from your favorite web subscriptions into a GUI that's easy to organize and browse. It supports: . * aggregating feeds in all the major syndication formats (including RSS/RDF, Atom, CDF, and more); * synchronizing feeds across devices, with TinyTinyRSS and TheOldReader support; * downloading articles to read while offline; * permanently saving headlines in news bins; * playing podcasts directly in Liferea's browser interface. Obligatory WhyTheName footnote: It's easy to guess that the person who coined the name was German; LiFeRea is a style of abbreviation that seems vaguely unpopular with native anglophones, though I don't know whether that's because it's hard to guess how it should be pronounced or whether such coinages just remind people too much of cases like "GeStaPo" and "KomSoMol". Sticking "Linux" on the front wasn't a great choice anyway, given that it apparently builds for kfreebsd-*. -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747376: Support for debian-lts mailing lists
I wish to add my support for the creation of these lists, to allow the Debian LTS project to operate as smoothly as possible. -- Matteo Filippetto http://www.op83.eu @matteo_1983 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747404: ITP: kxd -- Key exchange daemon
Package: wnpp Severity: wishlist Owner: Maximiliano Curia * Package name: kxd Version : 0.11 Upstream Author : Alberto Bertogli * URL : http://blitiri.com.ar/p/kxd/ * License : MIT Programming Lang: Go Description : Key exchange daemon kxd is a key exchange daemon, which serves blobs of data (keys) over https. It can be used to get keys remotely instead of using local storage. The main use case is to get keys to open dm-crypt devices automatically, without having to store them on the local machine. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#675008: bash should source package hooks into interractive shells
Am 07.05.2014 13:19, schrieb Dimitri John Ledkov: > > Hello all, > > I'm proposing below patch, which sources profile.d hooks into the > interactive shells from /etc/bash.bashrc. > > First of all, there is no reason to create a distinct /etc/bashrc.d, > since hooks can trivially inspect and figure out if they are sourced by > login or interactive shells (as vte.sh already does). > > If there is bad interaction between hooks, well, that's already a bug in > those hooks under login shells. > > Matthias and I, disagree on whether login & interractive shell > environments should be different or similar. I side, that the two should > be similar. Furthermore, looking at some of the existing hooks, I didn't > see any that would negatively affect interractive shells and/or where > for any reasons undesirable under interractive shells. > > Below change is also in-line with what other distributions are doing, > e.g. fedora 20 is sourcing profile.d from their system-wide bashrc. > > Everyone affected please test below patch, to see if it satisfies your > needs and unblocks shipping interractive shell hooks. I intend to NMU > this patch into delayed/10 on Friday, unless it is found buggy and/or > unacceptable, or maintainer chooses to fix this bug report using below > patch or any other means. I don't think this is the correct solution, so please don't NMU. I think it is wrong to piggy back on the /etc/profile.d mechanism, which was introduced by the LSB. Also mixing profile and bashrc stuff seems to be wrong. Citing implementations in other distributions doesn't help much, these may change without notice. So the best thing would be to bring such a proposal to the LSB, or to FreeDesktop, and then implement that one after it is accepted. Matthias -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#745402: fuse-emulator: Better support for ROM in Debian opense-basic package
On Thu, May 08, 2014 at 11:28:16AM +0200, Alberto Garcia wrote: > On Wed, May 07, 2014 at 06:20:13PM +0200, Santiago Vila wrote: > > > Well, the problem is that there is not any machine for which the > > default rom is opense.rom. > [...] > > Maybe a new machine for which this rom is the default, even if it's > > identical in hardware to the classical 48K Spectrum. > > At risk of repeating myself, the problem is that opense.rom can be > used in at least seven of the machines supported by Fuse, so I cannot > just add "Spectrum 48 + OpenSE" to the list. > > To make things more complex, it's also possible to mix opense.rom > and the original Spectrum ROMs in the 128k machines, as the OpenSE > documentation explains. Ok. Let's assume that fuse --rom-48 opense.rom is good enough. Can you forward upstream the part where tape saving routines do not work well enough? (Maybe the author will realize this way that this ROM exists to begin with). Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747292: gdm3 and session
Just to say that I have the exact same problem with my sid installation. The only workaround I found is to install lightdm which let me open a gnome-shell session. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700758: bcrypt: Bcrypt exposes patterns in data, it is broken
On Wed, Apr 09, 2014 at 01:09:40PM +0200, Agustin Martin wrote:
> On Mon, Apr 07, 2014 at 12:38:16PM +0200, Agustin Martin wrote:
> > If something Debian-only is to be done with this package to keep it
> > available, it could be disabling encryption, together with a descriptive
> > error message. This would be a minimal intervention and have the advantages
> > of (1) and (2).
> >
> > This should be documented in the package description and would allow users
> > to decrypt already encrypted data (you never know where that may appear),
> > but not to encrypt.
> >
> > What maintainer thinks about this?
> >
> > Note that this package has been proposed for removal (See cc'ed
> > http://bugs.debian.org/740748), so if any action is intended to keep this
> > package in the archive it should happen soon.
>
> Although my C skills are not good I played a bit with this.
>
> I'd expected attached patch to handle the encryption disabling.
Since I heard nothing from maintainer I plan a 0-day NMU with attached
patch. I noticed that I still have some stuff encrypted with bcrypt and
would not like to prepare a personal package just to deal with those not yet
found.
ftpmasters, what should I do regarding removal bug #740748?
I plan to upload encription-disabled bcrypt package closing #700758, wait for
it to reach testing in case any problem appear and then reassign #740748 to
bcrypt and forcemerge it with #700758.
Do you prefer both bug reports being closed on upload?
--
Agustin
>From 4de49e57ba2cf5261951841ac68c44b55cfabef1 Mon Sep 17 00:00:00 2001
From: Agustin Martin Domingo
Date: Tue, 8 Apr 2014 18:56:40 +0200
Subject: [PATCH] Disable encryption support. See http://bugs.debian.org/700758
[Bcrypt exposes patterns in data, it is broken]
---
debian/changelog | 8 +
debian/control | 4 ++-
debian/patches/00list | 1 +
.../patches/04_main.c_abort-on-encryption.dpatch | 39 ++
debian/patches/05_big_files.dpatch | 0
5 files changed, 51 insertions(+), 1 deletion(-)
create mode 100755 debian/patches/04_main.c_abort-on-encryption.dpatch
mode change 100644 => 100755 debian/patches/05_big_files.dpatch
diff --git a/debian/changelog b/debian/changelog
index 6a4195d..4cd20b7 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+bcrypt (1.1-8.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Disable RC broken encryption support (Closes: #700758). Make this a
+decrypt-only package for already created files.
+
+ -- Agustin Martin Domingo Thu, 08 May 2014 11:46:38 +0200
+
bcrypt (1.1-8) unstable; urgency=low
* Additional RC bug closed with patch added version 1.1-7. Closes: #693460.
diff --git a/debian/control b/debian/control
index 62b2f6e..0365c77 100644
--- a/debian/control
+++ b/debian/control
@@ -9,7 +9,9 @@ Standards-Version: 3.8.3
Package: bcrypt
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
-Description: Cross platform file encryption utility using blowfish
+Description: Cross platform file encryption utility using blowfish (Decrypt only)
+ WARNING: decrypt-only Debian package. Encryption disabled.
+ See http://bugs.debian.org/700758.
Bcrypt is a cross platform file encryption utility. Encrypted files are
portable across all supported operating systems and processors. In addition
to encrypting your data, bcrypt will by default overwrite the original input
diff --git a/debian/patches/00list b/debian/patches/00list
index 052aff1..3401a60 100644
--- a/debian/patches/00list
+++ b/debian/patches/00list
@@ -1 +1,2 @@
+04_main.c_abort-on-encryption
05_big_files
diff --git a/debian/patches/04_main.c_abort-on-encryption.dpatch b/debian/patches/04_main.c_abort-on-encryption.dpatch
new file mode 100755
index 000..66ab07f
--- /dev/null
+++ b/debian/patches/04_main.c_abort-on-encryption.dpatch
@@ -0,0 +1,39 @@
+#! /bin/sh /usr/share/dpatch/dpatch-run
+## 04_main.c_abort-on-encryption.dpatch by Agustin Martin
+##
+## All lines beginning with `## DP:' are a description of the patch.
+## DP: Disable encryption support. See http://bugs.debian.org/700758
+## DP: Bcrypt exposes patterns in data, it is broken]
+
+@DPATCH@
+diff -urNad '--exclude=CVS' '--exclude=.svn' '--exclude=.git' '--exclude=.arch' '--exclude=.hg' '--exclude=_darcs' '--exclude=.bzr' bcrypt~/main.c bcrypt/main.c
+--- bcrypt~/main.c 2014-04-08 18:38:59.0 +0200
bcrypt/main.c 2014-04-08 18:39:57.855694078 +0200
+@@ -51,6 +51,11 @@
+ exit(1);
+ }
+
++int abort_on_encryption() {
++ fprintf(stderr, "Encryption support disabled. See http://bugs.debian.org/700758\n";);
++ exit(1);
++}
++
+ int parseArgs(int *argc, char **argv, BCoptions *options) {
+ signed char ch;
+ char *progname;
+@@ -141,6 +146,7 @@
+ if (memcmp(*infile+(strlen(*infile) - 4), ".bfe", 4) == 0)
+ return(1);
+
++ abort_on_encryption();
+ s
Bug#742668: cups: Fails to install because can't listen to sockets
Hello Didier, and thanks for your reply. > Le mardi, 6 mai 2014, 14.23:41 Giuseppe Bilotta a écrit : >> I've just come across this issue during a dist-upgrade. The situation >> is the same as that of the original message: nothing is using port >> 631 or the cups socket, but: > > Are you sure of that? Can you paste the output of the following command > (run as root): > netstat -lnptu | grep 631 There is no output (running under sudo). >> so cups-daemon, cups and cups-core-drivers fail to complete the >> upgrade/configure. > > Do you have a specific ipv6 configuration (module unloaded or > blacklisted? The module is not blacklisted, but it's not loaded either (I'm not in an IPv6-enabled network). > Can you attach the content of all files and symlinks in > /etc/systemd/system/cups.socket.d ? There is only: /etc/systemd/system/cups.socket.d/cupsd-listen.conf -> ../../../cups/cupsd-systemd-listen.conf Contents: [Socket] # This file was generated by CUPS and _WILL_ be deleted or overwritten by it! # It has to be kept in sync with the Port and Listen stanzas in /etc/cups/cupsd.conf # It is by default symlinked as cups-listen.conf in the # /etc/systemd/system/cups.socket.d/ directory. Remove the symlink # and write your own file there if you don't want this. See systemd.socket(5). # Matches 'Listen localhost:631' from cupsd.conf ListenStream=127.0.0.1:631 ListenStream=[::1]:631 # Matches 'Port 631' from cupsd.conf ListenStream=0.0.0.0:631 ListenStream=[::]:631 > Could you also attach the output of `systemctl show cups.socket` ? Here it is: ---8< Id=cups.socket Names=cups.socket Requires=sysinit.target -.mount RequiredBy=cups.service configure-printer@usb-003-005.service WantedBy=sockets.target Conflicts=shutdown.target Before=cups.service sockets.target shutdown.target configure-printer@usb-003-005.service After=sysinit.target -.mount Triggers=cups.service Description=CUPS Printing Service Sockets LoadState=loaded ActiveState=failed SubState=failed FragmentPath=/lib/systemd/system/cups.socket DropInPaths=/etc/systemd/system/cups.socket.d/cupsd-listen.conf UnitFileState=enabled InactiveExitTimestampMonotonic=0 ActiveEnterTimestampMonotonic=0 ActiveExitTimestampMonotonic=0 InactiveEnterTimestampMonotonic=0 CanStart=yes CanStop=yes CanReload=no CanIsolate=no StopWhenUnneeded=no RefuseManualStart=no RefuseManualStop=no AllowIsolate=no DefaultDependencies=yes OnFailureIsolate=no IgnoreOnIsolate=no IgnoreOnSnapshot=no NeedDaemonReload=no JobTimeoutUSec=0 ConditionTimestamp=Wed 2014-05-07 19:32:51 CEST ConditionTimestampMonotonic=496589287791 ConditionResult=yes BindIPv6Only=ipv6-only Backlog=128 TimeoutUSec=1min 30s ControlPID=0 DirectoryMode=0755 SocketMode=0666 Accept=no KeepAlive=no Priority=-1 ReceiveBuffer=0 SendBuffer=0 IPTOS=-1 IPTTL=-1 PipeSize=0 FreeBind=no Transparent=no Broadcast=no PassCredentials=no PassSecurity=no ListenStream=/var/run/cups/cups.sock ListenStream=127.0.0.1:631 ListenStream=[::1]:631 ListenStream=0.0.0.0:631 ListenStream=[::]:631 Mark=-1 MaxConnections=64 NConnections=0 NAccepted=0 Result=resources UMask=0022 LimitCPU=18446744073709551615 LimitFSIZE=18446744073709551615 LimitDATA=18446744073709551615 LimitSTACK=18446744073709551615 LimitCORE=18446744073709551615 LimitRSS=18446744073709551615 LimitNOFILE=4096 LimitAS=18446744073709551615 LimitNPROC=61379 LimitMEMLOCK=65536 LimitLOCKS=18446744073709551615 LimitSIGPENDING=61379 LimitMSGQUEUE=819200 LimitNICE=0 LimitRTPRIO=0 LimitRTTIME=18446744073709551615 OOMScoreAdjust=0 Nice=0 IOScheduling=0 CPUSchedulingPolicy=0 CPUSchedulingPriority=0 TimerSlackNSec=5 CPUSchedulingResetOnFork=no NonBlocking=no StandardInput=null StandardOutput=journal StandardError=inherit TTYReset=no TTYVHangup=no TTYVTDisallocate=no SyslogPriority=30 SyslogLevelPrefix=yes SecureBits=0 CapabilityBoundingSet=18446744073709551615 MountFlags=0 PrivateTmp=no PrivateNetwork=no SameProcessGroup=no ControlGroupModify=no ControlGroupPersistent=no IgnoreSIGPIPE=yes NoNewPrivileges=no KillMode=control-group KillSignal=15 SendSIGKILL=yes DefaultControlGroup=name=systemd:/system/cups.socket ControlGroups=cpu:/system/cups.socket name=systemd:/system/cups.socket ---8< Cheers, -- Giuseppe "Oblomov" Bilotta -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747366: nvidia-driver: nvidia-uvm module is present but fails on load
Control: reassign -1 nvidia-driver 331.67-2 On Mi, 07 mai 14, 23:27:28, Serge Rijkers wrote: > Source: nvidia-driver > Version: 331.67-2 > Severity: important > > Dear Maintainer, > > > Some of the applications that I use are opencl enabled. I find that > since installing 331.67-2 version of the driver opencl no longer works > > This is due a load failure nvidia-uvm kernel module. The module is > present in my kernel. folliwing is output of modinfo nvidia-uwn > > %< -- snip > > root@rissa:~# modinfo nvidia-uvm > filename: > /lib/modules/3.14-2.dmz.1-liquorix-amd64/updates/dkms/nvidia-uvm.ko > supported: external > license:MIT > depends: > vermagic: 3.14-2.dmz.1-liquorix-amd64 SMP preempt mod_unload > modversions > > %< - end snip > > following is output of modprobe -v nvida-uvm > > %<-- snip > root@rissa:~# modprobe -v nvidia-uvm > insmod > /lib/modules/3.14-2.dmz.1-liquorix-amd64/updates/dkms/nvidia-current.ko > insmod /lib/modules/3.14-2.dmz.1-liquorix-amd64/updates/dkms/nvidia-uvm.ko > modprobe: ERROR: could not insert 'nvidia_uvm': Invalid argument > > %< end snip > > > The previous version of the package 331.67-1 failed build the nvidia-uvm > module. > reverting to 331.49-1 version of nvidia drivers manually restored > functionality. > > reverting to 331.49-1 no longer works. The dkms build of kernel module > for 331.49-1 fails. > > -- System Information: > Debian Release: jessie/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 3.14-2.dmz.1-liquorix-amd64 (SMP w/8 CPU cores; PREEMPT) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Bug#747232: Ruby should support SystemTap
* Sebastian Boehm [140508 00:12]:
> The current probe selection syntax is rather basic, but if the patch above is
> accepted, I could add a simple tap file in order to turn
>
>
> process("/usr/lib/x86_64-linux-gnu/libruby-2.1.so.2.1").mark("method__entry”)
>
> into
>
> ruby.method.entry
>
> I would add another bug report for this, though.
Please expand on this - would this mean additional "changes" to the
Ruby package? If so, please show us :-)
-ch
--
,''`. Christian Hofstaedtler
: :' : Debian Developer
`. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03
`-
pgpsgAc3GJvPs.pgp
Description: PGP signature
Bug#742853: transition: mpich2
Control: tag -1 moreinfo On Fri, Mar 28, 2014 at 06:17:31 +0100, Anton Gladky wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Dear release team, to remove old version of > mpich (2) prior version 3, we need to request > this transition. Some of packages probably will > need source uploads and I am ready to NMU them, > if needed. > Have those source uploads happened? Cheers, Julien signature.asc Description: Digital signature
Bug#737042: requirejs newer releases needed for jquery packaging
Hi Georges, It seems that Jonas' question is unanswered for a while. Also requirejs has two new upstream releases for months. It's needed for packaging newer jQuery packages, please see its build dependencies[1]. Thus node-requirejs seems to be correct as a build tool. Would you please update your package and/or let me be a co-maintainer of it under the JS packaging team's umbrella? Kind regards, Laszlo/GCS [1] https://github.com/jquery/jquery/blob/master/package.json -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#690531: Help needed: Porting IRAF to MIPS
On Thu, May 08, 2014 at 02:07:45AM +0200, David Kuehling wrote: > Index: zsvjmp/zsvjmp-mipsel.s why only mipsel ? The code should look the same for big endian MIPS... Thomas. -- Crap can work. Given enough thrust pigs will fly, but it's not necessarily a good idea.[ RFC1925, 2.3 ] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747405: missing license in debian/copyright
Package: ruby-gnome2 Version: 2.2.0-1 Severity: serious User: alteh...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks Dear Maintainer, please add the missing license of: goocanvas/sample/demo-fifteen.rb goocanvas/sample/demo-primitives.rb goocanvas/sample/demo.rb to debian/copyright. Thanks! Thorsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747230: Acknowledgement (opendnssec-signer: segfaults if NotifyCommand fails when adding a new zone)
Further debugging showed that the original bug report was flawed.
The problem was actually caused by
https://issues.opendnssec.org/browse/OPENDNSSEC-285
The bug has been fixed upstream in 1.3.10.
The following patch applies cleanly to 1.3.9-5 of current stable
release.
--- a/signer/src/signer/signconf.c 2014-05-08 12:58:54.0 +0300
+++ b/signer/src/signer/signconf.c 2014-05-08 12:59:12.0 +0300
@@ -179,7 +179,7 @@
st_mtime = ods_file_lastmodified(scfile);
if (st_mtime <= last_modified) {
ods_log_deeebug("[%s] file %s not modified since (file %u, "
-"mem %u)", sc_str, (unsigned) st_mtime,
+"mem %u)", sc_str, scfile, (unsigned) st_mtime,
(unsigned) last_modified);
return ODS_STATUS_UNCHANGED;
}
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#745711: AW: downtimed -- monitor of downtime, shutdown, and crashes
-Ursprüngliche Nachricht- Von:John Paul Adrian Glaubitz > Unless the other person who you think should adopt the package is > going to step up and do it right away, I have no problem in supporting > Stefan's efforts and sponsoring his upload. Hi, a few days passed by but no response from either Mats or anyone else with the intention to do the adoption. :) It would be kind to get the package sponsored :) thanks stefan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742853: transition: mpich2
2014-05-08 12:42 GMT+02:00 Julien Cristau : > Have those source uploads happened? No, not yet, I decided to wait till the new mpich will reach testing. Anton -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747292: gdm3: Unable to login after last upgrade (version 3.8.4-7): fails to start a GNOME session
Le Thu, 08 May 2014 11:20:41 +0200, Benjamin Menant a écrit : > The issue occurred again: > > 0. I submit the login form. > 1. I see a frozen desktop few seconds (while it should pop-in with a > fancy effect). > 2. The screen shutdown (standby). > 3. If I hit a key, I see the curtain screen. > 4. If I unlock it, I see the login screen, showing « authentication > error ». > > I attached the logs. Could you try to add "debug=yes" after the call to pam_systemd in the pam config and attached the auth.log file here again? Could you also check if you have a /run/user/$UID directory created? Otherwise I'm running out of idea :/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747232: Ruby should support SystemTap
On 8 May 2014 12:39, Christian Hofstaedtler wrote: > Please expand on this - would this mean additional "changes" to the > Ruby package? If so, please show us :-) Yes, but only minor changes. Basically we would have to install a tap file to /usr/share/systemtap/tapset which is then loaded by systemtap on startup. (Details in the "Processing" section of the stap(1) man page.) Fedora uses this tap file: http://pkgs.fedoraproject.org/cgit/ruby.git/tree/libruby.stp @LIBRARY_PATH@ is set to the correct path in the course of the package build process. As of 2.1, Ruby upstream also has a simple tap file generator, but as far as I can tell its incomplete (wrong simplified probe names, no string copying) at the moment: https://github.com/ruby/ruby/blob/ruby_2_1/tool/gen_ruby_tapset.rb I haven't talked to upstream yet, but I threw together a somewhat improved version of the current gen_ruby_tapset.rb that I would like to contribute if they are interested. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747406: rubygems intall/upgrade bug has corrupted the apt packaging system
Package: ruby Version: 2.0.0 Severity: normal Tags: d-i Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** after upgrading ruby (as a dependency) Setting up ruby2.0 (2.0.0.484+really457-3) ... Setting up ruby (1:2.0.0.2) ... Setting up perl-modules (5.18.2-2) ... Setting up libruby2.0:i386 (2.0.0.484+really457-3) ... the how-can-I-help, and apt-listbugs are both corrupted. This corrupts the apt system: [ end of an aptitude update: ] Setting up libtext-soundex-perl (3.4-1+b1) ... Processing triggers for libc-bin (2.18-4) ... Processing triggers for menu (2.1.46) ... /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- debian_version (LoadError) from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/vendor_ruby/debian.rb:24:in `' from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/bin/how-can-i-help:20:in `' E: Problem executing scripts DPkg::Post-Invoke '[ ! -e /usr/bin/how-can-i-help ] || /usr/bin/how-can-i-help' E: Sub-process returned an error code Failed to perform requested operation on package. Trying to recover: Press Return to continue. the apt system is now corrupt. Every action returns: /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- debian_version (LoadError) from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/vendor_ruby/debian.rb:24:in `' from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/sbin/apt-listbugs:314:in `' E: Sub-process /usr/sbin/apt-listbugs apt returned an error code (1) E: Failure running script /usr/sbin/apt-listbugs apt Failed to perform requested operation on package. Trying to recover: Press Return to continue. /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- debian_version (LoadError) from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/vendor_ruby/debian.rb:24:in `' from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/sbin/apt-listbugs:314:in `' E: Sub-process /usr/sbin/apt-listbugs apt returned an error code (1) E: Failure running script /usr/sbin/apt-listbugs apt Failed to perform requested operation on package. Trying to recover: Press Return to continue. and does NOT complete it's task. Thus the violating [that have these dependencies ] packages can NOT be removed: apt-get remove --purge apt-listbugs Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: apt-listbugs* 0 upgraded, 0 newly installed, 1 to remove and 345 not upgraded. After this operation, 430 kB disk space will be freed. Do you want to continue? [Y/n] Y /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- debian_version (LoadError) from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/vendor_ruby/debian.rb:24:in `' from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/sbin/apt-listbugs:314:in `' E: Sub-process /usr/sbin/apt-listbugs apt returned an error code (1) E: Failure running script /usr/sbin/apt-listbugs apt and apt-get remove --purge apt-listbugs how-can-i-help Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: apt-listbugs* how-can-i-help* 0 upgraded, 0 newly installed, 2 to remove and 345 not upgraded. After this operation, 493 kB disk space will be
Bug#745402: fuse-emulator: Better support for ROM in Debian opense-basic package
tags 745402 + upstream thanks On Thu, May 08, 2014 at 12:28:32PM +0200, Santiago Vila wrote: > Can you forward upstream the part where tape saving routines do not > work well enough? (Maybe the author will realize this way that this > ROM exists to begin with). Sure, I can do that. One thing that I realized is that Fuse disables the tape traps if one tries to override the default ROM, so even if you use the original Spectrum ROM with --rom-48 48.rom it will not work. This should be easy to fix, though. Berto -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747406: rubygems intall/upgrade bug has corrupted the apt packaging system
Thanks for your report. Please provide the output of these commands: ls -la /usr/bin/ruby* dpkg -l ruby\* how-can-i-help apt-listbugs -ch -- ,''`. Christian Hofstaedtler : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- pgpaJBLFUdDc9.pgp Description: PGP signature
Bug#745079: transition: kde4.12
¡Hola Debian Release Team! El 2014-04-30 a las 12:51 +0200, Maximiliano Curia escribió: > El 2014-04-17 a las 21:57 +0200, Maximiliano Curia escribió: > > I'd like to request a transition slot for kde 4.12, the current release is > > 4.12.4. > pending to upload packages: > > libkdcraw 4:4.12.3-2 > > marble 4:4.12.4-1 > > kdeplasma-addons 4:4.12.4-1 (build-depends on marble) calligra 1:2.8.2-1 calligra-l10n 1:2.8.2-1 Adrien Grellier has prepared calligra and calligra-l10n 1:2.8.2-1, which we would like to upload to unstable, but as calligra build depends on marble and libkdcraw it would mean a binnmu when the transition gets approved. So, I'm adding them to the pending to upload packages. -- "I decry the current tendency to seek patents on algorithms. There are better ways to earn a living than to prevent other people from making use of one's contributions to computer science." -- Donald Knuth Saludos /\/\ /\ >< `/ signature.asc Description: Digital signature
Bug#613143: there is /usr/lib64 symlink but no /usr/local/lib64
On Thu, May 08, 2014 at 09:08:58AM +0200, Tollef Fog Heen wrote: > ]] Aurelien Jarno > > > How can we progress on this bug? We now have bugs #720777, #720778 and > > #720780 which ask for /usr/lib to be created if /lib exists. > > It's something that can be implemented, but before doing so, I would > > like to know if a decision has been taken wrt the policy. > > I think the whole lib thing should be avoided and we should nack > it for any new ports. Ideally, we should also try to get ourselves out > of the hole we've dug ourselves into. Unfortunately given we still want to keep multilib compilers in the archive, we need to provide foreign binaries, and thus install them in lib. The policy clearly states that a foreign binary should not be installed in the multiarch path, and that's really a good thing given how much pain multilib packages are already (especially when people start to install libc6-dev-amd64:i386 on an amd64 system or things like that). Currently for being able to build i386 binaries on an amd64 system, you need to install libc6-i386:amd64, usually used in addition to libc6:i386. This is a pain from the glibc side as we have to handle the fact that they both provide ld.so and that they can be removed in any order. The development of multiarch seems to be more or less stalled now, people being satisfied of being able to install packages from foreign architectures. To be able to progress further we need to solve the toolchain issue. They are multiple solutions from using foreign packages to build multilib toolchain, to stopping providing a multilib toolchain and using either cross compiler or allow both gcc:amd64 and gcc:i386 to be co-installable. In any case to support kernel and bootloader packages we need to create new architectures with a minimal set of packages (basically the toolchain). On the other hand if we just continue to wait, 32-bit architectures are going to die, and the kernel and bootloader issue will simply disappear ;-). > I don't see anybody being against relaxing the requirement for > /usr/local/lib to exist, so we're presumably blocked on more > seconds. Ok, great. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747407: experimental-to-unstable-without-comment should allow "to sid"
Package: lintian Version: 2.5.22.1 Severity: wishlist Lintian looks for the phrase "to unstable". I think it would be sensible to also allow the string "to sid" which is a synonym for unstable for eternity AFAIK. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742853: transition: mpich2
On Thu, May 8, 2014 at 13:25:07 +0200, Anton Gladky wrote: > 2014-05-08 12:42 GMT+02:00 Julien Cristau : > > Have those source uploads happened? > > No, not yet, I decided to wait till the new mpich will reach testing. > Okay. That's happened now, FWIW. Cheers, Julien signature.asc Description: Digital signature
Bug#747408: nm.debian.org: get_portfolio_url() doesn't return the full url
Package: nm.debian.org
Severity: normal
Tags: patch
Hi,
backend/models.py get_portfolio_url() doesn't return the full portfolio
URL, it's missing replacement fields. Patch attached.
Cheers,
Santiago
-- System Information:
Debian Release: 7.2
APT prefers stable
APT policy: (500, 'stable'), (10, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff --git a/backend/models.py b/backend/models.py
index 02a29aa..2d17030 100644
--- a/backend/models.py
+++ b/backend/models.py
@@ -474,7 +474,7 @@ class Person(models.Model):
parms["gpgfp"] = self.fpr
if self.uid:
parms["username"] = self.uid
-return u"http://portfolio.debian.net/result?".format(urllib.urlencode(parms))
+return u"http://portfolio.debian.net/result?{}".format(urllib.urlencode(parms))
def get_allowed_processes(self):
"Return a lits of processes that this person can begin"
Bug#747409: RM: several -- ROP; outdated hurd-i386 binary packages
Package: ftp.debian.org Severity: normal The following list of source packages has hurd-i386 binary packages which are outdated and can be removed from the archive. dak rm --rdep-check -p -a=hurd-i386 -B burp dateutils ffe haskell-llvm libembperl-perl mail-notification mssh openocd resiprocate rpy2 since skimage tardy tupi xburst-tools xserver-xorg-video-openchrome The dak --no-action output from coccia.debian.org is attached. Cheers, Michael Will remove the following packages from unstable: anon-proxy | 00.05.38+20081230-2.1+b1 | hurd-i386 ants | 1.9.2+svn680.dfsg-4 | hurd-i386 asterisk-flite | 2.1-1+b1 | hurd-i386 colobot |0.1.2-3 | hurd-i386 colobot-dbg |0.1.2-3 | hurd-i386 cpuid | 3.3-9+b1 | hurd-i386 darkstat | 3.0.715-1+b1 | hurd-i386 denemo |0.9.2-3 | hurd-i386 dfu-programmer | 0.5.4-1+b2 | hurd-i386 emscripten | 1.4.9~20130620~0ad8724-1 | hurd-i386 environment-modules | 3.2.10-8 | hurd-i386 eventstat | 0.01.15-1 | hurd-i386 fish | 1.23.1+20120106.git8b407a3-1+b1 | hurd-i386 fish-dbg | 1.23.1+20120106.git8b407a3-1+b1 | hurd-i386 foo-yc20 |1.3.0-5 | hurd-i386 gauche-c-wrapper | 0.6.1-4.1+b1 | hurd-i386 gauche-gl | 0.4.4-5+b3 | hurd-i386 gnunet-gtk |0.9.3-1 | hurd-i386 gnunet-gtk-dbg |0.9.3-1 | hurd-i386 gnunet-gtk-dev |0.9.3-1 | hurd-i386 idzebra-2.0 | 2.0.44-3+b1 | hurd-i386 idzebra-2.0-utils | 2.0.44-3+b1 | hurd-i386 jwm | 2.1.0-3+b1 | hurd-i386 libapache2-mod-gnutls | 0.5.10-5 | hurd-i386 libcache-mmap-perl | 0.11-1+b4 | hurd-i386 libcss-parser-pp0 | 0.85-2 | hurd-i386 libcss-parser0 | 0.85-2 | hurd-i386 libghc-libzip-dev | 0.10.2-2+b3 | hurd-i386 libghc-libzip-prof | 0.10.2-2+b3 | hurd-i386 libhtmlcxx-dev | 0.85-2 | hurd-i386 libhtmlcxx3 | 0.85-2 | hurd-i386 libidzebra-2.0-0 | 2.0.44-3+b1 | hurd-i386 libidzebra-2.0-dev | 2.0.44-3+b1 | hurd-i386 libidzebra-2.0-mod-alvis | 2.0.44-3+b1 | hurd-i386 libidzebra-2.0-mod-dom | 2.0.44-3+b1 | hurd-i386 libidzebra-2.0-mod-grs-marc | 2.0.44-3+b1 | hurd-i386 libidzebra-2.0-mod-grs-regx | 2.0.44-3+b1 | hurd-i386 libidzebra-2.0-mod-grs-xml | 2.0.44-3+b1 | hurd-i386 libidzebra-2.0-mod-text | 2.0.44-3+b1 | hurd-i386 libidzebra-2.0-modules | 2.0.44-3+b1 | hurd-i386 libnet-rawip-perl | 0.25-1+b1 | hurd-i386 libpion-5.0 | 5.0.4+dfsg-2 | hurd-i386 libpion-5.0-dbg | 5.0.4+dfsg-2 | hurd-i386 libpion-dev | 5.0.4+dfsg-2 | hurd-i386 libpion-plugins | 5.0.4+dfsg-2 | hurd-i386 libpion-plugins-dbg | 5.0.4+dfsg-2 | hurd-i386 libpolybori-0.5.0-0 | 0.5~rc1-2.3+b1 | hurd-i386 libpolybori-dev | 0.5~rc1-2.3+b1 | hurd-i386 libsys-gamin-perl | 0.1-1+b1 | hurd-i386 libyade | 1.07.0-3 | hurd-i386 mandos-client | 1.5.3-1.1+b1 | hurd-i386 morse-simulator |1.1.1-1 | hurd-i386 parcellite | 1.0.2~rc5-1+b1 | hurd-i386 pdns-backend-geo | 3.1-4 | hurd-i386 pdns-backend-ldap | 3.1-4 | hurd-i386 pdns-backend-lua | 3.1-4 | hurd-i386 pdns-backend-mysql | 3.1-4 | hurd-i386 pdns-backend-pgsql | 3.1-4 | hurd-i386 pdns-backend-pipe | 3.1-4 | hurd-i386 pdns-backend-sqlite | 3.1-4 | hurd-i386 pdns-backend-sqlite3 | 3.1-4 | hurd-i386 pdns-server | 3.1-4 | hurd-i386 pdns-server-dbg | 3.1-4 | hurd-i386 phoneui-apps | 0.1+git20111214-1+b1 | hurd-i386 prads | 0.3.0-1+b1 | hurd-i386 psad | 2.1.7-1+b1 | hurd-i386 python-llvm | 0.6+svn105-2+b1 | hurd-i386 python-llvm-dbg | 0.6+svn105-2+b1 | hurd-i386 python-polybori | 0.5~rc1-2.3+b1 | hurd-i386 python-smbc | 1.0.6-1+b2 | hurd-i386 python-yade | 1.07.0-3 | hurd-i386 python3-morse-simulator |1.1.1-1 | hurd-i386 qiime | 1.7.0+dfsg-1+b1 | hurd-i386 read-edid | 2.0.0-3.1 | hurd-i386 ruby-lapack | 1.5-2 | hurd-i386 ruby-lapack-dbg | 1.5-2 | hurd-i386 stella |3.9.2-1 | hurd-i386 subsurface |3.1.1-2 | hurd-i386 vice | 2.4.dfsg-1 | hurd-i386 x42-plugins | 20130915-1 | hurd-i386 xdemorse | 1.3-7 | hurd-i386 xfce4-power-manager | 1.0.11-2+b2 | hurd-i386 xfce4-power-manager-plugins | 1.0.11-2+b2 | hurd-i386 xul-ext-gnome-keyring |0.6.6-1 | hurd-i386 yade | 1.07.0-3 | hurd-i386 Maintainer: Ximin Luo , Debian Xfce Maintainers , Jonas Smedegaard , Debian Science Maintainers , Rodolphe Pelloux-Prayer , Debian QA Group , Rene Mayorga , Debian Perl Group , Debian freesmartphone.org Team , Debian Ruby Extras Maintainers , Athena Capital Research , Tim Abbott , Prads package developers , Jari Aalto , LIU Qi , NeuroDebian Team , Carl Chenet , Mandos Maintainers , Debian Python Modules Team , Aurélien GÃRÃME , Daniel Kahn Gillmor , Debian Haskell Group , Debian Science Team , Ludovico Cavedon , Colin King , NIIBE Yutaka , Debian Multimedia Maintainers , Debian running development group , Bertrand Marc , Debian Games Team , Andrew Starr-Bochicchio , Franck Joncourt , Alastair McKinstry , Gustavo Noronha Silva , LLVM Packaging Team , David Spreen , Laszlo Boszormenyi (GCS) , Debian PowerDNS Maintainers , Debian Med Packa
Bug#747320: Mandate "type" in /bin/sh
On Wed, May 07, 2014 at 02:32:39PM +0100, Ian Jackson wrote: > Package: debian-policy > Version: 3.9.5.0 > > I came across this in /etc/init.d/exim4: > > OLDIFS="$IFS" > IFS=: > for p in $PATH; do > if [ -x "$p/$UPEX4CONF" ]; then > IFS="$OLDIFS" > $p/$UPEX4CONF $UPEX4OPTS > return 0 > fi > done > IFS="$OLDIFS" > > I imagine that this kind of thing is found in many other places. > > It seems to me that given that dash and bash both provide `type', and > the underlying functionality necessarily exists in the shell, it would > be better to mandate that the shell expose it. > > I therefore propose that the following should be added to the list of > additional features listed in policy 10.4: > > * The XSI extension `type' must be supported . It must exit > zero iff the command is found. The output format is not > specified and scripts must not rely on it; scripts should > rely only on the exit code using a construct such as >if type foo >/dev/null 2>&1; then ... Could you do a survey of current valid /bin/sh shells and see which of them suport XSI type already ? Cheers, -- Bill. Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#613143: there is /usr/lib64 symlink but no /usr/local/lib64
On Thu, May 08, 2014 at 09:08:58AM +0200, Tollef Fog Heen wrote: > ]] Aurelien Jarno > > > How can we progress on this bug? We now have bugs #720777, #720778 and > > #720780 which ask for /usr/lib to be created if /lib exists. > > It's something that can be implemented, but before doing so, I would > > like to know if a decision has been taken wrt the policy. > > I think the whole lib thing should be avoided and we should nack > it for any new ports. Ideally, we should also try to get ourselves out > of the hole we've dug ourselves into. > > I don't see anybody being against relaxing the requirement for > /usr/local/lib to exist, so we're presumably blocked on more > seconds. Indeed, for policy to move forward we need input from knowledgeable developers. Cheers, -- Bill. Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747410: meep: ignores errors from ./configure
Source: meep Version: 1.1.1-9 Severity: serious Your package ignores errors from ./configure. You shouldn't do that. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567183: Fancontrol init script removed by lm-sensors
Hi, On Sun, May 04, 2014 at 07:58:34PM +0300, Tuomas Suutari wrote: > I installed fancontrol package and it installed /etc/init.d/fancontrol > init script. I created configuration file with pwmconfig and then fan > speeds are controlled by fancontrol from the system boot. I was happy > with this, but then I needed the lm-sensors package too and installed > it. Installing lm-sensors removed /etc/init.d/fancontrol init script > and so fancontrol is not automatically started at boot anymore. > > What's the correct way to get fan speeds controlled by fancontrol from > system boot? That is indeed the correct way, but the lm-sensors package is buggy and your case is not correctly taken into account in your case. I will fix that in the next upload. > If I just rename /etc/init.d/fancontrol.dpkg-bak to > /etc/init.d/fancontrol, then next upgrade to lm-sensors will just > remove it again. Doesn't it? No, this happen only happens if you upgrade lm-sensors from a version lower than 1:3.1.1-5, so your configuration file should now be safe. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#702005: Bug #702005: Where can i get more attention on this?
Luis Alejandro Martínez Faneyth writes ("Bug #702005: Where can i get more
attention on this?"):
> I'm a little worried about bug #702005 and the lack of attention
> it's getting. This bug is marked as resolved, and indeed it has
> been resolved for jessie and sid, but not for wheezy. This bug
> breaks Python 2.7. Every person that tries to upgrade python2.7 and
> python2.7-minimal from version 2.7.3-6 to 2.7.3-6+deb7u2, is
> affected by this bug.
It's not clear from your messages here on -devel exactly what you
think the right next step is. Reading the bug report, I think you are
suggesting that a particular patch should be backported to
debian-stable.
> Please, can someone upload the fix to wheezy also? Or, how can i
> help? Thanks,
Uploads to stable following the process documented here:
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable
So the next step would be to file a bug against release.debian.org
asking for approval for inclusion of this patch in stable.
That approval request should come with clear explanation (from first
principles, aimed at someone who doesn't necessarily follow the
intricacies of the python packaging), of both the bug and the fix.
If you like I would be happy to review a draft of such an explanation
if you were to write one. If you produce an explanation that
satisfies me, and you get approval from the stable team, I would also
be happy to review and sponsor your upload.
If you would like to try to take the lead in this way, it's probably
best to email me privately, perhaps CC the bug, with your drafts etc.
I don't think debian-devel need to see all of this.
> This is affecting also every debian derivative based on stable, and
> is worth mentioning:
Of course we should try to do a good job in stable, but of course one
thing that a derivative can be expected to diverge on is questions of
release management.
Usually most of the work in backporting a fix is not in the technical
work of preparing the package - it is in analysing whether the fix is
appropriate for users or stable (and indeed, in persuading the
relevant release managemers).
Ian.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#746007: meep: please migrate to guile-2.0
severity 746007 serious retitle 746007 meep: FTBFS with guile-2.0 thanks meep FTBFS with guile-2.0, see: https://buildd.debian.org/status/package.php?p=meep&suite=sid Apparently this check in configure.ac fails because gh_enter no longer exists in guile-2.0: CPPFLAGS="$CPPFLAGS `$GUILE_CONFIG compile`" LIBS="`$GUILE_CONFIG link` $LIBS" AC_MSG_CHECKING([if linking to guile works]) AC_TRY_LINK_FUNC(gh_enter, AC_MSG_RESULT(yes), [ AC_MSG_RESULT(no) AC_MSG_ERROR(guile-config is broken) ]) Regards, Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#702005: Bug #702005: Where can i get more attention on this?
Ian Jackson writes ("Re: Bug #702005: Where can i get more attention on this?"):
> [some stuff to Luis Alejandro Martínez Faneyth ]
Unfortunately, Luis's mail domain is hosted at Hotmail which hates
chiark:
l...@huntingbears.com.ve
SMTP error from remote mail server after MAIL
FROM: SIZE=4130:
host 3fd47c7f131f4ca31143ff3af72008.pamx1.hotmail.com [65.54.188.78]:
550 SC-002 (BAY0-PAMC1-F10) Unfortunately, messages from 212.13.197.229
weren't sent. Please contact your Internet service provider since part of their
network is on our block list. You can also refer your provider to
http://mail.live.com/mail/troubleshooting.aspx#errors.
(I know of the causes of this; I disagree with Hotmail and resolving
things is nontrivial.)
So hopefully Luis will see my reply here on -devel or in the bug.
Luis, if you want to email me, please use a different email address
that doesn't go to Hotmail.
Thanks,
Ian.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#716778: #716778 - gnome-session: session is unusable (looks like memory problem)
Hey Axel, Could you please still reproduce this issue ? does it run fine with newer gnome-session version like 3.8.4-3 ? cheers, althaser
Bug#747412: uscan: option to verify current upstream tarball
Package: devscripts Severity: wishlist File: /usr/bin/uscan It would be great if there were an option to verify the current upstream tarball is the same as the one for the package and that the upstream cryptographic signatures still match. Currently sponsors have to do this manually, it would be much better if it could be automated. If the hash of the tarball is different to upstream, uscan could determine if the tarball was just recompressed, if the tarball itself was recreated or if the content of the tarball is different and maybe how it is different. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#747411: due dictionary, packbe b-d depends on python 2.5+ event 2.4
Package: chocolate-doom Version: 2.0.0-2 Severity: wishlist todya most release have recent python versions, but due depends said python >= 2.4, when backporting i have the following error: ./simplecpp -DDOOM -DPRECOMPILED < INSTALL.template > INSTALL.doom Traceback (most recent call last): File "./simplecpp", line 47, in ? defines = collections.defaultdict(lambda: False) AttributeError: 'module' object has no attribute 'defaultdict' due default dict attribute was introduce in python 2.5+ and not 2.4, so b-d must be >=2.5 -- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#716876: #716876 - gnome-session needs to update dependency on libatspi2.0-0:i386 2.5.1-1 2.9.3-1
Hey js, gnome-session doesn't depend directly on libatspi2.0-0. However could you please try with libatspi2.0-0 version 2.5.3-2 from wheezy ? thanks regards althaser
