| altair | Who is Brian Murray? Is he the Jon Skeet of Ubuntu? | 06:10 |
|---|---|---|
| hyperair | blargh. why has banshee-community-extensions gotten stuck in proposed when there hasn't been a new upload since saucy? | 07:18 |
| hyperair | it's been effectively removed from trusty | 07:18 |
| altair | guys. How can I name a new package when I build it from a specific github revision? similar to packagename_1.0_0ubuntu1+svn1234.deb ?? | 08:09 |
| Laney | hyperair: I guess it was when banshee was gtk3 | 08:10 |
| Laney | would it have ftbfsed then? | 08:10 |
| hyperair | Laney: hmm, but it doesn't show up | 08:23 |
| hyperair | Laney: i mean the ftbfses don't show up | 08:23 |
| hyperair | Laney: all arches except for arm64 are fine and arm64's becaues of gtk-sharp | 08:24 |
| hyperair | gtk-sharp2, that is | 08:24 |
| Laney | they've gone away now | 08:54 |
| Laney | doko filed a bug to keep it in proposed | 08:54 |
| Laney | and we don't even have mono on arm64 so I don't think that is relevant | 08:57 |
| edv | Good day | 13:20 |
| edv | I wish to upload a package I fixed to debian | 13:21 |
| edv | I followed the packaging guide but I encounter a problem after I enter the submittodebian command | 13:22 |
| edv | this is the error I encounter after stating that I do not wish to edit the debiff | 13:24 |
| edv | Distribution data outdated. Please check for an update for distro-info-data. See /usr/share/doc/distro-info-data/README.Debian for details. | 13:24 |
| edv | Traceback (most recent call last): File "/usr/bin/submittodebian", line 269, in <module> main() File "/usr/bin/submittodebian", line 263, in main submit_bugreport(body, debdiff, deb_version, changelog) File "/usr/bin/submittodebian", line 182, in submit_bugreport check_call(cmd, env=env) File "/usr/lib/python2.7/dist-packages/ubuntutools/subprocess.py", line 72, in check_call retcode = call(*popenargs, **kwar | 13:24 |
| edv | more of my terminal output here (just in case I wasn't clear enough) | 13:39 |
| edv | Building using working tree Building package in normal mode Looking for a way to retrieve the upstream tarball Upstream tarball already exists in build directory, using that Building the package in /home/voinea/build-area/dooble-0.0+svn874, using dpkg-buildpackage -uc -us -nc -S dpkg-buildpackage: source package dooble dpkg-buildpackage: source version 0.0+svn874-0ubuntu4 dpkg-buildpackage: source distribution UNRELEASED dpkg-buildp | 13:39 |
| edv | duard <edvoinea@gmail.com> dpkg-source --before-build dooble-0.0+svn874 dpkg-checkbuilddeps: Unmet build dependencies: libqt4-dev libqtwebkit-dev sharutils dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting dpkg-buildpackage: warning: (Use -d flag to override.) dpkg-buildpackage: warning: this is currently a non-fatal warning with -S, but will probably become fatal in the future dpkg-buildpackage: warnin | 13:41 |
| === bluesabre is now known as knoodle | ||
| === knoodle is now known as bluesabre | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!