Bug#1073515: git: FTBFS on mips64el

Source: git Version: 1:2.45.2-1 Severity: serious Justification: FTBFS (but possibly unreproducibly?) https://buildd.debian.org/status/logs.php?pkg=git&arch=mips64el shows the git package fairly regularly failing to build on mips64el this year. Example failure: ``` expecting success of 5526.25 '

Bug#1009167: xz-utils: diff for NMU version 5.2.5-2.1

Hi Salvatore, Salvatore Bonaccorso wrote: > On Sun, Apr 10, 2022 at 03:08:12PM +0200, Salvatore Bonaccorso wrote: >> I've prepared an NMU for xz-utils (versioned as 5.2.5-2.1) and >> uploaded it to DELAYED/2. Please feel free to tell me if I >> should delay it longer. > > I noted that the last up

Bug#985416: Bug#986565: unusable with current git

Hi, >> On Wed, 21 Apr 2021 10:12:03 + Damyan Ivanov wrote: >>> Sigh. Now git reverted to using /usr/lib again, and git-flow is broken. Why sigh? Directories such as /usr/lib/git-core and /usr/libexec/git-core are internal to git. Other packages should not install to either directory. Thi

Bug#985351: git: Moved git-sh-prompt shell library breaks user code

Hi! Guillem Jover wrote: > The latest version in sid, breaks user code sourcing the git-sh-prompt > shell library as it moved from /usr/lib/ to /usr/libexec, even though > I see the comment there says to copy it, but that means no automatic > upgrades. :/ > > Could you perhaps add a backwards com

Bug#972871: git-el: .el files not installed / byte-compiled

tags 972871 + patch pending quit Jonathan Nieder wrote: > Thanks for reporting. > > Strangely, debian-emacs-policy doesn't appear to be in the > emacsen-common package any more. Fortunately, it's in > https://www.debian.org/doc/packaging-manuals/debian-emacs-policy.

Bug#972871: git-el: .el files not installed / byte-compiled

Hi, Zack Weinberg wrote: > While updating my emacs configuration for 27.1 (now in unstable) > I noticed that /etc/emacs/site-start.d/50git-core.el prints > > git removed but not purged, skipping setup > > and does not autoload either git.el or git-blame.el. This appears to > be because /usr/lib/

Bug#965350: kgb-bot: autopkgtest makes assumption about exact merge commit message

Source: kgb-bot Version: 1.56-1 Tags: upstream Severity: serious Justification: tests fail with up-to-date Git Affects: src:git >From >https://ci.debian.net/data/autopkgtest/testing/amd64/k/kgb-bot/6323993/log.gz: | not ok 71 | | # Failed test at t/52-client-git.t line 393. | # got: '

Bug#961702: git breaks fdroidserver autopkgtest: Failed to parse line: ' git config pull.rebase false

reassign 961702 python3-git 3.1.1-1 affects 961702 git quit Hi, Hans-Christoph Steiner wrote: > I can't find any possible reference in fdroidserver, or in python3-git > for that matter. My guess is that the issue is caused by python3-git > failing to parse something that was added in the most r

Bug#955152: git-rebase ignores or squashes GIT_REFLOG_ACTION

Hi, Ian Jackson wrote[1]: > [ some git-debrebase invocation etc. ] > + git reflog > + egrep 'debrebase new-upstream.*checkout' > + rc=1 > > I have looked at the log and repro'd the bug. > > git-debrebase (which lives in src:dgit but does not depend on dgit) > must invoke git-rebase. It sets GIT_

Bug#949454: libctf-nobfd0: missing Breaks+Replaces against libbinutils versions with the same files

Package: libctf-nobfd0 Version: 2.33.50.20200115-2 Severity: serious Rationale: breaks upgrades libctf-nobfd0 takes over the file libctf-nobfd.so.0.0.0 from libbinutils but is missing a Breaks + Replaces declaring so: Unpacking libctf-nobfd0:amd64 (2.33.50.20200115-2) ... dpkg: error processing

Bug#945961: xz-utils: FTBFS: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*'

Hi, Sebastian Andrzej Siewior wrote: > I don't know what changed but I think it is debhelper. We have now: > > |(sid)bigeasy@debbuildd:~/xz/1/xz-utils-5.2.4$ dh binary --no-act > | debian/rules install > | dh_installdeb > | dh_gencontrol > | dh_md5sums > | dh_builddeb > > and that "debi

Bug#942353: python-evtx: ImportError: No module named hexdump

Package: python-evtx Version: 0.6.1-1 Severity: serious Justification: missing dependency $ evtx_dump.py Traceback (most recent call last): File "/usr/bin/evtx_dump.py", line 20, in import Evtx.Evtx as evtx File "/usr/local/buildtools/current/sitecustomize/sitecustomize.py", line 152, in

