On Tue, Feb 06, 2018 at 03:34:50PM +0200, Lars Wirzenius wrote:
> That would completely ruin my plan to only ever release version 1.0 of
> all of my future projects, but increase the epoch instead.
you are very evil indeed.
--
cheers,
Holger
signature.asc
Description: PGP signature
On Thu, Feb 01, 2018 at 01:12:21AM +0100, Adam Borowski wrote:
> Thus, I'd like to propose a new kind of wnpp bug: "Intent To Remove".
> It's pretty much the opposite of O:
[...]
> * by filing an ITR, you don't disclaim your commitment to the package (if
> you're the maintainer, you may or may no
On Wed, Jan 31, 2018 at 10:40:19PM +0100, Michael Biebl wrote:
> I think we should remove cruft more aggressively then we currently do.
> We are much too lenient with what we ship in our stable releases.
I agree, thanks. Re-adding stuff is easy.
(3 months before the freeze we should stop those cr
On Sat, Jan 20, 2018 at 10:59:24PM +0100, Alexander Wirt wrote:
> > I'd hope so too and would be very happy about some confirmation as well.
> as I already said several times on several channels: now that there is
> someone taking over list.a.d.o it is their job to define dates. The old dates
> wer
On Sat, Jan 20, 2018 at 10:29:44AM +, Dominic Hargreaves wrote:
> The February date is indeed now very soon and it's unlikely we would
> have this in place in time. However my understanding from the alioth
> admins is that this wasn't a hard deadline and was proposed before there
> was a sugges
On Fri, Jan 12, 2018 at 03:06:10PM +0100, Geert Stappers wrote:
> What is 'cme' ??
apt-cache show cme
--
cheers,
Holger
signature.asc
Description: PGP signature
package: lintian
severity: wishlist
x-debbugs-cc: debian-devel@lists.debian.org, d...@list.debian.org
On Wed, Jan 03, 2018 at 02:24:46PM +, Sean Whitton wrote:
[...lots of stuff I agree with deleted...]
> Lintian errors and warnings tell you, roughly, "watch out, your upload
> might/will make
On Wed, Jan 03, 2018 at 02:03:58PM +0100, Mattia Rizzolo wrote:
> It is actionable, in a way.
"in a way"…
> IME, Debian holds quite some lobbying power, saying "we may end up
> disabling this feature or not shipping the package at all" has some
> importance to many projects. That may cause porti
On Wed, Jan 03, 2018 at 07:44:01AM -0500, Jeremy Bicha wrote:
> Has the python2 dependency issue been reported upstream yet?
yes
--
cheers,
Holger
signature.asc
Description: PGP signature
On Sun, Dec 31, 2017 at 09:50:10PM +0800, Paul Wise wrote:
> > W: python-pysmi: new-package-should-not-package-python2-module
> > This is the translation of a group of people's opinion.
> With the Python 2 EOL coming in 2020, adding more Python 2 stuff isn't
> going to help us migrate to Python 3,
package: lintian
severity: wishlist
x-debbugs-cc: debian-devel@lists.debian.org
On Mon, Jan 01, 2018 at 05:26:35PM +, Sean Whitton wrote:
> I think that Lintian shouldn't warn about not using the latest
> Standards-Version; perhaps it should warn when you're using a really old
> one.
Same her
Hi,
first of all: thanks a lot for all your work on this!
On Mon, Dec 25, 2017 at 11:45:37AM +0100, Alexander Wirt wrote:
> External users are invited to create an account on salsa.
do you plan importing the current -guest accounts from alioth?
--
cheers,
Holger
signature.asc
Descri
On Wed, Dec 20, 2017 at 08:10:19PM +0100, Andreas Tille wrote:
> May be I should write an according query and than close all those
> bugs ...
please do ;)
--
cheers,
Holger
signature.asc
Description: PGP signature
On Wed, Dec 20, 2017 at 05:13:26PM +0100, Andreas Tille wrote:
> I can confirm that it also affects arch:all packages. But why shouldn't
> it be possible to detect this automatically also in this case?
because a build on any architecture will make the arch:all package
appear and then you cannot
On Wed, Dec 20, 2017 at 04:10:09PM +0100, IOhannes m zmölnig (Debian/GNU) wrote:
> but isn't this something that can be detected automatically?
> e.g. if <> on <> is not available in unstable and/or
> testing, exclude it from the rebuilds.
besides that it's not that easy (eg a package might not y
On Wed, Dec 20, 2017 at 02:31:42PM +, Wookey wrote:
> As a porter I notice quite a few packages where the maintainer has
> made things 'tidy' by giving an explicit architecture list when really
> the unlisted ones were really just 'doesn't build there yet, or arch
> is new since I made the list
On Tue, Dec 19, 2017 at 03:46:58PM -0800, Russ Allbery wrote:
> This is all kind of a mess, and I think Debian would be well-served by
> looking for opportunities to minimize the very real and significant cost
> to Debian contributors for doing boring and demotivating paperwork.
> That's probably m
On Tue, Dec 19, 2017 at 06:44:54PM +0100, Jonas Smedegaard wrote:
> > What if the author is anonymous then?
> Then who granted the license?
the anonymous author.
this of course can lead to certain problems, _maybe_.
> If you buy the Eiffel tower from someone anonymously, then you are in
> troub
On Mon, Dec 18, 2017 at 10:06:08PM +0900, Osamu Aoki wrote:
> When changing only the binary package name, it is easy to do it. All I
> have to do is package an empty transitional package with the old binary
> package name in its new source package with proper dependencies and
> upload it :-)
your
On Wed, Dec 06, 2017 at 03:45:38PM +0800, Paul Wise wrote:
> On Wed, Dec 6, 2017 at 2:58 PM, Russ Allbery wrote:
>
> > I think that's probably true, but it also has prerequisites that may not
> > be achievable. In other words, it's more user-friendly except when it's
> > completely impossible (be
On Mon, Dec 04, 2017 at 11:18:21PM +0100, Philipp Kern wrote:
> I guess the question from my side is if the list of archive components
> in §5 of the Social Contract is supposed to be exhaustive or not. I.e.
> if we need to change that or not. If we don't need to: yay. (Maybe
> because we editorial
On Mon, Dec 04, 2017 at 11:41:34PM +0500, Andrey Rahmatullin wrote:
> There are alternatives?
always.
--
cheers,
Holger
signature.asc
Description: PGP signature
On Mon, Dec 04, 2017 at 05:36:30PM +, Ian Jackson wrote:
> Lars Wirzenius writes ("Re: Debian Stretch new user report (vs Linux Mint)"):
> > Myself, I would prefer us to keep both the free-software-only ISO and
> > the non-free ISO with firmware and other things needed to get typical
> > modern
On Sat, Dec 02, 2017 at 12:32:29PM +0100, Geert Stappers wrote:
> URL is
> https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/
so who will make nonfree.debian.net and non-free.debian.net
http-redirect to that URL? :)
--
cheers,
Holger
signature.asc
Descript
On Fri, Dec 01, 2017 at 12:05:27PM -0600, Gunnar Wolf wrote:
> http://get.debian.org
> Might not be beautiful, but it has the needed information, clearly
> spelt out.
besides that I find that page still too confusing / not simple enough,
it also lacks information about the non-free images.
--
c
On Thu, Nov 30, 2017 at 01:52:18PM +, Ian Jackson wrote:
> Over the years, d-legal has discussed a number of packages which
> automatically download non-free software, under some circumstances.
can you point to current examples in Debian main, either in sid or
stretch?
--
cheers,
H
On Wed, Nov 29, 2017 at 07:26:26AM -0500, Michael Stone wrote:
> Exactly the same argument can be made for selinux. But for some reason just
> turning on selinux by default to fix everything wasn't a good solution, but
> turning on apparmor for the same reason is. I'm trying to understand this
> lo
On Wed, Nov 22, 2017 at 08:49:11AM +, Jonathan Dowland wrote:
> This is about standardising the label we use for marking offensive content,
> not about defining what is or isn't offensive. I'd argue that
> "-offensive" suffix proposal was a technical term.
so you're proposing to add this techn
On Tue, Nov 21, 2017 at 02:56:36PM -0700, Sean Whitton wrote:
> > Not involved in any of the packages, but I guess that whatever
> > agreement we make it is worth documenting elsewhere apart of the
> > mailing list archive. Wiki? policy?
> Policy.
no, please, no.
policy should document technical
On Thu, Nov 16, 2017 at 03:21:37PM -0700, Sean Whitton wrote:
> Wow! Thank you for sharing details of this, Jeremy.
indeed! thank you.
> What's
> particularly nice about this is that the upload stage is still manual,
> which satisfies the kind of reasons brought up by Russ and I, but a big
> c
On Thu, Nov 16, 2017 at 05:53:40PM +0100, Wouter Verhelst wrote:
> Yes; and semver.org is a formalized system for version numbering stuff.
> If upstream has committed to it (and does not make mistakes), then the c
> versions in the above example MUST (in the RFC definition of that word)
> only cont
On Wed, Nov 15, 2017 at 04:43:17PM +0100, Steffen Möller wrote:
> I would really like to see updates performed in some automated fashion.
I think this is an excelent idea, at least for the case of updates from
eg 2.0.3 to 2.0.4 or some such, and also of course accompanied with
automated tests.
I'
On Sat, Nov 11, 2017 at 01:04:09PM +0200, Adrian Bunk wrote:
> A build of all currently reproducible packages with the second build
> defaulting to "Rules-Requires-Root: no" might be helpful for finding
> remaining problems.
one day we (r-b) could do this, but for testing this, please use
"trad
On Tue, Nov 07, 2017 at 12:00:42PM +0100, Adam Borowski wrote:
> It would be great -- I tried to make an unofficial Jessie release for x32,
> but doing the equivalent of Britney turned out to be too hard. The main
> reason was binNMUs: any out-of-archive binNMU conflicts with official
> binNMUs th
On Fri, Oct 27, 2017 at 11:24:29AM -0400, Anthony DeRobertis wrote:
> > recommends wont work, they arent installed on upgrades…
> I haven't tested it, but at least according to apt's changelog new
> recommends are installed on upgrade as of 0.7.0 as log as
> APT::Install-Recommends is true, which h
On Fri, Oct 27, 2017 at 08:57:26AM -0400, Jeremy Bicha wrote:
> > 3. Have a Recommends or Depends on it from another package that is
> > installed. (Presumably that'd be a Recommends from the linux-image-*
> > packages, and would be dropped down to a Suggests for buster+1).
> Why shouldn't it stay
On Mon, Oct 23, 2017 at 04:47:52PM +0200, Adam Borowski wrote:
> It cleanly aborts installation in preinst.
that's a violation of the release teams requirement for a stable
release, where all packages *must* install cleanly…
--
cheers,
Holger
signature.asc
Description: PGP signature
On Mon, Oct 23, 2017 at 04:36:11PM +0200, Julian Andres Klode wrote:
> sse2-support and other packages that fail to install can massively
> screw up systems, potentially leaving dpkg in a state that people
> cannot easily recover from - that is, apt-get install -f might not
> be working at that poi
Hi,
On Sat, Oct 14, 2017 at 09:27:25PM +, Holger Levsen wrote:
> I'm doing an small mass bug filing against obsolete transitional packages
> which are at least marked "dummy transitional" since the jessie release,
> though many of them existed already in wheezy. I thin
On Sun, Oct 15, 2017 at 02:41:59PM +0100, Colin Watson wrote:
> Just because it didn't seem particularly important. But since you ask,
> I've done the paperwork now:
> https://bugs.debian.org/878660
Thanks, Colin.
I didnt mean to imply you should do that paperwork, but I guess it does more
har
On Sun, Oct 15, 2017 at 10:49:37AM +0100, Colin Watson wrote:
> I probably wouldn't bother. Although the project doesn't formally
> support skip-upgrades, a fair few maintainers probably do so informally.
yeah, I following the assumption that upgrades are not skipped.
> > Probably it's more usef
bird* lightning* and
multiarch-support as those are… special.)
This is an example bug: (though the 2nd paragraph is rather exceptional.)
On Sat, Oct 14, 2017 at 02:31:45PM +0200, Holger Levsen wrote:
> Package: ttf-liberation
> Version: 1.07.4-1
> Severity: normal
> user: qa.debian...
On Tue, Sep 26, 2017 at 07:21:51PM +0200, Adam Borowski wrote:
> > > > I now use dupload which does not have that kind of issues.
> > > Indeed, dupload worked right ahead. Thanks.
> > How odd. Is there a bug filed against dput ?
> Also note there's also dput-ng.
Look! Squirrels!
--
cheers,
On Tue, Sep 19, 2017 at 01:22:55PM +0200, Marc Haber wrote:
> Not doing something "central" just because it won't be perfect, or not
> supported by DSA, will not prevent things from happening, it will just
> force them to happen in a distributed, uncoordinated way, wasting way
> more resources for
On Tue, Sep 19, 2017 at 09:43:46AM +0200, Marc Haber wrote:
> How high are the requirements (CPU-, Memory) wise? I guess that one of
> those 5 Euros a month VPSses with 50 Gig Disk and 8 GB RAM would not
> be enough?
[...]
> I don't see running the Mailing list server the biggest challenge.
> Provi
On Mon, Sep 18, 2017 at 09:53:43PM +0200, Alexander Wirt wrote:
> > I have managed mailman installations for some time so I'm fairly familiar
> > with how it works, and have some time from November onwards to work on
> > this which I hope would be enough time to develop and implement a migration
>
On Mon, Sep 18, 2017 at 01:57:31AM +0100, peter green wrote:
> Just because a team isn't big or established doesn't mean they don't need a
> place to discuss issues relating to their activities, some of which do not
> relate to any one particular package. Contributers should be able to
> self-or
On Mon, Sep 11, 2017 at 03:20:36PM +0100, James Cowgill wrote:
> Maybe it should start using debhelper...
yes, please.
--
cheers,
Holger
signature.asc
Description: Digital signature
On Sun, Sep 03, 2017 at 11:40:53AM +0200, Philipp Kern wrote:
> Git is an interesting thought for incremental mirroring. But then it also
> seems to be a poor choice for something that is an only growing repository
> of data.
the nice thing with git is that you get a signed tree for free (or rathe
On Mon, Jul 03, 2017 at 07:23:29PM +0200, Philipp Kern wrote:
> > Not yet. We people from the reproducible team couldn't find a way to
> > usefully talk to ftp-masters people, whom never replied to any of the
> > questions in the thread at #763822 (they only did some quick comments on
> > IRC, and
On Fri, Sep 01, 2017 at 06:34:38PM +0100, Ian Campbell wrote:
> On Fri, 2017-09-01 at 12:43 +0200, Helmut Grohne wrote:
> > Whatever point you were trying to make around NEW, your argument is not
> > very convincing. I think Holger is right here: Where the package is
> > built should not matter. Pr
On Fri, Sep 01, 2017 at 09:34:53AM +0300, Adrian Bunk wrote:
> On Sun, Aug 23, 2015 at 12:48:50PM +0200, Chris Lamb wrote:
> >...
> > However, based on an informal survey at DebConf (and to reflect the
> > feeling towards software reproducibility in the free software community
> > in general) unles
On Fri, Sep 01, 2017 at 09:26:44AM +0300, Adrian Bunk wrote:
> AFAIK the only place where we currently still need binary packages that
> have been built on a maintainer machine is for [...]
the fun part is that once a package builds bit by bit identically, it doesnt
matter anymore where it's bee
On Wed, Aug 30, 2017 at 02:39:16PM +0100, Dimitri John Ledkov wrote:
> upstart - event-based init daemon has been removed from debian and is
> currently only present in oldstable.
>
> Many packages however still ship upstart integration. Please consider
> removing /etc/init/* conffiles from your p
Hi,
On Mon, Aug 21, 2017 at 02:35:39PM -0700, Sean Whitton wrote:
> Debian Policy 4.1.0.0 is on its way into unstable.
[...]
> 4.15
> Packages should build reproducibly when certain factors are held
> constant; see 4.15 for the list.
>
> 4.15
> Packages are recommended to build reprod
control: reopen -1
control: reassign -1 jenkins.debian.org
thanks
On Mon, Aug 21, 2017 at 11:27:12PM +0200, Marco d'Itri wrote:
> Not a bug:
not true, see above.
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844220#65
thanks for the pointer!
--
cheers,
Holger
signature.asc
D
Package: general
Severity: serious
Hi,
I seem to recall that there was a change causing the following (which is due to
"user mail not found") but I'm unable to remember which package was that…
So I'm seeing this in various jenkins tests testing package installations:
Setting up exim4-config (4.
On Sun, Aug 20, 2017 at 06:16:07PM +0200, Geert Stappers wrote:
> - Forwarded message from Enrico Zini -
> > SSO, as it is right now, is NOT a user managing thing. SSO is ONLY
> > taking existing users from one or more (two right now, db.d.o/alioth)
> > backends, and allows them to have a
On Wed, Aug 16, 2017 at 01:38:11AM +0200, Julian Andres Klode wrote:
> bsdiff was specifically invented for patching binaries. See the
> evaluation I posted a (few) hour(s) ago. It's used succesfully by
> FreeBSD, Chrome, Android, Apple App Store, and other places.
[...]
> Especially for security
On Sun, Aug 13, 2017 at 09:20:28AM -0400, Paul Wise wrote:
> Low-speed connections and low bandwidth quotas (especially on mobile)
> are still common enough around the world that delta upgrades make a
> difference right now, IIRC even Google uses them for Chrome.
fedora also has them and users enj
On Sat, Aug 05, 2017 at 09:05:46PM +0300, Adrian Bunk wrote:
> > I think using the uploaders: field to guess who's a team member is just a
> > work-around / an estimate, as we have nothing better.
> It is the official place to list co-maintainers.
you keep repeating this but its still broken by de
On Fri, Aug 04, 2017 at 07:31:36PM -0400, intrigeri wrote:
> tl;dr: I hereby propose we enable AppArmor by default in testing/sid,
> and decide one year later if we want to keep it this way in the
> Buster release.
loving it, please go ahead! ;-)
--
cheers,
Holger
signature.asc
Descri
On Sat, Aug 05, 2017 at 10:39:02AM +0300, Adrian Bunk wrote:
> > I don't understand this suggestion. If it can be automatically
> > generated, just generate it when you need it -- why store it in the
> > source package?
>
> What cannot be automatically generated is the other side of the
> inters
On Sat, Aug 05, 2017 at 04:35:35PM +0200, Bill Allombert wrote:
> > > Note that a prerequisite for such debian/changelog parsing would be
> > > that policy sets strict syntax and semantics requirements.
> >
> > No, we do not need to block such a feature that would work for 90% of
> > packages unti
On Fri, Aug 04, 2017 at 04:19:21AM +0300, Adrian Bunk wrote:
> Your definition is completely detached from the reality in Debian.
>
> Many (likely the majority) of teams in Debian have not more
> than 1 active member.
citation needed.
I seriously doubt this is true. There are some of these team
On Thu, Aug 03, 2017 at 06:04:17PM -0400, gregor herrmann wrote:
> On Thu, 03 Aug 2017 12:11:07 -0700, Russ Allbery wrote:
> […]
> Thanks for putting my thoughts (again!) into better words than I ever
> could!
+1
> > (I am entirely in favor of giving the MIA team more actual power.)
> (Me too.
On Tue, Jul 18, 2017 at 09:50:48PM +0200, Bernd Zeimetz wrote:
> So do I understand it right that you are actively going to test the CD
> build process in a long enough time before the release and send patches
> in time to make sure the changes will be part of the release?
>
> If not - please stop
On Mon, Jul 17, 2017 at 12:09:30AM +0200, Christian Seiler wrote:
> [...] downstreams should be able to reproduce Debian images.
> In the short term only in functionality and not bit-by-bit, but I
> would consider reproducible image builds a worthwhile long-term goal
> after fully reproducible pack
On Tue, Jul 11, 2017 at 10:44:47AM -0500, Don Armstrong wrote:
> On Tue, 11 Jul 2017, Bjørn Mork wrote:
> > Previously I could ask a user to do e.g. 'ifconfig wwan0'. Now?
>
> sudo ip link; sudo ip addr;
no need for sudo, this is enough:
ip link ; ip addr
or even shorter:
ip l ; ip a
--
c
On Fri, Jun 30, 2017 at 11:56:37AM -0400, gwmf...@openmailbox.org wrote:
> Ultimately, it wouldn't be as big a deal if it was possible to change the
> default umask for the gnome-session in Debian Stretch.
the fact that it's impossible for you, doesnt mean it's impossible for everyone.
sorry, but
On Mon, Jun 26, 2017 at 10:23:56PM +0200, Ralf Treinen wrote:
> What is your opinion? Policy says "should", not "must". If you agree
> with the MBF, what do you think would be the appropriate severity?
"normal" if there are no issues and "important" if you've encountered
possible problems.
and th
On Mon, Jun 26, 2017 at 02:30:24PM +0200, Benjamin Drung wrote:
> The same complaint can be said about the AMD microcode updates.
quite probably, yes. but that doesn't make any crap any better.
--
cheers,
Holger
signature.asc
Description: Digital signature
On Mon, Jun 26, 2017 at 08:39:10AM -0300, Henrique de Moraes Holschuh wrote:
> As far as I know, so far OCaml is the only one that was verified to be
> caused by the SKL150 erratum.
[...]
thanks for providing these details.
--
cheers,
Holger
signature.asc
Description: Digital signatu
On Mon, Jun 26, 2017 at 01:51:25PM +0500, Andrey Rahmatullin wrote:
> > but YOU MUST INSTALL THIS BINARY BLOB
> How is it worse than the blobs already in your hardware?
it opens the door for targeted attacks.
--
cheers,
Holger
signature.asc
Description: Digital signature
On Sun, Jun 25, 2017 at 09:19:36AM -0300, Henrique de Moraes Holschuh wrote:
[...]
> Apparently, Intel had indeed found the issue, *documented it* (see
> below) and *fixed it*. There was no direct feedback to the OCaml
> people, so they only found about it later.
[...]
> We do not have enough info
On Tue, Jun 06, 2017 at 09:38:29AM -0400, Nikolaus Rath wrote:
> Personally, I would only ever download a DVD image if I was on a *slow*
> connection and knew that I had to install to multiple machines.
still then, I would rather use netinst plus a proxy…
--
cheers,
Holger
signature.
On Mon, Jun 05, 2017 at 03:03:08PM +0100, Ian Jackson wrote:
> Recommends bloat as a whole is a serious problem for the whole
> project.
I disagree.
Both from my personal POV as well as from the feedback I get from Debian
users. There are many things in Debian being complained about, "recommend
On Tue, May 23, 2017 at 06:34:09PM +0100, Sean Whitton wrote:
> On Tue, May 23, 2017 at 06:38:29PM +0200, Emilio Pozuelo Monfort wrote:
> > I have to deal with packages in svn, git-bp and plain git, and have started
> > to
> > write a set of (ugly) scripts that perform common actions in each of th
Hi Andreas,
On Thu, May 18, 2017 at 09:07:53AM +0200, Andreas Tille wrote:
> > I think that in the mid-term (probably even in short term) you'll *save*
> > developer time by switching to git,
> And your thinking is based on what arguments?
a.) git is a lot faster than svn on most operations, wh
On Mon, May 22, 2017 at 07:52:34AM +, Riku Voipio wrote:
> Right now, if you have a minor change - such fixing Homepage: or typo on
> definition, it's not as straitforward as submitting a pull request. And
> it gets much worse if you want to patch against upstream or build a new
> upstream vers
On Wed, May 17, 2017 at 10:19:24PM +0200, Andreas Tille wrote:
> In short: There is no doubt that Git is the better VCS but spending
> developer time simply to switch lots of packages from an old VCS to a
> modern one has zero effect on users desktops and has no high priority.
I think that in th
On Mon, May 15, 2017 at 08:01:40PM +0200, Adam Borowski wrote:
> A good page is one that lets you find information quickly, [...]
which sadly www.debian.org doesnt deliver. I still use the sitemap to find
*anything*… and even with that, I still also resort to bookmarks
and search engines.
it's n
On Sun, May 14, 2017 at 10:06:06PM +0100, Ben Hutchings wrote:
> $ for type in arch bzr cvs darcs git hg mtn svn; do
> > printf '%s: ' $type
> > grep-dctrl -FVcs-$type -sPackage 'debian.org'
> > /var/lib/apt/lists/httpredir.debian.org_debian_dists_unstable_*_Sources \
> > | wc -l
> > d
On Sun, May 14, 2017 at 10:49:34AM -0700, Sean Whitton wrote:
> Alitoh is 90% simple git hosting, 5% managing push access to git repos,
> and 5% mailing lists.
I think you are forgetting about the other 90% of the work here…
And that is a really huge task, I'm wondering whether actually a GR mig
On Mon, May 01, 2017 at 11:09:26AM +0200, Christian Seiler wrote:
> My point is just the following: this is really nothing new.
> Some packages have been doing things like this for over a
> decade.
Thanks for coming up with these facts.
(Much more interesting than developers of "system A" discus
On Fri, Apr 21, 2017 at 01:44:40PM +0200, Paul Gevers wrote:
> I don't think this number is bad per-se (assuming this extra_source_only
> just meant it has "Build-Using"). The bad thing in my opinion is when
> multiple version are kept around for a long time.
I consider the life time of stretch t
On Fri, Apr 21, 2017 at 01:00:20PM +0200, Lucas Nussbaum wrote:
> FYI, that's the number of additional copies of source packages in
> stretch, per source package:
>
> udd=> select source, count(*) from sources where release='stretch' and
> component='main' and extra_source_only group by source ord
On Thu, Apr 06, 2017 at 09:42:33AM +, Holger Levsen wrote:
> Finally, as Lars pointed out, running
> /usr/lib/diaspora-common/scripts/diaspora-download.sh
> in postinst is both horrible from a security point of view, plus it's a
> policy violation, so that's two m
On Thu, Apr 06, 2017 at 11:17:26AM +0530, Pirate Praveen wrote:
> Current version in unstable does not have any RC bugs,
*filed*, as this very thread shows. It *has* RC bugs.
oh, and you seem to miss #856720 which is a open RC bug.
> Losing diaspora-installer after putting years long effort wou
On Thu, Mar 30, 2017 at 10:27:46AM +0200, Florian Weimer wrote:
> What really annoys me about this whole situation is this: I think no
> one presently argues that the GPLv2 prevents people from distributing
> pre-built binaries for proprietary operating systems. I can take
> Hotspot (a component o
Hi Patrick,
On Sun, Mar 26, 2017 at 11:22:00AM +, Patrick Schleizer wrote:
> A convention on listen port local or all network interfaces etc. would
> be desirable.
I agree, though I'm not sure we can get consensus on this…
However, I also think that you should restart this discussion once st
On Wed, Mar 15, 2017 at 09:23:47PM -0700, Michael Lustfield wrote:
> Where can i read more about our logo's history? (at least for how long they
> were used)
https://www.debian.org/doc/manuals/project-history/ch-detailed.en.html#s4.3
has some info about when the swirl logo was introduced but nothi
On Thu, Mar 09, 2017 at 10:14:13AM -0800, Russ Allbery wrote:
> Well, I strongly disagree with you. I think this would take things in the
> wrong direction; I like that software is fully useful when Recommends are
> enabled at the cost of some bloat.
>
> If you don't want possibly unused software
- Forwarded message from Francois Gouget -
Date: Thu, 9 Mar 2017 14:23:52 +0100 (CET)
From: Francois Gouget
To: debian-devel@lists.debian.org
Subject: Virus spam in the bug tracker
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
List-Id:
This has been mentionned before but today I discove
On Tue, Mar 07, 2017 at 04:40:15PM +, Ian Jackson wrote:
[...]
> I would like to shelve this suggestion. The concept of
> antimetapackages can certainly be used this way from a technical point
> of view, but I think the goal there is controversial. Maintainers of
> packages currently in main
On Mon, Feb 20, 2017 at 04:42:49PM -0800, Russ Allbery wrote:
> To say my opinion explicitly, since there's been a lot of discussion here,
> some of which I've been involved in somewhat ambiguously:
Thanks for writing this up, Russ. I fully agree with *everything* you said here:
> I think this i
On Mon, Feb 20, 2017 at 09:59:29PM +, Ian Jackson wrote:
> My advice would be to avoid asking the TC such general questions.
My advice too.
> There are two sensible questions:
>
> * Should the following bugs be RC ?
> [ list of 20 bugs or whatever ]
with a list of 20 bugs I dont think
On Mon, Feb 20, 2017 at 10:29:28AM -0800, Russ Allbery wrote:
> The point is that they don't randomly fail in the sense that they don't
> fail n% of the time when run in any possible build environment.
…but point taken, not all FTBFS bugs are RC(!) as
<20170220152410.3mkm5tebg5i2y...@perpetual.pse
On Mon, Feb 20, 2017 at 10:29:28AM -0800, Russ Allbery wrote:
> This is, in a sense, an unreliable test, but it's not unreliable in a way
> that directly affects the main line of package development.
until someone affected wants to contribute…
--
cheers,
Holger
signature.asc
Descript
On Mon, Feb 20, 2017 at 01:46:20PM +0100, Vincent Bernat wrote:
> As a rule of thumb, upstream usually knows better than me which tests
> are important. Tests are quite important for the packager to know if
> they didn't make an obvious mistake when updating a package (e.g new
> dependency missing,
401 - 500 of 1240 matches
Mail list logo
