On Fri, 13 Dec 2019, Steve Langasek wrote:
> On Fri, Dec 13, 2019 at 08:46:35PM +0100, Alexander Wirt wrote:
> > On Wed, 11 Dec 2019, Sam Hartman wrote:
>
> > > TL;DR: Treating people with respect is hard and very contextual.
> > > Choosing to change how you talk
On Wed, 11 Dec 2019, Sam Hartman wrote:
> TL;DR: Treating people with respect is hard and very contextual.
> Choosing to change how you talk about something to make people more
> comfortable doesn't always mean you were obligated to make that change.
> Sometimes you're just promoting connection.
On Wed, 09 Oct 2019, Sam Hartman wrote:
> >>>>> "Alexander" == Alexander Wirt writes:
>
> Alexander> On Sun, 15 Sep 2019, Jonas Meurer wrote:
> >> Sam Hartman: >>>>>> "Bastian" == Bastian Blank
> >>
On Sun, 15 Sep 2019, Jonas Meurer wrote:
> Sam Hartman:
> >> "Bastian" == Bastian Blank writes:
> >
> > Bastian> Hi Sam
> > Bastian> On Sun, Sep 08, 2019 at 05:35:10PM -0400, Sam Hartman wrote:
> > >> The Salsa CA pipeline is recommended.
> >
> > Bastian> For this I need to
On Fri, 30 Aug 2019, Raphael Hertzog wrote:
> Hi,
>
> On Fri, 30 Aug 2019, Alexander Wirt wrote:
> > > We're not speaking of crap software, we're just speaking of software that
> > > can't be maintained multiple years by backports of security patches, where
>
On Fri, 30 Aug 2019, Raphael Hertzog wrote:
> Hi,
>
> On Fri, 30 Aug 2019, Alexander Wirt wrote:
> > > We're not speaking of crap software, we're just speaking of software that
> > > can't be maintained multiple years by backports of security patches, where
>
On Fri, 30 Aug 2019, Raphael Hertzog wrote:
> Hi,
>
> On Fri, 30 Aug 2019, Alexander Wirt wrote:
> > > We're not speaking of crap software, we're just speaking of software that
> > > can't be maintained multiple years by backports of security patches, where
>
On Fri, 30 Aug 2019, Raphael Hertzog wrote:
> On Fri, 30 Aug 2019, Alexander Wirt wrote:
> > There were several discussions over the last years. And yes, our vision of
> > backports does not match the vision of those fastpace/not ready for
> > stable/whatever you call them
On Fri, 30 Aug 2019, Raphael Hertzog wrote:
> On Fri, 30 Aug 2019, Alexander Wirt wrote:
> > There were several discussions over the last years. And yes, our vision of
> > backports does not match the vision of those fastpace/not ready for
> > stable/whatever you call them
On Fri, 30 Aug 2019, Raphael Hertzog wrote:
> On Fri, 30 Aug 2019, Alexander Wirt wrote:
> > There were several discussions over the last years. And yes, our vision of
> > backports does not match the vision of those fastpace/not ready for
> > stable/whatever you call them
On Fri, 30 Aug 2019, Raphael Hertzog wrote:
> Hi,
>
> On Fri, 30 Aug 2019, Pirate Praveen wrote:
> > Fast Track repo works exactly like current backports except the packages
> > are added from unstable (or experimental during transitions and freeze)
> > as they cannot go to testing and hence to
On Fri, 30 Aug 2019, Raphael Hertzog wrote:
> Hi,
>
> On Fri, 30 Aug 2019, Pirate Praveen wrote:
> > Fast Track repo works exactly like current backports except the packages
> > are added from unstable (or experimental during transitions and freeze)
> > as they cannot go to testing and hence to
On Fri, 30 Aug 2019, Raphael Hertzog wrote:
> Hi,
>
> On Fri, 30 Aug 2019, Pirate Praveen wrote:
> > Fast Track repo works exactly like current backports except the packages
> > are added from unstable (or experimental during transitions and freeze)
> > as they cannot go to testing and hence to
Hi,
I was pointed to that thread within a listmaster complaint. Please let me all
remember you to our netiquette [1] and our code of conduct [2].
The thread is also completly off-topic for debian-users and I will shut it
down.
Alex - Debian Listmaster
P.S. I am not subscribed and answering to
On Fri, 16 Aug 2019, Raphael Hertzog wrote:
> Hi,
>
> On Fri, 16 Aug 2019, gregor herrmann wrote:
> > From what I know, this what not a "foolish user action" but an action
> > by a dedicated maintainer who enabled salsa-ci for all packages
> > ("projects") of a specific team; so they used a
On Fri, 16 Aug 2019, Daniel Leidert wrote:
> Am Freitag, den 16.08.2019, 08:58 +0200 schrieb Alexander Wirt:
> > On Fri, 16 Aug 2019, gregor herrmann wrote:
>
> [..]
> > > From what I know, this what not a "foolish user action" but an action
> > > by
On Fri, 16 Aug 2019, gregor herrmann wrote:
> On Wed, 14 Aug 2019 08:39:22 +0100, Ian Jackson wrote:
>
> > Alexander Wirt writes ("Re: salsa.debian.org partially down"):
> > > It is already recovered. We will investigate where we can extend the
> > &
On Tue, 13 Aug 2019, Hector Oron wrote:
> Hello,
>
> Missatge de Bastian Blank del dia dt., 13 d’ag.
> 2019 a les 11:51:
> >
> > Hi folks
> >
> > salsa.debian.org is partially down for now. Especially everything that
> > concerns Salsa CI.
> >
> > Someone decided to inject a few thousand CI
On Tue, 13 Aug 2019, Ian Jackson wrote:
> Alexander Wirt :
> > That list is still missing any other advocated speaking for the lists,
> > I would really prefer if at least Ian Jackson would speak up.
>
> Hi. I think this list would be a good idea. Indeed, it was during
On Mon, 12 Aug 2019, Andrej Shadura wrote:
> Hi,
>
> On Sun, 11 Aug 2019 at 14:57, Daniel Leidert wrote:
> >
> > Am Sonntag, den 11.08.2019, 07:26 +0200 schrieb Andrej Shadura:
> > > On Sun, 11 Aug 2019, 04:18 Drew Parsons, wrote:
> > > > We have the policy of not pulling files from the
On Wed, 31 Oct 2018, Hans van Kranenburg wrote:
> On 10/09/2018 06:09 PM, Debian Bug Tracking System wrote:
> > Thank you for filing a new Bug report with Debian.
>
> Ping! :)
>
> Is there anything else you want to know? We'd like to have this sorted
> out well beforehand getting into any
On Sat, 04 Aug 2018, Elana Hashman wrote:
> Package: lists.debian.org
> Severity: wishlist
>
> Hello!
>
> I realize that alioth-lists.debian.net is only a temporary service and
> will be going away within the next couple of years[1]. It would be
> better to move the Clojure packaging list
>
On Sat, 04 Aug 2018, Elana Hashman wrote:
> Package: lists.debian.org
> Severity: wishlist
>
> Hello!
>
> I realize that alioth-lists.debian.net is only a temporary service and
> will be going away within the next couple of years[1]. It would be
> better to move the Clojure packaging list
>
On Fri, 09 Aug 2019, Benny Pedersen wrote:
Hi,
> > Thanks, postscript is not part of the Debian package. I'll try to put:
> > service postfix restart
>
> this is not working, postfix send logs to syslogd, so restarting postfix is
> not what to do, restart the syslogd will work
>
> please
Wrong version
===
Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.
___
Pkg-ruby-extras-maintainers mailing list
On Wed, 24 Jul 2019, Alexander Zangerl wrote:
> On Wed, 24 Jul 2019 07:07:51 +0200, Philip Hands writes:
> >You may be responding on behalf of people who turn out not to exist.
>
> well, i do exist. i have a few packages that aren't vc'd, and i don't see
> any need to change that. while i don't
On Mi, 17 Jul 2019, Otto Kekäläinen wrote:
> Hello!
>
> There are now 10 people discussing "Licensing salsa-ci pipeline" in
> private thread that really should belong into a Debian mailing list.
>
> Can you please create this list now?
>
> If you think "debian-salsa-ci" is too small, then
Hi,
now that buster was released we are pleased to announce the availability of
buster-backports and stretch-backports-sloppy.
== What to upload where ==
As a reminder, uploads to a release-backports pocket are to be taken
from release + 1, uploads to a release-backports-sloppy pocket are to
Wrong version (10) and distribution (stretch-backports) combination
===
Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.
___
Pkg-grass-devel
On Mon, 08 Jul 2019, Jonas Meurer wrote:
> Package: lists.debian.org
> Severity: normal
>
> Hello,
>
> as discussed on debian-project and debian-mentors [1], the scope of
> debian-mentors@lists.d.o was broadened to explicitely include questions
> regarding Debian infrastructure projects.
>
>
On Sat, 06 Jul 2019, Stefano Zacchiroli wrote:
> On Sat, Jul 06, 2019 at 08:00:58PM +0200, Alexander Wirt wrote:
> > But that is my personal mindset I am coming from. If such a mindset is
> > outdated nowadays and not wanted anymore I offer to resign as a listmaster.
>
>
On Sat, 06 Jul 2019, Alexander Wirt wrote:
> On Tue, 02 Jul 2019, Joerg Jaspert wrote:
>
> > On 15451 March 1977, Alexander Wirt wrote:
> >
> > > > The tone is absolutely civilized.
> > > > And yet, the cost to people who have to do this educat
On Tue, 02 Jul 2019, Joerg Jaspert wrote:
> On 15451 March 1977, Alexander Wirt wrote:
>
> > > The tone is absolutely civilized.
> > > And yet, the cost to people who have to do this education again and
> > > again is really high.
> > Thats possible, b
On Tue, 02 Jul 2019, Sam Hartman wrote:
> >>>>> "Alexander" == Alexander Wirt writes:
>
> Alexander> On Tue, 02 Jul 2019, Sam Hartman wrote:
> >>
> >>
> >>
> >> [listmaster copied in hopes they will
On Tue, 02 Jul 2019, Sam Hartman wrote:
>
>
>
> [listmaster copied in hopes they will agree with my assessment here]
I don't agree, I think that discussion is important and the tone is still
civilized.
Alex - Listmaster - but mainly speaking for myself
On Wed, 19 Jun 2019, Ralph Seichter wrote:
> * Alexander Wirt:
>
> > $myhostname = 'bitfenix-server';
>
> Hmmm. Should that not be
>
> $myhostname = "bitfenix-server.$mydomain";
>
> instead? I thought that $myhostname is expected to be a
On Wed, 19 Jun 2019, Dorian ROSSE wrote:
> I don’t know where my setup want to drive me…
>
> Anyone has a repair ?
pardon? I attached a fixed version.
Alex
On Wed, 19 Jun 2019, Dorian ROSSE wrote:
> When I say the amavis shell want become myself crazy about my Ubuntu server… :
Sorry, I am too stupid. It is too warm, you need to quote:
use strict;
$myhostname = 'bitfenix-server';
1;
ank you in advance to bring your help,
>
> Regards.
>
>
> Dorian ROSSE.
>
>
>
> Provenance : Courrier<https://go.microsoft.com/fwlink/?LinkId=550986> pour
> Windows 10
>
>
>
> ____
> De : amavis-users de
&
On Wed, 19 Jun 2019, Ralf Hansen wrote:
Hi,
> i am using Ubuntu 16.04 and unable to find the decoders for the following
> extensions.
>
> Jun 18 17:54:00 xxx amavis[9921]: No decoder for .F
> Jun 18 17:54:00 xxx amavis[9921]: No decoder for .deb
> Jun 18 17:54:00 xxx amavis[9921]:
On Tue, 18 Jun 2019, Ralph Seichter wrote:
> * Olivier:
>
> > Il y a un message d'erreur clair pourtant:
>
> Please use English in the future (as required for most mailing lists).
>
> > Starting amavisd: Number found
> > where operator expected at /etc/amavis/conf.d/50-user line 13, near "1"
>
On Fri, 07 Jun 2019, Wookey wrote:
> On 2019-06-07 17:24 +0200, Adam Borowski wrote:
> > * CSD is still a thing. No, your special program shouldn't get to ignore
> > system theme, put controls in wrong order, miss some controls, not respond
> > to minimize/etc if it's currently busy, etc.
On Fri, 07 Jun 2019, Thomas Goirand wrote:
> On 6/5/19 4:08 PM, Norbert Preining wrote:
> > This should be
> > completely independent from what one can do on salsa.
> > So I propose that whatever one's level within Debian is, it should not
> > change the status on salsa.
>
> I also find it
On Thu, 06 Jun 2019, Sam Hartman wrote:
> > "Bastian" == Bastian Blank writes:
>
> Bastian> Hi Sam
> Bastian> On Thu, Jun 06, 2019 at 11:57:41AM -0400, Sam Hartman wrote:
> >> However, it's a lot easier to get a foo-guest account on salsa
> >> than it is to get a foo guest
On Wed, 05 Jun 2019, Ralph Seichter wrote:
> I have spent quite some time looking for a decent Perl IDE (and I mean
> IDE, not just an editor) with debugging capabilities. Alas, my search
> was not fruitful. Years back, I had a go with EPIC [1], but it is
> incompatible with current Eclipse
On Wed, 05 Jun 2019, Adrian Bunk wrote:
> On Wed, Jun 05, 2019 at 10:14:50AM -0400, Sam Hartman wrote:
> > > "Norbert" == Norbert Preining writes:
> >
> > Norbert> I would propose something else: Debian rights are defined
> > Norbert> by presence/absence of a GPG key in certain key
On Thu, 06 Jun 2019, Andreas Tille wrote:
> On Wed, Jun 05, 2019 at 10:14:50AM -0400, Sam Hartman wrote:
> > > "Norbert" == Norbert Preining writes:
> >
> > Norbert> I would propose something else: Debian rights are defined
> > Norbert> by presence/absence of a GPG key in certain
On Sun, 02 Jun 2019, mabi wrote:
Hi,
> With native SpamAssassin it is possible to have per domain or even per user
> custom scores for any SA rules.
>
> Now that I am using Amavis which manages SpamAssassin I was wondering if it
> is still possible to have per domain different rules scoring?
On Thu, 30 May 2019, Chris Lamb wrote:
> Hi Ivo,
>
> > > Please consider unblocking lintian 2.15.0 for buster (from 2.9.1). This
> > > was specifically requested in #929577 by Mattia Rizzollo:
> >
> > This really should have been discussed in advance.
>
> I completely agree. The problems
On Thu, 30 May 2019, Chris Lamb wrote:
> Hi Ivo,
>
> > > Please consider unblocking lintian 2.15.0 for buster (from 2.9.1). This
> > > was specifically requested in #929577 by Mattia Rizzollo:
> >
> > This really should have been discussed in advance.
>
> I completely agree. The problems
On Fri, 26 Apr 2019, mohit phulera wrote:
> Which projects are removed from Gsoc 2019
> list ?
The following slots were requested:
Android SDK Tools in Debian: 2
Continuous Integration for biological applications inside Debian: 0
Debian Cloud Image Finder: 1
On Fri, 26 Apr 2019, Kuashik Reddy wrote:
> oh . for 8 projects , there are only 6 slots :-(please let us know the slot
> allocation asap :-)
You are wrong. The other remaining projects already said that none of the
students were good enough.
Therefore we didn't request slots for those
On Fri, 26 Apr 2019, Kuashik Reddy wrote:
> hello team ,
>
> just saw fossasia announced that they got 16 slots for gsoc .want to know how
> much did debian get ?did it get the complete number of slot for every project
> ?or is there anything less than that ?can u tell the number of slots and
On Wed, 27 Mar 2019, Jonas Meurer wrote:
> Hi Alex,
>
> Alexander Wirt:
> > On Tue, 26 Mar 2019, Jonas Meurer wrote:
> >> Alexander Wirt:
> >>> In my experience as a former mailman admin and listadmin mailman is a
> >>> no-go.
> >>> Ge
On Tue, 26 Mar 2019, Jakob Hirsch wrote:
> Hi,
>
> so I noticed this morning that jessie-updates is gone from the mirrors.
> After some research, I found that this was kind of announced in
> https://lists.debian.org/debian-devel-announce/2019/03/msg6.html.
> Question is now, what should I
On Tue, 26 Mar 2019, Jonas Meurer wrote:
> Hi Alex,
>
> Alexander Wirt:
> >> While I agree that some "more modern" going way would be nice for lists,
> >> I don't think that is an easy task. Nor one where DPL can do much
> >> (unless listma
On Mon, 25 Mar 2019, Joerg Jaspert wrote:
> On 15352 March 1977, ans...@debian.org wrote:
>
> > Do you think Debian should be more active to establish (official)
> > presence on newer platforms?
>
> For those that are free, sure.
>
> > In particular I also wonder if Debian should look at
On Sat, 23 Mar 2019, Manas Kashyap wrote:
> Hola ,
> I am Manas Kashyap , an undergrad from India .
> I was looking in the projects that are approved by Debian for GSoC 2019 ,
> and i found the project *PHP packaging is still unapproved* .
> As time left for the application process is very less ,
On Thu, 21 Mar 2019, Steve Langasek wrote:
Hi Steve,
> On Thu, Mar 21, 2019 at 07:47:42PM +0100, Alexander Wirt wrote:
> > On Thu, 21 Mar 2019, Ghassan_Kanafani wrote:
>
> > > Can you provide the definitions of anti-semitism and "antirealis
On Thu, 21 Mar 2019, Nasir El-Amin wrote:
> So just to clarify your stance is that stating historically factual
> statements about human rights violations in a country where the project has
> decided to whole an event and where people of specific faiths and ethnicity
> will be excluded is off
Hi,
this is a warning and note from us listmasters. Please come back to a
civilized discussion style. I don't want to see any antisemitism or
antisrealism on that list. Either you have something substantial to add to
the _debconf_ discussion or please don't take part in that discussion.
On Tue, 19 Mar 2019, Kartik Kulkarni wrote:
Hi,
> I am interested in applying for the new contributor's wizard and was
> waiting for the mentor but no one has volunteered yet, I wanted to ask if
> anyone would be interested in mentoring for the project.
The project will not be part of our GSOC.
On Thu, 14 Mar 2019, Arthur de Jong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
>
> Hi,
>
> In jessie backports there is currently a 4.9 kernel (4.9.110-3+debu5~deb8u1)
> which is based on stretch 4.9.110-3+deb9u2. Since stretch now has
> 4.9.144-3.1 are there any plans to
Hi,
I was invited to be a speaker at the drupal con to talk about the
evolution of tooling in open source projects [1]. I will take part
in a panel together with other open source projects like Gnome
or Drupal, we talk about about the past - the tool we used, its history
and so on. Then we want
On Sat, 16 Feb 2019, Shashank wrote:
> Hello Manas
>
> ‐‐‐ Original Message ‐‐‐
> On Friday, February 15, 2019 5:03 PM, Manas Kashyap
> wrote:
>
> > Hola Mentors,
> > I am Manas Kashyap an undergrad at Amity University and i am applying for
> > GSOC this year and would like to be
On Thu, 14 Feb 2019, Ian Jackson wrote:
> Firstly, thanks for taking the time to read what I wrote. (Thanks
> also for Sam for his helpful perspective.)
>
>
> Stepping back a bit, and firmly putting my `user' hat on:
>
> My aim was to share my experience, because I guess the point of
>
On Wed, 13 Feb 2019, Ian Jackson wrote:
> Alexander Wirt writes ("Re: Removal of linux-base from jessie-backports broke
> Xen upstream CI"):
> > Jessie backports doesn't exist anymore. For some time now. It is already on
> > its way to archive.d.o.
>
> Thanks
On Wed, 13 Feb 2019, Ian Jackson wrote:
> Introduction
>
>
> I would like to recount a situation. I'm not sure where, if anywhere,
> the root bug(s) lie, but I am inclined to say that a big part of the
> problem was a change to the contents of jessie-backports. I would be
>
On Mon, 11 Feb 2019, Brad Warren wrote:
> I agree with the concerns about updating python3-cryptography in jessie.
>
> If we can’t update jessie, I’d ideally love to see the packages in
> jessie-backports updated. Despite the announcement that jessie-backports was
> discontinued ~6 months ago,
On Mon, 11 Feb 2019, Brad Warren wrote:
> I agree with the concerns about updating python3-cryptography in jessie.
>
> If we can’t update jessie, I’d ideally love to see the packages in
> jessie-backports updated. Despite the announcement that jessie-backports was
> discontinued ~6 months ago,
On Fri, 08 Feb 2019, Paul van der Vlis wrote:
> Op 08-02-19 om 15:29 schreef Alexander Wirt:
> > On Fri, 08 Feb 2019, Paul van der Vlis wrote:
> >
> >> Hello,
> >>
> >> I would like to have LTS support for backports. On most systems I use
> >>
On Fri, 08 Feb 2019, Paul van der Vlis wrote:
> Hello,
>
> I would like to have LTS support for backports. On most systems I use
> one or more packages from backports.
>
> When the same version of a package is in use in the next version of
> Debian, I guess backporting them is -in most cases-
On Sun, 03 Feb 2019, Ola Lundqvist wrote:
> Hi
>
> I can understand the view that gmail, yahoo and others are to blame for the
> lost message. It is after all that service that rejected it. I do however
> think we need to live with the fact that we may have users that tend to use
> such
On Sun, 03 Feb 2019, Ola Lundqvist wrote:
> Hi Antoine and Alexander
>
> Alexander:
> So what should we do to prevent this from happening?
Don't use gmail or at least tell me what exactly was wrong on the mail.
>
> Antoine:
> Thank you for pointing that out.
>
> I found this in the BTS:
>
On Sun, 03 Feb 2019, Antoine Beaupré wrote:
> On 2019-02-03 22:09:20, Ola Lundqvist wrote:
> > If someone have an idea on how I may have screwed this up myself I'm happy
> > to know. :-)
>
> After a quick glance, this might be gmail obsessing over DMARC. Typical
> problems all mailing lists
On Sun, 03 Feb 2019, Laura Arjona Reina wrote:
>
>
> El 3 de febrero de 2019 9:25:08 CET, Alexander Wirt
> escribió:
> >On Sun, 03 Feb 2019, Molly de Blanc wrote:
> >
> >> I changed the date on the draft to February 5th (because its the 3rd)
> >
Hi,
Debian is applying as a mentoring organization for the Google Summer of Code
2019 [1], an internship program open to university students aged 18 and up,
and will apply soon for the next round of Outreachy [2], an internship
program for people from groups traditionally underrepresented in
On Sun, 03 Feb 2019, Molly de Blanc wrote:
> I changed the date on the draft to February 5th (because its the 3rd)
> and edited it a little. I'm at FOSDEM and a little swamped right now. Is
> it possible for someone to send this out today?
That looks like a draft for a web page, not like a mail?
On Thu, 31 Jan 2019, Jaminy Prabaharan wrote:
Hi,
> Thanks for the consideration, Alex.
> Since the Organization application closes soon, it would be great if we
> could have a discussion in this thread to complete the application.
I am not sure if it makes sense, by now we have only one
On Thu, 31 Jan 2019, Hans-Christoph Steiner wrote:
>
> We the Debian Android Tools Team want to have a regular Debian team
> list, to entirely replace the alioth list. Just having a new list is
> good. Migrating the archives would be wonderful.
>
I don't that specific maintainer list is suited
On Tue, 29 Jan 2019, Michael Banck wrote:
> Ping?
its in my next round of list creations.
>
On Wed, 23 Jan 2019, Alexander Wirt wrote:
> Hi,
>
> the poll has spoken and the meeting will happen tomorrow at 20:00 UTC.
> I prepared an etherpad [1] for the agenda. Please add any additional points.
no one from the list showed up and we canceled the meeting.
Alex
s
Hi,
we want to have a meeting to organize the last details before submitting our
application to the gsoc interface. I created a poll [1].
If you want to participate please join us, please vote before wednesday
24:00UTC.
Thanks in advance
Alex
[1]
On Tue, 08 Jan 2019, Agustin Henze wrote:
> Hi Alex,
>
> On Wed, 2 Jan 2019 19:17:24 +0100 Alexander Wirt
> wrote:
> > On Wed, 02 Jan 2019, Agustin Henze wrote:
> >
> > > Hi formorer, I really appreciate your opinion but we still needing the
> > >
On Wed, 02 Jan 2019, Agustin Henze wrote:
> Hi formorer, I really appreciate your opinion but we still needing the
> mailing list.
Let me rephrase. I don't think that any other listmaster will create that
list.
So don't expect it.
Alex
signature.asc
Description: PGP signature
On Wed, 26 Dec 2018, Dominik George wrote:
> > >If there are other issues to solve than the lifespan of the package
> > >version, they must be solved in another way.
> >
> > I agree with you, it is the best outcome. But when people with power
> > (-backports ftp masters) are not willing to
On Wed, 26 Dec 2018, Dominik George wrote:
> > >If there are other issues to solve than the lifespan of the package
> > >version, they must be solved in another way.
> >
> > I agree with you, it is the best outcome. But when people with power
> > (-backports ftp masters) are not willing to
I agree with you, it is the best outcome. But when people with power
> (-backports ftp masters) are not willing to consider it, we have to go with
> plan B, which is less than ideal, but can move things forward.
>
> >On Wed, Dec 26, 2018 at 04:32:28PM +0100, Alexander Wirt wrote:
> &g
I agree with you, it is the best outcome. But when people with power
> (-backports ftp masters) are not willing to consider it, we have to go with
> plan B, which is less than ideal, but can move things forward.
>
> >On Wed, Dec 26, 2018 at 04:32:28PM +0100, Alexander Wirt wrote:
> &g
On Wed, 26 Dec 2018, Dominik George wrote:
> > I don't want backports to contain things are are not suited for a
> > release.
>
> That's why we are doing all this. It is NOT about anything to backports.
> It is about adding something new that uses the same RULES as backports,
> with a slight
On Wed, 26 Dec 2018, Dominik George wrote:
> > I don't want backports to contain things are are not suited for a
> > release.
>
> That's why we are doing all this. It is NOT about anything to backports.
> It is about adding something new that uses the same RULES as backports,
> with a slight
ng due to the exact one reason that hey have a shorter lifespan. No
> single other thing qualifies a package for -volatile if it is not
> qualified for -backports.
And this is also solved. I emptied the NEW queue two or three days ago. If
there are dependencies missing the backports wasn't test
ng due to the exact one reason that hey have a shorter lifespan. No
> single other thing qualifies a package for -volatile if it is not
> qualified for -backports.
And this is also solved. I emptied the NEW queue two or three days ago. If
there are dependencies missing the backports wasn't test
On Wed, 26 Dec 2018, Pirate Praveen wrote:
>
>
> On 2018, ഡിസംബർ 26 2:16:07 AM IST, Dominik George
> wrote:
> >Heisann, alle sammen,
> >
> >as announced in the recent thread about maintaining, I hereby propose a
> >repository that allows making “backports” of packages available to
> >users
>
On Wed, 26 Dec 2018, Pirate Praveen wrote:
>
>
> On 2018, ഡിസംബർ 26 2:16:07 AM IST, Dominik George
> wrote:
> >Heisann, alle sammen,
> >
> >as announced in the recent thread about maintaining, I hereby propose a
> >repository that allows making “backports” of packages available to
> >users
>
On Tue, 25 Dec 2018, Dominik George wrote:
> > We already told you to build your own repo.
>
> You should probably start with identifying the senders of mail
> correctly ☺. I am not the gitlab maintainer (and will never be).
https://lists.debian.org/debian-backports/2018/12/msg00028.html
This
On Tue, 25 Dec 2018, Dominik George wrote:
> > We already told you to build your own repo.
>
> You should probably start with identifying the senders of mail
> correctly ☺. I am not the gitlab maintainer (and will never be).
https://lists.debian.org/debian-backports/2018/12/msg00028.html
This
On Tue, 25 Dec 2018, Dominik George wrote:
> Heisann, alle sammen,
>
> as announced in the recent thread about maintaining, I hereby propose a
> repository that allows making “backports” of packages available to users
> of the stable distribution, if those packages cannot be maintained in
>
On Tue, 25 Dec 2018, Dominik George wrote:
> Heisann, alle sammen,
>
> as announced in the recent thread about maintaining, I hereby propose a
> repository that allows making “backports” of packages available to users
> of the stable distribution, if those packages cannot be maintained in
>
On Tue, 18 Dec 2018, Pirate Praveen wrote:
> [adding -devel to cc]
>
> On 12/3/18 8:11 PM, Dominik George wrote:
> >> well, Debian is using gitlab!!! so this sentence has no sense. The
> >> problem here
> >> is that is a complex software that depends of a lot of pieces and it's
> >> not
> >>
101 - 200 of 2991 matches
Mail list logo
