** Summary changed:
- Merge git 1:2.16.3-1 (main) from Debian unstable (main)
+ Merge git 1:2.17.0-1 (main) from Debian unstable (main)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748984
Title:
** Summary changed:
- Merge git 1:2.16.2-1 (main) from Debian unstable (main)
+ Merge git 1:2.16.3-1 (main) from Debian unstable (main)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748984
Title:
Ping. As described in https://lists.ubuntu.com/archives/ubuntu-
devel/2017-December/040080.html, I'm happy to help with making git
consumable by Ubuntu on the Debian side in any way I can. Is there
anything I can do to help?
--
You received this bug notification because you are a member of
Ping. 2.16.2 is now available as well.
** Summary changed:
- Merge git 1:2.16.1-1 (main) from Debian unstable (main)
+ Merge git 1:2.16.2-1 (main) from Debian unstable (main)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
/usr/share/doc (thx Paul Wise and Bastien Roucaries for suggesting
it through lintian).
-- Jonathan Nieder <jrnie...@gmail.com> Mon, 05 Feb 2018 12:27:37
-0800
git (1:2.15.1-3) unstable; urgency=low
* debian/rules: remove remnants of git-core package that prevented
buildi
Ping. Is there anything blocking this merge?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729075
Title:
Merge git 1:2.15.1-3 (main) from Debian unstable (main)
To manage notifications about this
Lacking further information, I don't see anything we can do about this
bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736094
Title:
git pull throws error : cannot fork() git credentials :
** Summary changed:
- Merge git 1:2.15.1-2 (main) from Debian unstable (main)
+ Merge git 1:2.15.1-3 (main) from Debian unstable (main)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729075
Title:
Do you have overcommit disabled?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736094
Title:
git pull throws error : cannot fork() git credentials : cannot
allocate memory
To manage
Also, do you have a reproduction recipe?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736094
Title:
git pull throws error : cannot fork() git credentials : cannot
allocate memory
To manage
** Summary changed:
- Merge git 1:2.15.0-1 (main) from Debian unstable (main)
+ Merge git 1:2.15.1-2 (main) from Debian unstable (main)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729075
Title:
@xnox: your comment is probably a better fit for
https://bugs.launchpad.net/ubuntu/+source/pcre2/+bug/163. This bug
is about git being out of date in bionic and appears to be fixed by
https://bugs.launchpad.net/ubuntu/+source/git/1:2.15.1-1ubuntu1.
--
You received this bug notification
Example where this would be useful:
https://bugs.launchpad.net/ubuntu/+source/git/+bug/1729075/comments/5
In Debian, we are able to use architecture qualification on build-
dependencies to set different build-deps for each target environment.
This feature would allow doing the same when a package
For
https://bugs.launchpad.net/ubuntu/+source/git/+bug/1729075/comments/5, a
'nopcre2' build profile would be good enough and would follow the spirit
of
https://wiki.debian.org/BuildProfileSpec#Derivative_specific_profiles.
--
You received this bug notification because you are a member of Ubuntu
Ping. Any changes you're waiting for in the Debian package before
merging?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729075
Title:
Merge git 1:2.15.0-1 (main) from Debian unstable (main)
To
> There is one other issue: Debian's pcre2 isn't really using what I
consider "best practice" packaging [specifically, it does not use source
format 3.0 (quilt) ] which makes doing security updates more of a pain
That's tracked at https://bugs.debian.org/862425 (thanks for filing
it!). I can look
> My understanding is that dependency resolution on the build server is unaware
> of the universe vs.
> main distinction. 2.14.0-1 was successfully built in artful-proposed
>(https://launchpad.net/ubuntu/+source/git/1:2.14.0-1), but was then blocked
>upon migration to
> artful by some separate
> To mirror what doko mentioned earlier, what is needed to demote pcre3?
Can we start (even a long running) transition? (So there should be a
tracker setup for that).
Sounds good to me. What's the process for making that happen?
Keep in mind that since pcre2 is a new API and ABI, packages will
** Attachment added: "pcre3 symbols"
https://bugs.launchpad.net/ubuntu/+source/pcre2/+bug/163/+attachment/5001389/+files/libpcre.so.3.dynsym
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On the subject of the relationship between pcre3 (the older one) and
pcre2 (the newer one):
$ eu-readelf -s.dynsym /usr/lib/x86_64-linux-gnu/libpcre2-8.so.0 |grep -v UNDEF
>/tmp/libpcre2-8.so.0.dynsym
$ eu-readelf -s.dynsym /lib/x86_64-linux-gnu/libpcre.so.3 |grep -v UNDEF
Thanks. https://bugs.launchpad.net/ubuntu/+source/pcre2/+bug/163 is
open for that.
Is there e.g. a build log illustrating why the
libpcre2-dev | libpcre3-dev,
in Build-Depends is not working? Would using build profiles to select
the pcre version help Ubuntu to avoid having to fork?
--
** CVE removed: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-14867
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729075
Title:
Sync git 1:2.15.0-1 (main) from Debian unstable (main)
To
Public bug reported:
Ubuntu's git package is unnecessarily forked from Debian. As a result,
the package is out of date. Please sync with Debian.
** Affects: git (Ubuntu)
Importance: Undecided
Status: New
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-14867
--
Ubuntu changelog:
> * Build against pcre v3 only, as that is the only on in
> main. Non-deterministic builds w.r.t. library ABI dependencies are
> bad.
Please feel free to file a bug at https://bugs.debian.org/src:git with
more details. Library ABI dependencies depending on the
Thanks. Is there a reason zesty has custom security patches instead of
reusing the work from Debian stretch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710016
Title:
Please update Git to get
+linkcve doesn't like the shape of 2017-1000117 or CVE-2017-1000117 so I
can't link it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710016
Title:
Please update Git to get the fix to
*** This bug is a security vulnerability ***
Public security bug reported:
A security bugfix was released today to Git: https://public-
inbox.org/git/xmqqh8xf482j@gitster.mtv.corp.google.com/T/#u.
Without it, cloning an attacker-controlled ssh:// URL (either directly
or indirectly via
Debian bug: http://bugs.debian.org/860927
** Bug watch added: Debian Bug tracker #860927
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860927
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
2.7.4 has the fixes you're looking for.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1557787
Title:
client/server RCEs in path_name()
To manage notifications about this bug go to:
*** This bug is a security vulnerability ***
Public security bug reported:
Please sync git 1:2.6.1-1 to fix http://www.openwall.com/lists/oss-
security/2015/10/06/1
** Affects: git (Ubuntu)
Importance: Undecided
Status: New
** Information type changed from Private Security to
** Bug watch added: Debian Bug tracker #669292
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669292
** Also affects: git (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669292
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
Public bug reported:
Anders Kaseorg reports[1]:
I noticed this warning while building git-doc:
ASCIIDOC technical/api-hashmap.html
/bin/sh: 1: source-highlight: not found
asciidoc: WARNING: api-hashmap.txt: line 218: filter non-zero exit code:
source-highlight -f xhtml -s c: returned 127
I assume this should be reopened now that 9756fe3 has been reverted
upstream?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064924
Title:
Please add LVDS quirk for the zotac zbox
To manage
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/806248
Title:
unity::TimeUtil::TimeDelta returns an int value which overflows after
24 days of uptime
To manage notifications
According to the description presented in the web UI, Invalid means Not
a bug. May be a support request or spam. Perhaps you misread the
request or meant won't fix.
I've updated the description to explain how it relates to the SRU
guidelines.
Thanks for looking it over,
Jonathan
** Description
Public bug reported:
Hi,
Updating git from lucid to precise brings in the change
6b67e0dc068d fetch: verify we have everything we need before updating
our ref
which caused a speed regression:
http://thread.gmane.org/gmane.comp.version-
control.git/191626/focus=193228
The fix is
How about just
d21c463d558a fetch/receive: remove over-pessimistic connectivity check
then? It is obviously safe and affects the git toolset, not critical
infrastructure.
** Changed in: git (Ubuntu)
Status: Invalid = New
--
You received this bug notification because you are a member
Reminiscent of the infamous Dell VT-d reboot bug:
https://bugzilla.kernel.org/show_bug.cgi?id=42542
** Bug watch added: Linux Kernel Bug Tracker #42542
http://bugzilla.kernel.org/show_bug.cgi?id=42542
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This was fixed upstream last year by http://git.debian.org/?p=collab-
maint/xz.git;h=6db1c35b; maverick includes the fixed version. Thanks to
Eleanor for a pointer.
--
String not translatable in the translation template xz-utils
https://bugs.launchpad.net/bugs/552796
You received this bug
Martin Pitt wrote:
Hm, none of the new features and packaging details seem urgent to have
to me?
Nor to me, for what it’s worth. (The requester can probably say more
about why it was important to him.)
By contrast, yesterday there was an interesting upstream patch [1]:
Fix missing
Martin Pitt wrote:
As for the lucid sync, does it introduce any new features, ABI changes,
etc.?
Yes.
ABI and API: The low-level API for examining a compressed file’s Index
information has been improved. See the 4.999.9beta+20100117-1 changelog
entry for details. The soname was bumped, but
I assume the Ubuntu release team should be unsubscribed, too, but I
don’t know how.
Thanks for the explanation. I don’t have much time for it and don’t have
an Ubuntu system to test on, but for anyone interested, the relevant
changes are:
- Edit debian/copyright to describe the actual license
Scott Kitterman wrote:
KDE in Karmic uses XZ for lzma support. I use it fairly frequently for
decompressing lzma .debs without apparent problems. If it were updated,
KDE 4.3 would need porting to the new ApI.
For what it’s worth, the only porting involved here is rebuilding (or
at least
Scott Kitterman wrote:
KDE in Karmic uses XZ for lzma support. I use it fairly frequently for
decompressing lzma .debs without apparent problems.
Thanks for the comment. That is what I am most afraid of.
If xz-utils is upgraded to the version in testing, the upgraded
xz-utils would not
Public bug reported:
Binary package hint: xz-utils
Hi,
The experimental xz-utils package currently used in Karmic cannot be
installed in apt-get and has a number of other serious problems making
it unusable in my opinion. A few months ago, I requested a sync [1] for
those reasons; thanks for
I forgot to mention: newer versions of XZ Utils of course also have
various minor API changes, new translatable strings, and new command
line options, so I assume this would require a freeze exception or
someone back-porting the packaging changes only.
If neither of those happen, could you remove
This is a grave problem in xz-utils in karmic, but it should be already
fixed in lucid. Please let me know if that is not the case.
--
Installing xz-utils: You are about to do something potentially harmful.
https://bugs.launchpad.net/bugs/426086
You received this bug notification because you
Fixed upstream by commit 38b8035b (Add a missing space to an error
message, 2010-01-26).
** Changed in: xz-utils (Ubuntu)
Status: Incomplete = Confirmed
--
Typo
https://bugs.launchpad.net/bugs/511593
You received this bug notification because you are a member of Ubuntu
Bugs, which is
48 matches
Mail list logo
