Hello all.
On Wed, Sep 16, 2015 at 09:10:15PM +0200, Sven Hartge wrote:
[...]
> Why? The vlan package is not needed since at least Wheezy to configure
> VLANs on devices since the program "ip" can do everything the same or
> even better.
>
> Also ifupdown was changed to be able to configure VLAN
On Thu, Sep 17, 2015 at 10:55:58AM +0200, Andreas Henriksson wrote:
this, I think it would be a *service* to our users if we removed this
(and many other packages in similar situation) from the archive so that
we don't fool users into using (or wasting time even looking at)
long-deprecated softwa
❦ 17 septembre 2015 10:55 +0200, Andreas Henriksson :
>> Why? The vlan package is not needed since at least Wheezy to configure
>> VLANs on devices since the program "ip" can do everything the same or
>> even better.
>>
>> Also ifupdown was changed to be able to configure VLANs using "ip"
>> d
Hi,
first off I haven't found a "Standard" document documenting the command
feature of dak as currently used for DMs, so if there is one, that
should be merged with what I wrote up now.
Second, the reason why I started writing: I defined the possible
commands for the upcoming bikeshed feature, wh
Hi,
On Thu, Sep 17, 2015 at 12:23:02PM +0200, Andrew Shadura wrote:
> Two years ago I wrote a replacement for vconfig [1], which I thought
> would replace it in Debian, but that still hasn't happened.
>
> [1] https://bitbucket.org/andrew_shadura/fake-vconfig/src
Can I include that as is? Ah, yes
Hi,
On Thu, 17 Sep 2015, Joerg Jaspert wrote:
> Please check if I forgot something obvious or if there is some big error
> in it. Patches/git trees to merge from/... are welcome.
Please don't call this feature "Bikesheds" and don't hardcode this naming
in the suggested API. It was funny during on
Hi all,
It is time for an update about the lsb source package status, especially
as a quite important change landed in testing.
After the discussion [0] about these changes back in July (on both
debian-lsb@ and debian-devel@), I have uploaded src:lsb 9.20150826 to
unstable, building no LSB com
On Thu, Sep 17, 2015 at 02:41:11PM +0200, Raphael Hertzog wrote:
> Hi,
>
> On Thu, 17 Sep 2015, Joerg Jaspert wrote:
> > Please check if I forgot something obvious or if there is some big error
> > in it. Patches/git trees to merge from/... are welcome.
>
> Please don't call this feature "Bikeshe
Package: wnpp
Severity: wishlist
Owner: "Pierre-Elliott Bécue"
* Package name: mailman3-core
Version : 3.0.0
Upstream Author : Barry Warsaw, Mark Sapiro, Aurélien Bompard, Florian Fuchs,
Terri Oda, Stephen J. Turnbull, Abhilash Raj
* URL : http://list.org/
* License
Package: wnpp
Severity: wishlist
Owner: "Pierre-Elliott Bécue"
* Package name: mailman3-core
Version : 1.0.0
Upstream Author : Barry Warsaw, Mark Sapiro, Aurélien Bompard, Florian Fuchs,
Terri Oda, Stephen J. Turnbull, Abhilash Raj
* URL : http://list.org/
* License
On Sep 17, Didier 'OdyX' Raboud wrote:
> This change landed in stretch on September 14. and is de facto the
> "outright giving up" of LSB support for Debian, from stretch onwards. As
Is there any point in (formally?) maintaining LSB compatibility?
Is there any proprietary application that does
Package: wnpp
Severity: wishlist
Owner: "Pierre-Elliott Bécue"
* Package name: mailman3-postorius
Version : 1.0.1
Upstream Author : Anna Senarclens de Grancy, Benedict Stein, Barry Warsaw,
Mark Sapiro, Aurélien Bompard, Florian Fuchs, Terri Oda, Stephen J. Turnbull,
Abhilash Raj
Package: wnpp
Severity: wishlist
Owner: "Pierre-Elliott Bécue"
* Package name: mailman3-hyperkitty
Version : 1.0.0
Upstream Author : Barry Warsaw, Mark Sapiro, Aurélien Bompard, Florian Fuchs,
Terri Oda, Stephen J. Turnbull, Abhilash Raj
* URL : http://list.org/
* Lic
Package: wnpp
Severity: wishlist
Owner: "Pierre-Elliott Bécue"
* Package name: mailman3-hyperkitty-plugin
Version : 1.0.0
Upstream Author : Barry Warsaw, Mark Sapiro, Aurélien Bompard, Florian Fuchs,
Terri Oda, Stephen J. Turnbull, Abhilash Raj
* URL : http://list.org
On 14067 March 1977, Raphael Hertzog wrote:
>> Please check if I forgot something obvious or if there is some big error
>> in it. Patches/git trees to merge from/... are welcome.
> Please don't call this feature "Bikesheds" and don't hardcode this naming
> in the suggested API. It was funny during
Package: wnpp
Severity: wishlist
Owner: "Pierre-Elliott Bécue"
* Package name: mailman3
Version : 1.0.0
Upstream Author : Pierre-Elliott Bécue
* URL : none
* License : GPLv3
Programming Lang: ?
Description : Mailman3 mailing list manager suite
This pa
+++ Raphael Hertzog [2015-09-17 14:41 +0200]:
> Hi,
>
> On Thu, 17 Sep 2015, Joerg Jaspert wrote:
> > Please check if I forgot something obvious or if there is some big error
> > in it. Patches/git trees to merge from/... are welcome.
>
> Please don't call this feature "Bikesheds" and don't hardc
On Sep 17 2015, m...@linux.it (Marco d'Itri) wrote:
> On Sep 17, Didier 'OdyX' Raboud wrote:
>
>> This change landed in stretch on September 14. and is de facto the
>> "outright giving up" of LSB support for Debian, from stretch onwards. As
>
> Is there any point in (formally?) maintaining LSB c
Le jeudi, 17 septembre 2015, 08.46:24 Nikolaus Rath a écrit :
> I don't know about formal LSB compatibility, but there are several
> proprietary applications that require nothing but the
> /{lib,lib64}/ld-lsb.so* symlinks to work properly under Debian. So it
> would be great if they could be preser
Joerg Jaspert wrote:
>On 14067 March 1977, Raphael Hertzog wrote:
>>> Please check if I forgot something obvious or if there is some big error
>>> in it. Patches/git trees to merge from/... are welcome.
>> Please don't call this feature "Bikesheds" and don't hardcode this naming
>> in the suggested
On Thu, Sep 17, 2015 at 04:39:43PM +0100, Wookey wrote:
> +++ Raphael Hertzog [2015-09-17 14:41 +0200]:
> > Hi,
> >
> > On Thu, 17 Sep 2015, Joerg Jaspert wrote:
> > > Please check if I forgot something obvious or if there is some big error
> > > in it. Patches/git trees to merge from/... are welc
Hi Didier,
(Please honor the Mail-Followup-To or Mail-Copies-To header, thanks!)
On Sep 17 2015, Didier 'OdyX' Raboud wrote:
> Le jeudi, 17 septembre 2015, 08.46:24 Nikolaus Rath a écrit :
>> I don't know about formal LSB compatibility, but there are several
>> proprietary applications that requ
On Thu, 17 Sep 2015 17:20:21 +0100
Dominic Hargreaves wrote:
> On Thu, Sep 17, 2015 at 04:39:43PM +0100, Wookey wrote:
> > +++ Raphael Hertzog [2015-09-17 14:41 +0200]:
> > > Hi,
> > >
> > > On Thu, 17 Sep 2015, Joerg Jaspert wrote:
> > > > Please check if I forgot something obvious or if there
On Thu, Sep 17, 2015 at 04:39:43PM +0100, Wookey wrote:
> It wasn't supposed to be a joke. Bikeshed is an appropriate name, in
> the unix tradition of mildly amusing/punny names.
Not to mention that this bikeshed thread about the Bikeshed name is
going to be both epic and very meta.
--
Stefano Z
Steve McIntyre writes:
> Joerg Jaspert wrote:
>>On 14067 March 1977, Raphael Hertzog wrote:
Please check if I forgot something obvious or if there is some big error
in it. Patches/git trees to merge from/... are welcome.
>>> Please don't call this feature "Bikesheds" and don't hardcode
Excerpts from Stig Sandbeck Mathisen's message of 2015-09-16 15:57:15 -0700:
> Package: wnpp
> Severity: wishlist
> Owner: Stig Sandbeck Mathisen
>
> * Package name: hitch
> Version : 1.0.0~beta5
> Upstream Author : Varnish Software AB (and others)
> * URL : https://hi
Wookey wrote:
> +++ Raphael Hertzog [2015-09-17 14:41 +0200]:
> > Hi,
> >
> > On Thu, 17 Sep 2015, Joerg Jaspert wrote:
> > > Please check if I forgot something obvious or if there is some big error
> > > in it. Patches/git trees to merge from/... are welcome.
> >
> > Please don't call this featu
Le jeudi 17 septembre 2015 à 18:52 +0200, Stefano Zacchiroli a écrit :
> Not to mention that this bikeshed thread about the Bikeshed name is
> going to be both epic and very meta.
I herd you like bikesheds…
--
.''`. Josselin Mouette
: :' :
`. `'
`-
Hello.
I see "serious" bug reports asking for packages to drop
"dh_installdocs --link-doc" (see Bug #799316 for an example).
However, binNMUs break the reproducibility of the packages being
NMUed, since apparently the requirement of providing the *exact*
source code that was used for the *.deb is
On 2015-09-17 22:02, Santiago Vila wrote:
> Hello.
>
Hi,
> I see "serious" bug reports asking for packages to drop
> "dh_installdocs --link-doc" (see Bug #799316 for an example).
>
To clarify (for those who haven't read the bug): I requested that
--link-doc between arch:any AND arch:all packag
BTW: We *do* have an "Architecture: all" autobuilder.
(Just in case lack of it was an argument in favour of current
practice).
Am 17.09.2015 um 14:56 schrieb Didier 'OdyX' Raboud:
> After the discussion [0] about these changes back in July (on both
> debian-lsb@ and debian-devel@), I have uploaded src:lsb 9.20150826 to
> unstable, building no LSB compatibility packages anymore (besides lsb-
> release and lsb-base). As fa
[ Dropping cc and moving to devel only ].
On Thu, Sep 17, 2015 at 10:26:11PM +0200, Niels Thykier wrote:
> binNMUs are much more lightweight than source-full NMUs. Notably:
>
> * They are not subject to the NMU policy which involves delays
>- These are certainly politics that could be chang
On Thu, Sep 17, 2015 at 22:53:15 +0200, Santiago Vila wrote:
> Well, from the point of view of build-reproducibility, what is broken is the
> whole binNMU idea.
>
Well, not at all...
Cheers,
Julien
signature.asc
Description: Digital signature
m...@linux.it (Marco d'Itri) writes:
> Is there any point in (formally?) maintaining LSB compatibility? Is
> there any proprietary application that does actually benefit from it in
> the real world?
LSB seems pretty dead. I'm dubious there's much point in investing effort
in this.
--
Russ All
+++ Santiago Vila [2015-09-17 22:53 +0200]:
> [ Dropping cc and moving to devel only ].
>
>
> Well, from the point of view of build-reproducibility, what is broken is the
> whole binNMU idea.
It also causes a lot of trouble for multiarch. To be co-installable
libraries need to have exactly the s
On 17 September 2015 at 22:29, Wookey wrote:
> +++ Santiago Vila [2015-09-17 22:53 +0200]:
>> [ Dropping cc and moving to devel only ].
>>
>>
>> Well, from the point of view of build-reproducibility, what is broken is the
>> whole binNMU idea.
>
> It also causes a lot of trouble for multiarch. To
On Thu, Sep 17, 2015 at 10:26:11PM +0200, Niels Thykier wrote:
> Again, not saying it could not be changed, but binNMUs are used fairly
> often. Having to download the source code, add a changelog entry and
> sign the result would make any non-trivial transition a living hell.
There's no reason w
On 17/09/15 21:53, Santiago Vila wrote:
> Ok. It may be worth to change the tool to do source-only uploads instead
> (which, combined with the Arch: all autobuilder, should yield the
> same result).
BinNMUs don't upload any source at all. They instruct the autobuilders
to run sbuild with some non-
The following is a listing of packages for which help has been requested
through the WNPP (Work-Needing and Prospective Packages) system in the
last week.
Total number of orphaned packages: 668 (new: 3)
Total number of packages offered up for adoption: 178 (new: 2)
Total number of packages request
Package: general
Severity: normal
Dear Maintainer,
We should prepare that invention of quantum computers may break
SSH, HTTPS, PGP, and other encryptions we use in practice.
Packages like these providing SSH should be developed around this problem.
Also there should be written a user manual abo
On 2015-09-17 at 15:04, Robert Edmonds wrote:
> Wookey wrote:
>
>> +++ Raphael Hertzog [2015-09-17 14:41 +0200]:
>>> Please don't call this feature "Bikesheds" and don't hardcode
>>> this naming in the suggested API. It was funny during one Debconf
>>> talk... but it won't be funny in the long t
Processing commands for cont...@bugs.debian.org:
> close 799336
Bug #799336 [general] general: Prepare for quantum computers breaking
encryptions
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
799336: http://bugs.debian.org/cgi-bin/bugreport.c
On Thu, Sep 17, 2015 at 11:19:57PM -0400, The Wanderer wrote:
> I concur that this sort of wordplay in naming is a *nix tradition;
> however, I withhold comment as to whether the name "bikeshed" is
> appropriate in this case, as the first I remember hearing about them is
> this thread and I don't k
Clint Byrum writes:
> "hitch is a fork of stud. The fork is maintained by the Varnish
> development team, as stud seems abandoned by its creators, after the
> project was taken over by Google, with no new commits after 2012."
>
> Perhaps hitch should replace stud?
"stud" only exists in oldstable
45 matches
Mail list logo
