Hi,
Quoting Raphael Hertzog (2017-06-26 15:00:28)
> On Mon, 26 Jun 2017, Johannes Schauer wrote:
> > > It would because actually I pass "--apt-update --apt-upgrade" but not
> > > "--apt-distupgrade" and I have no ~/.sbuildrc.
> > then why not pass --
Source: sbuild
Severity: normal
sbuild-createchroot attempts to check the output of $(schroot --list
--all-source-chroots) to make sure that the to be created chroot doesn't
exist already. In addition to checking the output of the command, it
should also check the exit code of the command because
Hi,
Quoting Raphael Hertzog (2017-06-26 20:22:01)
> On Mon, 26 Jun 2017, Johannes Schauer wrote:
> > > Because when I wrote that script, I was probably not aware that
> > > --apt-distupgrade was the default.
> >
> > so does the existence of that option help your
On Mon, 26 Jun 2017 21:14:31 -0400 Justin Gerhardt wrote:
> I have reached out to the developers in regards to licensing. The response
> I received via email was this: "Redistributing our headless is fine, As
> long as you include a notice that all the program data and binaries still
> belong to u
Quoting Ralf Treinen (2017-07-04 08:51:08)
> For the record, this can be triggered more directly by
>
> dose-debcheck --explain -f --coinst perl-base,libscalar-list-utils-perl
> Packages
Or even more directly by:
cat << END | dose-deb-coinstall --explain -f --deb-native-arch=amd64
Package: perl
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer
* Package name: node-sdp
Version : 2.2.0
Upstream Author : Philipp Hancke
* URL : https://github.com/fippo/sdp
* License : Expat
Programming Lang: JavaScript
Description : SDP parsing and
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer
* Package name: node-webrtc-adapter
Version : 4.1.0
Upstream Author : Philipp Hancke
* URL : https://github.com/webrtc/adapter
* License : BSD-3-Clause
Programming Lang: JavaScript
Description
Control: retitle -1 ITP: libjs-webrtc-adapter -- shim to insulate apps from
WebRTC spec changes and browser prefix differences
On Wed, 05 Jul 2017 13:40:29 +0200 Johannes Schauer wrote:
> * Package name: node-webrtc-adapter
Since this is a client-side JavaScript library, the right pack
Control: retitle -1 ITP: libjs-sdp -- SDP parsing and serialization utilities
On Wed, 05 Jul 2017 13:27:44 +0200 Johannes Schauer wrote:
> * Package name: node-sdp
Since this is a client-side JavaScript library, the right package name (for
source and binary package) would be:
libjs-
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer
* Package name: libjs-bootbox
Version : 4.4.0
Upstream Author : Nick Payne
* URL : http://bootboxjs.com/
* License : Expat
Programming Lang: JavaScript
Description : programmatic dialog boxes
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer
* Package name: libjs-toastr
Version : 2.1.3
Upstream Author : John Papa , Tim Ferrell
* URL : http://codeseven.github.io/toastr/
* License : Expat
Programming Lang: JavaScript
Description
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer
* Package name: libjs-blueimp-md5
Version : 2.7.0
Upstream Author : Sebastian Tschan
* URL : https://github.com/blueimp/JavaScript-MD5
* License : Expat
Programming Lang: JavaScript
Description
Package: janus-demos
Severity: wishlist
Control: block -1 by 867274 867272 867286 867290 867288
Hi,
the janus-demos package is currently in contrib because the JavaScript
it ships references scripts which are hosted on cdnjs.cloudflare.com
instead of versions packaged in Debian. To fix this prob
Package: npm2deb
Version: 0.2.7-1
Severity: wishlist
Not all packages distributed by npm are nodejs packages. Many are also
client side javascript code which then belongs into libjs-xxx packages
instead of into node-xxx packages.
Also, libjs-xxx packages will not need a dependency on nodejs and t
Package: npm2deb
Version: 0.2.7-1
Severity: wishlist
Currently, npm2deb puts lots of files into debian/install including
files which definitely do not belong into /usr/lib/nodejs/*/ like:
Hidden files like .travis.yml, .gitattribute, .npmignore, .jshintrc as
well as files that clearly belong to /
Package: npm2deb
Version: 0.2.7-1
Severity: wishlist
Standards-Version 3.9.8 is outdated. npm2deb should generate version
4.0.0 instead.
The current recommended compat level for debhelper is 10. npm2deb should
use that one instead of compat level 9.
On Fri, 24 Mar 2017 13:47:15 +0100 Paul Gevers wrote:
> During my work on castle-game-engine, where I am stripping files from the
> upstream tar ball via Files-Excluded in d/copyright, I was surprized to see
> that the compression=xz in d/watch was ignored. I had to explicitely add the
> repack op
Package: vim-runtime
Version: 2:8.0.0197-4
Severity: wishlist
Currently, the value "javascript" is not accepted by the syntax
highlighting for debian/control files for the "Section" field even
though "javascript" is a valid section name:
https://packages.debian.org/unstable/
Package: debian-policy
Version: 3.9.8.0
Severity: wishlist
According to https://packages.debian.org/unstable/ there exists the
section "javascript" filled with 1050 packages. But the "javascript"
section is missing from the list of valid section names in policy §2.4.
Please add it.
Package: dgit
Version: 4.0
Severity: normal
Steps to reproduce:
$ dgit clone janus
canonical suite name for unstable is sid
starting new git history
downloading http://ftp.debian.org/debian//pool/main/j/janus/janus_0.2.3-1.dsc...
last upload to archive: NO git hash
% Total% Received % Xferd
-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patch which removes the default google STUN server
+
+ -- Johannes Schauer Wed, 05 Jul 2017 18:13:57 +0200
+
janus (0.2.3-1) unstable; urgency=medium
[ upstream ]
diff -Nru janus-0.2.3/debian/janus-demos.README.Debian
Quoting Jonas Smedegaard (2017-07-05 17:46:19)
> Quoting Johannes Schauer (2017-07-05 17:15:46)
> > Standards-Version 3.9.8 is outdated. npm2deb should generate version
> > 4.0.0 instead.
> Just to avoid misunderstanding: Standards-Version should *only* be changed as
> a
On Wed, 05 Jul 2017 17:06:26 +0200 Johannes Schauer wrote:
> Also, libjs-xxx packages will not need a dependency on nodejs and the note
> "Node.js is an event-based server-side JavaScript engine." in the package
> description is unnecessary as well.
Furthermore, libjs-xxx pack
Package: git-buildpackage
Version: 0.8.12.2
Severity: wishlist
Currently, when using "gbp import-dsc" a debian/1.2.3-1 tag will be
created and for the top commit on the master branch. But this doesn't
make sense if the most recent changelog entry is marked as UNRELEASED.
In that case, no such tag
Quoting Jonas Smedegaard (2017-07-05 21:04:44)
> Quoting Johannes Schauer (2017-07-05 18:26:40)
> > Maybe I misunderstand but this bug report is not about "changing" or
> > "bumping" anything.
> >
> > Since npm2deb creates the *initial* Debian pack
On Wed, 05 Jul 2017 16:36:15 +0200 Johannes Schauer wrote:
> the janus-demos package is currently in contrib because the JavaScript it
> ships references scripts which are hosted on cdnjs.cloudflare.com instead of
> versions packaged in Debian.
What must also not be forgotten is to r
Hi,
Quoting Guido Günther (2017-07-06 08:33:11)
> On Wed, Jul 05, 2017 at 08:22:56PM +0200, Johannes Schauer wrote:
> > Currently, when using "gbp import-dsc" a debian/1.2.3-1 tag will be created
> > and for the top commit on the master branch. But this doesn't mak
The current status of packaging the new linphone version can be found in this
thread on the pkg-voip mailing list:
http://lists.alioth.debian.org/pipermail/pkg-voip-maintainers/2017-April/030495.html
Essentially, the big blocker is, that three packages that the new linphone
version requires are n
The long tag description of testsuite-autopkgtest-missing suggests that they
have to simply add the field Testsuite:autopkgtest to debian/control and
everything is fixed.
But this is not the real fix. The real fix is to add a debian/tests/control
*and* at least one test.
I think the testsuite-aut
Source: pelican
Version: 3.7.1
Severity: serious
Justification: Policy 2.2.1
The directory pelican/themes/notmyidea/static/images/icons/ is full of
non-free files which need to be removed.
Source: pelican
Version: 3.7.1-1
Severity: serious
Justification: Policy 2.2.1
The "notmyidea" theme shipped by the pelican package references several
files outside the archive. Specifically:
- pelican/themes/notmyidea/static/css/main.css imports
https://fonts.googleapis.com/css?family=Yanone
Quoting Ian Jackson (2017-07-16 14:32:17)
> It would be nice if it were easier to use sbuild with a gitish
> downstream workflow which does not produce "3.0 (quilt)" source
> packages.
>
> [snip]
>
> The above attempt will probably fail.
>
> This is because the package "foo" is probably "3.0 (qu
Quoting Ian Jackson (2017-07-17 11:31:07)
> That would be a perfectly fine answer from my point of view. However,
> it has a few different behaviours. I'm not sure what is best.
>
> Things I thought of:
>
> 1. If there are files which are ignored, or uncommitted, this would
>use the committ
Quoting Ben Hutchings (2017-07-17 02:17:12)
> However, I can see it has changed since I last looked and now says that
> "stage1" has been deprecated. I don't understand why this is or how we're
> supposed to give this hint to bootstrapping tools now.
When package maintainers implement build profi
Control: tags + patch
On Mon, 03 Jul 2017 14:02:49 +0300 Adrian Bunk wrote:
> Some recent change in unstable makes botch FTBFS:
>
> https://tests.reproducible-builds.org/debian/history/botch.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/botch.html
>
> ...
> /usr/bin/
Source: game-data-packager
Severity: wishlist
Hi,
maintainer of vcmi here. Vcmi is a free re-implementation of the Heroes
of Might and Magic III engine. I have no idea whether this kind of bug
should be filed against vcmi or against g-d-p but since I never
contributed to g-d-p myself, I will just
Hi Alexandre & Simon,
Quoting Alexandre Detiste (2017-07-25 09:17:29)
> GDP already support HOMM3 in stable:
>
> https://anonscm.debian.org/cgit/pkg-games/game-data-packager.git/tree/data/heroes3.yaml
indeed I missed that!
Is there anything I can/should do in the vcmi packaging to make the two
Quoting Simon McVittie (2017-07-25 09:01:45)
> If there are files in "$dest_dir" that are edited at runtime, we will also
> need to know which ones (compare the clean "$dest_dir" with the one you moved
> out of the way). If there are files that you know are not strictly required
> (the music?) we w
Quoting Stephen Kitt (2017-07-26 09:03:39)
> It’s not needed:
>
> $ cabextract -F Disk1/data1.cab h3demo.exe
> Extracting cabinet: h3demo.exe
> extracting Disk1/data1.cab
>
> All done, no errors.
Indeed.
> Unfortunately the next step fails:
>
> $ unshield x Disk1/data1.cab
> Failed to open D
Control: tag -1 + moreinfo
Hi,
Quoting Tianon Gravi (2017-07-27 18:22:55)
> While attempting to use sbuild to test the reverse-dependencies of a
> package before uploading a new upstream revision, I ran into the
> following error using "--extra-package":
>
> | $ sbuild --arch-all --dist=unstable
Quoting Antoine Beaupre (2017-07-29 22:15:29)
> It would be nice if sbuild automatically updated the configured
> schroots. As things stand now, a configured schroot will slowly rot
> down to a point where new builds will have to download a bunch of base
> packages at each run, if sbuild is configu
Quoting Antoine Beaupré (2017-07-30 16:05:08)
> On 2017-07-30 08:31:08, Johannes Schauer wrote:
> > Do you not find the script in
> > /usr/share/doc/sbuild/examples/sbuild-update-all
> > sufficient?
>
> s/sufficient// :) I didn't notice that one at all.
>
&
Quoting Antoine Beaupré (2017-07-30 16:26:08)
> On 2017-07-30 16:06:29, Johannes Schauer wrote:
> > Quoting Antoine Beaupré (2017-07-30 16:05:08)
> >> On 2017-07-30 08:31:08, Johannes Schauer wrote:
> >> > Do you not find the script in
> >> > /usr/s
Quoting Antoine Beaupré (2017-07-30 16:42:29)
> > For documenting. The cron script already exists. ;)
> I mean in /etc/cron.weekly for example.
But putting it there would enable it by default which I'd like to avoid.
> > It even has documentation of how to use it at the top. What's missing is to
Package: nikola
Version: 7.1.0-1
Severity: grave
Justification: renders package unusable
When running nikola I get the following message:
ERROR: You are using doit version 0.28.0, it is too new! This application
requires version <= 0.27.
Thus, nikola seems to currently be unusable.
Thanks!
ch
Package: multistrap
Version: 2.2.9
Severity: normal
Tags: patch
Steps to reproduce:
Create a config file where multiple sections have the same keyring entry
with the same keyring package name. The result will be that one of the
earlier loop iterations removes the package name that is used in late
Hi,
Quoting Michael Stapelberg (2017-06-02 18:23:02)
> Thanks for the review. Answers inline:
sorry for the delay. I'm under a pile of work and this wasn't on the top of my
todo list. But let me not stall your work:
> > > # Enable eatmydata: occasionally losing a test build is preferable over
>
Quoting Michael Stapelberg (2017-07-31 14:19:16)
> Unless I’m mistaken, the following is what we’d need to recommend to new
> users:
>
> % sudo apt install sbuild apt-cacher-ng lintian
Why install lintian?
> % sudo adduser --quiet -- "$USER" sbuild
Better:
sudo sbuild-adduser $USER
> % sudo s
Quoting Michael Stapelberg (2017-08-01 10:51:41)
> I think the following suggestion takes care of all the concerns you brought
> up: Let’s name it sbuild-debian-developer-setup, describe that the goal is to
> provide an sbuild setup which can build packages for Debian unstable,
> automates maintena
Quoting Michael Stapelberg (2017-08-01 11:04:16)
> That works for me :).
>
> How shall we proceed? Should I prepare a patch against the sbuild package?
Yes please!
Put the patch into this bug and then we can talk about it. :)
signature.asc
Description: signature
Hi,
this bug has been listed in the "NMU campaign" email on d-devel. But I wonder
how it ended up there. There are still open problems that are not answered, the
fix for this is still blocked by another bug (#802241) which is not on the NMU
list, and the code I wrote to fix the problem (debrebuild
Quoting Michael Stapelberg (2017-08-01 23:15:04)
> Alright! Patch attached and provided inline, for your convenience:
Cool!
> +if (!defined($ENV{SUDO_USER})) {
> +die "Please run sudo $0";
> +}
Should you not rather check the UID instead?
> +system("adduser", "--quiet", "--", $ENV{SUDO_USER
Hi,
On Fri, 07 Jul 2017 20:19:59 +0200 Paul Gevers wrote:
> I am about to upload jquery-tablesorter to unstable. It replaces
> jquery-goodies as the source for libjs-jquery-tablesorter. In the process, I
> switch upstream (more active) and build system. As a result, the files in the
> libjs-jquer
Package: hevea
Version: 2.29-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps toolchain
Hi,
currently, latex sources which include statements like \today and thus
have to be built with '-exec xxdate.exe' do not respect the timestamp
set via t
Control: tag -1 + moreinfo
Hi,
On Mon, 24 Jul 2017 16:01:58 +0100 Dimitri John Ledkov wrote:
> botch fails ADT tests with python3.6. On the surface the output looks sane,
> and it's not just the ordering differences as there are new things reported
> in the cycle output and some things missing.
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer
* Package name: rss-bridge
Version : 2017-08-03
Upstream Author : sebsauvage
Mitsukarenai
Pierre Mazière
logmanoriginal
* URL : https://github.com
Hi pabs,
Quoting Paul Wise (2017-08-04 15:22:03)
> > Description : generate ATOM feeds for websites that don't have them
> >
> > Generates ATOM feeds for facebook, twitter, youtube, flickr, google,
> > instagram, pinterest and more than 130 other web services which do not
> > provide ATOM or
Quoting Paul Wise (2017-08-04 16:05:20)
> > So yes, you can use it from the command line, but the service has to run in
> > the
> > background and you would use curl or wget to do the correct GET request to
> > get
> > the RSS feed from the command line.
> I see, would you be willing to run rss-b
Package: libjs-jquery-tablesorter
Version: 1:2.28.15+dfsg1-1
Severity: wishlist
Hi,
the old packaging contained
/usr/share/javascript/jquery-tablesorter/addons/pager/jquery.tablesorter.pager.js
that file doesn't exist anymore. Could you please add it again?
Thanks!
cheers, josch
Quoting Michael Hudson-Doyle (2017-08-03 09:28:47)
> > I saw attached log but I cannot reproduce your findings in Debian. The
> > package builds fine and passes its autopkgtests.
> Python 3.6 is not yet the default in debian is it? You could try sbuild -d
> sid --extra-package or something like t
Hi,
Quoting Michael Stapelberg (2017-04-08 11:28:12)
> One area where sbuild sorely lacks is configuration, though: pbuilder is very
> easy to set up, whereas sbuild requires reading through
> https://wiki.debian.org/sbuild, performing a bunch of steps, only to end up
> with a setup which works fi
Hi,
Quoting Michael Stapelberg (2017-04-08 11:21:46)
> I may very well be doing something wrong, but I repeatedly run into
> the following problem and have no clue as to how to approach fixing
> it.
>
> Every once in a while, an sbuild invocation will fail with the
> following message:
>
> R
Hi,
Quoting Michael Stapelberg (2017-04-11 12:41:03)
> On Tue, Apr 11, 2017 at 10:43 AM, Johannes Schauer wrote:
> > Quoting Michael Stapelberg (2017-04-08 11:21:46)
> > > I may very well be doing something wrong, but I repeatedly run into
> > > the following problem
Package: debhelper
Version: 10.2.3
Severity: wishlist
Tags: patch
Hi,
I didn't find the dh_link man page very helpful when I trued to create a
debian/I.links file. I noticed the following shortcomings:
- the man page uses the source/destination nomenclature which I find
quite confusing. I wo
Quoting Niels Thykier (2017-04-12 10:46:00)
> One question though, are you sure about the path not being allowed to have a
> leading slash? AFAICT, the code at least handles the link target perfectly
> fine if it has a leading slash. And I am inclined to say that it is a bug if
> it does not supp
Hi Ben,
Quoting Ben Finney (2017-04-21 14:44:52)
> How is this going?
thanks a lot for the ping!
> Jordan, have you made more changes that should be released?
>
> Johannes, are you waiting on any changes before you approve and upload
> this package?
Jordan and I were writing each other private
Package: gitlab
Version: 8.13.3+dfsg1-2
Severity: grave
Justification: renders package unusable
Hi,
sorry for reporting another RC bug.
Because you were so quick in fixing #846916, I just upgraded my gitlab
chroot. Here are the relevant lines from my "apt-get upgrade" run
(showing all the packag
Package: gitlab
Version: 8.13.3+dfsg1-2
Severity: important
Hi,
in #846916 you advised me to run "rake assets:precompile" after I
upgraded my version of ruby-jquery-rails. This really should not be
necessary and the gitlab package should do this itself if any relevant
package versions get upgrade
Hi,
On Thu, 08 Dec 2016 04:12:57 +0100 Johannes Schauer wrote:
> When I now enter my gitlab instance I only get a 502 error with the message
> "Whoops, GitLab is taking too much time to respond".
>
> Since the last time I changed the version of a ruby packag
Hi,
On Sun, 08 May 2016 12:50:41 +0200 Johannes Schauer wrote:
> please consider the attached patch to update README.Debian with more detailed
> explanations of how to upgrade gitlab from non-Debian installations.
I updated the patch to use runuser instead of su.
Please find it at
Hi Martin,
Quoting Martin Pitt (2016-12-08 16:37:58)
> Johannes Schauer [2016-11-26 6:03 +]:
> > I don't know what the best course of action here is. Should sbuild expect
> > that
> > after the user presses Ctrl+C, the autopkgtest backend takes care to
> &
Hi,
Quoting Martin Pitt (2016-12-08 17:43:39)
> Maybe I misunderstood you above, but you said that sbuild was creating the
> "session", which I assumed was the schroot session that it uses to build the
> package and run its autopkgtest in.
>
> If sbuild *does* control the schroot session, then it
outdated in
the future without you noticing via a build failure.
What do you think?
cheers, josch
>From 8d642b4b6c32716e7d2669f27132f801d363bdd3 Mon Sep 17 00:00:00 2001
From: Johannes Schauer
Date: Thu, 8 Dec 2016 18:31:54 +0100
Subject: [PATCH] Move lxc-unshare and lxc-usernsexec to a new bi
Hi Martin,
Quoting Martin Pitt (2016-12-08 17:59:44)
> Johannes Schauer [2016-11-16 17:32 +0100]:
> > For example, most notably, "mount -t proc proc /proc" never worked without
> > doing the systemcalls manually using the perl script I present there. This
> > pr
Hi again,
Quoting Johannes Schauer (2016-12-08 18:10:18)
> Firstly, because the autopkgtest-virt-* program is in the same process group
> it will also receive the Ctrl+C sent by the user and will immediately clean
> up and exit. The problem with autopkgtest doing that from the sbuild
Package: ruby-jquery-ui-rails
Version: 6.0.1+dfsg-1
Severity: serious
Justification: fails to build from source
Hi,
the package currently FTBFS. Here are the last lines from the log:
dpkg-buildpackage
-
dpkg-buildpackage: info: source package ruby-jquery-ui-rails
dpkg-buildpacka
Package: botch
Version: 0.20-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi,
botch currently FTBFS because its tests fail. More precisely, the
"selfcontained" tests fail. This seems to happen because the output of
botch-optuniv changed (opt-p
Package: botch
Version: 0.20-3
Severity: normal
Hi,
currently, the botch autopkgtest scripts contain:
diff -u "tests/$testname/$t/$f" "$ADTTMP/$t/$f" | head --lines 100 || exit 1;;
This will never result in failure because the exit code of a pipe is the
exit code of the last process. Instead, t
Hi Sean,
Quoting Sean Whitton (2016-12-12 00:44:05)
> On Sun, Dec 11, 2016 at 03:12:57PM -0700, Sean Whitton wrote:
> > I have sbuild properly set up on my machine, and I want to use it to
> > test package reproducibility. Something like this, where PWD is an
> > unpacked source package:
> >
> >
Hi,
Quoting Sean Whitton (2016-12-12 16:44:54)
> Thank you for your replies. sbuild is definitely sufficient, it's just a bit
> of a drag -- you have to rename the .changes to save the checksums, and then
> run sbuild a second time, and compare. I was going to write a shell script
> to do this,
Package: multistrap
Version: 2.2.7
Severity: wishlist
Currently, only one repository can be specified per section. Each
section is translated into one file in /etc/apt/sources.list.d. It would
be convenient and safe typing if one could specify more than one
repository per section. That would then
Hi,
Quoting Niko Tyni (2016-12-15 14:04:19)
> > But then on IRC, HW42 suggested to approach this problem differently.
> > Instead of integrating the functionality of figuring out the right
> > repositories to reproduce the contents of a buildinfo file into sbuild,
> > write a tool that can drive a
Hi,
Quoting Niko Tyni (2016-12-17 13:40:32)
> On Thu, Dec 15, 2016 at 02:21:49PM +0100, Johannes Schauer wrote:
> > Quoting Niko Tyni (2016-12-15 14:04:19)
> > > In general, I like the concept of sbuild/pbuilder accepting .buildinfo
> > > files
> > > as
Hi,
Quoting Raphael Hertzog (2016-07-22 12:01:41)
> On Fri, 22 Jul 2016, Johannes Schauer wrote:
> > Quoting Raphaël Hertzog (2016-07-21 21:18:52)
> > > I have updated a library and in the process I renamed ftplib-dev into
> > > libftp-dev (which provides "ftplib
Hi,
On Mon, 09 May 2016 21:07:40 +0200 Johannes Schauer wrote:
> The main disadvantage of the current srebuild implementation is, that it will
> only make use of a single snapshot.d.o timestamp. This makes it impossible to
> reproduce situations where packages are not built in a clean c
Control: tag -1 + pending patch
Hi Sean,
CC-ing Martin Pitt to get this right.
On Wed, 8 Jun 2016 15:13:58 +0900 Sean Whitton wrote:
> So the problem is to come up with a sensible default set of options to pass
> to adt-run that will Just Work? This should work without any schroot:
>
> ad
Hi,
On Mon, 09 May 2016 21:07:40 +0200 Johannes Schauer wrote:
> The main disadvantage of the current srebuild implementation is, that it will
> only make use of a single snapshot.d.o timestamp. This makes it impossible to
> reproduce situations where packages are not built in a clean c
Hi Sean,
On Tue, 2 Aug 2016 07:23:08 -0700 Sean Whitton wrote:
> Per the discussion in #828025, I'm pretty sure this will fail because the
> .changes generated by sbuild doesn't contain the .dsc. So I think you need
>
> sudo -- autopkgtest foo.dsc foobar.changes -- null
not unconditionally
Hi Jonathan,
Quoting Jonathan McDowell (2016-07-25 22:29:39)
> Having been impressed by the current status of reproducible builds and
> the fact it looks like we're close to having the important pieces in
> Debian proper, I have started to have a look at how I could help out
> with this bug. I've
Hi Sean,
Quoting Sean Whitton (2016-08-03 21:11:57)
> It should be possible to instruct sbuild not to run autopkgtest or
> piuparts as root. If using a schroot backend for autopkgtest, root is
> not required, and hopefully this will soon be true for piuparts too
> (#708663).
>
> At present, the
Hi,
Quoting Christian Seiler (2016-08-04 10:03:04)
> Shell snipped I used to get this data:
> awk '/^Package:/ { pkg = $2; }
> /^Installed-Size:/ { is = $2; }
> /^Size:/ { print pkg, $2, is }' \
> < /var/lib/apt/lists/*_debian_dists_sid_main_binary-amd64_Packages \
> | sort -k3 -n
Package: sbuild
Version: 0.70.0-1
Severity: important
Control: block -1 by 833407
Hi,
the autopkgtest 4.0.2 release broke the adt-virt-* interface that
autopkgtest used to provide before this release.
Sbuild thus now lost support for the qemu, ssh and lxc backends that it
used to support by maki
Hi,
On Thu, 4 Aug 2016 00:47:47 +0100 Ian Jackson
wrote:
> I see that after installing a recent autopkgtest, I no longer have
> adt-virt-schroot, adt-virt-null, etc. I would like to suggest that
> this change be reverted, for the following reasons:
>
> My original design intent was that:
than
Control: block -1 by 833407
Hi,
On Fri, 17 May 2013 16:45:15 +0200 Holger Levsen wrote:
> while piuparts has a --schroot option, this is just for reusing a schroot
> chroot as a piuparts base directory, piuparts itself still needs to be run
> with sudo as root. With schroot it should be possible
Hi,
On Thu, 04 Aug 2016 18:05:37 +0200 Johannes Schauer wrote:
> current piuparts implements a adt-run backend. Through that, schroot could be
> used without needing superuser privileges. Unfortunately, the latest
> autopkgtest upload removed the adt-run interface. Thus blocking th
Hi again,
On Thu, 4 Aug 2016 17:20:00 +0100 Ian Jackson
wrote:
> Johannes Schauer writes ("Re: Please put adt-virt-* binaries back onto PATH"):
> > Using codesearch.debian.net it is not hard to find that others depend on
> > specific functionality of your software. Next
Hi Ian,
Quoting Ian Jackson (2016-08-04 18:20:00)
> > In fact I only noticed this breakage because I wanted to add support for
> > adt-run-* to another tool: piuparts which already comes with lots of code
> > supporting the adt-run-* utilities. Now its broken.
>
> I think in the rest of this mail
Control: tag -1 + patch
On Fri, 05 Aug 2016 13:55:14 +0100 Brian Drummond
wrote:
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What led up to the situation?
> 0) Okay, this will be embarrassing...
> 1) Occasional need to work on i386 software on an x8
Control: tag -1 + pending
Hi Sean,
Quoting Sean Whitton (2016-08-05 23:21:47)
> In its final build summary, sbuild highlights "Lintian: pass" in green and
> "Lintian: fail" in red. This is useful for seeing at a glance whether there
> is anything to fix.
>
> The attached patch extends this beha
Hi,
Quoting Sean Whitton (2016-08-05 22:29:29)
> When sbuild obtains the .dsc to build from the archive with `apt-get
> source`, autopkgtest fails. It seems that sbuild is not passing the
> .dsc to autopkgtest in this case.
>
> For example, if I run
>
> $ sbuild y-u-no-validate
>
> autopkg
901 - 1000 of 2502 matches
Mail list logo
