The verification of the Stable Release Update for ubuntu-dev-tools has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you en
Public bug reported:
src:ubuntu-dev-tools 0.193ubuntu4~20.04.2 regressed behaviour in how
python3-ubuntutools downloads source packages from Launchpad. This is
currently breaking the git-ubuntu importer, causing it to fail to update
repositories for some packages, since the git-ubuntu snap is base
Also reproduced on Mantic with 0.193ubuntu4.
** Also affects: ubuntu-dev-tools (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: ubuntu-dev-tools (Ubuntu)
Importance: Critical => Medium
** Changed in: ubuntu-dev-tools (Ubuntu Focal)
Status: New => Triaged
** Ch
It seems that python3-ubuntutools switched from using
urllib.request.urlopen() to requests.get() when fetching sources using
the pull() method. For the sake of providing a progress bar, both the
old code and the new code "streamed" the data by asking for chunks at a
time, incrementally saving those
Also relevant is https://git.launchpad.net/ubuntu-dev-
tools/commit/ubuntutools/misc.py?id=1e2036399e535c939c6e581259e5aa9fdae99f27
which explicitly swapped raw access for the purposes of decoding.
--
You received this bug notification because you are a member of MOTU,
which is subscribed to ubun
> I don't see a way of getting the requests library to handle transfer
encoding but not content encoding without using undocumented API. As far
as I can tell, the raw attribute would give me neither.
Digging into this much deeper, the handling of transfer encoding doesn't
seem to be documented any
** Changed in: ubuntu-dev-tools (Ubuntu)
Assignee: (unassigned) => Robie Basak (racb)
** Changed in: ubuntu-dev-tools (Ubuntu Focal)
Assignee: (unassigned) => Robie Basak (racb)
** Changed in: ubuntu-dev-tools (Ubuntu)
Status: Triaged => In Progress
** Changed in: u
** Description changed:
src:ubuntu-dev-tools 0.193ubuntu4~20.04.2 regressed behaviour in how
python3-ubuntutools downloads source packages from Launchpad. This is
currently breaking the git-ubuntu importer, causing it to fail to update
repositories for some packages, since the git-ubuntu s
** Description changed:
+ [Impact]
+
src:ubuntu-dev-tools 0.193ubuntu4~20.04.2 regressed behaviour in how
python3-ubuntutools downloads source packages from Launchpad. This is
currently breaking the git-ubuntu importer, causing it to fail to update
repositories for some packages, since th
Progress
** Changed in: ubuntu-dev-tools (Ubuntu Jammy)
Assignee: (unassigned) => Robie Basak (racb)
** Changed in: ubuntu-dev-tools (Ubuntu Kinetic)
Assignee: (unassigned) => Robie Basak (racb)
** Changed in: ubuntu-dev-tools (Ubuntu Lunar)
Assignee: (unassigned) => Robie Bas
Fixed in 0.193ubuntu5 in mantic-proposed; awaiting migration.
** Changed in: ubuntu-dev-tools (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of MOTU,
which is subscribed to ubuntu-dev-tools in Ubuntu.
https://bugs.launchpad.net
I performed the Test Plan on Lunar, Kinetic, Jammy and Focal. With the
current versions the problem reproduced as expected in scenarios A and
B, and scenario C worked as expected. Then I upgraded to proposed and
scenarios A, B and C all worked as expected.
The current versions were:
Lunar: 0.193u
Public bug reported:
I presume that check-mir is expected to be run on a system with
appropriate apt sources enabled. But having the proposed pocket of the
development release enabled is not appropriate even on a development
system. This means that when a package is blocked from proposed
migration
Public bug reported:
On my system, /etc/localtime points to Etc/UTC. When I run mk-sbuild, it
fails as follows:
I: Base system installed successfully.
cp: '/etc/localtime' and '/var/lib/schroot/chroots/xenial-amd64/etc/localtime'
are the same file
rbasak@diglett:~$ stat /etc/localtime
File: '/
I patched my live system as attached, which fixed the problem.
** Patch added: "fix.patch"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1569400/+attachment/4634267/+files/fix.patch
--
You received this bug notification because you are a member of MOTU,
which is subscribed
Public bug reported:
$ grep-merges Basak
Traceback (most recent call last):
File "/usr/bin/grep-merges", line 74, in
main()
File "/usr/bin/grep-merges", line 68, in main
pretty_uploader = ' '.join((author, uploader)).strip()
TypeError: sequence item 0: expected string, NoneType found
Public bug reported:
lxc launch ubuntu-daily:artful test
lxc exec test bash
apt update
apt install python3-ubuntutools
python3
>>> import ubuntutools.archive
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/ubuntutools/archive.py", line 52, in
Version 0.158 in Artful.
--
You received this bug notification because you are a member of MOTU,
which is subscribed to ubuntu-dev-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1691735
Title:
python3-ubuntutools does not depend on python3-httplib2 or
python3-launchpadlib
To manage notifi
Public bug reported:
On Eoan with ubuntu-dev-tools 0.171
$ /usr/bin/pull-debian-source
Traceback (most recent call last):
File "/usr/bin/pull-debian-source", line 22, in
import urllib.request
ImportError: No module named request
Root cause: despite the "/usr/bin/python3" shebang in the so
02:11 Pretty sure you can turn off shebang rewriting. I think
it's dh_python, not setuptools.
--
You received this bug notification because you are a member of MOTU,
which is subscribed to ubuntu-dev-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1841127
Title:
pull-debian-source fails wit
Thank you! It wasn't clear to me how to resolve this.
--
You received this bug notification because you are a member of MOTU,
which is subscribed to ubuntu-dev-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1841127
Title:
pull-debian-source fails with "ImportError: No module named request"
Public bug reported:
Steps to reproduce:
import ubuntutools.archive
ubuntutools.archive.UbuntuSourcePackage('akonadi',
'1.1.2-0ubuntu1~jaunty1').pull()
This fails with an ubuntutools.archive.DownloadError.
** Affects: ubuntu-dev-tools (Ubuntu)
Importance: Undecided
Status: New
-
Colin has a working patch for this.
--
You received this bug notification because you are a member of MOTU,
which is subscribed to ubuntu-dev-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1860456
Title:
ubuntutools.archive.UbuntuSourcePackage().pull() fails
To manage notifications about th
> Since the checksum actually is incorrect for this package/version...
I believe that's inaccurate. I suggest you wait to see Colin's patch. He
was going to prepare an MP when he has time. The problem AIUI is
something to do with ambiguity when multiple different orig tarballs are
associated with
> ack, no hurry, thanks.
Actually this blocks progress in fixing a class of import failures in
git-ubuntu, so I would appreciate getting this landed sooner rather than
later. I'd prefer not to have to patch the git-ubuntu snap's bundled
ubuntu-dev-tools as that opens up a whole bunch of extra comp
> Can we just review and land Colin's patch please...
I just realised that my words could be taken to mean that I'm being
impatient at mapreri. I didn't mean that - only that if we just consider
Colin's patch alone, then there's far less review work necessary. I'm
hoping we can be less demanding o
Public bug reported:
Steps to reproduce:
import ubuntutools.archive
ubuntutools.archive.UbuntuSourcePackage('apache2', '2.2.8-1ubuntu0.4').pull()
This raises the following exception:
DownloadError('https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/apache2/2.2.8-1ubuntu0.4/apache2_2.2.8
This problem still exists.
** Changed in: ubuntu-dev-tools (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of MOTU,
which is subscribed to ubuntu-dev-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1199751
Title:
[check-mir] does not use
I've had the same problem (Intrepid). I already had the PDF directory
(755) from Hardy. My workaround: chmod 711 ~, do print to PDF, then
chmod 700 ~ again.
I think that there are two connected problems.
1) cups-pdf fails to create PDF directory (bug #295318)
2) cups-pdf cannot navigate to PDF di
To clarify, I think that this bug affects those who have home directory
permissions of 700 or similar. Those who fixed the problem by just
creating ~/PDF really want bug #295318.
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug
30 matches
Mail list logo
