package: node-rollup-plugin-typescript
Version: 0.8.1-1
Severity: serious
Justification: the package is not usable
Got same error in node-locate-character and node-sourcemap-codec (tried with
node-rollup-plugin-typescript 1.0.0 in git as well and got same error)
node-sourcemap-codec$ rollup -c
On 2019, ജൂലൈ 26 7:04:07 PM IST, "Jérémy Lal" wrote:
>It seems several packages are installing files into
>"rollup-plugin-typescript".
I did not understand this, can you specify which packages you are referring to
here ?
>In this case, all such packages should agree upon the place where
to
load 'tslib/tslib.es6.js'
While running rollup from node-sourcemap-codec it failed
praveen@mahishasura:~/forge/node-sourcemap-codec$ rollup -c
[!] Error: Cannot find module 'tslib/tslib.es6.js' from
'/usr/lib/nodejs/rollup-plugin-typescript/dist
I was able to reproduce in a clean sid chroot.
Created chroot with debootstrap, chroot to directory, install nodejs, node-y18n
node -e "require('y18n');" internal/modules/cjs/loader.js:583
throw err; ^
On 2019, ജൂലൈ 10 8:40:21 PM IST, Xavier wrote:
>Le 10/07/2019 à 14:40, Pirate Praveen a écrit :
>> Package: pkg-js-autopkgtest
>> version: 0.8
>> severity: serious
>>
>> autopkgtest_rollup_src.js → autopkgtest_rollup_dest.js...
>> (!) Generated an empt
Package: uglifyjs.terser
Version: 4.1.0-1
Severity: serious
justification: insufficient minimum version breaks the package
If uglify.terser is updated to 4.1.0, node-terser and libjs-terser is
not updated along with it, causing the following error.
uglifyjs.terser dist/d3-zoom.js -o
Package: pkg-js-autopkgtest
version: 0.8
severity: serious
autopkgtest_rollup_src.js → autopkgtest_rollup_dest.js...
(!) Generated an empty bundle
(!) Unresolved dependencies
https://github.com/rollup/rollup/wiki/Troubleshooting#treating-module-as-external-dependency
d3-zoom (imported by
[adding Jonas to cc]
On Fri, 21 Jun 2019 08:36:15 +0200 Xavier wrote:
> Le 21/06/2019 à 06:04, Pirate Praveen a écrit :
> >
> >
> > On 2019, ജൂൺ 20 5:08:24 PM IST, Xavier wrote:
> >> Hello,
> >>
> >> there is something wrong with your patch
[adding Jonas to cc]
On Fri, 21 Jun 2019 08:36:15 +0200 Xavier wrote:
> Le 21/06/2019 à 06:04, Pirate Praveen a écrit :
> >
> >
> > On 2019, ജൂൺ 20 5:08:24 PM IST, Xavier wrote:
> >> Hello,
> >>
> >> there is something wrong with your patch
[adding Jonas to cc]
On Fri, 21 Jun 2019 08:36:15 +0200 Xavier wrote:
> Le 21/06/2019 à 06:04, Pirate Praveen a écrit :
> >
> >
> > On 2019, ജൂൺ 20 5:08:24 PM IST, Xavier wrote:
> >> Hello,
> >>
> >> there is something wrong with your patch
On 2019, ജൂൺ 20 5:08:24 PM IST, Xavier wrote:
>Hello,
>
>there is something wrong with your patch:
>W: node-terser source: binaries-have-file-conflict node-terser
>uglifyjs.terser usr/lib/nodejs/terser/dist/bundle.js
>
>Your link overrides a regular file
Only node-terser should include this
Package: node-terser
version: 3.14.1-2
severity: grave
Control: tags -1 patch
pravi@andhaka:~/forge/debian/git/js-team/vue.js$ sudo apt install
node-terser
[sudo] password for pravi:
Sorry, try again.
[sudo] password for pravi:
Reading package lists... Done
Building dependency tree
Reading
Control: tag -1 help
On Sun, 16 Jun, 2019 at 1:25 PM, Pirate Praveen
wrote:
When trying to use packaged version of node-vue-resource, Web Console
shows this error. UI elements just show the spinning circle forever.
Upstream is using rollup based build system and we converted
Package: node-vue-resource
Version: 1.5.1-1
severity: grave
Control: block 930404 by -1
When trying to use packaged version of node-vue-resource, Web Console
shows this error. UI elements just show the spinning circle forever.
Upstream is using rollup based build system and we converted it to
On Tue, 11 Dec 2018 17:21:56 +0100 Andreas Tille wrote:
> $ sudo apt-get install node-prismjs
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible
[Ccing doko explicitly]
On Sun, 21 Apr 2019 15:27:52 +0200 Paul Gevers wrote:
> Just to confirm, you do consider openjdk-11/11.0.3+7-2 suitable for
> buster, right? I haven't seen an unblock request, but would not be
> surprised if you are expecting that I'll just unblock it.
^^
--
Sent from
On 2019, ജൂൺ 6 11:00:16 AM IST, Xavier wrote:
>My reducejs tool gives a new analysis:
> * downgraded modules to embed
> - process-nextick-args : 2.0.0 => 1.0.7
This is handled by a patch.
On Wed, 05 Jun 2019 08:39:18 + Pirate Praveen
wrote:
> gitlab (11.10.5+dfsg-1) experimental; urgency=medium
Uploading to experimental because of freeze and libgit2 transition (even
though its a security update).
signature.asc
Description: OpenPGP digital signature
: source changed by Pirate Praveen
dpkg-buildpackage: info: host architecture amd64
dpkg-source --before-build .
fakeroot debian/rules clean
dh clean --with nodejs
debian/rules override_dh_auto_clean
make[1]: Entering directory
'/home/pravi/forge/debian/git/js-team/node-babel'
dh_auto_clean
make
package: uglifyjs.terser
version: 3.14.1-1
severity: grave
justification: it does not work at all
Sample repo https://salsa.debian.org/gi-boi-guest/node-d3-fetch
Also tried in https://salsa.debian.org/js-team/node-d3-scale-chromatic
with same error when trying to minimize
package: gitaly
severity: grave
version: 1.34.1+debian-1
Control: forwarded -1 https://gitlab.com/gitlab-org/gitaly/issues/1667
There was some code movement from gitlab-shell to gitaly and we need to
adjust gitaly configuration accordingly.
On Fri, 10 May 2019 21:04:33 +0200 Salvatore Bonaccorso
wrote:
> Source: sqlite3
> Version: 3.27.2-2
> Severity: grave
> Tags: security
> Justification: user security hole
>
> Hi,
>
> The following vulnerability was published for sqlite3.
>
> CVE-2019-5018[0]:
> Window Function Remote Code
On Tue, May 14, 2019 at 8:51 AM, d...@debian.org wrote:
Hi,
On Sun, May 12, 2019 at 09:55:33PM +0530, Pirate Praveen wrote:
We will have to file an unblock request for this to migrate to
testing.
Can you file it?
sorry for my afk, but thanks to release team (maybe), it migrated
>
Hi dai,
We will have to file an unblock request for this to migrate to testing.
Can you file it?
Thanks
Praveen
signature.asc
Description: OpenPGP digital signature
Control: severity -1 important
Control: reassign -1 ruby-bootsnap
On Tue, 23 Apr 2019 14:11:09 +0200 Gianfranco Costamagna
wrote:
> Source: rails
> Version: 2:5.2.2+dfsg-6
> Severity: important
> tags: patch
>
> Hello, as said, ruby+bootsnap is completely broken on at least armhf platform.
>
>
On Tue, 30 Apr 2019 23:20:41 +0200 Andreas Beckmann wrote:
> that error seems to be unrelated to the bundler version used:
This seems unrelated to diaspora-installer then. As I was able to
reproduce it with bundler 2.0 and after changing to bundler 1.17.3 it
worked. So it seems a fresh
On Sun, 31 Mar 2019 21:01:11 + =?utf-8?b?UGhpbGlwcGUgQ2zDqXJpw6k=?=
wrote:
> Package: gitlab
> Version: 11.4.9+dfsg-2~bpo9+1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> gitlab could not be installed.
>
> carrierwave 1.3.1 is installed but it's
On Sat, 13 Apr 2019 16:18:34 +0200 Andreas Beckmann wrote:
> Control: severity -1 serious
>
> On Mon, 18 Feb 2019 13:02:56 +0530 Pirate Praveen
> wrote:
> > > Installing gems with rubygems ...
> > > sh: 1: bundle: not found
>
> I can reproduce that in piup
On Fri, 18 Jan 2019 23:41:55 + Santiago Vila wrote:
> Failures:
>
> 1) Premailer::Rails::Hook when message also contains a text part does not
> replace any message part
> Failure/Error:
>expect { run_hook(message) }.to_not \
> change {
On 2019, മാർച്ച് 18 2:33:00 AM IST, Ximin Luo wrote:
>On Thu, 08 Mar 2018 17:53:27 + Ghislain Vaillant
> wrote:
>I had an attempt at this, but it is getting a bit hairy and I think it
>may be time to call it quits. My recommendation is for jupyter-notebook
>to patch out this functionality
Package: ruby-puppet-forge
Version: 2.2.9-2
Severity: serious
all tests pass with new faraday.
https://salsa.debian.org/puppet-team/ruby-puppet-forge/merge_requests/1
On 2019, മാർച്ച് 3 10:45:19 PM IST, Justin Hallett
wrote:
>Well I hope it comes to that personally, cause I think you have been
>doing a great job, it’s a TON of work to maintain all the depends you
>do for gitlab and honestly there are rarely issues and when they are
>you fix them very
On Mon, 25 Feb 2019 07:45:36 -0700 Justin Hallett
wrote:
> This ticket is bogus and should be closed and removed so that gitlab can be
> fixed in testing and restore the faith of its users.
I think we have not received the same level of respect from the rest of the
project. Since everyone is
) I have never had a major package just get pulled. I couldn’t use the
> back ports version since it required rails 2.3, so I had to go to
> experimental which is nuts. Pirate Praveen has been doing a great job trying
> to keep up with countless depends and keeping things up to date and s
On Mon, 18 Feb 2019 19:09:53 +0530 Pirate Praveen
wrote:
> It was originally packaged for gitlab and since we could not complete
> packaging all dependencies of gitlab, this was not a priority for
> buster. I was intending to get gitlab back in main including fix for
> this in time
On Thu, 14 Feb 2019 09:41:13 +0100 Paul Gevers wrote:
> While investigating ways to fix bug #896468 (new version for
> libjs-chartjs), I discovered that ruby-rails-assets-chartjs doesn't
> contain the source of Chart.js and for sure doesn't build Chart.js from
> the upstream source.
>
>
Control: severity -1 important
On Mon, 21 Jan 2019 09:53:39 +0100 Karl Stenerud
wrote:
> Package: disaspora-installer
> Version: 0.7.6.1
> Severity: grave
>
> Attempting to install diaspora-installer via apt fails with an error.
>
> Transcript:
>
> $ lxc launch images:debian/sid tester && lxc
On Fri, 15 Feb 2019 14:04:29 +0500 Pirate Praveen
wrote:
> Package: ruby-chromedriver-helper
> version: 2.1.0-1
> Severity: serious
> justification: unable use the package
> Control: affects -1 ruby-rails
>
> Bundler::GemRequireError: There was an error while tryi
Package: ruby-chromedriver-helper
version: 2.1.0-1
Severity: serious
justification: unable use the package
Control: affects -1 ruby-rails
Bundler::GemRequireError: There was an error while trying to load the
gem 'chromedriver-helper'.
Gem Load Error is: can't find executable chromedriver-helper
On Wed, 19 Dec 2018 00:55:39 +0100 Dominik George
wrote:
> >> We had volatile, which, redefined properly, could help. I am trying
> >to draft such a definition.
> >
> >Did you get a chance to work on it?
>
> I do have this on my todo list for around Christmas.
>
> People who know me that I
On Wed, Feb 13, 2019 at 2:16 PM, Chris Lamb wrote:
Hi Pirate,
> (ie. I don't think you can rule out apparmor either just yet.)
yes, culprit is apparmor only. After aa-teardown, I can start redis
service.
Great stuff. What's the next step here? Cearly this should Just
Work but I'm not
On Tue, Feb 12, 2019 at 11:17 PM, Chris Lamb wrote:
Hi Pirate,
Initially I tried editing /lib/systemd/system/redis-server.service
and
later I edited /lib/systemd/system/redis-server\@.service as well
(edited both these files)
> b) Exactly how you are editing the shipped .service
On Tue, Feb 12, 2019 at 9:44 PM, Chris Lamb wrote:
Hi Pirate,
https://wiki.debian.org/Packaging/Pre-Requisites#LXC has networking
setup instructions.
Still no dice and I don't really have the bandwidth to learn
another container technology. :(
May be ask lxc team for help?
I
On Tue, Feb 12, 2019 at 6:09 PM, Chris Lamb wrote:
Hi Pirate,
> (However, I am not sure why I do not have working networking
inside
> my container so I cannot debug it better on my end.)
But loopback is enough for redis-server, right?
Yes, but I can't even install without network. :)
On ചൊ, ഫെബ്രു 5, 2019 at 11:14 വൈകു, Chris Lamb
wrote:
severity 921176 serious
thanks
Hi Pirate,
[Dropping severity as it only affects LXC right now]
It is working on the same host machine with stretch(-backports)
container (5:5.0.3-3~bpo9+2). So host machine seems fine.
Thanks for
Package: ruby-spring
version: 2.0.2-1
severity: serious
justification: breaks rails newapp autopkgtest
Bundle complete! 18 Gemfile dependencies, 76 gems now installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
run bundle exec spring binstub --all
* bin/rake:
Control: fixed -1 1.1.6-1
Control: fixed -1 ruby-rack-oauth2/1.6.2-1
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Control: fixed -1 0.2.5-1
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Control: fixed -1 3.2.1-1
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
On Mon, 04 Feb 2019 15:30:20 +0500 Pirate Praveen
wrote:
>
>
> On തി, ഫെബ്രു 4, 2019 at 1:26 വൈകു, Pirate
> Praveen wrote:
> >
> >
> > On 2019, ഫെബ്രുവരി 4 1:20:11 PM IST, Chris Lamb
> > wrote:
> >> Hi,
> >>
> >>>
On തി, ഫെബ്രു 4, 2019 at 1:26 വൈകു, Pirate
Praveen wrote:
On 2019, ഫെബ്രുവരി 4 1:20:11 PM IST, Chris Lamb
wrote:
Hi,
redis-server service is failing to start in buster lxc container
Any update on this? :)
I'm traveling. hopefully tonight or tomorrow night I can try.
Adding Raju
On 2019, ഫെബ്രുവരി 4 1:20:11 PM IST, Chris Lamb wrote:
>Hi,
>
>> redis-server service is failing to start in buster lxc container
>
>Any update on this? :)
I'm traveling. hopefully tonight or tomorrow night I can try.
Adding Raju, and Abhijith, who may be able to try this before.
>
>Regards,
package: redis-server
version: 5:5.0.3-4
severity: grave
justification: unstable to start the service
journalctl -xe shows this error. This used to work before. It is clean
lxc install on a sid host.
sudo lxc-create -n buster -t debian -- -r buster
I was trying to install gitlab, but that
On 2019, ജനുവരി 13 11:26:54 PM IST, Dragos Jarca
wrote:
>after apt-get update and apt-get dist-upgrade...
>
>now gitlab cannot be used...
This is a different issue, please open a new bug.
>cannot upgrade to experimental to...
>
>root@omv:/usr/share/gitlab# apt-get install
On 2019, ജനുവരി 12 5:53:28 PM IST, Dmitry Smirnov wrote:
>Package: gitlab
>Version: 11.5.6+dfsg-1
>Severity: serious
>
>Installing "gitlab" on "testing" (with enabled "unstable") fails as
>follows:
>
>
>Setting up gitlab (11.5.6+dfsg-1) ...
>Could not find gem 'unicorn (~> 5.1)' in any of
Package: pcs
Version: 0.9.166-5
Severity: serious
https://ci.debian.net/packages/p/pcs/unstable/amd64
May be 0.10 version has a fix, it is delaying rails 5 testing migration, so
please fix it.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Control: fixed -1 0.9.15-1
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
On Wed, Jan 9, 2019 at 3:46 PM, t...@schleuder.org wrote:
You probably mean a debian package? Unfortunately the maintainer is
traveling currently and the rest of us don't know enough to build
the package.
We could probably produce an unofficial gem once the change is
finished
if that also
tion? You can update it to stable version as
per your current schedule.
Thanks
Praveen
signature.asc
Description: OpenPGP digital signature
into buster.
Thanks
Praveen
signature.asc
Description: OpenPGP digital signature
Control: reassign -1 debci
On Sun, 6 Jan 2019 20:12:58 +0100 Paul Gevers wrote:
> The same can be seen in the CI logs [1] for debci (and other packages)
> that were triggered for rails/2:5.2.0+dfsg-2 [2]. The issue is caused by
> a new version of rails.
This should be fixed in debci. We are
Control: fixed -1 2.0.6-1
Really add fixed version.
signature.asc
Description: OpenPGP digital signature
Control: severity -1 important
On Wed, 2 Jan 2019 10:57:31 +0100 Ruben Undheim
wrote:
> Bumped the severity since now nodejs 10 is in unstable.
I don't think this warrants an rc bug. It is only a warning and does not
affect npm functionality or violates any policy. Serious bugs are for
packages
Control: notfound -1 5.8.0+ds6-2
Control: found -1 1.2.18~dfsg-1
Control: fixed -1 5.8.0+ds-1
On Mon, 24 Dec 2018 10:33:48 +0100 Ralf Jung wrote:
> COMP_WORDBREAKS=${COMP_WORDBREAKS/=/}
>
> Please remove that line, or otherwise stop breaking unrelated packages.
This is indeed left over from
On Mon, 24 Dec 2018 10:33:48 +0100 Ralf Jung wrote:
>
> COMP_WORDBREAKS=${COMP_WORDBREAKS/=/}
>
> Please remove that line, or otherwise stop breaking unrelated packages.
>
I don't see such a line here.
https://salsa.debian.org/js-team/npm/blob/master/lib/utils/completion.sh
May be that came
On 2018, ഡിസംബർ 30 5:06:04 PM IST, Hideki Yamane wrote:
>Hi,
>
>On Tue, 13 Jun 2017 14:35:03 +0530 Pirate Praveen
>wrote:
>> I selected Malayalam during installation of last testing snapshot of
>> stretch, but the system did not have a Malayalam font installed. I'd
On 2018, ഡിസംബർ 29 12:29:12 AM IST, Jonas Smedegaard wrote:
>Quoting Pirate Praveen (2018-12-28 19:19:12)
>> When trying to build autoprefixer.js which build depends on
>> node-caniuse-lite, I got this error and upon inspection I found
>> data/features directory is
Package: node-caniuse-lite
version: 1.0.3915+dfsg-1
severity: grave
Justification: Makes it unusable
Control: block 837463 by -1
Control: tag -1 help
When trying to build autoprefixer.js which build depends on
node-caniuse-lite, I got this error and upon inspection I found
data/features
On 12/18/18 8:41 PM, Holger Levsen wrote:
> On Tue, Dec 18, 2018 at 08:38:39PM +0530, Pirate Praveen wrote:
>> But if that is not possible, volatile as a separate archive is also fine.
>
> instead of volatile we need PPAs.
I think a redefined volatile is the best option f
On 2018, ഡിസംബർ 18 7:14:14 PM IST, Rhonda D'Vine wrote:
> And yes, I'm with Alexander, the volatile maintenance can't be dumped
>on the backports team. It's a different workflow anyway.
My proposal for backports is to have only the dependencies of packages in
volatile that fall in the
[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
>> easy/possible to fit the definition. So, maybe we should create
Control: fixed -1 gitlab/11.5.3+dfsg-1
Closing this bug.
signature.asc
Description: OpenPGP digital signature
On Thu, 06 Dec 2018 17:17:46 +0100 Andreas Beckmann wrote:
>
> during a test with piuparts I noticed your package failed to install.
> gitaly is in main, but depends on gitlab-common which is in contrib.
> One of the two packages needs to move ...
gitlab-common is moved to main in 11.5.3+dfsg-1
On Thu, 29 Nov 2018 20:59:59 +0100 Moritz Muehlenhoff
wrote:
> Source: gitlab
> Severity: serious
>
> Gitlab is too fast-moving with weekly releases and backporting security fixes
> has already
> failed us for stretch, keep it out of testing.
Just a clarification, major release happens every
Control: severity -1 important
On Tue, 11 Dec 2018 14:18:30 -0800 Pranith Kumar wrote:
> Package: gitlab
> Version: 11.3.11+dfsg-1
> Severity: important
>
> Dear Maintainer,
>
> Trying to install gitlab throws the following error, please fix.
>
> Setting up gitlab (11.3.11+dfsg-1) ...
>
Control: severity -1 important
On Wed, 5 Dec 2018 13:16:29 +0100
=?UTF-8?B?RGF2aWQgTMOzcGV6IFphamFyYSAoRXJfTWFxdWkp?=
wrote:
> There's any new data about this bug?
Since I can't reproduce it in multiple systems, I'm reducing the severity. Did
you try 11.4.9?
--
Sent from my Android device
Control: severity -1 important
On Fri, 30 Nov 2018 10:50:54 +0530 Pirate Praveen
wrote:
> On Thu, 29 Nov 2018 18:08:13 +0100 Dominik George
> wrote:
> > Hi,
> >
> > >> It is not a regression in unstable, so it need not block the testing
> > >migrati
Control: fixed -1 11.4.9+dfsg-1
On Fri, 07 Dec 2018 09:56:54 +0530 Pirate Praveen
wrote:
> It should be fixed in 10.4.9 in experimental. I was able to update from
> 11.3.11 but I will confirm on a clean install too.
Confirmed on a clean install as well.
signature.asc
Description: O
On Tue, 04 Dec 2018 16:14:25 +1100 Dean Hamstead wrote:
> Package: gitlab
> Version: 11.3.11+dfsg-1
> Severity: important
>
> Dear Maintainer,
>
> Install gets stuck on this output, answering doest seem to help
>
> Precompiling assets...
> Webpacking...
> One CLI for webpack must be installed.
Control: severity -1 normal
On Thu, 06 Dec 2018 11:03:57 -0800 Pranith Kumar wrote:
> Package: gitlab
> Version: 11.3.11+dfsg-1
> Severity: important
>
> Dear Maintainer,
>
> When trying to install gitlab using "apt install gitlab", it fails with the
> following error message. The user chosen
On 2018, ഡിസംബർ 3 8:11:58 PM IST, Dominik George
wrote:
>We had volatile, which, redefined properly, could help. I am trying to
>draft such a definition.
Thanks, that is required to keep gitlab in a supportable form (unstable
directly is not the best option).
I think an Ubuntu PPA like
Control: fixed -1 8.3.3+dfsg-2
On Mon, 26 Nov 2018 08:49:25 -0700 Justin Hallett
wrote:
> I am also seeing the exact same issue with pull as well, I’d assume anything
> that uses gitlab-shell will see it.
>
> Looking at gitlab-shell it looks like it’s either missing or was renamed to
>
>
On 2018, ഡിസംബർ 2 10:57:54 AM IST, Pirate Praveen
wrote:
>Just check if gitaly version is latest. It looks like an issue with
>older gitaly version.
The root cause could be
#914496
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
On 2018, ഡിസംബർ 2 5:19:06 AM IST, "David López Zajara"
wrote:
>Control: severity -1 grave
>thanks.
>
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>Hi,
>
>I've done some more tests, the problem accesing repository on gitlab
>interface appears on all repositories.
>Here's the error
On 2018, നവംബർ 30 5:14:20 PM IST, Thorsten Glaser wrote:
>On Fri, 30 Nov 2018, Pirate Praveen wrote:
>
>> How about allowing gitlab to be backported directly from unstable?
>
>No.
>
>Backports are *always* from testing because a backport is
>supposed to be rep
On 2018, നവംബർ 30 1:29:59 AM IST, Moritz Muehlenhoff wrote:
>Source: gitlab
>Severity: serious
>
>Gitlab is too fast-moving with weekly releases and backporting security
>fixes has already
>failed us for stretch, keep it out of testing.
>
>To meaningfully support it for use on stable, this
On Thu, 29 Nov 2018 18:08:13 +0100 Dominik George
wrote:
> Hi,
>
> >> It is not a regression in unstable, so it need not block the testing
> >migration.
>
> ...but it needs get gitlab autoremoved from testing if not fixed :).
Yes, we need to find the root cause or reduce severity if there is
Control: severity -1 important
On Thu, 29 Nov 2018 22:19:14 +0200 Dragos Jarca
wrote:
> Package: gitlab
> Version: 11.3.10+dfsg-2
> Severity: grave
> Justification: renders package unusable
I have seen such transient failures go away after a restart of gitlab and
gitaly services. So
On Thu, 29 Nov 2018 22:19:14 +0200 Dragos Jarca
wrote:
> Dear Maintainer,
>
> When go to any project receive Err 500:
Did you try restarting gitlab and gitaly services?
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
On Thu, 29 Nov 2018 19:58:24 +0530 Pirate Praveen
wrote:
> It is not a regression in unstable, so it need not block the testing
> migration. I will dig deeper to find the root cause. At least the gitlab's
> main Gemfile.lock is supposed to be regenerated every time a ruby package is
Control: found -1 10.8.7+dfsg-1
It is not a regression in unstable, so it need not block the testing migration.
I will dig deeper to find the root cause. At least the gitlab's main
Gemfile.lock is supposed to be regenerated every time a ruby package is updated
via dpkg triggers.
--
Sent from
Control: fixed -1 11.3.10+dfsg-1
On 2018, നവംബർ 26 10:16:05 PM IST, Claudius Steinhauser
wrote:
>Package: gitlab
>Version: 10.8.7+dfsg-1
>Severity: grave
>Justification: renders package unusable
>
>Dear Maintainer,
>
> * What led up to the situation?
>
>Updating all packages resulted in this
On 2018, നവംബർ 26 8:48:54 PM IST, eamanu15 wrote:
>> eamanu15, gnukhata-core-engine is no longer maintained upstream, it
>is
>> replaced by gnukhata-core.
>>
>> ah! ok! so, definitely gnukhata-core-engine should be remove from
>debian
>database, isn't?
Yes, I will request removal when
On 11/26/18 8:37 PM, eamanu15 wrote:
> If this package is used for many people, I can maintain it.
eamanu15, gnukhata-core-engine is no longer maintained upstream, it is
replaced by gnukhata-core.
Manas, removing gnukhata-core-engine will not fix this bug, did you read
the link shared by Andreas
Control: reassign -1 gitaly
On Mon, 19 Nov 2018 08:42:32 +0530 Pirate Praveen
wrote:
> Control: reassign -1 golang-gitaly-proto
Unlike C libraries, we don't track api bumps in package names, so can't
break older versions.
signature.asc
Description: OpenPGP digital signature
Control: reassign -1 golang-gitaly-proto
On 2018, നവംബർ 19 2:20:39 AM IST, Paul Gevers wrote:
>Dear maintainers,
>
>With a recent upload of gitlab the autopkgtest of gitaly fails in
>testing when that autopkgtest is run with the binary packages of gitlab
>from unstable. It passes when run with
On 2018, നവംബർ 15 8:54:58 PM IST, Mathieu Malaterre wrote:
>The following information may help to resolve the situation:
>
>The following packages have unmet dependencies:
>node-boxen : Depends: node-camelcase (>= 4.0.0) but 3.0.0-1 is to be
>installed
>E: Unable to correct problems, you have
On 2018, നവംബർ 15 9:01:15 PM IST, Mathieu Malaterre wrote:
>The following information may help to resolve the situation:
>
>The following packages have unmet dependencies:
>node-tar : Depends: node-yallist (>= 3.0.2~) but 2.0.0-1 is to be
>installed
>E: Unable to correct problems, you have
Package: ruby-kubeclient
Version: 3.0.0-3
severity: serious
Control: forwarded -1 https://github.com/abonas/kubeclient/issues/359
Autopkgtest is also failing
https://ci.debian.net/data/packages/unstable/amd64/r/ruby-kubeclient/latest-autopkgtest/log.gz
signature.asc
Description: OpenPGP
On 2018, ഒക്ടോബർ 27 2:38:23 AM IST, Adrian Bunk wrote:
>No, it is not.
>
>I would expect everything that fails during build time to fail the same
>
>way at runtime.
>
Can you reproduce the bug? Once it is built against the correct version, it
will use that version only.
--
Sent from my
401 - 500 of 933 matches
Mail list logo