Bug#915426: git breaks git-remote-hg autopkgtest

Hi again, On 25 January 2019, Jonathan McCrohan wrote: > I am happy to work on fixing up the FTBFS, but > because I am not a DD, I would need a sponsor to upload for me. I'm happy to sponsor an upload, especially if this is a first step toward team maintenance with Jonas (who I can speak from ex

Bug#915426: git breaks git-remote-hg autopkgtest

Hi Jonas, Jonas Smedegaard wrote: > I can do yet another NMU to fix this, but am hesitating as I worry if > that will masquerade a lack of responsive maintenance. > > Please tell if it is sensible that I take over maintenance of this > package, or join as co-maintainer, or however is appreciated.

Bug#919296: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

Dmitry Bogatov wrote: >> Jonathan Nieder wrote: >>> + * git-daemon-run: pre-create supervise directory so that postinst >>> +can start the service (thx Celejar and Dmitry Bogatov; closes: >>> +#919296). [...] > Wierd. It should work. /etc/sv/git-daemo

Bug#919296: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

tags 919296 - patch pending quit Jonathan Nieder wrote: > For "buster", I prefer a minimal fix within the framework of the > current packages, along the lines you suggested upthread: > > diff --git i/debian/changelog w/debian/changelog > index ef513b2e1d..fb996c9

Bug#919296: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

description (thx Jens Reyer; closes: #707790). + * git-daemon-run: pre-create supervise directory so that postinst +can start the service (thx Celejar and Dmitry Bogatov; closes: +#919296). -- Jonathan Nieder Mon, 21 Jan 2019 19:36:25 -0800 diff --git i/debian/git-daemon-run.

Bug#919296: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

# missing Depends severity 919296 serious quit Celejar wrote: >> Celejar wrote: >>> Any attempt to manage the daemon (e.g., 'sv stat git-daemon', as per >>> README.debian) fails with: >>> >>> warning: git-daemon: unable to open supervise/ok: file does not exist [...] > ii runit 2.1.2-22

Bug#919296: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

Hi again, Celejar wrote: > Severity: grave > > Any attempt to manage the daemon (e.g., 'sv stat git-daemon', as per > README.debian) fails with: > > warning: git-daemon: unable to open supervise/ok: file does not exist [...] > Versions of packages git-daemon-run depends on: > ii adduser 3.118 >

Bug#919296: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

Hi, Celejar wrote: > Severity: grave > > Any attempt to manage the daemon (e.g., 'sv stat git-daemon', as per > README.debian) fails with: > > warning: git-daemon: unable to open supervise/ok: file does not exist > > I see that there's an old, archived bug about this: > > https://bugs.debian.org/

Bug#915426: git breaks git-remote-hg autopkgtest

Paul Gevers wrote: > https://ci.debian.net/data/autopkgtest/testing/amd64/g/git-remote-hg/1428119/log.gz > > not ok 32 - pull tags The package ought to run "make TEST_OPTS=-v" to produce a more useful log[*]. Bisects to the following Git change: e198b3a740409fabe5ba774c5f1255b55fdd21c1 is the f

Bug#914695: dgit autopkgtest breaks with git 2.20

Hi Ian, Ian Jackson wrote: > https://ci.debian.net/data/autopkgtest/testing/amd64/d/dgit/1382882/log.gz [...] > Looking at the test log did not immediately suggest a cause to me. > But it is probably much easier for me to (at least initially) > investigate this, since I will hopefully underst

Bug#888549: chrome-gnome-shell: Please don't use /etc/opt, it's not FHS-compliant

Jeremy Bicha wrote: > On Thu, Sep 13, 2018 at 5:57 PM Jonathan Nieder wrote: >>> There is no reason this functionality cannot be offered in Debian. We >>> got complaints when we supported other browsers but not Google Chrome. >> >> Since Google Chrome is n

Bug#888549: chrome-gnome-shell: Please don't use /etc/opt, it's not FHS-compliant

Hi, Jeremy Bicha wrote: > On Thu, Sep 13, 2018 at 4:40 PM Santiago Vila wrote: >> What I said is that no sane package in Debian/main should need to put >> files directly in /etc/opt. That's an oddity, a very unorthodox thing, >> it would be like a Debian package in main putting stuff directly in

Bug#901900: dgit in stretch-backports

Hi Sean, Sean Whitton wrote: > On Fri, Jun 22 2018, Jonathan Nieder wrote: >> Is there somewhere I can read more about that policy? Not that I'm >> complaining :) > > https://backports.debian.org/Contribute/ > > "... you have to ... update your backpor

Bug#901897: closed by Jonathan Nieder (Bug#901897: fixed in git 1:2.18.0~rc2-2)

Hi, Ian Jackson wrote: > Paul Gevers writes ("Re: Bug#901897 closed by Jonathan Nieder > (Bug#901897: fixed in git 1:2.18.0~rc2-2)"): >> And I just helped the test for git a bit as due to bug 896023 in >> autopkgtest it didn't use the right autopkgtest from dgi

Bug#901900: dgit in stretch-backports

hink that's the situation we're in. > On Fri, Jun 22 2018, Jonathan Nieder wrote: >> Is there somewhere I can read more about that policy? Not that I'm >> complaining :) > > https://backports.debian.org/Contribute/ > > "... you have to ... update your

Bug#901900: dgit in stretch-backports

Hi Sean, Sean Whitton wrote: > On Fri, Jun 22 2018, Jonathan Nieder wrote: >> Do you plan to update dgit in backports once it hits testing? > > Yes. Excellent, thank you. [...] >> Is there anything I can do to help? For example, should I prepare an >> upload for 4

Bug#901900: dgit in stretch-backports

Ian Jackson wrote: > Jonathan Nieder writes ("Bug#901900: dgit in stretch-backports"): >> Once git 2.18.0 is in testing, I want to update the git package in >> stable-backports. This would require updating dgit as well to a >> version that supports the working-tr

Bug#901900: dgit in stretch-backports

Hi Sean et al, Once git 2.18.0 is in testing, I want to update the git package in stable-backports. This would require updating dgit as well to a version supports the working-tree-encoding attribute (https://bugs.debian.org/901900). Do you plan to update dgit in backports once it hits testing?

Bug#901900: git introduces new hazardous working-tree-encoding attribute

Ian Jackson wrote: > 5.1 is ready and has passed all its tests. It works fine with the git > in sid. I am not able to upload it right now, but this will happen > later today. Thanks. $ git ls-remote git://git.chiark.greenend.org.uk/~ianmdlvl/dgit.git fatal: Could not read from remote reposit

Bug#901897: git introduces new hazardous working-tree-encoding attribute

Hi Ian, My mail host appears to be blacklisted on your end: > There was a problem delivering your message to > ijack...@chiark.greenend.org.uk. See the technical details below, or > try resending in a few minutes. > > The response was: > 550 Blacklisted site `[74.125.83.53]' [Irritated] What is

Bug#901897: git introduces new hazardous working-tree-encoding attribute

severity 851679 wishlist tags 851679 + upstream clone 901897 -1 retitle -1 dgit fails autopkgtest: true/false are no valid working-tree-encodings reassign -1 dgit 5.0 retitle 901897 git needs Breaks against dgit versions without working-tree-encoding support block 901897 by -1 quit Hi Ian, Ian

Bug#901185: Checkbashisms

Hi, 積丹尼 wrote: Be sure the package passes Checkbashisms! > Which package? Is there a particular bashism you noticed? Please keep in mind that these reports appear as emails in a crowded inbox, where a little context in the subject line can go a long way. Thanks, Jonathan >

Bug#900393: runit 2.1.2-14 breaks git-daemon-run

Package: runit Version: 2.1.2-14 Severity: serious Justification: breaks upgrades The changelog to runit 2.1.2-14 explains: * Do not install `update-service' script. but it doesn't give any more context than that. This breaks the git-daemon-run package, as noticed e.g. by piuparts: https:

Bug#895446: gitk: Error in startup script: bad screen distance "4.5"

reassign 895446 libfontconfig1 2.13.0-2 severity 895470 serious retitle 895470 fontconfig-2.13.0 globally sets the locale from the environment forcemerge 895470 895446 affects 895470 + gitk tags 895470 + patch fixed-upstream quit Jonathan Nieder wrote: > Michael Biebl wrote: >> gitk

Bug#895446: gitk: Error in startup script: bad screen distance "4.5"

tags 895446 + moreinfo quit Hi Michael, Michael Biebl wrote: > gitk no longer successfully starts here. When I run it from a terminal, > I get > > $ gitk > Error in startup script: bad screen distance "4.5" > while executing > "$canv conf -scrollregion [list 0 0 $canvxmax $ymax]" > (proc

Bug#892488: pcre2: FTBFS on mips* - test failures

Hi, Matthew Vernon wrote: > On 09/03/18 15:20, James Cowgill wrote: >> Source: pcre2 >> Version: 10.31-1 >> Severity: serious [...] >> pcre2 FTBFS on mips* with lots of testsuite failures. It looks to me >> like the JIT is bust. >> >> I forwarded the log upstream to the above address. I'll try to

Bug#884038: [git] 2.15.x fails to fetch remote repository

# regression but not reproducible severity 884038 important tags 884038 + upstream unreproducible quit Hi, mirq-debo...@rere.qmqm.pl wrote: > git 2.15.x from testing can't properly fetch from remote repository: > > $ git fetch --all > Fetching origin > remote: Counting objects: 752, done. > remo

Bug#871570: git FTBFS on i386: t7006-pager.sh test failure

found 871570 git/1:2.13.2-3 tags 871570 + upstream quit Hi, Adrian Bunk wrote: > https://buildd.debian.org/status/fetch.php?pkg=git&arch=i386&ver=1%3A2.14.0-1&stamp=1502132890&raw=0 > > ... > expecting success: > ( > sane_unset LESS LV && > PAGER="env >pager-en

Bug#868738: git FTBFS on several architectures: not ok 134 - --dump-aliases must be used alone

Hi, Adrian Bunk wrote: > https://buildd.debian.org/status/package.php?p=git&suite=sid > > expecting success: > test_must_fail git send-email --dump-aliases --to=jan...@example.com -1 > refs/heads/accounting > > --dump-aliases incompatible with other options > test_must_fail: command not f

Bug#860774: openldap on armhf and armel needs bootstrapping

Ryan Tandy wrote: > Debian Bug Tracking System wrote: >> Bug #860774 [libldap-2.4-2] relax dependency on libldap-common >> Added indication that 860774 affects src:git, src:heimdal, and src:subversion > > It will be a few more hours before I can get to an upload, so if > this is blocking others' w

Bug#866059: Please remove the git-arch package

severity 866059 important tags 866059 + pending quit Hi Adrian, Adrian Bunk wrote: > Severity: serious Why? > Already for a couple of years, the only realistic usecase > for the tla package in Debian was to allow git-arch to > migrate repositories to git. > > The final release of GNU Arch was

Bug#818318: git: CVE-2016-2324 and CVE-2016-2315 (currently unpublished) server and client RCE

On Thu, Mar 17, 2016 at 12:37:27AM +, Ben Hutchings wrote: > On Wed, 2016-03-16 at 17:16 -0700, Jonathan Nieder wrote: >> Ben Hutchings wrote: >>> I intend to NMU git to fix these bugs in unstable, as they make most of >>> my development activity unsafe. >>>

Bug#818318: git: CVE-2016-2324 and CVE-2016-2315 (currently unpublished) server and client RCE

Ben Hutchings wrote: > I intend to NMU git to fix these bugs in unstable, as they make most of > my development activity unsafe. > > git maintainers, please let me know if you're already preparing an > update. I'm already preparing an update. Jonathan

Bug#801046: git: "Out of memory, malloc failed" cloning certain repos

tags 801046 + moreinfo quit Hi Lenz, PICCORO McKAY Lenz wrote: > Version: 1:1.7.10.4-1+wheezy1 > Severity: grave I am able to use git. Are you sure the package is actually unusable? For example, do commands like "git init" work? [...] > Current version of git for wheeze and squeeze are unusab

Bug#774607: git: diff for NMU version 1:2.1.4-2.1

Niels Thykier wrote: > I've prepared an NMU for git (versioned as 1:2.1.4-2.1) and > uploaded it to DELAYED/2. Thanks. Could you bump it to DELAYED/0? Regards, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listm

Bug#774607: gitweb breaks apache upgrade

(dpkg -> bcc) Niels Thykier wrote: > Any updates on this bug? The gitweb trigger cycle is currently the last > trigger cycle left[1]. It should be interest-noawait. I was preparing an upload to do that, but other things preempted that :/. I will try to make the upload tonight and don't mind if

Bug#774607: gitweb breaks apache upgrade

Guillem Jover wrote: > In this case though, it seems switching to interest-noawait is the > correct fix, because gitweb just wants to be notified when the > apache2-maintscript-helper program appears to be able to configure > itself, but apache does not care and does not need to await the > trigge

Bug#774803: gitweb: dpkg trigger cycle via apache2

Hi Niels, Niels Thykier wrote: > Debian `dpkg' package management program version 1.17.23 (amd64). [...] > chain of packages whose triggers are or may be responsible: > gitweb -> gitweb > packages' pending triggers which are or may be unresolvable: > gitweb: /usr/share/apache2/apache2-maint

Bug#774607: gitweb breaks apache upgrade

reassign 774607 dpkg 1.7.22 affects 774607 + gitweb src:git forcemerge 771730 774607 quit Jonathan Nieder wrote: > Erwan David wrote[1]: >> dpkg: cycle found while processing triggers: >> chain of packages whose triggers are or may be responsible: >> gitweb -> gitw

Bug#774607: gitweb breaks apache upgrade

Hi dpkg maintainers, Erwan David wrote[1]: > Package: gitweb > Version: 1:2.1.4-2 > Severity: normal > > When upgrading apache and gitweb I get : > > dpkg: cycle found while processing triggers: > chain of packages whose triggers are or may be responsible: > gitweb -> gitweb > packages' pendi

Bug#770655: git FTBFS: failure in t9500-gitweb-standalone-no-errors.sh

Reiner Herrmann wrote: > --- /dev/null > +++ b/debian/patches/gitweb_cgi_param.patch Patches go in debian/diff/. I can take care of an upload to fix this bug and #768795 this week. Advice on #669292 would be welcome. Currently the gitweb package is essentially useless. gitweb itself is part o

Bug#765525: gitweb broken by libcgi-pm-perl 4.06-1

Jonathan Nieder wrote: > * gitweb: use start_form instead of startform for compatibility >with CGI.pm 4.04 and newer (thx Roland Max; closes: #765525). Gah. I've fixed the spelling in this changelog entry in the development repo, so it should be back to sanity in the

Bug#767960: gitweb: no longer works: Undefined subroutine CGI::startform

log w/debian/changelog index e2cf1d9..1e527d2 100644 --- i/debian/changelog +++ w/debian/changelog @@ -1,3 +1,10 @@ +libcgi-pm-perl (4.09-1.1) local; urgency=low + + * Add Breaks against versions of git in which gitweb and 'git instaweb' +use the startform function. + + -- Jonathan Nieder

Bug#758675: metis: GKlib/random.c is missing license grant

Source: metis Version: 5.1.0.dfsg-3 Severity: serious Justification: undistributable Tags: upstream Hi Anton et al, The copyright file of metis says the following is the license for GKlib/random.c: Copyright 2004, Makoto Matsumoto and Takuji Nishimura THIS SOFTWARE IS PROVIDED B

Bug#538822: dash fails to upgrade if /bin/sh is locally diverted

reopen 538822 # difficult, invasive severity 538822 wishlist tags 538822 = quit Hi, Niels Thykier wrote: > I am taking the liberty of closing this bug, because: > 1) there is no sign of progress in this bug for the past 1-and-a-half > 2) there is no sign of desire/need for being able to locall

Bug#750687: "git status" becomes fork-bomb if a submodule's .git directory is not accessible

severity 750687 important quit Hi, Axel Beckert wrote: > Axel Beckert wrote: >> I couldn't willingly reproduce it yet outside the setup where I ran >> into that issue, > > Here's how to reproduce: Yay! Thanks for this. [...] > Control: severity -1 grave [...] > Since I consider such a setup

Bug#750687: "git status" becomes fork-bomb under some circumstances

Hi, Axel Beckert wrote: > 10/0/0 root@acromantula:pts/4 18:53:47 [~] # ps auxwwwf | fgrep git > abe 11352 77.1 0.0 4552 596 pts/2R+ 18:53 0:10 | > | \_ strace -f -e fork git status > abe 11353 6.3 0.1 24632 6848 pts/2S+ 18:53 0:00 |

Bug#748387: liblockfile: missing debian/copyright

severity 748387 important quit Cyril Brulebois wrote: > Jonathan Nieder (2014-05-16): >> Source: liblockfile >> Version: 1.09-6 >> Severity: serious >> Justification: policy 4.5 > > What you're talking about is a 'should' in Policy 12.5; doesn&#x

Bug#748387: liblockfile: missing debian/copyright

Source: liblockfile Version: 1.09-6 Severity: serious Justification: policy 4.5 In liblockfile 1.09-6: $ ls debian/ changelog control liblockfile-bin.overrides patches postinst postrm rules shlibs source $ tar -tf ../liblockfile_1.09-6.debian.tar.bz2 debian/ debian/control debian/so

Bug#745646: chromium: certificate revocation is not checked

Hi, Giuseppe Iuculano wrote: > On 30/04/2014 19:49, Vincent Lefevre wrote: >> Bug 745646 is a different bug, specifically about the CRLSet system, >> which is very broken. > > What you write is not a bug, if you want to do revocation check you must > enable it in settings. However Vincent is rig

Bug#669292: RFH: updating gitweb packaging for Apache 2.4

Hi, With Apache 2.2, the gitweb package worked out of the box. With Apache 2.4, it doesn't. http://bugs.debian.org/669292 tracks this problem. Last year, I tried to fix it --- patch at https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=23;filename=update-apache-packaging.patch;att=1;bug=669292

Bug#737232: git upgrade breaks gitolite 2

Package: git Version: 1:1.9~rc1-1 Severity: serious Justification: broken upgrade Control: block -1 by 737174 In the 1.9-rc series, Git has a 2-component instead of 3-component version number for the first time, breaking gitolite 2 (but not gitolite 3). http://bugs.debian.org/737174 has details.

Bug#735746: pillow: FTBFS: _imagingtk.cpython-33m.so not found

tags 735746 + pending quit Hi Matthias, Jonathan Nieder wrote: > + * Adjust installation rules for python3 extensions to include multiarch > +tag. Closes: #735746. > + * Build-conflict on python3.3 (<< 3.3.3-5). I've uploaded this fix to DELAYED/2. If I should cance

Bug#735746: pillow: FTBFS: _imagingtk.cpython-33m.so not found

11 insertions(+), 1 deletion(-) diff --git a/debian/changelog b/debian/changelog index f921140..e16d960 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +pillow (2.2.1-3.1) local; urgency=medium + + * Adjust installation rules for python3 extensions to include multiarch +tag. C

Bug#736144: python-webm: needs update for libwebp5

:30.0 -0700 +++ python-webm-0.2.2/debian/changelog 2014-01-23 16:36:25.0 -0800 @@ -1,3 +1,10 @@ +python-webm (0.2.2-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Rebuild for libwebp transition (Closes: #736144) + + -- Jonathan Nieder Thu, 23 Jan 2014 16:36:23 -0800 +

Bug#735336: git-svn fails 'tempfile' can't be called as a method at /usr/share/perl5/Git.pm line 1042.

James Michael DuPont wrote: > Using the freshly built version the problem does not occur : > git version 1.8.5.3.321.g14598b9 Weird. I don't think there's been a change that should have fixed it. Does 1.8.5.2 from testing or sid (putting /usr/bin earlier in $PATH again) still reproduce the prob

Bug#735336: git-svn fails 'tempfile' can't be called as a method at /usr/share/perl5/Git.pm line 1042.

James Michael DuPont wrote: > This is with : Gerrit Code Review (2.7) > No shallow clones. Using git review to make the most basic changes. > It seems to be all the time when I want to update an existing changes. > Yes, I am able to build native version, debs and

Bug#735336: git-svn fails 'tempfile' can't be called as a method at /usr/share/perl5/Git.pm line 1042.

James Michael DuPont wrote: > Well I started to use gerrit and got this problem, using the newest version > of git 1.8 something that is why i had to downgrade. What Gerrit version? Does it happen only some of the time, or 100% of the time when you try to push changes of a certain kind? Are you

Bug#735336: git-svn fails 'tempfile' can't be called as a method at /usr/share/perl5/Git.pm line 1042.

Jonathan Nieder wrote: > James Michael DuPont wrote: >> I am forced to use an older version of git because of the problems with >> gerrit. >> http://stackoverflow.com/questions/16586642/git-unpack-error-on-push-to-gerrit >> >> That is why I instlled the older ver

Bug#669292: gitweb: automatic configuration breaks with apache2 2.4

Jonathan Nieder wrote: > As described at [1], apache's scheme for supporting webapps has > changed a little. [2] describes what we need to do. Here's a start. Thoughts welcome, as always. From: Jonathan Nieder Date: Thu, 2 Jan 2014 16:22:17 -0800 Subject: debian/gitweb: ada

Bug#709947: closed by ty...@mit.edu (Theodore Y. Ts'o) (Bug#708307: fixed in e2fsprogs 1.42.8-1)

Hi, Theodore Ts'o wrote: > We have a minor problem with uploading a fix. E2fsprogs currently > FTBFS on stable, due to bug #707996, whose root cause is #708061. > > Personally, I blame glibc (#708061) for once again making a > library-visible API change. (If they didn't want programs to use >

Bug#718655: [kfreebsd] git FTBFS: hang in tests

tags 718655 + unreproducible quit Jonathan Nieder wrote: > From the build log on fano (kfreebsd-amd64): [...] > make[3]: *** [t5523-push-upstream.sh] Error 1 > make[3]: *** Waiting for unfinished jobs > E: Caught signal ‘Terminated’: terminating immediately > make

Bug#718655: [kfreebsd] git FTBFS: hang in tests

Source: git Version: 1:1.8.4~rc1-1 Severity: serious Justification: build failure From the build log on fano (kfreebsd-amd64): ok 16 - push --no-progress suppresses progress not ok 17 - quiet push # # ensure_fresh_upstream && # # test_terminal git push --quiet --no

Bug#718654: [kfreebsd] "git grep" often segfaults

Package: git Version: 1:1.8.3~rc3-1 Severity: serious Justification: build failure Hi, A test failure story. "git grep" compiles a bunch of copies of a regex and then executes them in different threads. Git 1:1.8.3~rc3-1 failed to build on both 32-bit and 64-bit GNU/kFreeBSD. 1:1.8.3~rc2-1 buil

Bug#692884: guilt conflicts with git 1.8

tags 692884 + upstream fixed-upstream quit Axel Beckert wrote: >> Thomas Koch wrote: >>> I'm not aware of any changes in Git 1.8 that could make guilt >>> incompatible. [...] > I intend to NMU this issue via the DELAYED/N queue. Patch will be > based on Jonathan Nieder's suggestion in http://bugs

Bug#709382: Built-Using, libgcc, and libc_nonshared

Russ Allbery wrote: >mksh-static of > course links statically and therefore pulls in substantial portions of > library source, but there are parts of libgcc and possibly libc that are > always incorporated into binaries, even ones that are dy

Bug#707306: libc6: unable to upgrade to 2.17 getting errors while configuring

Hi, shirish शिरीष wrote: > A copy of the C library was found in an unexpected directory: > '/lib/libdl-2.11.2.so' [...] > I removed the offending library copy as well as the original, quite a > few of them before I was able to correctly install it without any > errors :- Where did these files

Bug#706400: git: FTBFS on some arches: t4205 fails

Source: git Version: 1:1.8.3~rc0-1 Severity: serious Justification: ftbfs Tags: upstream patch Control: forwarded -1 http://thread.gmane.org/gmane.comp.version-control.git/222680 >From https://buildd.debian.org/status/logs.php?pkg=git&ver=1%3A1.8.3~rc0-1: | expecting success: | git log --

Bug#703092: dpkg --set-selections ignores available packages never installed or removed by dpkg

severity 703092 important quit Hi, Norbert Preining wrote: > [Subject: setting this to critical] Please keep in mind that these appear as emails in a crowded inbox, where a subject line can provide valuable context. > It might look harmless, but we do *NOT* want to release Debian > with a dpkg

Bug#704498: git: FTBFS on a random selection of arches

Jonathan Nieder wrote: > Based on <https://buildd.debian.org/status/logs.php?pkg=git&ver=1%3A1.8.2-1>, > it seems that the git 1:1.8.2-1 build is unreliable. hurd-i386: *** t5500-fetch-pack.sh *** ok 1 - setup ok 2 - 1st pull ok 3 - post 1st pull

Bug#704498: git: FTBFS on a random selection of arches

Source: git Version: 1:1.8.2-1 Severity: serious Justification: ftbfs Tags: patch Hi, Based on , it seems that the git 1:1.8.2-1 build is unreliable. The most relevant seeming recent change was enabling parallel build. Here's a

Bug#703468: [3.2.35-2 -> 3.2.39-1 regression] fails to boot on apple iMac

found 703468 linux/3.2.41-2 quit Jonathan Nieder wrote: > I think a good place to start would be to try 3.2.41-2 from unstable, > since it includes some i915 fixes. Ah, looking back over the log I see that's been tried. So: > A good next step would be to try 3.8.y from experi

Bug#703468: [3.2.35-2 -> 3.2.39-1 regression] fails to boot on apple iMac

Hi, Michael Gilbert wrote: >> The following string is still recognizable: >> i915_gem_init_ppgtt+0x93/0x16c [i915] > > This is going to take some work on your end to get fixed. 3.2.39-1 > included backported patches from aspects of the i915 driver. I think a good place to start would be to try

Bug#699937: [wheezy] crash caused by disconnecting usb audio device

forcemerge 696321 699937 quit Hi Mark, Mark A. Hershberger wrote: > If I remove the USB headset while sound is playing, the screen goes > blank and a kernel trace is displayed. Please attach a photograph of the kernel trace. Thanks for writing and sorry for the trouble, Jonathan -- To UNSUB

Bug#699218: procps: FTBFS with test suite error: testsuite/lib.test/fileutils_badfd.sh missing

Hi, Craig Small wrote: > On Tue, Jan 29, 2013 at 09:22:59AM +0100, Sascha Silbe wrote: >> ERROR: couldn't execute >> "/home/sascha.silbe/src/deb/procps-3.3.3/testsuite/lib.test/fileutils_badfd.sh": >> no such file or directory > > This file now appears in procps 3.3.6 I'm not sure why you trigg

Bug#699177: Wrong sorting in pathname expansion

retitle 699177 dash ignores locale tags 699177 + upstream # standards compliance, i18n severity 699177 important quit Hi Alexander, Alexander Gerasiov wrote: > If the pattern matches any existing filenames or pathnames, the pattern > shall be replaced with those filenames and pathnames, sorted a

Bug#691180: connman: Connman won't run due to missing libxtables.so.7

Julien Cristau wrote: > On Sat, Jan 26, 2013 at 07:04:16 -0800, Jonathan Nieder wrote: >> Julien Cristau wrote: >>> NAK. iptables in sid needs to add Breaks on the packages in wheezy that >>> want libxtables.so.7. And 691180 should be reassigned to iptables. [..

Bug#691180: connman: Connman won't run due to missing libxtables.so.7

reassign 691180 iptables 1.4.14-3 affects 691180 + connman quit Hi Julien, Julien Cristau wrote: > On Thu, Jan 24, 2013 at 01:22:21 -0800, Jonathan Nieder wrote: >> In wheezy, there is instead an unversioned dependency on iptables, >> which is not enough to ensure the correct sh

Bug#691180: connman: Connman won't run due to missing libxtables.so.7

Adam D. Barratt wrote: > On 24.01.2013 09:22, Jonathan Nieder wrote: >> Fixing this properly would presumably require an iptables update in >> testing (either bumping shlibs or, better, backporting the >> introduction of a separate libxtables9 package from sid) fo

Bug#691180: connman: Connman won't run due to missing libxtables.so.7

found 691180 connman/1.0-1.1+wheezy1 fixed 691180 connman/1.0-1.2 quit Hi Adrian, John Paul Adrian Glaubitz wrote: > close 691180 > thanks > > Hi, > > there have been new uploads of connman both into testing and unstable, > the issue has been resolved as the package has been rebuilt in both > ca

Bug#697085: qemu-system: tries to overwrite doc/qemu/qemu-doc.html from qemu (missing Breaks+Replaces?)

Michael Tokarev wrote: > We believe that the bug you reported is fixed in the latest version of > qemu, which is due to be installed in the Debian FTP archive. Thanks. [...] > qemu (1.3.0+dfsg-2exp) experimental; urgency=low [...] >* move vde2 from Recommends to Suggests, since it isn't >

Bug#698259: guilt: Maintainer address does not accept mail

, 15 Jan 2013 18:31:44 -0800 From: Jonathan Nieder To: Josef 'Jeff' Sipek Cc: g...@vger.kernel.org, Per Cederqvist , Theodore Ts'o , Iulian Udrea , Axel Beckert Subject: [GUILT] [PATCH 7/7] Drop unneeded git version check. Message-ID: <20130116023144.gp12...@goog

Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze

Hi Paul, Paul C wrote: > I think I am having the same issue here with Ivy Bridge. [...] > I've followed this thread through trying out various different options with > boot parameters (mtrr) and also have now got the system on the Liquorix > 3.7.x kernel. Same crashes. That doesn't match Per's e

Bug#696909: chromium segfaults on startup on armhf

Hi Peter, peter green wrote: > Patch to make the package use bfd rather than gold on armel and armhf is > attached. I may or may not upload this as a NMU. If you'll have time to continue working on chromium:arm in the future, it would probably be better to just add yourself to pkg-chromium on al

Bug#697085: qemu-system: tries to overwrite doc/qemu/qemu-doc.html from qemu (missing Breaks+Replaces?)

# uninstallable severity 697085 grave quit Jonathan Nieder wrote: > | Preparing to replace qemu-system 1.3.0+dfsg-1~exp1 (using > .../qemu-system_1.3.0+dfsg-1~exp3_amd64.deb) ... > | Unpacking replacement qemu-system ... > | dpkg: error processing > //var/cache/apt/archives/qe

Bug#697085: qemu-system: tries to overwrite doc/qemu/qemu-doc.html from qemu (missing Breaks+Replaces?)

Package: qemu-system Version: 1.3.0+dfsg-1~exp1 Severity: serious Justification: failed upgrade >From today's upgrade: | Preparing to replace qemu-system 1.3.0+dfsg-1~exp1 (using .../qemu-system_1.3.0+dfsg-1~exp3_amd64.deb) ... | Unpacking replacement qemu-system ... | dpkg: error processing //

Bug#686502: pxz produces archives broken for busybox's unxz

Abou Al Montacir wrote: > Hover, I assume we can save this extra code as soon as we don't loose > data. That's fine with me. All you'd need to do is error out if there is anything after the first stream. That would make it a conformant decoder and prevent silent data loss, though it would mean

Bug#686502: pxz produces archives broken for busybox's unxz

Abou Al Montacir wrote: > On Sat, 2012-12-22 at 10:21 -0800, Jonathan Nieder wrote: >> What happens if a stream ends at a buffer boundary, followed by >> padding? Or if padding doesn't fit in the buffer, for that >> matter? [...] > Please find attached new debdif

  1   2   3   4   5   6   7   8   >